Product Development Life Cycle
Phases and requirements to create and launch a product
The Product Development Life Cycle (PDLC) details the phases and requirements to create and launch a product. It’s comprised of seven stages, each with expected deliverables and contributions per team. Once Beta level has been completed, the product is ready for general availability.
Phases in the PDLC
Steps in the Product Life Cycle
1. Planned + Future
In this first phase the teams involved review proposed solutions and features, prioritize them, and define what will be planned for the upcoming quarter. Other items are categorized as NEXT and LATER based on prioritization.
Inputs: Insights
Outputs: Planned Product Features
Deliverables: Catagorizing Features as NOW, NEXT, LATER
Teams Involved:
Accountable: Product Management
Responsible: Product PJM
Consulted: Marketing, Lead Engineer/Architect, Sales, Data Analytics, Customer Success, Executives, Engagement Services / PIE, The Customer
2. Ideation
Ideation is defining the what. This will be completed through brainstorming, research, defining user stories and supported use cases. For any new product initiatives, an MVP will also be defined for initial launch to market.
Inputs: Features + Product Ideas
Outputs: Commercial Structure, Initial SEO Audit, Data Validation
Deliverables: Definition Document
Teams Involved:
Accountable: Product Management
Responsible: Product Management, UX/UI Design
Consulted: Marketing, Lead Engineer/Architect, Sales, Data Analytics, Customer Success, Executives, Engagement Services / PIE, The Customer
3. Architecture
Architecture + Design means defining the how. A technical feasibility audit is completed on the requirements, and any POC is carried out to ensure the solution is feasible. At this stage all features and requirements for the product update are confirmed.
Inputs: Product features presentation
Outputs: marketing message draft, Ticket creation & Prioritization, Dependencies documented
Deliverables: Development Plan, Development Solution, QA Plan + Test Cases
Teams Involved:
Accountable: Lead Engineer / Architect, Product PJM
Responsible: Product PJM, roduct Management, Engineering
Consulted: Product Management, UX /UI Design, QA, Dev Ops, SEO, Data Analytics
4. Development
Development phase covers the Product / Feature buildout. Engineers will work on carrying out the development plan and work closely with their project managers to meet targets.
Inputs: Development Plan & Tickets, Development Solution
Outputs: Implementation Process, Support Plan, Labels and Translations
Deliverables: Release Plan, Content / Labels
Teams Involved:
Accountable: Engineering, Product PJM, Content
Responsible: Product Management, Lead Engineer / Architect
Consulted: Product Management, UX /UI Design, QA, Dev Ops, Engagement Services / PIA, Customer Success
5. Testing + QA
The Testing + QA phase includes the internal QA and fixes, as well as the customer’s review (when involved). During this phase the feedback from QA and users is analyzed and the product may be adjusted, as needed. Any feedback not added immediately will be moved to insights and/or Planned + Future.
Inputs: Solution Available
Outputs: QA Feedback Completed, Feedback & Suggestions Reviewed
Deliverables: Implementation Process, Marketing Plan
Teams Involved:
Accountable: QA, Product Management
Responsible: Product Management, Engineering, Product PJM, Content
Consulted: UX /UI Design, Dev Ops, Lead Engineer / Architect, Engagement Services / PIA, the Customer
6. Beta
In the BETA Phase we launch the Product / Feature in Production for any defined Beta customer(s). Additionally, there will be monitoring and suggestions made for future improvements and iterations of the product.
Inputs: Availability in Prod
Outputs: Beta Product, QA Automation Tests
Deliverables: Support Plan, Training Plan, Customer Documentation
Teams Involved:
Accountable: Product Management
Responsible: Product Support, Product PJM, Customer Success
Consulted: The Customer, Marketing, Customer Success, Engagement Services / PIE, Engineering, DevOps, SEO
7. General Availability
The General Availability phase is reached with there is a stable product that is generally available for all customers (must meet product requirements). Sales Department has clear understanding to leverage the Product / Feature to customers.
Inputs: Product / Feature Documentation
Outputs: Product Availability, Marketing Message
Teams Involved:
Accountable: Product Management
Responsible: Sales
Consulted: Data Analytics, Customer Success, Engagement Services / PAO