1.
What do markets and customers need? What can / should we build? What’s working and not working? Product Management Processes JohnGibbon.com

2.
Agile Product Management <ul><ul><li>Define: Biz Case - Market Intelligence, Feedback </li></ul></ul><ul><ul><li>Design: Product Requirements </li></ul></ul><ul><ul><li>Development: Support Develop; Refine Requirements </li></ul></ul><ul><ul><li>Deploy: Launch, Marketing, Support Sales, Feedback / Monitoring </li></ul></ul>Feedback Market

3.
Product Management and Product Development Processes and Documents

4.
Biz Case: Value Proposition

5.
Where and Why: Longer Business Case or MRD

6.
Use Case Diagram: Functional Requirements Describing System from User Perspective member Photo Sharing Site upload organize view friend administrator What: Use Case Focused Product Requirements

7.
Upload Photo Share? Shares Photo w/ Group UML Activity Use Case Diagram UML (Unified Modeling Language) provides a variety of different diagram types to describe a software system: use case diagram, activity diagram, collaboration diagrams, etc. Member Photo Site

8.
Use Case Functional Requirements Documentation <ul><ul><li>Use Case Name </li></ul></ul><ul><ul><li>Goal / Summary </li></ul></ul><ul><ul><li>Actors </li></ul></ul><ul><ul><li>Preconditions </li></ul></ul><ul><ul><li>Triggers </li></ul></ul><ul><ul><li>Basic Course of Events </li></ul></ul><ul><ul><li>Alternative Paths </li></ul></ul><ul><ul><li>Postconditions </li></ul></ul><ul><ul><li>Business rules </li></ul></ul>

9.
What: Use Case Focused Product Requirements <ul><li>PRD (Product Requirements Document): </li></ul><ul><li>Uses Cases and More ! </li></ul><ul><ul><ul><li>Description of Actors or Users </li></ul></ul></ul><ul><ul><ul><li>Series of Use Cases: General to Specific </li></ul></ul></ul><ul><ul><ul><li>Non-Functional Product Requirements: Scalability, Security, Reliability, Availability, Installation, etc . </li></ul></ul></ul>Or Interactive Prototypes!

10.
Requirements: High Fidelity Prototypes <ul><ul><li>Discussed by Marty Cagan </li></ul></ul><ul><ul><li>Realistic Enough to Test Idea with Target Customer </li></ul></ul><ul><ul><li>Refine Business Idea Before Commit </li></ul></ul><ul><ul><li>Helps Product Be Better Understood Throughout Org </li></ul></ul><ul><ul><li>Underlines Functionality and User Experience Intertwined </li></ul></ul>1/29/09

11.
Prototypes Tools <ul><ul><li>Lower Fidelity </li></ul></ul><ul><ul><ul><li>-PowerPoint / Visio (Storyboarding) </li></ul></ul></ul><ul><ul><li>HTML Development Tools: </li></ul></ul><ul><ul><ul><li>- Weebly, Google Sites, SquareSpace (free, drag and drop) </li></ul></ul></ul><ul><ul><ul><li>- Dreamweaver, FrontPage (not free, web authoring tools) </li></ul></ul></ul><ul><ul><li>Code Development Tool </li></ul></ul><ul><ul><ul><li>-VisualBasic, etc. </li></ul></ul></ul><ul><ul><li>High Fidelity Prototyping Tools: </li></ul></ul><ul><ul><ul><li>- Axure and Irise </li></ul></ul></ul><ul><ul><ul><li>- Also Serena Composer, Lucid Spec, Intuitect, Profesy </li></ul></ul></ul>1/29/09

12.
Which features? Which processes? For Features listen to: clients, customer usage analytics, internal stakeholders, competitors, industry experts For Processes it depends on: type of market, type of product, target reader of documents, company stage, size, and structure