Scrum Artifacts
- Product Backlog
- Sprint Backlog
- Increment
Product and Sprint backlog - what to do?
Increment -values which providing transparency and opportunity for Inspection and Adaptation
- Inspection
- Adaptation
- Transparency
Complex environment -Transparency enables collaboration and creativity
- Product Backlog - Product Goal
- Sprint Backlog -Sprint Goal
- Increment -Definition of Done
Scrum Artifacts should Maximize the transparency. Scrum master responsibility to make transparency artifacts by scrum team
Define Product?
A product is a vehicle to deliver value
To Achieve Product vison
- Clear Boundary
- Known Stakeholder
- Well defined users or customers
Define Product Goal?
A future state of the product which can serve as a target for the scrum team to plan against
Product Goal is in Product Backlog
Summary:
- Only one Product Backlog per product
- Product backlog items contain a description -Epics and user stories
- Higher ordered product backlog items - Clear and more detailed
Product Owner -Orders Product backlog depends on Size,Risk,Value and Dependencies
ROI -Business value/size
Dependencies of user stories and Technical availability(Mob Dev is not there) also taken in to the consideration and do product backlog order
Developer is responsible for Sizing(estimate)and Product owner influence the developers
Developer is estimate the Product backlog
Increment:
Definition of Done
A formal description of the state of the increment when it meets quality measures required for the product
Who Defines Definition of Done?
Organization
Scrum team
When Defines Definition of done?
Sprint retrospective
Continuous
Technical Debt
- Consequence of poor software development practices
- Might leas to code decay and Architecture deterioration
- Scrum can manage it
- It is not necessarily bad
Don't need to release at the end of every sprint
The Sprint is not gate-Release might be performed during a sprint
No comments:
Post a Comment