Summary Page Management

Background

• The first MVP for the KB. Establish a "Project Summary Front Page"
  • The starting point for each project that uses BOWs and TIPS to maintain most active subjects on each project
  • Provides a place that allows users to drill down to IS Q & A documents, Action Page documents etc.
    • The test case for this is the IS Q & A development process for Glass Packaging Institute Project (GPI).
• Not in scope is use case and workflow for non-staff professional stakeholders.  Though the use case would be pretty similar.

Challenges

• We have to maintain a highest level starting place for each project that brings users up-to-date on next steps for a project's goals as well as allowing users to drill down and make comments and input on each project
• Do we need a better name than "Project Summary Front Page" for this feature

Design

For purposes of definition:  USE CASE: A business process or activity for doing work. WORK FLOW: How categories of work flow through your business.

1. All Projects start with their own Front Page that originates on the KB site Main Page: OnTrackNorthAmerica's CAPSI Project under the heading "Projects"
2. For example, right now the GPI project is a Client Project. Click on  Glass Packaging Institute under Client Projects
3. You now see the Front Page for the GPI Project. This would be the ongoing "Glass Packaging Institute Summary Front Page" for the life of the project. Of course this project might morph into another project which would be prominently recorded here, noting that this change had taken place.
   • This page, like all others, uses Big Organizing Words (BOWs) headers like: GPI MOVES, Context, Opportunity, Problems, Process, Background Documents. Under each BOW are relevant Topics and Information Points (TIPs) which are plan text. Within TIPs is where we include links to other pages and links to outside web pages
     • Some sort of functionality is included here for using discussion pages attached to each page
     • As the project moves along, the BOWs and TIPs can change
4. Background Documents are complete whole documents uploaded to the site. This would include emails relevant to major project issues, memos that birthed the project, other relevant outsider memos, as well as completed whole IS Q&A documents and completed formatted Action documents generated from the IS Q & A work. (Note: A separate use case and work flow needs to be created for the possibility of how we get stakeholder input on evolving IS Q&As within the KB, probably using the discussion tab pages with some scripts or something else.)