End-to-End Delivery Lifecycle
Start
SSDLC
Defined by conducting interviews with different Teams of the Product & Engineering Department.
Next
Training content
JIRA
SSDLC Phases
Play
Play
Next
Click on the first phase to get started.
The SSDLC Phases & Accountability
Customer & Market Discovery
Product Discovery
Feature Design
Release & Launch
Live
Build
Deploy
PMM
EM
EM
PMM/PM
IM
PM/EM
PM
Click on each and to learn about each step.
Customer & Market Discovery
Product Discovery
Feature Design
Build
Release & Launch
Deploy
Live
to understand the market landscape (trends, competitors and potential demand for the product)
identifying target customer segments who are likely to benefit from the product or solution.
to understand the potential customers needs, pain points and preferences (through surveys, interviews....)
PM
PM/EM
IM
EM
PMO
PMM
PMM
Determine if the idea fits in an existing Squad scope or if it’s wider:- Existing squad scope => the Squad Product Manager (PM) will handle its prioritization and later steps.
- Wider => the Product Marketing Manager (PMM) will handle the Prioritization step to determine the feasibility and priority.
defining the unique value proposition of the product, highlighting how it will solve customer problems.
By focusing on these activities, the Customer and Market Discovery phase aims to ensure that the product is not only technically feasible but also commercially viable and aligned with market needs. This helps to reduce the risk of product failure before significant resources are invested in development.
Outcome
Back
Next
Customer & Market Discovery - JIRA Demo
Click on the video to watch a demo of the phase on JIRA.
Jira structure
Jira workflows vs SSDLC
Jira issue types
Status
Epic
Defining
User Story
No tickets in the Epic yet
Next
Back
Congrats! You've completed the first phase. Now click on the Product Discovery phase.
The SSDLC Phases & Accountability
Customer & Market Discovery
Product Discovery
Feature Design
Release & Launch
Live
Build
Deploy
PMM
EM
EM
PMM/PM
IM
PM/EM
PM
Click on each and the numbers to learn about each step.
Customer & Market Discovery
Product Discovery
Feature Design
Build
Release & Launch
Deploy
Live
- Assessing Market and Competitive Landscape:
to define the market size and business value for the idea.
to understand the target audience and their pain points, preferences, and behaviors.
PM
PM/EM
IM
EM
PMO
PMM
PM
PMM
PMM
- Defining Product Vision and Scope:
to clarify the product’s goals, features, and functionalities, and establish a clear vision that aligns with business objectives.
to ensure that all stakeholders have a shared understanding and agreement on the product’s direction and priorities.
The Product Discovery phase aims to reduce risks associated with product development by ensuring that the team builds a product that users need, want, and will use.
Do we need a third-party provider to implement it?
Do we need more thanan existing client's communication?
Yes
Outcome
No
Back
Next
Yes
Product Discovery - JIRA Demo
Click on the video to watch a demo of the phase on JIRA.
Jira structure
Jira workflows vs SSDLC
Jira issue types
Status
Discovery
Epic
User Story
No tickets in the Epic yet
Next
Back
Well done! Now it's time to delve into the Feature Design.
The SSDLC Phases & Accountability
Feature Design
Customer & Market Discovery
Product Discovery
Release & Launch
Live
Build
Deploy
PMM
EM
EM
PMM/PM
IM
PM/EM
PM
Click on each to learn about each step.
Customer & Market Discovery
Product Discovery
Feature Design
Build
Release & Launch
Deploy
Live
PM
PM/EM
IM
EM
PMO
- Product Backlog items redaction:
to define the user stories with functional details, use cases & acceptance criteria.
to create detailed UI/UX designs, wireframes, and prototypes.
PM/EM
PMM
PM
PMM
to clarity the user stories and ensure a shared understanding of what needs to be built.
Customer Communication only
No Approval Required
to discuss the upcoming user stories with the Team and ensure they are complete, clear, estimated and ready to be developed.
to specify the technical implementation details.
- Non-Functional Requirements:
to address performance, security, databases impacts, scalability...
The Feature Design phase aims to provide a clear, detailed, and validated plan for developing each feature, ensuring that it meets user needs, integrates smoothly with the system, and can be implemented efficiently and effectively by the development Team.
Outcome
Next
Back
Feature Design and Product Approval Process - JIRA Demo
Click on the video to watch a demo of the phase on JIRA.
Jira structure
Jira workflows vs SSDLC
Jira issue types
PAP
Architecture
Status
User stories
Epic
User Story
Defining
Should I create an Epic, a Story or a Task?
Back
Next
Feature Design - Defining & Refining User Stories - JIRA Demo
Click on the video to watch a demo of the phase on JIRA.
Jira structure
Jira workflows vs SSDLC
Jira issue types
Security
Status
Epic
Design
User Story
Ready for Sprint
Refining
When designing your stories, you can use these issues to follow the progress of the design: When refining your stories, you can use these issues to detail your tickets needs:
Functional Design
Technical Design
QA Sub-Task
Sub-Task
Database Impacts
Acceptance Criteria
Next
Back
Congrats! You've completed the first 3 phases. Now click on Build phase.
The SSDLC Phases & Accountability
Feature Design
Customer & Market Discovery
Product Discovery
Release & Launch
Live
Build
Deploy
PMM
EM
EM
PMM/PM
IM
PM/EM
PM
Click on each to learn about each step.
Customer & Market Discovery
Product Discovery
Feature Design
Build
Release & Launch
Deploy
Live
PM
PM/EM
EM
PMO
PMM
PM
PMM
PM/EM
EM
to manage changes to the codebase.
features implementation, unit testing and integration.
IM
executed on the developers individual development environments before committing code to the shared repository.
- Continuous Integration Tests:
executed automatically on a Continuous Integration server whenever code is committed to the shared repository.
Customer Communication only
Buid is approved
No Approval Required
by another developer to ensure code quality & best practices.
if there are impacts on the Databases, the dedicated DBA Team reviews and validates these impacts.
The Build phase goal is to transform the detailed design into a working software product, ensuring that it is correctly implemented, integrated, and ready for thorough testing.
Outcome
Next
Back
Build - JIRA Demo
Click on the video to watch a demo of the phase on JIRA.
Jira structure
Jira workflows vs SSDLC
Jira issue types
Status
Epic
Build
User Story
Building Reviewing
Back
Next
Congrats! You've completed the first 4 phases. Now click on Deploy phase.
The SSDLC Phases & Accountability
Feature Design
Customer & Market Discovery
Build
Product Discovery
Release & Launch
Live
Build
Deploy
PMM
EM
EM
PMM/PM
IM
PM/EM
PM
Click on each to learn about each step.
Customer & Market Discovery
Product Discovery
Feature Design
Build
Release & Launch
Deploy
Live
functional and behavioral validation of the feature.
PM
PM/EM
IM
EM
PMO
PMM
EM
PM
PMM
PM/EM
EM
- After Merging:
- continuous integration pipelines ensure ongoing stability and compatibility of the software.
- non regression tests ensure that all the recent changes work as expected and do not break existing functionalities.
Customer Communication only
Buid is approved
No Approval Required
checklist of criteria that a user story must meet to be considered complete and ready to be deployed.All the Development Teams comply to Mangopay Definition of Done.
- Deployment & Feature flags
the Deploy phase aims to make the software available to its intended users in a stable and reliable manner.
Outcome
Back
Next
Deploy - JIRA Demo
Click on the video to watch a demo of the phase on JIRA.
Jira structure
Jira workflows vs SSDLC
Jira issue types
Definition of Done
Status
Pre-release
Epic
User Story
Production
Testing
Validating
Sandbox
Incident / Ugly Fruit
Bug
discovered during Testing/ Validating.
discovered on Production.
Next
Back
Congrats! You've completed the first 5 phases. Now, it's time for the Release & Launch.
The SSDLC Phases & Accountability
Feature Design
Customer & Market Discovery
Product Discovery
Live
Release & Launch
Build
Deploy
PMM
EM
EM
PMM/PM
IM
PM/EM
PM
Click on each to learn about each step.
Customer & Market Discovery
Product Discovery
Feature Design
Build
Release & Launch
Deploy
Live
PM
PM/EM
IM
EM
PMO
PMM/PM
PMM
EM
PM
PM/EM
PMM
EM
- Communication & Marketing:
inform stakeholders generating awareness and excitement.
- User Training and Documentation:
provide necessary training for end users, support teams, and stakeholders.
set up support structures and processes to handle user queries, issues, and feedback post-launch.
Customer Communication only
Buid is approved
No Approval Required
Release is approved
The Release and Launch phase aims to achieve a successful adoption of the software by the end users.
Outcome
Next
Back
Release & Launch - JIRA Demo
Click on the video to watch a demo of the phase on JIRA.
Jira structure
Jira workflows vs SSDLC
Jira issue types
Status
Release
Epic
User Story
Back
Next
Congrats! Now, it's time to explore the Live phase.
The SSDLC Phases & Accountability
Feature Design
Customer & Market Discovery
Product Discovery
Live
Release & Launch
Build
Deploy
PMM
EM
EM
PMM/PM
IM
PM/EM
PM
Click on each number to learn about each step.
Customer & Market Discovery
Product Discovery
Feature Design
Build
Release & Launch
Deploy
Live
PM
PM/EM
IM
EM
PMO
PMM/PM
PMM
EM
PM
PMM
PM/EM
EM
IM
Customer Communication only
Buid is approved
No Approval Required
Release is approved
The Live phase aims to keep the software operational, efficient and secure while continuously meeting the needs of its users.
Outcome
Next
Back
Live - JIRA Demo
Click on the video to watch a demo of the phase on JIRA.
Jira structure
Jira workflows vs SSDLC
Jira issue types
Status
Release
Epic
User Story
Inidents or Ugly Fruits issues will be created if needed
Back
Next
Customer & Market Discovery
Product Discovery
Feature Design
Build
Release & Launch
Deploy
Live
PM
PM/EM
IM
EM
PMO
PMM/PM
PMM
EM
PM
PM/EM
PMM
EM
IM
Customer Communication only
Buid is approved
No Approval Required
Release is approved
Back
Next
You've completed all the SSDLC Phases!
The successful execution of Mangopay SSDLC requires the commitment, active participation and effective collaboration of all the Teams. The definition of Mangopay SSDLC will continue to evolve and improve.If you have improvements suggestions, please let us know to build together the SSDLC v2!
Architecture Review Process - EM
Epic
Epic Status transitions from to
When
Discovery
User Stories
Architecture Review
Automatically creates ticket in the Epic.
What happens
notifies the Architecture Team on the dedicated Slack channel.
What to do
The Architecture Review ticket needs to be filled by the EM.
Jira Structure
Team's JIRA Projects
Team Projects Structure Examples
Team's Project
Experience
Activity
Monolith
Team's project
Activity Team project
Experience Team project
Component Project
The Team tasks on the Monolith
Monolith project
Monolith project
Component Project
Flare Project
HUB Project
The Team tasks on other Components
Karma Project
Billing Project
Scrum Board
Epic Board
Readiness Board
Dashboard Project
To follow the progress of the tickets in the Sprint
To follow the preparation of the tickets before the start of the Sprint
To follow the progress of the Epics.
Docs Project
Demo Project
Customer & Market Discovery
Accountability -> PMM Goal -> To thouroughly understand the needs, preferences, and behaviors of potential users and the market environment in which the product will operate. This will increase the chances of success of the product.
Customer & Market Discovery - Overview & Demo
Epic / Story / Task / Sub-task
Epic
Level1
A large body of work that can be broken down into smaller, more manageable pieces. It often represents a significant feature or a major milestone.
Scope: Epics span multiple sprints and may take weeks or months to complete.
Purpose: Used to organize and track progress on large subjects or major functionalities that might sometimes require coordination across multiple teams or workstreams.
Story
Level0
A description of a specific feature or functionality from the end user's perspective.It represents a piece of work that delivers value to the user. Scope: Stories are smaller than epics and are usually completed within a single sprint. Purpose: Used to capture specific requirements and user needs in a clear, concise format that can be easily understood and implemented by the Development Team.
Task
Technical Task
An individual piece of work that needs to be done and which value might not be visible to the users.Scope: Tasks are very granular and can often be completed in a few hours to a couple of days. Purpose: Used to describe actionable items needed and might be separate from other Stories.
Level-1
Sub-Task
An individual piece of work that needs to be done to complete a Story.Sub-tasks are the smallest unit of work and are often technical in nature. Scope: Sub-tasks are very granular and can often be completed in a few hours to a couple of days. Purpose: Used to break down stories into actionable items that developers can work on.
Product Approval Process - PM
Epic
Epic Status transitions from to
When
Discovery
User Stories
Automatically creates ticket in the Epic.
PAP
What happens
notifies the involved Team on the dedicated Slack channel
What to do
The PAP contains sub-tasks that need to be filled by the PM
PAP ticket can have these sub-tasks:
Bugs, Ugly Fruits & Incidents are important, we must treat them with the good speed & attention.
Jira Issue types
- Incidents are created when there are critical issues like service outages or major disruptions affecting many clients (Production).
When it is escalated by the Incident Manager, your Team will get notified on Slack to work on the Incident. An Incident should never be discussed in private, if you need to discuss, create a channel if not already done by Incident manager ( #inc-...)
Ugly Fruit Incident
Incident
Bug
- created when an issue is found in Production.
When it is escalated by the Incident Manager, your Team will get notified on Slack to work on the Ugly Fruit.An Ugly Fruit should never be discussed in private, if you need to discuss, create a channel if not already done by Incident manager ( #inc-...)
- discovered during the testing / Validation phase of a feature.
They are an anomaly compared to the target behavior of the feature(i.e acceptance criteria). When the Team creates a bug in JIRA, it should always be linked to an aceptance criteria.=> sometimes, a bug can lead to add /remove/update an acceptance criteria, otherwise, it's a implementation issue.
Product Discovery
Accountability -> PMGoal -> Ensure that the Development Team builds the right product that addresses real user needs and market demands effectively.
Product Discovery - Overview
Jira Issue types
OKR
Level3
Initiative
Level2
Epic
Level1
Story
Task
Level0
Bug
Definition of Done
Technical Design
Incident
Technical Task
Functional Design
Ugly Fruit Incident
Level-1
Sub-Task
QA Sub-Task
Acceptance Criteria
Database Impacts
JIRA
Deploy
Accountability -> EMGoal -> To ensure that the software is successfully transitioned from Development to a live environment and available to its intended users.
Deploy - Overview
Product Discovery
Accountability -> PMGoal -> Ensure that the Development Team builds the right product that addresses real user needs and market demands effectively.
Product Discovery - Overview
Customer & Market Discovery
Live
Feature Design
Product Discovery
Release & Launch
Build
Deploy
Incident Manager (IM)
Product Marketing Manager (PMM) & Product Manager (PM)
Engineering Manager (EM)
Engineering Manager (EM)
Product Marketing Manager (PMM)
Product Manager (PM) & Engineering Manager (EM)
Product Manager (PM)
Product Discovery
Accountability -> PMGoal -> Ensure that the Development Team builds the right product that addresses real user needs and market demands effectively.
Product Discovery - Overview
Deploy
Accountability -> EMGoal -> To ensure that the software is successfully transitioned from Development to a live environment and available to its intended users.
Deploy - Overview
Customer & Market Discovery
Accountability -> PMM Goal -> To thouroughly understand the needs, preferences, and behaviors of potential users and the market environment in which the product will operate. This will increase the chances of success of the product.
Customer & Market Discovery - Overview & Demo
Feature Design
Accountability -> PM/EMGoal -> To create well-defined plans and Product Backlog items for the features & functionalities that the software will include. This step ensures that the Development Team has a good understanding of the features to build, reducing the risk of misunderstandings or scope changes later.
Feature Design - Overview
Customer & Market Discovery
Accountability -> PMM Goal -> To thouroughly understand the needs, preferences, and behaviors of potential users and the market environment in which the product will operate. This will increase the chances of success of the product.
Customer & Market Discovery - Overview & Demo
Feature Design
Accountability -> PM/EMGoal -> To create well-defined plans and Product Backlog items for the features & functionalities that the software will include. This step ensures that the Development Team has a good understanding of the features to build, reducing the risk of misunderstandings or scope changes later.
Feature Design - Overview
Epic / Story / Task / Sub-task
Epic
Level1
A large body of work that can be broken down into smaller, more manageable pieces. It often represents a significant feature or a major milestone.
Scope: Epics span multiple sprints and may take weeks or months to complete.
Purpose: Used to organize and track progress on large subjects or major functionalities that might sometimes require coordination across multiple teams or workstreams.
Story
Level0
A description of a specific feature or functionality from the end user's perspective.It represents a piece of work that delivers value to the user. Scope: Stories are smaller than epics and are usually completed within a single sprint. Purpose: Used to capture specific requirements and user needs in a clear, concise format that can be easily understood and implemented by the Development Team.
Task
Technical Task
An individual piece of work that needs to be done and which value might not be visible to the users.Scope: Tasks are very granular and can often be completed in a few hours to a couple of days. Purpose: Used to describe actionable items needed and might be separate from other Stories.
Level-1
Sub-Task
An individual piece of work that needs to be done to complete a Story.Sub-tasks are the smallest unit of work and are often technical in nature. Scope: Sub-tasks are very granular and can often be completed in a few hours to a couple of days. Purpose: Used to break down stories into actionable items that developers can work on.
Jira Issue types
OKR
Level3
Initiative
Level2
Epic
Level1
Story
Task
Level0
Bug
Definition of Done
Technical Design
Incident
Technical Task
Functional Design
Ugly Fruit Incident
Level-1
Sub-Task
QA Sub-Task
Acceptance Criteria
Database Impacts
Build
Accountability -> EMGoal -> To ensure that the software is developed according to the design specifications and is ready for more comprehensive testing and validation in the coming phase.
Building
Build - Overview
Build
Accountability -> EMGoal -> To ensure that the software is developed according to the design specifications and is ready for more comprehensive testing and validation in the coming phase.
Building
Build - Overview
Feature Design
Accountability -> PM/EMGoal -> To create well-defined plans and Product Backlog items for the features & functionalities that the software will include. This step ensures that the Development Team has a good understanding of the features to build, reducing the risk of misunderstandings or scope changes later.
Feature Design - Overview
Jira Structure
Team's JIRA Projects
Team Projects Structure Examples
Team's Project
Experience
Activity
Monolith
Team's project
Activity Team project
Experience Team project
Component Project
The Team tasks on the Monolith
Monolith project
Monolith project
Component Project
Flare Project
HUB Project
The Team tasks on other Components
Karma Project
Billing Project
Scrum Board
Epic Board
Readiness Board
Dashboard Project
To follow the progress of the tickets in the Sprint
To follow the preparation of the tickets before the start of the Sprint
To follow the progress of the Epics.
Docs Project
Demo Project
Jira Structure
Team's JIRA Projects
Team Projects Structure Examples
Team's Project
Experience
Activity
Monolith
Team's project
Activity Team project
Experience Team project
Component Project
The Team tasks on the Monolith
Monolith project
Monolith project
Component Project
Flare Project
HUB Project
The Team tasks on other Components
Karma Project
Billing Project
Scrum Board
Epic Board
Readiness Board
Dashboard Project
To follow the progress of the tickets in the Sprint
To follow the preparation of the tickets before the start of the Sprint
To follow the progress of the Epics.
Docs Project
Demo Project
Architecture Review Process - EM
Epic
Epic Status transitions from to
When
Discovery
User Stories
Architecture Review
Automatically creates ticket in the Epic.
What happens
notifies the Architecture Team on the dedicated Slack channel.
What to do
The Architecture Review ticket needs to be filled by the EM.
Jira Issue types
OKR
Level3
Initiative
Level2
Epic
Level1
Story
Task
Level0
Bug
Definition of Done
Technical Design
Incident
Technical Task
Functional Design
Ugly Fruit Incident
Level-1
Sub-Task
QA Sub-Task
Acceptance Criteria
Database Impacts
Deploy
Accountability -> EMGoal -> To ensure that the software is successfully transitioned from Development to a live environment and available to its intended users.
Deploy - Overview
Build
Accountability -> EMGoal -> To ensure that the software is developed according to the design specifications and is ready for more comprehensive testing and validation in the coming phase.
Building
Build - Overview
Jira Issue types
OKR
Level3
Initiative
Level2
Epic
Level1
Story
Task
Level0
Bug
Definition of Done
Technical Design
Incident
Technical Task
Functional Design
Ugly Fruit Incident
Level-1
Sub-Task
QA Sub-Task
Acceptance Criteria
Database Impacts
Customer & Market Discovery
Accountability -> PMM Goal -> To thouroughly understand the needs, preferences, and behaviors of potential users and the market environment in which the product will operate. This will increase the chances of success of the product.
Customer & Market Discovery - Overview & Demo
Release & Launch
Accountability -> PMM/PMGoal -> To ensure that the software is successfuly introduced to the market and the users have the necessary support in its adoption.
Release & Launch - Overview
Release & Launch
Accountability -> PMM/PMGoal -> To ensure that the software is successfuly introduced to the market and the users have the necessary support in its adoption.
Release & Launch - Overview
Customer & Market Discovery
Accountability -> PMM Goal -> To thouroughly understand the needs, preferences, and behaviors of potential users and the market environment in which the product will operate. This will increase the chances of success of the product.
Customer & Market Discovery - Overview & Demo
Definition of Done in JIRA
Jira Issue type
Definition of Done
When
A Release (version) is created in JIRA.
What happens
Automatically creates in the Release a ticket.
The checklist in the ticket needs to be reviewed and all steps validated before Deploying.
What to do
Jira Structure
Team's JIRA Projects
Team Projects Structure Examples
Team's Project
Experience
Activity
Monolith
Team's project
Activity Team project
Experience Team project
Component Project
The Team tasks on the Monolith
Monolith project
Monolith project
Component Project
Flare Project
HUB Project
The Team tasks on other Components
Karma Project
Billing Project
Scrum Board
Epic Board
Readiness Board
Dashboard Project
To follow the progress of the tickets in the Sprint
To follow the preparation of the tickets before the start of the Sprint
To follow the progress of the Epics.
Docs Project
Demo Project
Jira Workflow VS SSDLC
Customer & Market Discovery
Product Discovery
Release & Launch
SSDLC Phase
Feature Design
Build
Deploy
Live
PM
EM
PMM
PM/EM
EM
PMM/PM
IM
Release
Pre-release
Epic
Building
Design
Defining
Discovery
User stories
StoryBug Task
No tickets in the Epic yet
Defining Refining Ready for Dev Building Reviewing Testing Validating Sandbox Production
Incidents & Ugly Fruits
Feature Design
Accountability -> PM/EMGoal -> To create well-defined plans and Product Backlog items for the features and functionalities that the software will include. This step ensures that the Development Team has a good understanding of the features to build, reducing the risk of misunderstandings or scope changes later.
Feature Design - Overview
Jira Structure
Team's JIRA Projects
Team Projects Structure Examples
Team's Project
Experience
Activity
Monolith
Team's project
Activity Team project
Experience Team project
Component Project
The Team tasks on the Monolith
Monolith project
Monolith project
Component Project
Flare Project
HUB Project
The Team tasks on other Components
Karma Project
Billing Project
Scrum Board
Epic Board
Readiness Board
Dashboard Project
To follow the progress of the tickets in the Sprint
To follow the preparation of the tickets before the start of the Sprint
To follow the progress of the Epics.
Docs Project
Demo Project
Jira Workflow VS SSDLC
Customer & Market Discovery
Product Discovery
Release & Launch
SSDLC Phase
Feature Design
Build
Deploy
Live
PM
EM
PMM
PM/EM
EM
PMM/PM
IM
Release
Pre-release
Epic
Building
Design
Defining
Discovery
User stories
StoryBug Task
No tickets in the Epic yet
Defining Refining Ready for Dev Building Reviewing Testing Validating Sandbox Production
Incidents & Ugly Fruits
Feature Design
Accountability -> PM/EMGoal -> To create well-defined plans and Product Backlog items for the features & functionalities that the software will include. This step ensures that the Development Team has a good understanding of the features to build, reducing the risk of misunderstandings or scope changes later.
Feature Design - Overview
Release & Launch
Accountability -> PMM/PMGoal -> To ensure that the software is successfuly introduced to the market and the users have the necessary support in its adoption.
Release & Launch - Overview
Customer & Market Discovery
Accountability -> PMM Goal -> To thouroughly understand the needs, preferences, and behaviors of potential users and the market environment in which the product will operate. This will increase the chances of success of the product.
Customer & Market Discovery - Overview & Demo
Live
Accountability -> IMGoal -> To ensure that the software remains functional, secure and relevant over time, providing ongoing value to the users.
Live
Live - Overview
Product Discovery
Accountability -> PMGoal -> Ensure that the Development Team builds the right product that addresses real user needs and market demands effectively.
Product Discovery - Overview
Customer & Market Discovery
Accountability -> PMM Goal -> To thouroughly understand the needs, preferences, and behaviors of potential users and the market environment in which the product will operate. This will increase the chances of success of the product.
Customer & Market Discovery - Overview & Demo
Build
Accountability -> EMGoal -> To ensure that the software is developed according to the design specifications and is ready for more comprehensive testing and validation in the coming phase.
Building
Build - Overview
Build
Accountability -> EMGoal -> To ensure that the software is developed according to the design specifications and is ready for more comprehensive testing and validation in the coming phase.
Building
Build - Overview
Build
Accountability -> EMGoal -> To ensure that the software is developed according to the design specifications and is ready for more comprehensive testing and validation in the coming phase.
Building
Build - Overview
Customer & Market Discovery
Accountability: PMM
- is investigating what kind of problem needs to be solved and what kind of solution must be brought.
- is looking into the insights (Insight Review step) from the clients or the market.
Get Started
Build
Accountability -> EMGoal -> To ensure that the software is developed according to the design specifications and is ready for more comprehensive testing and validation in the coming phase.
Building
Build - Overview
Jira Issue types
OKR
Level3
Initiative
Level2
Epic
Level1
Story
Task
Level0
Bug
Definition of Done
Technical Design
Incident
Technical Task
Functional Design
Ugly Fruit Incident
Level-1
Sub-Task
QA Sub-Task
Acceptance Criteria
Database Impacts
Customer & Market Discovery
Accountability: PMM
- is investigating what kind of problem needs to be solved and what kind of solution must be brought.
- is looking into the insights (Insight Review step) from the clients or the market.
Get Started
Bugs, Ugly Fruits & Incidents are important, we must treat them with the good speed & attention.
Jira Issue types
- Incidents are created when there are critical issues like service outages or major disruptions affecting many clients (Production).
When it is escalated by the Incident Manager, your Team will get notified on Slack to work on the Incident. An Incident should never be discussed in private, if you need to discuss, create a channel if not already done by Incident manager ( #inc-...)
Incident
Ugly Fruit Incident
Bug
- created when an issue is found in Production.
When it is escalated by the Incident Manager, your Team will get notified on Slack to work on the Ugly Fruit.An Ugly Fruit should never be discussed in private, if you need to discuss, create a channel if not already done by Incident manager ( #inc-...)
- discovered during the testing / Validation phase of a feature.
They are an anomaly compared to the target behavior of the feature(i.e acceptance criteria). When the Team creates a bug in JIRA, it should always be linked to an aceptance criteria.=> sometimes, a bug can lead to add /remove/update an acceptance criteria, otherwise, it's a implementation issue.
Deploy
Accountability -> EMGoal -> To ensure that the software is successfully transitioned from Development to a live environment and available to its intended users.
Deploy - Overview
Product Discovery
Accountability -> PMGoal -> Ensure that the Development Team builds the right product that addresses real user needs and market demands effectively.
Product Discovery - Overview
Live
Accountability -> IMGoal -> To ensure that the software remains functional, secure and relevant over time, providing ongoing value to the users.
Live
Live - Overview
Deploy
Accountability -> EMGoal -> To ensure that the software is successfully transitioned from Development to a live environment and available to its intended users.
Deploy - Overview
Jira Workflow VS SSDLC
Customer & Market Discovery
Product Discovery
Release & Launch
SSDLC Phase
Feature Design
Build
Deploy
Live
PM
EM
PMM
PM/EM
EM
PMM/PM
IM
Release
Pre-release
Epic
Building
Design
Defining
Discovery
User stories
StoryBug Task
No tickets in the Epic yet
Defining Refining Ready for Dev Building Reviewing Testing Validating Sandbox Production
Incidents & Ugly Fruits
Deploy
Accountability -> EMGoal -> To ensure that the software is successfully transitioned from Development to a live environment and available to its intended users.
Deploy - Overview
Product Discovery
Accountability -> PMGoal -> Ensure that the Development Team builds the right product that addresses real user needs and market demands effectively.
Product Discovery - Overview
Build
Accountability -> EMGoal -> To ensure that the software is developed according to the design specifications and is ready for more comprehensive testing and validation in the coming phase.
Building
Build - Overview
Customer & Market Discovery
Accountability -> PMM Goal -> To thouroughly understand the needs, preferences, and behaviors of potential users and the market environment in which the product will operate. This will increase the chances of success of the product.
Customer & Market Discovery - Overview & Demo
Customer & Market Discovery
Accountability -> PMM Goal -> To thouroughly understand the needs, preferences, and behaviors of potential users and the market environment in which the product will operate. This will increase the chances of success of the product.
Customer & Market Discovery - Overview & Demo
Customer & Market Discovery
Accountability -> PMM Goal -> To thouroughly understand the needs, preferences, and behaviors of potential users and the market environment in which the product will operate. This will increase the chances of success of the product.
Customer & Market Discovery - Overview & Demo
Deploy
Accountability -> EMGoal -> To ensure that the software is successfully transitioned from Development to a live environment and available to its intended users.
Deploy - Overview
No deployment without securiy checks pentest for sensitive features
Security
Security Approval Process - EM
Epic
Epic Status transitions from to
When
User Stories
Design
Automatically creates ticket in the Epic.
Security Review
What happens
notifies the Security Team on the dedicated Slack channel.
What to do
The Security Review ticket needs to be filled by the EM.
Security Review ticket can have:
- Automated scan ticket
Contains results from automated scans against repos relevant to the Epic
- Pentest
Contains results from pentest, if necessary
- Threat model
Contains issues identified by threat model
In addition to a Security Review checklist.
Bugs, Ugly Fruits & Incidents are important, we must treat them with the good speed & attention.
Jira Issue types
- Incidents are created when there are critical issues like service outages or major disruptions affecting many clients (Production).
When it is escalated by the Incident Manager, your Team will get notified on Slack to work on the Incident. An Incident should never be discussed in private, if you need to discuss, create a channel if not already done by Incident manager ( #inc-...)
Incident
Ugly Fruit Incident
Bug
- created when an issue is found in Production.
When it is escalated by the Incident Manager, your Team will get notified on Slack to work on the Ugly Fruit.An Ugly Fruit should never be discussed in private, if you need to discuss, create a channel if not already done by Incident manager ( #inc-...)
- discovered during the testing / Validation phase of a feature.
They are an anomaly compared to the target behavior of the feature(i.e acceptance criteria). When the Team creates a bug in JIRA, it should always be linked to an aceptance criteria.=> sometimes, a bug can lead to add /remove/update an acceptance criteria, otherwise, it's a implementation issue.
Product Discovery
Accountability -> PMGoal -> Ensure that the Development Team builds the right product that addresses real user needs and market demands effectively.
Product Discovery - Overview
Live
Accountability -> IMGoal -> To ensure that the software remains functional, secure and relevant over time, providing ongoing value to the users.
Live
Live - Overview
Feature Design
Accountability -> PM/EMGoal -> To create well-defined plans and Product Backlog items for the features and functionalities that the software will include. This step ensures that the Development Team has a good understanding of the features to build, reducing the risk of misunderstandings or scope changes later.
Feature Design - Overview
Jira Issue types
OKR
Level3
Initiative
Level2
Epic
Level1
Story
Task
Level0
Bug
Definition of Done
Technical Design
Incident
Technical Task
Functional Design
Ugly Fruit Incident
Level-1
Sub-Task
QA Sub-Task
Acceptance Criteria
Database Impacts
Live
Accountability -> IMGoal -> To ensure that the software remains functional, secure and relevant over time, providing ongoing value to the users.
Live
Live - Overview
Customer & Market Discovery
Accountability -> PMM Goal -> To thouroughly understand the needs, preferences, and behaviors of potential users and the market environment in which the product will operate. This will increase the chances of success of the product.
Customer & Market Discovery - Overview & Demo
Customer & Market Discovery
Accountability -> PMM Goal -> To thouroughly understand the needs, preferences, and behaviors of potential users and the market environment in which the product will operate. This will increase the chances of success of the product.
Customer & Market Discovery - Overview & Demo
Jira Workflow VS SSDLC
Customer & Market Discovery
Product Discovery
Release & Launch
SSDLC Phase
Feature Design
Build
Deploy
Live
PM
EM
PMM
PM/EM
EM
PMM/PM
IM
Release
Pre-release
Epic
Building
Design
Defining
Discovery
User stories
StoryBug Task
No tickets in the Epic yet
Defining Refining Ready for Dev Building Reviewing Testing Validating Sandbox Production
Incidents & Ugly Fruits
Jira Workflow VS SSDLC
Customer & Market Discovery
Product Discovery
Release & Launch
SSDLC Phase
Feature Design
Build
Deploy
Live
PM
EM
PMM
PM/EM
EM
PMM/PM
IM
Release
Pre-release
Epic
Building
Design
Defining
Discovery
User stories
StoryBug Task
No tickets in the Epic yet
Defining Refining Ready for Dev Building Reviewing Testing Validating Sandbox Production
Incidents & Ugly Fruits
Jira Structure
Team's JIRA Projects
Team Projects Structure Examples
Team's Project
Experience
Activity
Monolith
Team's project
Activity Team project
Experience Team project
Component Project
The Team tasks on the Monolith
Monolith project
Monolith project
Component Project
Flare Project
HUB Project
The Team tasks on other Components
Karma Project
Billing Project
Scrum Board
Epic Board
Readiness Board
Dashboard Project
To follow the progress of the tickets in the Sprint
To follow the preparation of the tickets before the start of the Sprint
To follow the progress of the Epics.
Docs Project
Demo Project
Jira Workflow VS SSDLC
Customer & Market Discovery
Product Discovery
Release & Launch
SSDLC Phase
Feature Design
Build
Deploy
Live
PM
EM
PMM
PM/EM
EM
PMM/PM
IM
Release
Pre-release
Epic
Building
Design
Defining
Discovery
User stories
StoryBug Task
No tickets in the Epic yet
Defining Refining Ready for Dev Building Reviewing Testing Validating Sandbox Production
Incidents & Ugly Fruits
Customer & Market Discovery
Accountability -> PMM Goal -> To thouroughly understand the needs, preferences, and behaviors of potential users and the market environment in which the product will operate. This will increase the chances of success of the product.
Customer & Market Discovery - Overview & Demo
Product Discovery
Accountability -> PMGoal -> Ensure that the Development Team builds the right product that addresses real user needs and market demands effectively.
Product Discovery - Overview
Product Discovery
Accountability -> PMGoal -> Ensure that the Development Team builds the right product that addresses real user needs and market demands effectively.
Product Discovery - Overview
Customer & Market Discovery
Accountability: PMM
- is investigating what kind of problem needs to be solved and what kind of solution must be brought.
- is looking into the insights (Insight Review step) from the clients or the market.
Get Started
Release & Launch
Accountability -> PMM/PMGoal -> To ensure that the software is successfuly introduced to the market and the users have the necessary support in its adoption.
Release & Launch - Overview
Definition of Ready
- The ticket is attached to an Epic
- Acceptance criteria are established for the story
- The Sprint is indicated
- The ticket is understood and estimated
- Security Design Review performed
- (when required) Architectural impact identified
- (when required) Tre-Amigos:
Technicals aspects added (Endpoints / payloads - ux/ui)
Epic / Story / Task / Sub-task
Epic
Level1
A large body of work that can be broken down into smaller, more manageable pieces. It often represents a significant feature or a major milestone.
Scope: Epics span multiple sprints and may take weeks or months to complete.
Purpose: Used to organize and track progress on large subjects or major functionalities that might sometimes require coordination across multiple teams or workstreams.
Story
Level0
A description of a specific feature or functionality from the end user's perspective.It represents a piece of work that delivers value to the user. Scope: Stories are smaller than epics and are usually completed within a single sprint. Purpose: Used to capture specific requirements and user needs in a clear, concise format that can be easily understood and implemented by the Development Team.
Task
Technical Task
An individual piece of work that needs to be done and which value might not be visible to the users.Scope: Tasks are very granular and can often be completed in a few hours to a couple of days. Purpose: Used to describe actionable items needed and might be separate from other Stories.
Level-1
Sub-Task
An individual piece of work that needs to be done to complete a Story.Sub-tasks are the smallest unit of work and are often technical in nature. Scope: Sub-tasks are very granular and can often be completed in a few hours to a couple of days. Purpose: Used to break down stories into actionable items that developers can work on.
Build
Accountability -> EMGoal -> To ensure that the software is developed according to the design specifications and is ready for more comprehensive testing and validation in the coming phase.
Building
Build - Overview
Product Discovery
Accountability -> PMGoal -> Ensure that the Development Team builds the right product that addresses real user needs and market demands effectively.
Product Discovery - Overview
Jira Structure
Team's JIRA Projects
Team Projects Structure Examples
Team's Project
Experience
Activity
Monolith
Team's project
Activity Team project
Experience Team project
Component Project
The Team tasks on the Monolith
Monolith project
Monolith project
Component Project
Flare Project
HUB Project
The Team tasks on other Components
Karma Project
Billing Project
Scrum Board
Epic Board
Readiness Board
Dashboard Project
To follow the progress of the tickets in the Sprint
To follow the preparation of the tickets before the start of the Sprint
To follow the progress of the Epics.
Docs Project
Demo Project
Product Approval Process - PM
Epic
Epic Status transitions from to
When
Discovery
User Stories
Automatically creates ticket in the Epic.
PAP
What happens
notifies the involved Team on the dedicated Slack channel
What to do
The PAP contains sub-tasks that need to be filled by the PM
PAP ticket can have these sub-tasks:
Release & Launch
Accountability -> PMOGoal -> To ensure that the software is successfuly introduced to the market and the users have the necessary support in its adoption.
Release & Launch - Overview
Release & Launch
Accountability -> PMOGoal -> To ensure that the software is successfuly introduced to the market and the users have the necessary support in its adoption.
Release & Launch - Overview
Jira Issue types
OKR
Level3
Initiative
Level2
Epic
Level1
Story
Task
Level0
Bug
Definition of Done
Technical Design
Incident
Technical Task
Functional Design
Ugly Fruit Incident
Level-1
Sub-Task
QA Sub-Task
Acceptance Criteria
Database Impacts
Build
Accountability -> EMGoal -> To ensure that the software is developed according to the design specifications and is ready for more comprehensive testing and validation in the coming phase.
Building
Build - Overview
Product Discovery
Accountability -> PMGoal -> Ensure that the Development Team builds the right product that addresses real user needs and market demands effectively.
Product Discovery - Overview
Feature Design
Accountability -> PM/EMGoal -> To create well-defined plans and Product Backlog items for the features & functionalities that the software will include. This step ensures that the Development Team has a good understanding of the features to build, reducing the risk of misunderstandings or scope changes later.
Feature Design - Overview
Product Discovery
Accountability -> PMGoal -> Ensure that the Development Team builds the right product that addresses real user needs and market demands effectively.
Product Discovery - Overview
Deploy
Accountability -> EMGoal -> To ensure that the software is successfully transitioned from Development to a live environment and available to its intended users.
Deploy - Overview
Jira Workflow VS SSDLC
Customer & Market Discovery
Product Discovery
Release & Launch
SSDLC Phase
Feature Design
Build
Deploy
Live
PM
EM
PMM
PM/EM
EM
PMM/PM
IM
Release
Pre-release
Epic
Building
Design
Defining
Discovery
User stories
StoryBug Task
No tickets in the Epic yet
Defining Refining Ready for Dev Building Reviewing Testing Validating Sandbox Production
Incidents & Ugly Fruits
Customer & Market Discovery
Accountability -> PMM Goal -> To thouroughly understand the needs, preferences, and behaviors of potential users and the market environment in which the product will operate. This will increase the chances of success of the product.
Customer & Market Discovery - Overview & Demo
Customer & Market Discovery
Accountability: PMM
- is investigating what kind of problem needs to be solved and what kind of solution must be brought.
- is looking into the insights (Insight Review step) from the clients or the market.
Get Started
Product Discovery
Accountability -> PMGoal -> Ensure that the Development Team builds the right product that addresses real user needs and market demands effectively.
Product Discovery - Overview
Product Approval Process - PM
Epic
Epic Status transitions from to
When
Discovery
User Stories
Automatically creates ticket in the Epic.
PAP
What happens
notifies the involved Team on the dedicated Slack channel
What to do
The PAP contains sub-tasks that need to be filled by the PM
PAP ticket can have these sub-tasks:
Jira Issue types
OKR
Level3
Initiative
Level2
Epic
Level1
Story
Task
Level0
Bug
Definition of Done
Technical Design
Incident
Technical Task
Functional Design
Ugly Fruit Incident
Level-1
Sub-Task
QA Sub-Task
Acceptance Criteria
Database Impacts
Jira Workflow VS SSDLC
Customer & Market Discovery
Product Discovery
Release & Launch
SSDLC Phase
Feature Design
Build
Deploy
Live
PM
EM
PMM
PM/EM
EM
PMM/PM
IM
Release
Pre-release
Epic
Building
Design
Defining
Discovery
User stories
StoryBug Task
No tickets in the Epic yet
Defining Refining Ready for Dev Building Reviewing Testing Validating Sandbox Production
Incidents & Ugly Fruits
Jira Structure
Team's JIRA Projects
Team Projects Structure Examples
Team's Project
Experience
Activity
Monolith
Team's project
Activity Team project
Experience Team project
Component Project
The Team tasks on the Monolith
Monolith project
Monolith project
Component Project
Flare Project
HUB Project
The Team tasks on other Components
Karma Project
Billing Project
Scrum Board
Epic Board
Readiness Board
Dashboard Project
To follow the progress of the tickets in the Sprint
To follow the preparation of the tickets before the start of the Sprint
To follow the progress of the Epics.
Docs Project
Demo Project
Customer & Market Discovery
Accountability -> PMM Goal -> To thouroughly understand the needs, preferences, and behaviors of potential users and the market environment in which the product will operate. This will increase the chances of success of the product.
Customer & Market Discovery - Overview & Demo
Product Discovery
Accountability -> PMGoal -> Ensure that the Development Team builds the right product that addresses real user needs and market demands effectively.
Product Discovery - Overview
Customer & Market Discovery
Accountability -> PMM Goal -> To thouroughly understand the needs, preferences, and behaviors of potential users and the market environment in which the product will operate. This will increase the chances of success of the product.
Customer & Market Discovery - Overview & Demo
Definition of Done
- All conditions, or acceptance criteria, of product delivery, are met by an end-user, customer, admin, and/or consuming system in a production environment.
- No open defects
- Packages deployed into the PreMerge environment
- Non Regression tests passed
- Integration tests passed
- Performance & load testing complete
- Nightly regression tests passed
- Relevant security tests passed
- Automated checks passed
- Scripts reviewed by DBAs
- Code quality checked
- Peer code review done
- Security Application Review performed
SSDLC
Mangopay Academy
Created on April 24, 2024
Start designing with a free template
Discover more than 1500 professional designs like these:
View
Dynamic Visual Presentation
View
Corporate Christmas Presentation
View
Customer Service Manual
View
Business Results Presentation
View
Meeting Plan Presentation
View
Business vision deck
View
Economic Presentation
Explore all templates
Transcript
End-to-End Delivery Lifecycle
Start
SSDLC
Defined by conducting interviews with different Teams of the Product & Engineering Department.
Next
Training content
JIRA
SSDLC Phases
Play
Play
Next
Click on the first phase to get started.
The SSDLC Phases & Accountability
Customer & Market Discovery
Product Discovery
Feature Design
Release & Launch
Live
Build
Deploy
PMM
EM
EM
PMM/PM
IM
PM/EM
PM
Click on each and to learn about each step.
Customer & Market Discovery
Product Discovery
Feature Design
Build
Release & Launch
Deploy
Live
- Market Research:
to understand the market landscape (trends, competitors and potential demand for the product)- Customer Identification:
identifying target customer segments who are likely to benefit from the product or solution.- Needs Assessment:
to understand the potential customers needs, pain points and preferences (through surveys, interviews....)PM
PM/EM
IM
EM
PMO
PMM
PMM
Determine if the idea fits in an existing Squad scope or if it’s wider:- Existing squad scope => the Squad Product Manager (PM) will handle its prioritization and later steps.
- Wider => the Product Marketing Manager (PMM) will handle the Prioritization step to determine the feasibility and priority.
- Value Proposition:
defining the unique value proposition of the product, highlighting how it will solve customer problems.By focusing on these activities, the Customer and Market Discovery phase aims to ensure that the product is not only technically feasible but also commercially viable and aligned with market needs. This helps to reduce the risk of product failure before significant resources are invested in development.
Outcome
Back
Next
Customer & Market Discovery - JIRA Demo
Click on the video to watch a demo of the phase on JIRA.
Jira structure
Jira workflows vs SSDLC
Jira issue types
Status
Epic
Defining
User Story
No tickets in the Epic yet
Next
Back
Congrats! You've completed the first phase. Now click on the Product Discovery phase.
The SSDLC Phases & Accountability
Customer & Market Discovery
Product Discovery
Feature Design
Release & Launch
Live
Build
Deploy
PMM
EM
EM
PMM/PM
IM
PM/EM
PM
Click on each and the numbers to learn about each step.
Customer & Market Discovery
Product Discovery
Feature Design
Build
Release & Launch
Deploy
Live
- Assessing Market and Competitive Landscape:
to define the market size and business value for the idea.- Identifying User Needs:
to understand the target audience and their pain points, preferences, and behaviors.PM
PM/EM
IM
EM
PMO
PMM
PM
PMM
PMM
- Defining Product Vision and Scope:
to clarify the product’s goals, features, and functionalities, and establish a clear vision that aligns with business objectives.- Aligning Stakeholders:
to ensure that all stakeholders have a shared understanding and agreement on the product’s direction and priorities.The Product Discovery phase aims to reduce risks associated with product development by ensuring that the team builds a product that users need, want, and will use.
Do we need a third-party provider to implement it?
Do we need more thanan existing client's communication?
Yes
Outcome
No
Back
Next
Yes
Product Discovery - JIRA Demo
Click on the video to watch a demo of the phase on JIRA.
Jira structure
Jira workflows vs SSDLC
Jira issue types
Status
Discovery
Epic
User Story
No tickets in the Epic yet
Next
Back
Well done! Now it's time to delve into the Feature Design.
The SSDLC Phases & Accountability
Feature Design
Customer & Market Discovery
Product Discovery
Release & Launch
Live
Build
Deploy
PMM
EM
EM
PMM/PM
IM
PM/EM
PM
Click on each to learn about each step.
Customer & Market Discovery
Product Discovery
Feature Design
Build
Release & Launch
Deploy
Live
PM
PM/EM
IM
EM
PMO
- Product Backlog items redaction:
to define the user stories with functional details, use cases & acceptance criteria.- User Experience Design:
to create detailed UI/UX designs, wireframes, and prototypes.PM/EM
PMM
PM
PMM
- Tres-amigos:
to clarity the user stories and ensure a shared understanding of what needs to be built.Customer Communication only
No Approval Required
- Refinement:
to discuss the upcoming user stories with the Team and ensure they are complete, clear, estimated and ready to be developed.- Technical Design:
to specify the technical implementation details.- Non-Functional Requirements:
to address performance, security, databases impacts, scalability...The Feature Design phase aims to provide a clear, detailed, and validated plan for developing each feature, ensuring that it meets user needs, integrates smoothly with the system, and can be implemented efficiently and effectively by the development Team.
Outcome
Next
Back
Feature Design and Product Approval Process - JIRA Demo
Click on the video to watch a demo of the phase on JIRA.
Jira structure
Jira workflows vs SSDLC
Jira issue types
PAP
Architecture
Status
User stories
Epic
User Story
Defining
Should I create an Epic, a Story or a Task?
Back
Next
Feature Design - Defining & Refining User Stories - JIRA Demo
Click on the video to watch a demo of the phase on JIRA.
Jira structure
Jira workflows vs SSDLC
Jira issue types
Security
Status
Epic
Design
User Story
Ready for Sprint
Refining
When designing your stories, you can use these issues to follow the progress of the design: When refining your stories, you can use these issues to detail your tickets needs:
Functional Design
Technical Design
QA Sub-Task
Sub-Task
Database Impacts
Acceptance Criteria
Next
Back
Congrats! You've completed the first 3 phases. Now click on Build phase.
The SSDLC Phases & Accountability
Feature Design
Customer & Market Discovery
Product Discovery
Release & Launch
Live
Build
Deploy
PMM
EM
EM
PMM/PM
IM
PM/EM
PM
Click on each to learn about each step.
Customer & Market Discovery
Product Discovery
Feature Design
Build
Release & Launch
Deploy
Live
PM
PM/EM
EM
PMO
PMM
PM
PMM
PM/EM
EM
- Version Control:
to manage changes to the codebase.- Coding & Integration:
features implementation, unit testing and integration.IM
- Local Tests:
executed on the developers individual development environments before committing code to the shared repository.- Continuous Integration Tests:
executed automatically on a Continuous Integration server whenever code is committed to the shared repository.Customer Communication only
Buid is approved
No Approval Required
- Code Review
by another developer to ensure code quality & best practices.- Data Review:
if there are impacts on the Databases, the dedicated DBA Team reviews and validates these impacts.The Build phase goal is to transform the detailed design into a working software product, ensuring that it is correctly implemented, integrated, and ready for thorough testing.
Outcome
Next
Back
Build - JIRA Demo
Click on the video to watch a demo of the phase on JIRA.
Jira structure
Jira workflows vs SSDLC
Jira issue types
Status
Epic
Build
User Story
Building Reviewing
Back
Next
Congrats! You've completed the first 4 phases. Now click on Deploy phase.
The SSDLC Phases & Accountability
Feature Design
Customer & Market Discovery
Build
Product Discovery
Release & Launch
Live
Build
Deploy
PMM
EM
EM
PMM/PM
IM
PM/EM
PM
Click on each to learn about each step.
Customer & Market Discovery
Product Discovery
Feature Design
Build
Release & Launch
Deploy
Live
- Before Merging:
functional and behavioral validation of the feature.PM
PM/EM
IM
EM
PMO
PMM
EM
PM
PMM
PM/EM
EM
Customer Communication only
Buid is approved
No Approval Required
- Definition of Done:
checklist of criteria that a user story must meet to be considered complete and ready to be deployed.All the Development Teams comply to Mangopay Definition of Done.the Deploy phase aims to make the software available to its intended users in a stable and reliable manner.
Outcome
Back
Next
Deploy - JIRA Demo
Click on the video to watch a demo of the phase on JIRA.
Jira structure
Jira workflows vs SSDLC
Jira issue types
Definition of Done
Status
Pre-release
Epic
User Story
Production
Testing
Validating
Sandbox
Incident / Ugly Fruit
Bug
discovered during Testing/ Validating.
discovered on Production.
Next
Back
Congrats! You've completed the first 5 phases. Now, it's time for the Release & Launch.
The SSDLC Phases & Accountability
Feature Design
Customer & Market Discovery
Product Discovery
Live
Release & Launch
Build
Deploy
PMM
EM
EM
PMM/PM
IM
PM/EM
PM
Click on each to learn about each step.
Customer & Market Discovery
Product Discovery
Feature Design
Build
Release & Launch
Deploy
Live
PM
PM/EM
IM
EM
PMO
PMM/PM
PMM
EM
PM
PM/EM
PMM
EM
- Communication & Marketing:
inform stakeholders generating awareness and excitement.- User Training and Documentation:
provide necessary training for end users, support teams, and stakeholders.- Feedback Collection:
set up support structures and processes to handle user queries, issues, and feedback post-launch.Customer Communication only
Buid is approved
No Approval Required
Release is approved
The Release and Launch phase aims to achieve a successful adoption of the software by the end users.
Outcome
Next
Back
Release & Launch - JIRA Demo
Click on the video to watch a demo of the phase on JIRA.
Jira structure
Jira workflows vs SSDLC
Jira issue types
Status
Release
Epic
User Story
Back
Next
Congrats! Now, it's time to explore the Live phase.
The SSDLC Phases & Accountability
Feature Design
Customer & Market Discovery
Product Discovery
Live
Release & Launch
Build
Deploy
PMM
EM
EM
PMM/PM
IM
PM/EM
PM
Click on each number to learn about each step.
Customer & Market Discovery
Product Discovery
Feature Design
Build
Release & Launch
Deploy
Live
PM
PM/EM
IM
EM
PMO
PMM/PM
PMM
EM
PM
PMM
PM/EM
EM
IM
Customer Communication only
Buid is approved
No Approval Required
Release is approved
The Live phase aims to keep the software operational, efficient and secure while continuously meeting the needs of its users.
Outcome
Next
Back
Live - JIRA Demo
Click on the video to watch a demo of the phase on JIRA.
Jira structure
Jira workflows vs SSDLC
Jira issue types
Status
Release
Epic
User Story
Inidents or Ugly Fruits issues will be created if needed
Back
Next
Customer & Market Discovery
Product Discovery
Feature Design
Build
Release & Launch
Deploy
Live
PM
PM/EM
IM
EM
PMO
PMM/PM
PMM
EM
PM
PM/EM
PMM
EM
IM
Customer Communication only
Buid is approved
No Approval Required
Release is approved
Back
Next
You've completed all the SSDLC Phases!
The successful execution of Mangopay SSDLC requires the commitment, active participation and effective collaboration of all the Teams. The definition of Mangopay SSDLC will continue to evolve and improve.If you have improvements suggestions, please let us know to build together the SSDLC v2!
Architecture Review Process - EM
Epic
Epic Status transitions from to
When
Discovery
User Stories
Architecture Review
Automatically creates ticket in the Epic.
What happens
notifies the Architecture Team on the dedicated Slack channel.
What to do
The Architecture Review ticket needs to be filled by the EM.
Jira Structure
Team's JIRA Projects
Team Projects Structure Examples
Team's Project
Experience
Activity
Monolith
Team's project
Activity Team project
Experience Team project
Component Project
The Team tasks on the Monolith
Monolith project
Monolith project
Component Project
Flare Project
HUB Project
The Team tasks on other Components
Karma Project
Billing Project
Scrum Board
Epic Board
Readiness Board
Dashboard Project
To follow the progress of the tickets in the Sprint
To follow the preparation of the tickets before the start of the Sprint
To follow the progress of the Epics.
Docs Project
Demo Project
Customer & Market Discovery
Accountability -> PMM Goal -> To thouroughly understand the needs, preferences, and behaviors of potential users and the market environment in which the product will operate. This will increase the chances of success of the product.
Customer & Market Discovery - Overview & Demo
Epic / Story / Task / Sub-task
Epic
Level1
A large body of work that can be broken down into smaller, more manageable pieces. It often represents a significant feature or a major milestone. Scope: Epics span multiple sprints and may take weeks or months to complete. Purpose: Used to organize and track progress on large subjects or major functionalities that might sometimes require coordination across multiple teams or workstreams.
Story
Level0
A description of a specific feature or functionality from the end user's perspective.It represents a piece of work that delivers value to the user. Scope: Stories are smaller than epics and are usually completed within a single sprint. Purpose: Used to capture specific requirements and user needs in a clear, concise format that can be easily understood and implemented by the Development Team.
Task
Technical Task
An individual piece of work that needs to be done and which value might not be visible to the users.Scope: Tasks are very granular and can often be completed in a few hours to a couple of days. Purpose: Used to describe actionable items needed and might be separate from other Stories.
Level-1
Sub-Task
An individual piece of work that needs to be done to complete a Story.Sub-tasks are the smallest unit of work and are often technical in nature. Scope: Sub-tasks are very granular and can often be completed in a few hours to a couple of days. Purpose: Used to break down stories into actionable items that developers can work on.
Product Approval Process - PM
Epic
Epic Status transitions from to
When
Discovery
User Stories
Automatically creates ticket in the Epic.
PAP
What happens
notifies the involved Team on the dedicated Slack channel
What to do
The PAP contains sub-tasks that need to be filled by the PM
PAP ticket can have these sub-tasks:
Bugs, Ugly Fruits & Incidents are important, we must treat them with the good speed & attention.
Jira Issue types
- Incidents are created when there are critical issues like service outages or major disruptions affecting many clients (Production).
When it is escalated by the Incident Manager, your Team will get notified on Slack to work on the Incident. An Incident should never be discussed in private, if you need to discuss, create a channel if not already done by Incident manager ( #inc-...)Ugly Fruit Incident
Incident
Bug
- created when an issue is found in Production.
When it is escalated by the Incident Manager, your Team will get notified on Slack to work on the Ugly Fruit.An Ugly Fruit should never be discussed in private, if you need to discuss, create a channel if not already done by Incident manager ( #inc-...)- discovered during the testing / Validation phase of a feature.
They are an anomaly compared to the target behavior of the feature(i.e acceptance criteria). When the Team creates a bug in JIRA, it should always be linked to an aceptance criteria.=> sometimes, a bug can lead to add /remove/update an acceptance criteria, otherwise, it's a implementation issue.Product Discovery
Accountability -> PMGoal -> Ensure that the Development Team builds the right product that addresses real user needs and market demands effectively.
Product Discovery - Overview
Jira Issue types
OKR
Level3
Initiative
Level2
Epic
Level1
Story
Task
Level0
Bug
Definition of Done
Technical Design
Incident
Technical Task
Functional Design
Ugly Fruit Incident
Level-1
Sub-Task
QA Sub-Task
Acceptance Criteria
Database Impacts
JIRA
Deploy
Accountability -> EMGoal -> To ensure that the software is successfully transitioned from Development to a live environment and available to its intended users.
Deploy - Overview
Product Discovery
Accountability -> PMGoal -> Ensure that the Development Team builds the right product that addresses real user needs and market demands effectively.
Product Discovery - Overview
Customer & Market Discovery
Live
Feature Design
Product Discovery
Release & Launch
Build
Deploy
Incident Manager (IM)
Product Marketing Manager (PMM) & Product Manager (PM)
Engineering Manager (EM)
Engineering Manager (EM)
Product Marketing Manager (PMM)
Product Manager (PM) & Engineering Manager (EM)
Product Manager (PM)
Product Discovery
Accountability -> PMGoal -> Ensure that the Development Team builds the right product that addresses real user needs and market demands effectively.
Product Discovery - Overview
Deploy
Accountability -> EMGoal -> To ensure that the software is successfully transitioned from Development to a live environment and available to its intended users.
Deploy - Overview
Customer & Market Discovery
Accountability -> PMM Goal -> To thouroughly understand the needs, preferences, and behaviors of potential users and the market environment in which the product will operate. This will increase the chances of success of the product.
Customer & Market Discovery - Overview & Demo
Feature Design
Accountability -> PM/EMGoal -> To create well-defined plans and Product Backlog items for the features & functionalities that the software will include. This step ensures that the Development Team has a good understanding of the features to build, reducing the risk of misunderstandings or scope changes later.
Feature Design - Overview
Customer & Market Discovery
Accountability -> PMM Goal -> To thouroughly understand the needs, preferences, and behaviors of potential users and the market environment in which the product will operate. This will increase the chances of success of the product.
Customer & Market Discovery - Overview & Demo
Feature Design
Accountability -> PM/EMGoal -> To create well-defined plans and Product Backlog items for the features & functionalities that the software will include. This step ensures that the Development Team has a good understanding of the features to build, reducing the risk of misunderstandings or scope changes later.
Feature Design - Overview
Epic / Story / Task / Sub-task
Epic
Level1
A large body of work that can be broken down into smaller, more manageable pieces. It often represents a significant feature or a major milestone. Scope: Epics span multiple sprints and may take weeks or months to complete. Purpose: Used to organize and track progress on large subjects or major functionalities that might sometimes require coordination across multiple teams or workstreams.
Story
Level0
A description of a specific feature or functionality from the end user's perspective.It represents a piece of work that delivers value to the user. Scope: Stories are smaller than epics and are usually completed within a single sprint. Purpose: Used to capture specific requirements and user needs in a clear, concise format that can be easily understood and implemented by the Development Team.
Task
Technical Task
An individual piece of work that needs to be done and which value might not be visible to the users.Scope: Tasks are very granular and can often be completed in a few hours to a couple of days. Purpose: Used to describe actionable items needed and might be separate from other Stories.
Level-1
Sub-Task
An individual piece of work that needs to be done to complete a Story.Sub-tasks are the smallest unit of work and are often technical in nature. Scope: Sub-tasks are very granular and can often be completed in a few hours to a couple of days. Purpose: Used to break down stories into actionable items that developers can work on.
Jira Issue types
OKR
Level3
Initiative
Level2
Epic
Level1
Story
Task
Level0
Bug
Definition of Done
Technical Design
Incident
Technical Task
Functional Design
Ugly Fruit Incident
Level-1
Sub-Task
QA Sub-Task
Acceptance Criteria
Database Impacts
Build
Accountability -> EMGoal -> To ensure that the software is developed according to the design specifications and is ready for more comprehensive testing and validation in the coming phase.
Building
Build - Overview
Build
Accountability -> EMGoal -> To ensure that the software is developed according to the design specifications and is ready for more comprehensive testing and validation in the coming phase.
Building
Build - Overview
Feature Design
Accountability -> PM/EMGoal -> To create well-defined plans and Product Backlog items for the features & functionalities that the software will include. This step ensures that the Development Team has a good understanding of the features to build, reducing the risk of misunderstandings or scope changes later.
Feature Design - Overview
Jira Structure
Team's JIRA Projects
Team Projects Structure Examples
Team's Project
Experience
Activity
Monolith
Team's project
Activity Team project
Experience Team project
Component Project
The Team tasks on the Monolith
Monolith project
Monolith project
Component Project
Flare Project
HUB Project
The Team tasks on other Components
Karma Project
Billing Project
Scrum Board
Epic Board
Readiness Board
Dashboard Project
To follow the progress of the tickets in the Sprint
To follow the preparation of the tickets before the start of the Sprint
To follow the progress of the Epics.
Docs Project
Demo Project
Jira Structure
Team's JIRA Projects
Team Projects Structure Examples
Team's Project
Experience
Activity
Monolith
Team's project
Activity Team project
Experience Team project
Component Project
The Team tasks on the Monolith
Monolith project
Monolith project
Component Project
Flare Project
HUB Project
The Team tasks on other Components
Karma Project
Billing Project
Scrum Board
Epic Board
Readiness Board
Dashboard Project
To follow the progress of the tickets in the Sprint
To follow the preparation of the tickets before the start of the Sprint
To follow the progress of the Epics.
Docs Project
Demo Project
Architecture Review Process - EM
Epic
Epic Status transitions from to
When
Discovery
User Stories
Architecture Review
Automatically creates ticket in the Epic.
What happens
notifies the Architecture Team on the dedicated Slack channel.
What to do
The Architecture Review ticket needs to be filled by the EM.
Jira Issue types
OKR
Level3
Initiative
Level2
Epic
Level1
Story
Task
Level0
Bug
Definition of Done
Technical Design
Incident
Technical Task
Functional Design
Ugly Fruit Incident
Level-1
Sub-Task
QA Sub-Task
Acceptance Criteria
Database Impacts
Deploy
Accountability -> EMGoal -> To ensure that the software is successfully transitioned from Development to a live environment and available to its intended users.
Deploy - Overview
Build
Accountability -> EMGoal -> To ensure that the software is developed according to the design specifications and is ready for more comprehensive testing and validation in the coming phase.
Building
Build - Overview
Jira Issue types
OKR
Level3
Initiative
Level2
Epic
Level1
Story
Task
Level0
Bug
Definition of Done
Technical Design
Incident
Technical Task
Functional Design
Ugly Fruit Incident
Level-1
Sub-Task
QA Sub-Task
Acceptance Criteria
Database Impacts
Customer & Market Discovery
Accountability -> PMM Goal -> To thouroughly understand the needs, preferences, and behaviors of potential users and the market environment in which the product will operate. This will increase the chances of success of the product.
Customer & Market Discovery - Overview & Demo
Release & Launch
Accountability -> PMM/PMGoal -> To ensure that the software is successfuly introduced to the market and the users have the necessary support in its adoption.
Release & Launch - Overview
Release & Launch
Accountability -> PMM/PMGoal -> To ensure that the software is successfuly introduced to the market and the users have the necessary support in its adoption.
Release & Launch - Overview
Customer & Market Discovery
Accountability -> PMM Goal -> To thouroughly understand the needs, preferences, and behaviors of potential users and the market environment in which the product will operate. This will increase the chances of success of the product.
Customer & Market Discovery - Overview & Demo
Definition of Done in JIRA
Jira Issue type
Definition of Done
When
A Release (version) is created in JIRA.
What happens
Automatically creates in the Release a ticket.
The checklist in the ticket needs to be reviewed and all steps validated before Deploying.
What to do
Jira Structure
Team's JIRA Projects
Team Projects Structure Examples
Team's Project
Experience
Activity
Monolith
Team's project
Activity Team project
Experience Team project
Component Project
The Team tasks on the Monolith
Monolith project
Monolith project
Component Project
Flare Project
HUB Project
The Team tasks on other Components
Karma Project
Billing Project
Scrum Board
Epic Board
Readiness Board
Dashboard Project
To follow the progress of the tickets in the Sprint
To follow the preparation of the tickets before the start of the Sprint
To follow the progress of the Epics.
Docs Project
Demo Project
Jira Workflow VS SSDLC
Customer & Market Discovery
Product Discovery
Release & Launch
SSDLC Phase
Feature Design
Build
Deploy
Live
PM
EM
PMM
PM/EM
EM
PMM/PM
IM
Release
Pre-release
Epic
Building
Design
Defining
Discovery
User stories
StoryBug Task
No tickets in the Epic yet
Defining Refining Ready for Dev Building Reviewing Testing Validating Sandbox Production
Incidents & Ugly Fruits
Feature Design
Accountability -> PM/EMGoal -> To create well-defined plans and Product Backlog items for the features and functionalities that the software will include. This step ensures that the Development Team has a good understanding of the features to build, reducing the risk of misunderstandings or scope changes later.
Feature Design - Overview
Jira Structure
Team's JIRA Projects
Team Projects Structure Examples
Team's Project
Experience
Activity
Monolith
Team's project
Activity Team project
Experience Team project
Component Project
The Team tasks on the Monolith
Monolith project
Monolith project
Component Project
Flare Project
HUB Project
The Team tasks on other Components
Karma Project
Billing Project
Scrum Board
Epic Board
Readiness Board
Dashboard Project
To follow the progress of the tickets in the Sprint
To follow the preparation of the tickets before the start of the Sprint
To follow the progress of the Epics.
Docs Project
Demo Project
Jira Workflow VS SSDLC
Customer & Market Discovery
Product Discovery
Release & Launch
SSDLC Phase
Feature Design
Build
Deploy
Live
PM
EM
PMM
PM/EM
EM
PMM/PM
IM
Release
Pre-release
Epic
Building
Design
Defining
Discovery
User stories
StoryBug Task
No tickets in the Epic yet
Defining Refining Ready for Dev Building Reviewing Testing Validating Sandbox Production
Incidents & Ugly Fruits
Feature Design
Accountability -> PM/EMGoal -> To create well-defined plans and Product Backlog items for the features & functionalities that the software will include. This step ensures that the Development Team has a good understanding of the features to build, reducing the risk of misunderstandings or scope changes later.
Feature Design - Overview
Release & Launch
Accountability -> PMM/PMGoal -> To ensure that the software is successfuly introduced to the market and the users have the necessary support in its adoption.
Release & Launch - Overview
Customer & Market Discovery
Accountability -> PMM Goal -> To thouroughly understand the needs, preferences, and behaviors of potential users and the market environment in which the product will operate. This will increase the chances of success of the product.
Customer & Market Discovery - Overview & Demo
Live
Accountability -> IMGoal -> To ensure that the software remains functional, secure and relevant over time, providing ongoing value to the users.
Live
Live - Overview
Product Discovery
Accountability -> PMGoal -> Ensure that the Development Team builds the right product that addresses real user needs and market demands effectively.
Product Discovery - Overview
Customer & Market Discovery
Accountability -> PMM Goal -> To thouroughly understand the needs, preferences, and behaviors of potential users and the market environment in which the product will operate. This will increase the chances of success of the product.
Customer & Market Discovery - Overview & Demo
Build
Accountability -> EMGoal -> To ensure that the software is developed according to the design specifications and is ready for more comprehensive testing and validation in the coming phase.
Building
Build - Overview
Build
Accountability -> EMGoal -> To ensure that the software is developed according to the design specifications and is ready for more comprehensive testing and validation in the coming phase.
Building
Build - Overview
Build
Accountability -> EMGoal -> To ensure that the software is developed according to the design specifications and is ready for more comprehensive testing and validation in the coming phase.
Building
Build - Overview
Customer & Market Discovery
Accountability: PMM
Get Started
Build
Accountability -> EMGoal -> To ensure that the software is developed according to the design specifications and is ready for more comprehensive testing and validation in the coming phase.
Building
Build - Overview
Jira Issue types
OKR
Level3
Initiative
Level2
Epic
Level1
Story
Task
Level0
Bug
Definition of Done
Technical Design
Incident
Technical Task
Functional Design
Ugly Fruit Incident
Level-1
Sub-Task
QA Sub-Task
Acceptance Criteria
Database Impacts
Customer & Market Discovery
Accountability: PMM
Get Started
Bugs, Ugly Fruits & Incidents are important, we must treat them with the good speed & attention.
Jira Issue types
- Incidents are created when there are critical issues like service outages or major disruptions affecting many clients (Production).
When it is escalated by the Incident Manager, your Team will get notified on Slack to work on the Incident. An Incident should never be discussed in private, if you need to discuss, create a channel if not already done by Incident manager ( #inc-...)Incident
Ugly Fruit Incident
Bug
- created when an issue is found in Production.
When it is escalated by the Incident Manager, your Team will get notified on Slack to work on the Ugly Fruit.An Ugly Fruit should never be discussed in private, if you need to discuss, create a channel if not already done by Incident manager ( #inc-...)- discovered during the testing / Validation phase of a feature.
They are an anomaly compared to the target behavior of the feature(i.e acceptance criteria). When the Team creates a bug in JIRA, it should always be linked to an aceptance criteria.=> sometimes, a bug can lead to add /remove/update an acceptance criteria, otherwise, it's a implementation issue.Deploy
Accountability -> EMGoal -> To ensure that the software is successfully transitioned from Development to a live environment and available to its intended users.
Deploy - Overview
Product Discovery
Accountability -> PMGoal -> Ensure that the Development Team builds the right product that addresses real user needs and market demands effectively.
Product Discovery - Overview
Live
Accountability -> IMGoal -> To ensure that the software remains functional, secure and relevant over time, providing ongoing value to the users.
Live
Live - Overview
Deploy
Accountability -> EMGoal -> To ensure that the software is successfully transitioned from Development to a live environment and available to its intended users.
Deploy - Overview
Jira Workflow VS SSDLC
Customer & Market Discovery
Product Discovery
Release & Launch
SSDLC Phase
Feature Design
Build
Deploy
Live
PM
EM
PMM
PM/EM
EM
PMM/PM
IM
Release
Pre-release
Epic
Building
Design
Defining
Discovery
User stories
StoryBug Task
No tickets in the Epic yet
Defining Refining Ready for Dev Building Reviewing Testing Validating Sandbox Production
Incidents & Ugly Fruits
Deploy
Accountability -> EMGoal -> To ensure that the software is successfully transitioned from Development to a live environment and available to its intended users.
Deploy - Overview
Product Discovery
Accountability -> PMGoal -> Ensure that the Development Team builds the right product that addresses real user needs and market demands effectively.
Product Discovery - Overview
Build
Accountability -> EMGoal -> To ensure that the software is developed according to the design specifications and is ready for more comprehensive testing and validation in the coming phase.
Building
Build - Overview
Customer & Market Discovery
Accountability -> PMM Goal -> To thouroughly understand the needs, preferences, and behaviors of potential users and the market environment in which the product will operate. This will increase the chances of success of the product.
Customer & Market Discovery - Overview & Demo
Customer & Market Discovery
Accountability -> PMM Goal -> To thouroughly understand the needs, preferences, and behaviors of potential users and the market environment in which the product will operate. This will increase the chances of success of the product.
Customer & Market Discovery - Overview & Demo
Customer & Market Discovery
Accountability -> PMM Goal -> To thouroughly understand the needs, preferences, and behaviors of potential users and the market environment in which the product will operate. This will increase the chances of success of the product.
Customer & Market Discovery - Overview & Demo
Deploy
Accountability -> EMGoal -> To ensure that the software is successfully transitioned from Development to a live environment and available to its intended users.
Deploy - Overview
No deployment without securiy checks pentest for sensitive features
Security
Security Approval Process - EM
Epic
Epic Status transitions from to
When
User Stories
Design
Automatically creates ticket in the Epic.
Security Review
What happens
notifies the Security Team on the dedicated Slack channel.
What to do
The Security Review ticket needs to be filled by the EM.
Security Review ticket can have:
- Threat model
Contains issues identified by threat model
In addition to a Security Review checklist.Bugs, Ugly Fruits & Incidents are important, we must treat them with the good speed & attention.
Jira Issue types
- Incidents are created when there are critical issues like service outages or major disruptions affecting many clients (Production).
When it is escalated by the Incident Manager, your Team will get notified on Slack to work on the Incident. An Incident should never be discussed in private, if you need to discuss, create a channel if not already done by Incident manager ( #inc-...)Incident
Ugly Fruit Incident
Bug
- created when an issue is found in Production.
When it is escalated by the Incident Manager, your Team will get notified on Slack to work on the Ugly Fruit.An Ugly Fruit should never be discussed in private, if you need to discuss, create a channel if not already done by Incident manager ( #inc-...)- discovered during the testing / Validation phase of a feature.
They are an anomaly compared to the target behavior of the feature(i.e acceptance criteria). When the Team creates a bug in JIRA, it should always be linked to an aceptance criteria.=> sometimes, a bug can lead to add /remove/update an acceptance criteria, otherwise, it's a implementation issue.Product Discovery
Accountability -> PMGoal -> Ensure that the Development Team builds the right product that addresses real user needs and market demands effectively.
Product Discovery - Overview
Live
Accountability -> IMGoal -> To ensure that the software remains functional, secure and relevant over time, providing ongoing value to the users.
Live
Live - Overview
Feature Design
Accountability -> PM/EMGoal -> To create well-defined plans and Product Backlog items for the features and functionalities that the software will include. This step ensures that the Development Team has a good understanding of the features to build, reducing the risk of misunderstandings or scope changes later.
Feature Design - Overview
Jira Issue types
OKR
Level3
Initiative
Level2
Epic
Level1
Story
Task
Level0
Bug
Definition of Done
Technical Design
Incident
Technical Task
Functional Design
Ugly Fruit Incident
Level-1
Sub-Task
QA Sub-Task
Acceptance Criteria
Database Impacts
Live
Accountability -> IMGoal -> To ensure that the software remains functional, secure and relevant over time, providing ongoing value to the users.
Live
Live - Overview
Customer & Market Discovery
Accountability -> PMM Goal -> To thouroughly understand the needs, preferences, and behaviors of potential users and the market environment in which the product will operate. This will increase the chances of success of the product.
Customer & Market Discovery - Overview & Demo
Customer & Market Discovery
Accountability -> PMM Goal -> To thouroughly understand the needs, preferences, and behaviors of potential users and the market environment in which the product will operate. This will increase the chances of success of the product.
Customer & Market Discovery - Overview & Demo
Jira Workflow VS SSDLC
Customer & Market Discovery
Product Discovery
Release & Launch
SSDLC Phase
Feature Design
Build
Deploy
Live
PM
EM
PMM
PM/EM
EM
PMM/PM
IM
Release
Pre-release
Epic
Building
Design
Defining
Discovery
User stories
StoryBug Task
No tickets in the Epic yet
Defining Refining Ready for Dev Building Reviewing Testing Validating Sandbox Production
Incidents & Ugly Fruits
Jira Workflow VS SSDLC
Customer & Market Discovery
Product Discovery
Release & Launch
SSDLC Phase
Feature Design
Build
Deploy
Live
PM
EM
PMM
PM/EM
EM
PMM/PM
IM
Release
Pre-release
Epic
Building
Design
Defining
Discovery
User stories
StoryBug Task
No tickets in the Epic yet
Defining Refining Ready for Dev Building Reviewing Testing Validating Sandbox Production
Incidents & Ugly Fruits
Jira Structure
Team's JIRA Projects
Team Projects Structure Examples
Team's Project
Experience
Activity
Monolith
Team's project
Activity Team project
Experience Team project
Component Project
The Team tasks on the Monolith
Monolith project
Monolith project
Component Project
Flare Project
HUB Project
The Team tasks on other Components
Karma Project
Billing Project
Scrum Board
Epic Board
Readiness Board
Dashboard Project
To follow the progress of the tickets in the Sprint
To follow the preparation of the tickets before the start of the Sprint
To follow the progress of the Epics.
Docs Project
Demo Project
Jira Workflow VS SSDLC
Customer & Market Discovery
Product Discovery
Release & Launch
SSDLC Phase
Feature Design
Build
Deploy
Live
PM
EM
PMM
PM/EM
EM
PMM/PM
IM
Release
Pre-release
Epic
Building
Design
Defining
Discovery
User stories
StoryBug Task
No tickets in the Epic yet
Defining Refining Ready for Dev Building Reviewing Testing Validating Sandbox Production
Incidents & Ugly Fruits
Customer & Market Discovery
Accountability -> PMM Goal -> To thouroughly understand the needs, preferences, and behaviors of potential users and the market environment in which the product will operate. This will increase the chances of success of the product.
Customer & Market Discovery - Overview & Demo
Product Discovery
Accountability -> PMGoal -> Ensure that the Development Team builds the right product that addresses real user needs and market demands effectively.
Product Discovery - Overview
Product Discovery
Accountability -> PMGoal -> Ensure that the Development Team builds the right product that addresses real user needs and market demands effectively.
Product Discovery - Overview
Customer & Market Discovery
Accountability: PMM
Get Started
Release & Launch
Accountability -> PMM/PMGoal -> To ensure that the software is successfuly introduced to the market and the users have the necessary support in its adoption.
Release & Launch - Overview
Definition of Ready
- The ticket is attached to an Epic
- Acceptance criteria are established for the story
- The Sprint is indicated
- The ticket is understood and estimated
- Security Design Review performed
- (when required) Architectural impact identified
- (when required) Tre-Amigos:
Technicals aspects added (Endpoints / payloads - ux/ui)Epic / Story / Task / Sub-task
Epic
Level1
A large body of work that can be broken down into smaller, more manageable pieces. It often represents a significant feature or a major milestone. Scope: Epics span multiple sprints and may take weeks or months to complete. Purpose: Used to organize and track progress on large subjects or major functionalities that might sometimes require coordination across multiple teams or workstreams.
Story
Level0
A description of a specific feature or functionality from the end user's perspective.It represents a piece of work that delivers value to the user. Scope: Stories are smaller than epics and are usually completed within a single sprint. Purpose: Used to capture specific requirements and user needs in a clear, concise format that can be easily understood and implemented by the Development Team.
Task
Technical Task
An individual piece of work that needs to be done and which value might not be visible to the users.Scope: Tasks are very granular and can often be completed in a few hours to a couple of days. Purpose: Used to describe actionable items needed and might be separate from other Stories.
Level-1
Sub-Task
An individual piece of work that needs to be done to complete a Story.Sub-tasks are the smallest unit of work and are often technical in nature. Scope: Sub-tasks are very granular and can often be completed in a few hours to a couple of days. Purpose: Used to break down stories into actionable items that developers can work on.
Build
Accountability -> EMGoal -> To ensure that the software is developed according to the design specifications and is ready for more comprehensive testing and validation in the coming phase.
Building
Build - Overview
Product Discovery
Accountability -> PMGoal -> Ensure that the Development Team builds the right product that addresses real user needs and market demands effectively.
Product Discovery - Overview
Jira Structure
Team's JIRA Projects
Team Projects Structure Examples
Team's Project
Experience
Activity
Monolith
Team's project
Activity Team project
Experience Team project
Component Project
The Team tasks on the Monolith
Monolith project
Monolith project
Component Project
Flare Project
HUB Project
The Team tasks on other Components
Karma Project
Billing Project
Scrum Board
Epic Board
Readiness Board
Dashboard Project
To follow the progress of the tickets in the Sprint
To follow the preparation of the tickets before the start of the Sprint
To follow the progress of the Epics.
Docs Project
Demo Project
Product Approval Process - PM
Epic
Epic Status transitions from to
When
Discovery
User Stories
Automatically creates ticket in the Epic.
PAP
What happens
notifies the involved Team on the dedicated Slack channel
What to do
The PAP contains sub-tasks that need to be filled by the PM
PAP ticket can have these sub-tasks:
Release & Launch
Accountability -> PMOGoal -> To ensure that the software is successfuly introduced to the market and the users have the necessary support in its adoption.
Release & Launch - Overview
Release & Launch
Accountability -> PMOGoal -> To ensure that the software is successfuly introduced to the market and the users have the necessary support in its adoption.
Release & Launch - Overview
Jira Issue types
OKR
Level3
Initiative
Level2
Epic
Level1
Story
Task
Level0
Bug
Definition of Done
Technical Design
Incident
Technical Task
Functional Design
Ugly Fruit Incident
Level-1
Sub-Task
QA Sub-Task
Acceptance Criteria
Database Impacts
Build
Accountability -> EMGoal -> To ensure that the software is developed according to the design specifications and is ready for more comprehensive testing and validation in the coming phase.
Building
Build - Overview
Product Discovery
Accountability -> PMGoal -> Ensure that the Development Team builds the right product that addresses real user needs and market demands effectively.
Product Discovery - Overview
Feature Design
Accountability -> PM/EMGoal -> To create well-defined plans and Product Backlog items for the features & functionalities that the software will include. This step ensures that the Development Team has a good understanding of the features to build, reducing the risk of misunderstandings or scope changes later.
Feature Design - Overview
Product Discovery
Accountability -> PMGoal -> Ensure that the Development Team builds the right product that addresses real user needs and market demands effectively.
Product Discovery - Overview
Deploy
Accountability -> EMGoal -> To ensure that the software is successfully transitioned from Development to a live environment and available to its intended users.
Deploy - Overview
Jira Workflow VS SSDLC
Customer & Market Discovery
Product Discovery
Release & Launch
SSDLC Phase
Feature Design
Build
Deploy
Live
PM
EM
PMM
PM/EM
EM
PMM/PM
IM
Release
Pre-release
Epic
Building
Design
Defining
Discovery
User stories
StoryBug Task
No tickets in the Epic yet
Defining Refining Ready for Dev Building Reviewing Testing Validating Sandbox Production
Incidents & Ugly Fruits
Customer & Market Discovery
Accountability -> PMM Goal -> To thouroughly understand the needs, preferences, and behaviors of potential users and the market environment in which the product will operate. This will increase the chances of success of the product.
Customer & Market Discovery - Overview & Demo
Customer & Market Discovery
Accountability: PMM
Get Started
Product Discovery
Accountability -> PMGoal -> Ensure that the Development Team builds the right product that addresses real user needs and market demands effectively.
Product Discovery - Overview
Product Approval Process - PM
Epic
Epic Status transitions from to
When
Discovery
User Stories
Automatically creates ticket in the Epic.
PAP
What happens
notifies the involved Team on the dedicated Slack channel
What to do
The PAP contains sub-tasks that need to be filled by the PM
PAP ticket can have these sub-tasks:
Jira Issue types
OKR
Level3
Initiative
Level2
Epic
Level1
Story
Task
Level0
Bug
Definition of Done
Technical Design
Incident
Technical Task
Functional Design
Ugly Fruit Incident
Level-1
Sub-Task
QA Sub-Task
Acceptance Criteria
Database Impacts
Jira Workflow VS SSDLC
Customer & Market Discovery
Product Discovery
Release & Launch
SSDLC Phase
Feature Design
Build
Deploy
Live
PM
EM
PMM
PM/EM
EM
PMM/PM
IM
Release
Pre-release
Epic
Building
Design
Defining
Discovery
User stories
StoryBug Task
No tickets in the Epic yet
Defining Refining Ready for Dev Building Reviewing Testing Validating Sandbox Production
Incidents & Ugly Fruits
Jira Structure
Team's JIRA Projects
Team Projects Structure Examples
Team's Project
Experience
Activity
Monolith
Team's project
Activity Team project
Experience Team project
Component Project
The Team tasks on the Monolith
Monolith project
Monolith project
Component Project
Flare Project
HUB Project
The Team tasks on other Components
Karma Project
Billing Project
Scrum Board
Epic Board
Readiness Board
Dashboard Project
To follow the progress of the tickets in the Sprint
To follow the preparation of the tickets before the start of the Sprint
To follow the progress of the Epics.
Docs Project
Demo Project
Customer & Market Discovery
Accountability -> PMM Goal -> To thouroughly understand the needs, preferences, and behaviors of potential users and the market environment in which the product will operate. This will increase the chances of success of the product.
Customer & Market Discovery - Overview & Demo
Product Discovery
Accountability -> PMGoal -> Ensure that the Development Team builds the right product that addresses real user needs and market demands effectively.
Product Discovery - Overview
Customer & Market Discovery
Accountability -> PMM Goal -> To thouroughly understand the needs, preferences, and behaviors of potential users and the market environment in which the product will operate. This will increase the chances of success of the product.
Customer & Market Discovery - Overview & Demo
Definition of Done