Use Case guidelines and format proposal

Guidelines 

For initial use case proposals only: 

• End user workflows only 
  • Should be from the end user’s point of view, highlighting a clear customer need E.g. use case
  • No implementation details at this stage
• Desktop specific (for now)Structure of Use Cases:
  • Is it a single workflow or can it be multiple?
  • Should there be a limit to the number of scenarios? 
• Factual & detailed

Format:

• User Persona
• Overview of what is on user’s desktop: What applications they are using, what is open, what is not etc. 
• Detailed workflow (from user's perspective)
• Status: Includes Status macro
• Tagging / Categorization: Propose to categorize use cases into different types to help prioritize

Bookkeeping:

• A confluence Template may be used to create a "Use Case" document object.
  • must be created by Space Administrator
  • includes label (e.g. "use-case")
  • includes Page Properties macro, containing metadata specified in Format section above (e.g. creation date, status macro, short description, last edit)
• Top level report showing table of all use cases with meta-data, using the Page Properties Report macro.
• Top level report table contains button to create "New Use Case".  You can see an example here:  Meeting notes