Product Management Flashcards
Ceremonies:
Refinement
The Refinement process exists to prepare user stories for development. Business and IT work together to find a solution that finds the ideal solution from both a functional and technical perspective
Ceremonies: Planning
Planning is an opportunity for the Team to dig into the details of what they will do in the coming weeks to have a successful iteration. A well-developed plan ensures that everyone in the team knows how they will contribute to the team’s success
Ceremonies: Review
The Review is an opportunity for the Team to share the result of their sprint with Product Stakeholders. The Review encourages accountability, transparency and facilitates frequent feedback
Ceremonies: Retrospective
The Retrospective is an opportunity for the Team to improve the way in which it has been working. Learning from success and failure is a critical part of Agile Product Development
Ceremonies: Standup
The Stand Up is an opportunity for the Team to align its’ efforts on a daily basis. The Stand Up creates transparency on the sprint status and facilitates alignment across team members
Jira Workflow - Phases, Status, Detials
Engineering ready
Status: Ready for Dev or Reopened
Details: Refinement done, tasked out and ready for development
Definition of Ready is met
Jira Workflow - Phases, Status, Detials
Development
In Progress - Implementaiton in progress
In Review - Development - finished, peer review
Jira Workflow - Phases, Status, Detials
Ready to test
Status: Integration
Details: Development finished and waiting for development in SIT environment environment (Golden Build)
Jira Workflow - Phases, Status, Detials
Testing
Status: In test
Detials: Currently in testing by the QA team in SIT environment (Golden Build) - technical sign off
Jira Workflow - Phases, Status, Detials
Ready for PO Review
Status: Resolved
Details: Technically signed off and ready for vertification from PO
Jira Workflow - Phases, Status, Detials
PO Review
Status: Deployment
Details: To be reviewed and signed off by PO, business partners or other stakeholders if necessary
UAT/Busines Sign off
Jira Workflow - Phases, Status, Detials
Development
Status: In verificaiton
Details: Business sign off successful, waiting for deployment to production
Jira Workflow - Phases, Status, Detials
Done
Status: Closed
Details: Deployed to production, validation and handed over to business/ops
Definition of Done is met
Classifying Defects
Blocker
Defect causes critical loss of business functionality or a complete loss of service has occurred or has a huge financial impact. All countries and large number of customers are affected.
Example Cart not working, catalogue not loading, orders do not work
Classifying Defects
Critical
A highly severe defect that can collapse the system. However, certain parts of the system remain functional. Or a severe defect which affects only small number of customers in multiple countries
Example Cart not working with 300 line items or more, workaround warn customer when he has to many line items
Classifying Defects
Major
Defect causes some undesirable behavior, but hte system is still funcitonal
Classifying Defects
Minor
The defect does not affect functionality or data. It might impact productivity or efficiency (more clicks). It’s merely an inconvenience.
Classifying Defects
Urgency: High
There is no workaround available and/or the damage is rapidly increasing over time. Blocker - P1 Critial - P2(P1) Major - P2 Minor - P3
Classifying Defects
Medium
There is no workaround available but the damage is not high because the feature is not frequently used Blocker - P2(P1) Critical - P2 Major - P3 Minor - P4
Classifying Defects
Low
There is a workaround available and there is no time pressure Blocker - P2 Critical - P3 Major - P4 Minor - P4