Product Management And Service Delivery Process - FlackVentures Example

19,763 views

Published on

A lifecycle methodology enforces some very important processes that deliver critical value to Service Delivery. Some key contributions are:
Business driven goals (e.g. profit, performance, credible schedules, resource effectiveness….)
Roles and responsibility clarification (e.g. delegation, decision making, optimization….)
Organizational effectiveness (e.g. resource structure for task, enable cross functional efforts….)
Planning enforcement at the beginning before major resources committed
Continuous learning enabled that builds core competency in credible delivery plans.

Published in: Business, Technology
4 Comments
22 Likes
Statistics
Notes
No Downloads
Views
Total views
19,763
On SlideShare
0
From Embeds
0
Number of Embeds
77
Actions
Shares
0
Downloads
1,090
Comments
4
Likes
22
Embeds 0
No embeds

No notes for slide

Product Management And Service Delivery Process - FlackVentures Example

  1. 1. Product Management and Service Delivery Process A FlackVentures Process Example January 2002 Prometric Technology and Service Delivery
  2. 2. PMSD Process Key Ideas <ul><li>Multiple Revision Phases to create the PMSD Process </li></ul><ul><ul><li>Phase One is the foundation </li></ul></ul><ul><ul><li>Phase Two is providing efficiencies </li></ul></ul><ul><li>“ Bookend” Phases – Strategic Planning and Lessons Learned </li></ul><ul><ul><li>If these are not done and done well, the process fails </li></ul></ul><ul><li>Communication </li></ul><ul><ul><li>Over-communication to start </li></ul></ul><ul><ul><ul><li>better to over communicate than to not communicate enough </li></ul></ul></ul><ul><li>Collaboration is absolutely KEY </li></ul><ul><ul><li>Sales with Marketing and visa versa </li></ul></ul><ul><ul><li>Product Management with Business Representatives and visa versa </li></ul></ul><ul><ul><li>Development with Sales and visa versa </li></ul></ul><ul><ul><li>Etc…. </li></ul></ul><ul><li>FACTS and nothing but the FACTS </li></ul><ul><ul><li>Decisions must utilize factual information, be documented, and communicated thoroughly </li></ul></ul><ul><ul><li>conscious decisions only </li></ul></ul>
  3. 3. Corporate Process Development Marketing Sales Product Management Customer Care Technical Operations HR Finance MIS Facilities Legal Corporate Services Technical Development Information Support Information Support Business Operations Development Development Business Development Channel Management
  4. 4. Re-Development Focus – Phase 1 <ul><li>Stakeholders in the Prometric Technology and Service Delivery process to be interviewed </li></ul><ul><ul><li>Marketing/Strategy, Sales, Channel Management, Product Management, Client Services, Development </li></ul></ul><ul><ul><li>Issue areas to be discussed </li></ul></ul><ul><ul><ul><li>Focus and Priority </li></ul></ul></ul><ul><ul><ul><li>Requirements Management </li></ul></ul></ul><ul><ul><ul><li>Quality </li></ul></ul></ul><ul><ul><ul><li>Communication </li></ul></ul></ul><ul><ul><ul><li>Process and Documentation (Participation, Change management, Feasibility, Flexibility, Metrics, Technology/Service Reviews, Training etc.) </li></ul></ul></ul>
  5. 5. Creating a Methodology Not Just a Process <ul><li>A lifecycle methodology enforces some very important processes that deliver critical value to Service Delivery. Some key contributions are: </li></ul><ul><ul><li>Business driven goals (e.g. profit, performance, credible schedules, resource effectiveness….) </li></ul></ul><ul><ul><li>Roles and responsibility clarification (e.g. delegation, decision making, optimization….) </li></ul></ul><ul><ul><li>Organizational effectiveness (e.g. resource structure for task, enable cross functional efforts….) </li></ul></ul><ul><ul><li>Planning enforcement at the beginning before major resources committed </li></ul></ul><ul><ul><li>Continuous learning enabled that builds core competency in credible delivery plans. </li></ul></ul>
  6. 6. Combining History With Best Practices <ul><li>Solid up-front PLANNING, both market and technical, before development begins </li></ul><ul><li>A strong MARKET ORIENTATION and attention to the voice of the customer throughout – early engagement of Sales, Marketing, and Customer Service </li></ul><ul><li>Sharp, early technology/service DEFINITION, before development begins </li></ul><ul><li>CLEAR GO/NO GO decision points throughout the process, where technology/service projects really are killed or phases are revised for further details, clarification, or consensus </li></ul><ul><li>A focus on QUALITY of execution – key activities carried out in a quality fashion </li></ul><ul><li>A complete and thorough PROCESS, but also a flexible process, as dictated by the nature and risk of the project </li></ul>
  7. 7. PMSD Methodology <ul><li>Standard, repeatable processes and documents will improve our ability to deliver quality, marketable technology and services in a timely manner: </li></ul><ul><ul><li>Step-by-step approach w/ checklists </li></ul></ul><ul><ul><ul><li>Process guide for each step </li></ul></ul></ul><ul><ul><ul><li>Templates as needed for each step </li></ul></ul></ul><ul><ul><ul><li>Checklists to ensure completeness and quality </li></ul></ul></ul><ul><ul><li>Pre-defined structure </li></ul></ul><ul><ul><ul><li>Standard formats </li></ul></ul></ul><ul><ul><ul><li>Process and document change control </li></ul></ul></ul><ul><ul><ul><li>Naming, numbering conventions </li></ul></ul></ul><ul><ul><ul><li>Storage, retrieval conventions </li></ul></ul></ul><ul><ul><li>All the templates work together </li></ul></ul><ul><ul><ul><li>Refer to each other as necessary </li></ul></ul></ul><ul><ul><ul><li>Hyper linked for web access </li></ul></ul></ul><ul><ul><li>Uses modern, known tools and models </li></ul></ul><ul><ul><ul><li>MS Office Suite, MS Project </li></ul></ul></ul>
  8. 8. Sample Enhancements to the Process <ul><li>Technology/Service Launch Readiness </li></ul><ul><li>Issue: lack of timely and complete product information prior to and after launch </li></ul><ul><ul><li>Communications Plan is developed and utilized from the beginning of the Service Delivery process to keep stakeholders informed. </li></ul></ul><ul><ul><li>Standard, predictable, and consistent approach to each technology/service release effort with the use of step-by-step processes, templates, and checklists </li></ul></ul><ul><ul><li>Decision Point Meetings will require documents to be complete and approved before sign-off. </li></ul></ul><ul><ul><li>Marketing is engaged in the Discovery and Scope phase and marketing strategy is requested in the business case phase. </li></ul></ul><ul><ul><li>Sales training is standardized to include the same information release to release. Training is scheduled 14-30 days in advance of launch. </li></ul></ul><ul><ul><li>A training plan is created in the development phase to make sure that all relevant parties are trained at the appropriate time </li></ul></ul>
  9. 9. Sample Enhancements to the Process (cont’d) <ul><li>Productivity </li></ul><ul><li>Issue: Unnecessary time spent on products that will fail to sell or produce revenue </li></ul><ul><li>Issue: Creating documentation/doing steps that are unnecessary </li></ul><ul><ul><li>Up-front work in the Discovery and Scope Phases will reduce the risk of failure </li></ul></ul><ul><ul><li>Reviewing past projects, reporting on Lessons Learned, completing the analysis, and making sound corrections to our future product efforts will reduce risk. </li></ul></ul><ul><ul><li>Risk Management will inform decision makers of possible failure points and enable them to make Risk Mitigation Plans and decisions. </li></ul></ul><ul><ul><li>Clear decision points, early project cost analysis and periodic risk assessments facilitate making decisions to stop further work on a risky project. </li></ul></ul><ul><ul><li>Templates are easy guides for creation of documents. </li></ul></ul><ul><ul><li>Process is flexible so that unnecessary documentation or steps that are not applicable need not be created/followed (project plan template helps to identify what is needed and what is not while maintaining the credibility of the process). </li></ul></ul><ul><ul><li>Communication will be improved by the standardized templates making absorbing and assessing information easier and by a adhering to a communication plan that will keep internal and external entities informed </li></ul></ul><ul><ul><li>Tools will improve the process </li></ul></ul><ul><ul><ul><li>Templates will speed document creation and information sharing </li></ul></ul></ul><ul><ul><ul><li>Project management training will be given to improve employee skills </li></ul></ul></ul>
  10. 10. Ongoing Development of Skills <ul><li>Project Management </li></ul><ul><ul><li>Learning how to manage a technology and service release project is the most important key to a successful launch. From scope to time to resources to quality, any member of the PMSD Team must be aware and manage these aspects expertly. </li></ul></ul><ul><li>Teamwork: </li></ul><ul><ul><li>Being a good team member means putting the good of the team ahead of any personal ambitions and agendas. It means respecting other opinions, hearing people out and involving everyone in finding a solution. </li></ul></ul><ul><li>Communication skills: </li></ul><ul><ul><li>From answering the phone, writing e-mail or putting together a proposal, how well a team member carries a point across will affect others’ perceptions of their abilities. </li></ul></ul><ul><li>Running meetings: </li></ul><ul><ul><li>Learning how to facilitate meetings and manage group interactions is an important first step to becoming a team leader. </li></ul></ul><ul><li>Leadership: </li></ul><ul><ul><li>A strong leader understands team dynamics and harnesses the diverse energies within an organization and pulls everyone together. </li></ul></ul><ul><li>Problem-solving: </li></ul><ul><ul><li>To some, problem solving comes instinctively. To others, it’s not so natural. The key is to find a process that works and apply it. </li></ul></ul><ul><li>Customer service: </li></ul><ul><ul><li>From dealing with difficult people to making customers feel valued and important, customer service means that the customer should always feel like they’re No. 1. Just remember: If we don’t treat them right, someone else will. </li></ul></ul><ul><li>Presentation skills: </li></ul><ul><ul><li>These skills are a must for any situation, from running a meeting, pitching a technology or solution or justifying getting funding for a new project. </li></ul></ul>
  11. 11. Technology and Service Delivery Lifecycle Flowchart Process assumes “GO” decision from beginning to end Discovery Release and Review Scope Business Case Design/ Develop Quality Assurance Pre- Release DP2 DP1 DP3 DP4 DP5 DP6 End of Life Early Adopter Program Proof of Concept Typically 1-6 months – Depending on Complexity and Risk New Upgrade? New Version? New Product? Monthly Planning and Decision Meeting Monthly Review and Planning Meeting 1 2 3
  12. 12. Product Lifecycle – Discovery and Scope QUALITY ASSURANCE BUSINESS CASE DESIGN AND DEVELOPMENT PRE-RELEASE RELEASE AND REVIEW SERVICE DELIVERY DISCOVERY AND SCOPE PLANNING REVIEW Deliverables: Milestones: Stakeholders: Key Responsibilities <ul><li>Product Vision Complete </li></ul><ul><li>Preliminary Market Assessment complete </li></ul><ul><li>Preliminary Cost/Benefit Analysis complete </li></ul><ul><li>Preliminary Technical Assessment Complete </li></ul><ul><li>Project Scope Complete </li></ul><ul><li>Decision Point 1 Complete </li></ul><ul><li>Risk Assessment Complete </li></ul><ul><li>Decision Point 2 </li></ul><ul><li>Sales </li></ul><ul><li>Customer Service </li></ul><ul><li>Strategy/Marketing </li></ul><ul><li>New Business Development </li></ul><ul><li>Executive Management </li></ul><ul><li>Have vision and see big picture. </li></ul><ul><li>Listen, analyze, align, commit </li></ul><ul><li>Conceive of new ideas that will satisfy a customer need and be profitable for Prometric. </li></ul><ul><li>Articulate vision and benefits to management </li></ul><ul><li>Advocate quality ideas and quickly drop problem products </li></ul><ul><li>Complete Business and Technical Evaluation of technology and service concept to proceed to next phase </li></ul><ul><li>Customer and Market Needs Identification </li></ul><ul><li>Solution Concept Identification </li></ul><ul><li>Financial Impact Analysis </li></ul><ul><li>Risk Assessment </li></ul><ul><li>Optional Proof of Concept Plan (NA) </li></ul>Resources: <ul><li>Customer </li></ul><ul><li>Market </li></ul><ul><li>Channel Services </li></ul><ul><li>Product Management </li></ul><ul><li>Development </li></ul>
  13. 13. Discovery Phase Philosophy <ul><li>Breakthrough Idea Generation and Capture </li></ul><ul><ul><li>From all areas of the corporation </li></ul></ul><ul><ul><li>From our Customers and Potential Market </li></ul></ul><ul><ul><li>Reviewed throughout the year </li></ul></ul><ul><ul><li>Priority Driven </li></ul></ul><ul><li>Strategic Focus </li></ul><ul><ul><li>How does the Idea fit into the: </li></ul></ul><ul><ul><ul><li>Corporate Strategy </li></ul></ul></ul><ul><ul><ul><li>Market Strategy </li></ul></ul></ul><ul><ul><ul><li>Financial Goals </li></ul></ul></ul><ul><ul><ul><li>Product Line Strategy </li></ul></ul></ul><ul><li>Solution Based Categorization </li></ul><ul><ul><li>How does it fit into the existing solutions and portfolio Suites? </li></ul></ul><ul><ul><li>Is it the start of a new Solution Set? </li></ul></ul><ul><li>Voice-of-the-Customer/Market </li></ul><ul><ul><li>Working closely with core customers </li></ul></ul><ul><ul><li>Innovative thinkers and market leaders </li></ul></ul><ul><li>Decision Point Meetings are executive level and occur regularly on a Quarterly Basis or on-demand (emergency/highest priority) </li></ul>
  14. 14. Scope Phase Philosophy <ul><li>Preliminary Market Assessment </li></ul><ul><ul><li>Assess Market Attractiveness and Potential </li></ul></ul><ul><ul><li>Gauge Product Acceptance </li></ul></ul><ul><ul><li>Determine competitive situation </li></ul></ul><ul><ul><li>Shape the “idea” into a tentative product </li></ul></ul><ul><li>Preliminary Vendor Analysis </li></ul><ul><ul><li>Who are the market drivers in this product line? What are our competitors using? </li></ul></ul><ul><li>Preliminary Technical Assessment </li></ul><ul><ul><li>Establish rough technical and performance objectives </li></ul></ul><ul><ul><li>Undertake a very preliminary feasibility study </li></ul></ul><ul><ul><li>Pinpoint possible technical risks </li></ul></ul><ul><li>Preliminary Business and Financial Assessment </li></ul><ul><ul><li>A sanity check: estimates of expected sales, costs, and required investments </li></ul></ul><ul><ul><li>Rudimentary and quick check of the business rationale and financial prospects </li></ul></ul><ul><ul><li>Strategic and competitive rationale for the product are mapped out </li></ul></ul><ul><li>Priority Driven </li></ul><ul><ul><li>Timeline, resources, people and person-days, deliverables, and milestone dates are approved </li></ul></ul><ul><li>Decision Point Meetings are executive level and occur regularly on a monthly Basis or on-demand (emergency/highest priority) </li></ul>
  15. 15. Outcomes – Discovery and Scope <ul><li>Outcomes during Discovery and Scope: </li></ul><ul><ul><li>Product Sponsor identified </li></ul></ul><ul><ul><li>Business Strategy/Product Context understood including a high level assessment of the Marketplace, customer requirements, and competitive situation </li></ul></ul><ul><ul><li>Link to “Wow Factor” present </li></ul></ul><ul><ul><li>Expectations expressed in terms of Time, Resources, Scope, Quality and preliminary approval of initial commitment of resources/money granted </li></ul></ul><ul><ul><li>Rough business case stated </li></ul></ul><ul><ul><li>Product Mission drafted </li></ul></ul><ul><ul><li>Rough Product and Project and Boundaries understood including high level technical feasibility and product/project risks </li></ul></ul><ul><ul><li>Nature of project determined: Accelerated or Normal </li></ul></ul><ul><ul><li>Approval from Executive to proceed </li></ul></ul>
  16. 16. Product Lifecycle – Business Case QUALITY ASSURANCE BUSINESS CASE DESIGN AND DEVELOPMENT PRE-RELEASE RELEASE AND REVIEW INTEGRATED SERVICES DELIVERY DISCOVERY AND SCOPE PLANNING REVIEW Deliverables: Milestones: Stakeholders: Key Responsibilities <ul><li>Product Definition Complete </li></ul><ul><li>Product Justification Complete </li></ul><ul><li>Product Plan Complete </li></ul><ul><li>Product Communications Strategy Complete </li></ul><ul><li>Requirements Definition Document Complete </li></ul><ul><li>International Compliance Plan Complete </li></ul><ul><li>Decision Point 3 </li></ul><ul><li>Product Kick-Off Meeting Complete </li></ul><ul><li>Product Management </li></ul><ul><li>Finance </li></ul><ul><li>Executive Management </li></ul><ul><li>Product Business Case </li></ul><ul><li>Pricing and Packaging Plan </li></ul><ul><li>Detailed Project Plan and Schedule </li></ul><ul><li>Communications Plan </li></ul><ul><li>Requirements Definition Document including provisioning and billing considerations </li></ul><ul><li>International Compliance Plan </li></ul>Resources: <ul><li>Marketing </li></ul><ul><li>Product Development </li></ul><ul><li>Sales </li></ul><ul><li>Legal </li></ul><ul><li>SD&O Management </li></ul><ul><li>Research, analyze, document, commit </li></ul><ul><li>Quality Product Justification </li></ul><ul><li>Financial Justification </li></ul><ul><li>Design/Development pre-work </li></ul><ul><li>Complete Stakeholder Buy-In </li></ul><ul><li>Signoff from Executive Steering Committee </li></ul>
  17. 17. Business Case Phase Philosophy <ul><li>Product Definition is completed </li></ul><ul><ul><li>The “for whom” and “what” questions are answered </li></ul></ul><ul><ul><li>Detailed Product Scope and Concept </li></ul></ul><ul><ul><li>Customer Benefits and Market Positioning Strategy </li></ul></ul><ul><ul><li>Product Features, attributes, customer/business/technical requirements, and high-level specs </li></ul></ul><ul><li>Product Justification is completed </li></ul><ul><ul><li>The “why” questions are answered </li></ul></ul><ul><ul><li>Corporate Investment justification </li></ul></ul><ul><ul><li>Review of the business, financial, profitability, and risk considerations </li></ul></ul><ul><ul><li>Strategic rationale, competitive advantage, leverage, and market attractiveness </li></ul></ul><ul><ul><li>Partnering and outsourcing considerations </li></ul></ul><ul><li>Project Plan – the path to success – is completed </li></ul><ul><ul><li>The “how” and “by whom” questions are answered </li></ul></ul><ul><ul><li>Plan of action from development to release to review plan </li></ul></ul><ul><ul><li>Money, people and equipment are defined </li></ul></ul><ul><ul><li>Launch date is specified </li></ul></ul><ul><ul><li>Plans for preliminary Market Launch and for Operations and Support </li></ul></ul><ul><ul><li>All dates are tentative </li></ul></ul><ul><ul><li>Solid dates, activities, events, and milestones are provided during the Design and Development Stage </li></ul></ul><ul><li>Decision Point Meetings are at Product Sponsor and PMSD Product Team level and occur regularly on an “as-needed” basis </li></ul>
  18. 18. Outcomes – Business Case <ul><li>Outcomes during Business Case: </li></ul><ul><ul><li>Product/Project Business Plan that describes a new project for inclusion in the corporation portfolio of projects. </li></ul></ul><ul><ul><li>The Business Plan delivers a repeatable and consistent set of information, which is very helpful for objective and fast evaluation, comparison and decision-making by senior management. </li></ul></ul><ul><ul><li>The format ensures that the project’s business objectives and contribution are documented. </li></ul></ul><ul><ul><li>Business Case phase will provide complete justification for the product and and assess the priority for launch. The business case will include such information as: </li></ul></ul><ul><ul><ul><li>Product scope and target market </li></ul></ul></ul><ul><ul><ul><li>Fit with corporate strategy </li></ul></ul></ul><ul><ul><ul><li>Profitability analysis </li></ul></ul></ul><ul><ul><ul><li>Market and Competitive situation and time to market window of opportunity </li></ul></ul></ul><ul><ul><ul><li>High level impact analysis </li></ul></ul></ul><ul><ul><ul><li>Risks </li></ul></ul></ul>
  19. 19. Product Lifecycle – Design and Development QUALITY ASSURANCE BUSINESS CASE DESIGN AND DEVELOPMENT PRE-RELEASE RELEASE AND REVIEW INTEGRATED SERVICES DELIVERY DISCOVERY AND SCOPE PLANNING REVIEW Deliverables: Milestones: Stakeholders: Key Responsibilities <ul><li>Functional Requirements Approved </li></ul><ul><li>Development Software/ Hardware Preparation Completed </li></ul><ul><li>Documentation Preparation Completed </li></ul><ul><li>Design & Development Completed </li></ul><ul><li>Final Documentation and Handoff Completed </li></ul><ul><li>Training Material Developed </li></ul><ul><li>Marketing strategy developed </li></ul><ul><li>Decision Point 4 </li></ul><ul><li>Development </li></ul><ul><li>Product Management </li></ul><ul><li>Project Team Members </li></ul><ul><li>Participative, technical, and committed </li></ul><ul><li>Quality Product Design and Development </li></ul><ul><li>Cooperative and Cross-Functional Environment </li></ul><ul><li>Realignment of goals as needed </li></ul><ul><li>Process Flows from customer contract signature through post implementation support </li></ul><ul><li>Design and Development Plans and Documents </li></ul><ul><li>Training Strategy </li></ul><ul><li>Technical Support Strategy </li></ul><ul><li>Marketing Strategy </li></ul>Resources: <ul><li>Sales </li></ul><ul><li>Finance </li></ul><ul><li>Marketing </li></ul>
  20. 20. Design and Development Phase Philosophy <ul><li>Development Efforts </li></ul><ul><ul><li>Business Case is translated into concrete deliverables </li></ul></ul><ul><ul><li>Continual feedback is sought from the PMSD Product Team during both design and development </li></ul></ul><ul><ul><li>Product Development follows Quality Standards </li></ul></ul><ul><ul><li>Comprehensive Test Plans are developed </li></ul></ul><ul><ul><ul><li>Finely detailed with Operations for Acceptance Testing </li></ul></ul></ul><ul><ul><li>Make every effort to reduce cycle times </li></ul></ul><ul><ul><li>Develop Operations Strategies and Plans for future phases </li></ul></ul><ul><ul><ul><li>Operational Acceptance </li></ul></ul></ul><ul><ul><ul><li>Training </li></ul></ul></ul><ul><ul><ul><li>Technical Support </li></ul></ul></ul><ul><ul><li>Decision Point Meetings are at Product Sponsor and PMSD Product Team level and occur regularly on an “as-needed” basis </li></ul></ul><ul><li>Parallel Business efforts </li></ul><ul><ul><li>Market Development – monitor and research the market and competitive situation to reaffirm Business Case </li></ul></ul><ul><ul><li>Resolve any Intellectual Property Issues – Reaffirm your Technology Protection Strategy </li></ul></ul><ul><ul><li>Production and Operations Process – Production Costs and Capital Expenditures are firmly understood and agreed to </li></ul></ul><ul><ul><li>Update Business and Financial Analysis </li></ul></ul>
  21. 21. Outcomes – Design & Development <ul><li>Outcomes during Design and Development Phase: </li></ul><ul><ul><li>Design Architecture or Prototype </li></ul></ul><ul><ul><li>A Critical Design Review (CDR). This review is held when a design architecture or prototype exists that everyone can huddle around and constructively criticize. </li></ul></ul><ul><ul><li>Development Plan document that summarizes the project goals and the major activities across the different functional groups necessary to achieve those goals. </li></ul></ul><ul><ul><ul><li>Includes sections for describing major activities of the project, including activities that are sometimes neglected during planning. </li></ul></ul></ul><ul><ul><ul><li>Identify resources and tasks as the Team creates a more detailed plan and work breakdown. </li></ul></ul></ul><ul><ul><li>Operational considerations are identified and appropriate departments are engaged </li></ul></ul><ul><ul><li>Business units including marketing and sales are engaged to start planning for launch and appropriate marketing activities </li></ul></ul>
  22. 22. Product Lifecycle – Quality Assurance QUALITY ASSURANCE BUSINESS CASE DESIGN AND DEVELOPMENT PRE-RELEASE RELEASE AND REVIEW INTEGRATED SERVICES DELIVERY DISCOVERY AND SCOPE PLANNING REVIEW Deliverables: Milestones: Stakeholders: Key Responsibilities <ul><li>Functional Testing Complete and Accepted </li></ul><ul><li>Performance Testing Complete and Accepted </li></ul><ul><li>Support Acceptance Test and Validation Complete and Accepted </li></ul><ul><li>Decision Point 5 </li></ul><ul><li>Development </li></ul><ul><li>Project Team Members </li></ul><ul><li>Channel Services </li></ul><ul><li>Client Services </li></ul><ul><li>Product Management </li></ul><ul><li>Participative, technical, and committed </li></ul><ul><li>Quality Product Test and Validation </li></ul><ul><li>Cooperative and Cross-Functional Environment </li></ul><ul><li>Automated Tests as much as possible </li></ul><ul><li>Realignment of goals as needed </li></ul><ul><li>In-House and Customer Product Test Plans </li></ul><ul><li>Performance Test Plan and Results </li></ul><ul><li>Standard Operating Procedures for Implementation and Support </li></ul><ul><li>Quality Acceptance Review </li></ul>Resources: <ul><li>Sales </li></ul><ul><li>Finance </li></ul>
  23. 23. Quality Assurance Phase Philosophy <ul><li>Testing is not an afterthought – it is our gauge for continued success. Make sure enough time is devoted to testing. </li></ul><ul><li>Test and Validate throughout Lifecycle </li></ul><ul><ul><li>If there is appropriate levels of collaboration and participation from the Core PMSD Product Team during the Design and Development Phase, the Product will be partially approved before the QA Phase via continuous involvement </li></ul></ul><ul><li>Provide final and total validation of the entire Product Release Project </li></ul><ul><ul><li>The Actual Product </li></ul></ul><ul><ul><li>The support needed for the product </li></ul></ul><ul><ul><li>The Marketing plan for Release to Sales </li></ul></ul><ul><li>Technical and Client Support Validation and Acceptance is absolutely KEY to a successful Product Release </li></ul><ul><ul><li>Not only should the Product work right in the lab or development department, but it must also work right when the customer uses it and abuses it. </li></ul></ul><ul><li>Decision Point Meetings are at Product Sponsor and PMSD Product Team level and occur regularly on an “as-needed” basis </li></ul>
  24. 24. Outcomes– Quality Assurance <ul><li>Outcomes during Quality Assurance Phase: </li></ul><ul><ul><li>Test Results </li></ul></ul><ul><ul><li>Formal review of open issues and decision making regarding which ones must be corrected before going to Pre-Release. </li></ul></ul><ul><ul><li>Support documents updated for the new product </li></ul></ul><ul><ul><ul><li>Eg. Support SOPs, Pre-sales processes, billing processes, etc. </li></ul></ul></ul><ul><ul><li>Release of the product for market launch based on a thorough understanding of the product's true state.   </li></ul></ul>
  25. 25. Product Lifecycle – Pre-release QUALITY ASSURANCE BUSINESS CASE DESIGN AND DEVELOPMENT PRE-RELEASE RELEASE AND REVIEW INTEGRATED SERVICES DELIVERY DISCOVERY AND SCOPE PLANNING REVIEW Deliverables: Milestones: Stakeholders: Key Responsibilities <ul><li>Business Plan Complete </li></ul><ul><li>Marketing and communications plan complete </li></ul><ul><li>Support Matrix Complete </li></ul><ul><li>Std. Operating Procedures Complete </li></ul><ul><li>Training Complete </li></ul><ul><li>Decision Point 6 </li></ul><ul><li>Product Management </li></ul><ul><li>Marketing </li></ul><ul><li>Channel Services </li></ul><ul><li>Sales </li></ul><ul><li>Client Services </li></ul><ul><li>Project Team Members </li></ul><ul><li>Executive Mgt. </li></ul><ul><li>Transfer quality product and information to Client Services, Channel, and Sales </li></ul><ul><li>Final Decision Point – Go/No Go </li></ul><ul><li>Finalized Product / Business Plan </li></ul><ul><li>Product Maintenance and Support Documents </li></ul><ul><li>Sales Collateral and Documentation </li></ul><ul><li>Training Guides </li></ul><ul><li>Market Launch Communications Plan </li></ul><ul><li>Launch checklist </li></ul><ul><li>Optional Pilot Project Plan and Review </li></ul>Resources: <ul><li>Finance </li></ul><ul><li>Legal </li></ul><ul><li>Development </li></ul>
  26. 26. Pre-Release Phase Philosophy <ul><li>Throughout the lifecycle, the PMSD Product Team has been developing plans for releasing a Product for Sale and Support. In the Pre-Release Phase, the plans become reality. </li></ul><ul><li>Each Team has a stake in the success of the product. If the planning is complete and the plans are well communicated, there is a much higher probability for success. </li></ul><ul><ul><li>Teams are fully trained and have appropriate support documentation available. </li></ul></ul><ul><ul><li>Teams are fully aware of the business reasons for the product. </li></ul></ul><ul><ul><li>Teams have had full involvement in the decision-making process. </li></ul></ul><ul><ul><li>Teams feel comfortable with the quality of the product and supporting work </li></ul></ul><ul><li>Decision Point Meetings are at Product Sponsor and PMSD Product Team level and occur regularly on an “as-needed” basis </li></ul>
  27. 27. Outcomes – Pre-Release <ul><li>Outcomes during Pre-Release Phase: </li></ul><ul><ul><li>A completed product that is ready for market. </li></ul></ul><ul><ul><li>Preparations for customer implementation and support are made and all relevant parties are prepared. </li></ul></ul><ul><ul><li>Marketing activities are ready to announce and release the product. </li></ul></ul><ul><ul><li>Decision Point - Ensure that sufficient work has been completed in the current Product phase to allow the Product to be released </li></ul></ul>
  28. 28. Product Lifecycle – Release and Review QUALITY ASSURANCE BUSINESS CASE DESIGN AND DEVELOPMENT PRE-RELEASE RELEASE AND REVIEW INTEGRATED SERVICES DELIVERY DISCOVERY AND SCOPE PLANNING REVIEW Deliverables: Milestones: Stakeholders: Key Responsibilities <ul><li>Metrics and Gathering decided </li></ul><ul><li>Marketing activities conducted </li></ul><ul><li>Lessons Learned Meeting </li></ul><ul><li>30 Day Review Meeting </li></ul><ul><li>60 Day Review Meeting </li></ul><ul><li>90 Day Review Meeting </li></ul><ul><li>Optional: End of Life Plan and Review </li></ul><ul><li>Marketing </li></ul><ul><li>Product Management </li></ul><ul><li>Client Services </li></ul><ul><li>Channel Services </li></ul><ul><li>Sales </li></ul><ul><li>Continuous Improvement </li></ul><ul><li>Success Measurement </li></ul><ul><li>Concept Validation </li></ul><ul><li>Product End of Life Decision </li></ul><ul><li>Sales and Support Execution </li></ul><ul><li>Product Procedures Improvements and Efficiencies </li></ul><ul><li>Support, Sales, Financial and Product Maintenance Metrics </li></ul>Resources: <ul><li>Development </li></ul><ul><li>Executive Management </li></ul><ul><li>Project Team Members </li></ul>
  29. 29. Release Phase Philosophy <ul><li>It is time to execute on all the plans, strategies, training, work, and product development </li></ul><ul><li>Via PMSD Product Team involvement and collaboration, each team is satisfied that this product will reach, and exceed, the Business Case expectations </li></ul><ul><li>If there are any misgivings, speak now or forever hold your peace. </li></ul><ul><li>Decision Point Meetings are at Product Sponsor and PMSD Product Team level (depending on the priority, risk, and costs involved, executive level may be needed) and occur regularly on an “as-needed” basis </li></ul>
  30. 30. Review Phase Philosophy <ul><li>Continuous Improvement is KEY to the future success of Product Releases </li></ul><ul><ul><li>Lessons Learned Meeting and Follow-up after major Product Releases (and as determined by the Core PMSD Team) </li></ul></ul><ul><ul><li>30/60/90 Day Reviews of Product after first sale </li></ul></ul><ul><ul><li>Long Sales Cycle – Reviews with Sales to ensure they have what they need to close the sale </li></ul></ul><ul><li>Clear metrics are essential and gather/review/analysis of the metrics are imperative </li></ul><ul><li>Product Management has clear responsibility of the Profit/Loss of a Product </li></ul><ul><li>Product Management has clear responsibility of the Product RoadMap (including end-of-life strategy) </li></ul><ul><li>Timing is everything in our Business </li></ul><ul><ul><li>Constant review of the Market </li></ul></ul><ul><ul><li>Constant defining and redefining of the Target Market </li></ul></ul><ul><ul><li>End-of-Life Strategy </li></ul></ul>
  31. 31. Outcomes – Release & Review <ul><li>Outcomes during Release & Review Phase: </li></ul><ul><ul><li>Released Product for General Availability </li></ul></ul><ul><ul><li>Continuous Improvement of the product </li></ul></ul><ul><ul><li>Success Measurements gathered and monitored </li></ul></ul><ul><ul><li>Product roadmap developed and maintained </li></ul></ul><ul><ul><ul><li>Product End of Life Decision </li></ul></ul></ul>
  32. 32. Setting the Stage for the Future <ul><li>Corporate Change - the Ultimate Challenge </li></ul><ul><ul><li>Philosophical and Mind-set </li></ul></ul><ul><ul><li>We are changing the way we do business with each other </li></ul></ul><ul><ul><li>Lots to change, lots to do, lots to accomplish – Full organization support and assistance needed </li></ul></ul><ul><ul><li>It’s ok to make a mistake once, but learn from it, help each other to prevent mistakes </li></ul></ul><ul><ul><li>Allow your teams to get the work done – they are to be quality driven </li></ul></ul><ul><ul><li>Everything is a balancing act – time, cost, effort, resources – except Quality </li></ul></ul><ul><li>Support your PMSD Product Teams to: </li></ul><ul><ul><li>Have the courage to say “no, but yes if…” </li></ul></ul><ul><ul><li>Make decisions with facts, not feelings </li></ul></ul><ul><ul><li>Arrive with solutions, not complaints </li></ul></ul><ul><ul><li>Be a part of the solution, not leave it others </li></ul></ul>

×