Sample Product Management Lifecycle Presentation

6,715 views

Published on

Julie Grosse Technology Marketing portfolio

Published in: Technology, Business

Sample Product Management Lifecycle Presentation

  1. 1. Product Management Methodology
  2. 2. Contents • Product Management at SIVA • Product office • Change request process • Product life cycle • Human Factors Engineering at SIVA
  3. 3. SIVA Marketing Department • Product Management • Human Factors Engineering • Documentation/ Training • Marketing Communications
  4. 4. Product Management at SIVA Market Research PLC General Product Competitive Analysis Contractor Product Business Case Management PLC Process Change Request Process Schedule Product Customer Sales/Prof Development Office Services Business Exec/Finance
  5. 5. Key Planning Tools • Product Roadmap • User Interface Plan • Product Calendar • Product Office
  6. 6. Product Office • Includes company leadership • Ensures strategic direction and goals are always considered • Enforces priorities/sequencing • Clearly communicates decisions Kill • Enhances communications across organization Continue Delay
  7. 7. Product Office Members • Dan Barron, Senior Vice President Technology • Christine Fuchs, Director Product Management • Julie Grosse, Vice President Marketing • Jim Melvin, CEO
  8. 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. 9. Decision Criteria (Go, Delay, Kill) • All current & • Appropriate balance targeted efforts and scrutiny of risks considered • Clearly defined • Hard prioritization ‘completeness’ of required products addressed • Trade-offs must • Stability, packaging, balance tactical support, training, and strategic marketing • Value is • Tracking is visible commensurate with • “Big Picture” of cost & exposure where things are • Value clear for customers and SIVA
  10. 10. Decision Gates Revisit Determine after Delay & recycle criteria/timing condition to recycle is met Prior Next Kill Cease PLC Step? work Phase Proceed to Communicate Continue next PLC decision Internal phase External
  11. 11. Example of Gated Approach 1 2 3 4 5 6 Purpose Initial Preliminary Decision on Decision to Decision for Decision to screen screen business build beta or launch case pilot phase Input Product idea Concept Business Requirements QA & Product Product definition case Management complete- Customer assessment ness & Customer Short inputs of readiness quality request Summary -Product Competing -Support Operational SWAG projects, readiness schedules Decision Elaboration Need more Invest in Invest in Invest in on concept detailed requirement product market business definition development launch & case operations Next Stage Concept Business Requirement Design & Beta test Packaging case construction
  12. 12. Product Office Status Tracking • New submissions • Committed • Weekly development schedule • Future • Hold • Pending CRFs • Action Items
  13. 13. Change Request Process Customer Request Bugzilla SIVA Impact SWAG Product Office Approval CRF Customer Acceptance Requirements Revised SWAG, CRF & Development Customer Acceptance If Necessary Scheduled Delivery Date Communicated
  14. 14. What is PLC? • Provides methodology • New product development • Updates and enhancements • Customer-requested development • Program fixes • Standardizes inputs and outputs PLC = product • Involves all functional life cycle from areas inception to post- production
  15. 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. 16. Process Overview Integrated Idea Bucket Concept Requirements Logical Design Physical Design Construction System Testing Packaging General Release Beta Envision Phase Generate and collect ALL ideas from customers, employees & partners Concept Phase Pick ideas as product concepts to investigate – “Is this worth doing?” Requirements Phase Determine the details of the target product – “What is it exactly?” Design Phase Determine “How to solve the requirements” Construction Phases Build and test the product Deployment Phases Bring the product and its value to our customers
  17. 17. Companywide Process Concept & Integrated Business Case Requirements Logical Design Physical Design Construction System Testing/Beta Packaging Post-Production Product Project Product Concept Requirements & Project Management, Management Review & Product Plan Project Plan Management As-Built Project Charter Review Critical Product Construction, High-Level Design, Final Code Development Concept Design Unit Test Code Rework (Hard Freeze) Review (Soft Freeze) Plans Doc Draft 1 Doc Draft 2 Final Documentation Doc Plan Doc Creation Review and Review and Doc Issues Analysis Rework Rework Training Draft 1 Training Training Final Training Plan Creation Review and Training Issues Analysis Rework Integrated Performance Quality Traceability Test Scripts, QA Metrics Matrix Test Plan Test Plan & Platform Testing Review Product Version Config Release Control & Final Media / Integration & Mgmt Product Env. Packaging & Live Production Prep & Setup Beta Mgmt Infrastructure Setup Support Customer SLA Support Training & Deployment & Service Targets Plan Implementation, Prep Issues Analysis Collateral Sales/ Product Sales & Sales & Product Launch Development, Final Collateral, Concept Marketing Return Plan Launch Plan Sales Training Product Launch Marketing Review Execution Communications Analysis
  18. 18. Phases Concept & Integrated Business Case Requirements Logical Design Physical Design Construction System Testing/Beta Packaging Post-Production Product Project Product Product Concept Requirements & Architecture & Project Management, Management Review & Product Plan Management As-Built Project Plan Project Charter Review Critical Product Construction, High-Level Design, Final Code Development Concept Design Unit Test Code Rework (Hard Freeze) Review (Soft Freeze) Plans Doc Draft 1 Doc Draft 2 Final Documentation Doc Plan Doc Creation Review and Review and Ty Doc Rework Rework p ica Training Draft 1 lF Training Training Final Training Plan Creation Review and Training Rework Quality Traceability lo w Integrated Test Scripts, Performance QA Metrics Matrix Test Plan Test Plan & Platform Testing Review Product Version Config Release Control & Final Media / Integration & Mgmt Product Env. Packaging & Live Production Prep & Setup Beta Mgmt Infrastructure Setup Support Customer SLA Support Training & Deployment & Service Targets Plan Implementation Prep Collateral Final Collateral, Sales/ Product Sales & Sales & Sales & Product Launch Development, Concept Sales Training, Marketing Marketing Return Plan Launch Plan Marketing Review Execution Launch, Sales Communications Communications Analysis
  19. 19. A Flexible Framework Integrated Envision Concept Requirements Logical Design Physical Design Construction System Testing/ Beta Packaging Post Production • PLC is adapted to a Project  - Not needed in project Product Product Product Project Management, Concept Requirements & Management Architecture & Management As-Built Review & Product Plan Overlapping Project Plan Review Project Charter Critical Product specific project Design, Construction, Final Code Development Concept High-Level Code Rework Review Design Unit Test (Hard Freeze) Plans (Soft Freeze) Documentation    Doc Plan Doc Creation Doc Draft 1 Review and Rework Doc Draft 2 Review and Rework Final Doc • Project flow is always Example of how short 3 week Training    Training Plan Training Creation Training Draft 1 Review and Rework Final Training based upon prototyping effort   Integrated Performance Test Scripts, QA Quality Traceability Test Plan & Platform Metrics Matrix Test Plan Testing may apply the Review  Config Version process Product Release Final Media / framework flow Mgmt Control & Integration & Prep & Setup Product Env. Packaging & Live Production Infrastructure Setup Beta Mgmt Customer Service   SLA Targets Support Plan Support Training & Prep Deployment & Implementation • Phase activities are       Collateral Product Final Collateral, Sales & Sales/ Product Launch Development, Concept Sales Training, Marketing Sales Marketing Plan Launch Plan Review Launch, Sales Communications Execution 1 week 2 weeks 2 days defined at project planning Formal Review Checkpoints • Smaller projects do Envision Product Concept Product Concept Requirements Requirements & Logical Design Product Physical Design Project Construction Project Management, Integrated System Testing/ Beta Packaging Post Production not require the same Management Architecture & Management As-Built Review & Product Plan Project Plan Review Project Charter Product Critical Design, Construction, Final Code Development Concept High-Level Code Rework Review Design Unit Test (Hard Freeze) level of formality Plans (Soft Freeze) Doc Draft 1 Doc Draft 2 Final Documentation Doc Plan Doc Creation Review and Review and Doc Rework Rework Example of how Training PLC is a common Training Training Draft 1 Final • Training larger multi-month Plan Creation Review and Training Rework project can be QA Quality Traceability Test Plan Integrated Test Scripts, Test Plan Performance & Platform foundation for Metrics Matrix Testing highly structured Review and formalized Config Version Product Mgmt Control & Release Final Media / Integration & Prep & Setup Product Env. Packaging & Live Production Infrastructure Setup Beta Mgmt projects, not a fixed, Customer Service SLA Targets Support Plan Support Training & Prep Deployment & Implementation rigid set of rules Collateral Product Final Collateral, Sales & Sales/ Product Launch Development, Concept Sales Training, Marketing Sales Marketing Review Plan Launch Plan Launch, Sales Communications Execution 2 months 1 3 month months
  20. 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. 21. Idea Submission System Process Idea Submission Submission Bucket Form Acknowledgement Review Submissions Submission Concept Decision Gate (typical)
  22. 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. 23. Requirements Phase • Objectives • Gate criteria • Define the product • Have all inputs been • Product considered? functionality • Is the product well- • Deployment and defined? support requirements • Is it clear what the product will do? • Create high-level project & resources • Are major features & plan costs traceable to the Concept? • Do we really want to build/pursue this?
  24. 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. 25. Construction Phase • Objectives • Gate criteria • Execute design & • Significant changes build product warrant stoppage? • Analyze impact of all • Are both primary changes development tasks & • Ensure visibility of ancillary activities on progress via status target? updates • Does any functional • Development, area need immediate Testing, Support, corrective action? Operations, Marketing/Sales
  26. 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. 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. 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. 29. Tools Compiler Jbuilder Tracking Bugzilla Windows Operating System Linux MySQL Database MSSQL Version Control Microsoft SourceSafe Tomcat Application Server JRun
  30. 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
  31. 31. Life Cycle Overview
  32. 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. 33. Human Factors • Work-centered application design • Usability studies • Post-deployment issues analysis • User Interface Plan
  34. 34. pretty + usability = acceptance + less training 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. Icon & position conveys status and context faster than text. 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) 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. Use of color and layout helps users quickly identify areas of screen with different data types, function, and purpose.
  35. 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

×