More Related Content
Similar to Sample Product Management Lifecycle Presentation (20)
Sample Product Management Lifecycle Presentation
- 2. Contents Product Management at SIVA Product office Change request process Product life cycle Human Factors Engineering at SIVA
- 3. SIVA Marketing Department Product Management Human Factors Engineering Documentation/ Training Marketing Communications
- 4. Product Management at SIVA Schedule Development Customer Sales/Prof Services Product Product Management Business Exec/Finance Product Office PLC General Contractor Market Research Competitive Analysis Business Case PLC Process Change Request Process
- 5. Key Planning Tools Product Roadmap User Interface Plan Product Calendar Product Office
- 6. Product Office Includes company leadership Ensures strategic direction and goals are always considered Enforces priorities/sequencing Clearly communicates decisions Enhances communications across organization Continue Delay Kill
- 7. Product Office Members Dan Barron, Senior Vice President Technology Christine Fuchs, Director Product Management Julie Grosse, Vice President Marketing Jim Melvin, CEO
- 8. Product Office Responsibilities Meet weekly Steer projects and products Update project status Review new opportunities Authorize PLC phases Audit PLC compliance Provide clear decisions
- 9. Decision Criteria (Go, Delay, Kill) All current & targeted efforts considered Hard prioritization required Trade-offs must balance tactical and strategic Value is commensurate with cost & exposure Value clear for customers and SIVA Appropriate balance and scrutiny of risks Clearly defined ‘completeness’ of products addressed Stability, packaging, support, training, marketing Tracking is visible “ Big Picture” of where things are
- 10. Decision Gates Delay & recycle Continue Kill Prior PLC Phase Revisit after condition is met Cease work Proceed to next PLC phase Determine criteria/timing to recycle Communicate decision Internal External Next Step?
- 11. Example of Gated Approach Purpose Next Stage Decision Input 3 Requirement Decision on business case Invest in requirement definition Business case 2 Concept definition Short Summary SWAG Preliminary screen Need more detailed business case Business case 1 Initial screen Product idea Customer request Elaboration on concept Concept 6 Product complete- ness & quality Operational readiness Decision to launch Invest in market launch & operations Packaging 4 Decision to build Design & construction Invest in product development Requirements Customer inputs Competing projects, schedules 5 Decision for beta or pilot phase Beta test QA & Product Management assessment of readiness -Product -Support
- 12. Product Office Status Tracking New submissions Committed Weekly development schedule Future Hold Pending CRFs Action Items
- 13. Change Request Process Customer Request SIVA Impact SWAG CRF Requirements Development Scheduled Delivery Date Communicated Bugzilla Product Office Approval Customer Acceptance Revised SWAG, CRF & Customer Acceptance If Necessary
- 14. What is PLC? Provides methodology New product development Updates and enhancements Customer-requested development Program fixes Standardizes inputs and outputs Involves all functional areas PLC = product life cycle from inception to post- production
- 15. PLC Objectives Provide focus Unlimited opportunities Finite resources Improve quality Quality checks built in Reduce cycle time Iterative releases Parallel efforts Reduce cost Lower project management overhead Elimination of bloat & scope creep Improve customer satisfaction More rapid results Less costly solutions
- 16. Process Overview Construction C oncept Phase Pick ideas as product concepts to investigate – “Is this worth doing?” R equirements Phase Determine the details of the target product – “What is it exactly?” C onstruction Phases Build and test the product D eployment Phases Bring the product and its value to our customers D esign Phase Determine “How to solve the requirements” E nvision Phase Generate and collect ALL ideas from customers, employees & partners Concept Requirements Logical Design Physical Design Integrated System Testing Beta Packaging General Release Idea Bucket
- 17. Companywide Process Product Management Training Documentation QA Sales/ Marketing Development Product Integration & Infrastructure Packaging Customer Service Post-Production Construction Logical Design Requirements Concept & Business Case Physical Design Issues Analysis Issues Analysis Project Management, As-Built Review Project Plan Requirements & Product Plan Product Concept Review & Project Charter Project Management Final Training Training Creation Training Plan Training Draft 1 Review and Rework Final Doc Doc Draft 1 Review and Rework Doc Plan Doc Creation Doc Draft 2 Review and Rework Integrated Test Scripts, Test Plan Review Traceability Matrix Quality Metrics Test Plan Performance & Platform Testing Final Code (Hard Freeze) Construction, Code (Soft Freeze) High-Level Design Product Concept Review Critical Design, Unit Test Plans Rework Final Media / Live Production Version Control & Product Env. Setup Config Mgmt Prep & Setup Release Packaging & Beta Mgmt Deployment & Implementation, Issues Analysis Support Plan SLA Targets Support Training & Prep Sales & Marketing Communications Sales & Return Analysis Final Collateral, Sales Training Product Launch Plan Product Concept Review Collateral Development, Launch Plan Execution Product Launch Integrated System Testing/Beta
- 18. Phases Product Management Training Documentation QA Sales/ Marketing Development Product Integration & Infrastructure Packaging Customer Service Post-Production Construction Logical Design Requirements Concept & Business Case Physical Design Typical Flow Project Management, As-Built Review Product Architecture & Project Plan Requirements & Product Plan Product Concept Review & Project Charter Project Management Final Training Training Creation Training Plan Training Draft 1 Review and Rework Final Doc Doc Draft 1 Review and Rework Doc Plan Doc Creation Doc Draft 2 Review and Rework Integrated Test Scripts, Test Plan Review Traceability Matrix Quality Metrics Test Plan Performance & Platform Testing Final Code (Hard Freeze) Construction, Code (Soft Freeze) High-Level Design Product Concept Review Critical Design, Unit Test Plans Rework Final Media / Live Production Version Control & Product Env. Setup Config Mgmt Prep & Setup Release Packaging & Beta Mgmt Deployment & Implementation Support Plan SLA Targets Support Training & Prep Sales & Marketing Communications Sales & Return Analysis Final Collateral, Sales Training, Launch, Sales Product Launch Plan Product Concept Review Collateral Development, Launch Plan Execution Sales & Marketing Communications Integrated System Testing/Beta
- 19. A Flexible Framework Overlapping Formal Review Checkpoints PLC is adapted to a specific project Project flow is always based upon framework flow Phase activities are defined at project planning Smaller projects do not require the same level of formality PLC is a common foundation for projects, not a fixed, rigid set of rules Example of how short 3 week prototyping effort may apply the process Example of how larger multi-month project can be highly structured and formalized - Not needed in project 1 week 2 weeks 2 days 2 months 1 month 3 months
- 20. Envision Phase Objectives Generate and collect ALL ideas from customers, employees & partners Create idea list to facilitate evaluation of opportunities Gate criteria Ideas promoted based on decision of the Product Office Go/Kill Decision
- 21. Idea Submission System Submission Form Submissions Process Submission Review Submission Idea Bucket Acknowledgement Concept Decision Gate (typical)
- 22. Concept Phase Objectives Create a high-level understanding of the proposed project Demonstrate the value proposition Determine degree of risk/strategic alignment Gate criteria Does it fit SIVA’s business? Can we afford to pursue it? Is the benefit (or loss avoidance) compelling? Is the risk acceptable?
- 23. Requirements Phase Objectives Define the product Product functionality Deployment and support requirements Create high-level project & resources plan Gate criteria Have all inputs been considered? Is the product well-defined? Is it clear what the product will do? Are major features & costs traceable to the Concept? Do we really want to build/pursue this?
- 24. Design Phase Objectives Define application Data, business logic, user interface Component interfaces Update project plan Cost & timeline Gate criteria Is design traceable to Concept and Requirements? Are risks understood? Do we still want to build/pursue this?
- 25. Construction Phase Objectives Execute design & build product Analyze impact of all changes Ensure visibility of progress via status updates Development, Testing, Support, Operations, Marketing/Sales Gate criteria Significant changes warrant stoppage? Are both primary development tasks & ancillary activities on target? Does any functional area need immediate corrective action?
- 26. Quality Assurance Phase Objectives Shake out bugs & address issues Establish product completeness Product functionality Training & documentation Deployment & support models Gate criteria Is product ready? Is service/support for product ready? Is product endorsed by QA? Is product likely to succeed in Beta?
- 27. Beta Test Phase Objectives Gain user acceptance Validate usability Prove support model Establish value (ROI, soft $ benefits) Gate criteria Are product/support ready? Does customer endorsement exist? Does product represent SIVA in good light? Is it likely to be successful in the marketplace?
- 28. Post-Production Phase Objectives Measure results - actual vs. planned Monitor customer satisfaction level Make necessary adjustments Improve support & deployment Track sales Gate criteria Enhance, fix, and/or maintain? Allocate appropriate resources? Revisit this gate quarterly
- 29. Tools Tomcat JRun Application Server Microsoft SourceSafe Version Control MySQL MSSQL Database Windows Linux Operating System Bugzilla Tracking Jbuilder Compiler
- 30. Guides & Templates PLC Framework document Templates Concept Business Case Requirement Design Specification PLC Project Shell Guides Unit Testing Integration Test Planning Check Lists Requirements thru Design
- 32. PLC Audits Performed by Product Office Assure compliance with the PLC process Indicate health of active projects Gauge overall product status through PLC phases Measure projects at two levels of detail Vital Signs – 15 data points Health Check – in-depth
- 33. Human Factors Work-centered application design Usability studies Post-deployment issues analysis User Interface Plan
- 34. pretty + usability = acceptance + less training Icon & position conveys status and context faster than text. Use of color and layout helps users quickly identify areas of screen with different data types, function, and purpose. Controls use every day language not cryptic computer jargon such as filter, sort, or scroll. Designed to match the work and work flow, not function and data retrieval. Color, layout, and text used to quickly convey context (what am I looking at and how do I change the view?) . “FOR PICKUP” is not going to change the list of drivers at the bottom left. Contrast is used to help the user focus on the primary purpose of the screen. Layout reduces the number of “hard lines” ... which, in turn, reduces time to comprehension. Text is carefully aligned to improve reading comprehension (see time column)
- 35. is what’s next 3333 South Congress Avenue Suite 400 Delray Beach, Florida 33445 Phone: (561) 272-2121 Fax: (561) 272-7177 www.sivacorp.com