The purpose of writing this blog is to provide the synopsis of the whole.
Scrum is an incremental delivery approach that makes it possible to get the highest priority task out of the door first and fast. It eliminates the features that are not important or are redundant and hence saving cost and resources.
- Product Owner: Responsible for the product and business needs. Is the voice of the customer.
- Scrum Master: Servant-leader responsible for facilitating the process and for removing the impediments that hinder the team from focusing on development.
- Development Team: Cross-functional, self-organized team responsible for delivering shippable product increment.
- Stakeholders: Any person or team who has a vested interest in the product.
Stakeholder Meeting: A meeting held to discuss and formulate the business case between the stakeholders, customers and product owner. The result is the product backlog.
- Sprint Planning Meeting: A meeting of team to determine what will be done in the next sprint. Outcome is the Sprint backlog.
- Daily Scrum and Scrum Execution: A 15 min daily stand up meeting to inform the team of the status, progress and roadblocks.
- Sprint Review: A meeting to demonstrate the sprint results and get immediate feedback from the product owner and the stakeholders.
- Sprint Retrospective: A meeting to reflect on the past and to improve the future.
- Backlog Refinement Meeting: Also called backlog grooming for breaking down epics into user stories and maintaining the prioritization of the product backlog.
- Product Backlog: Prioritized list of items with item of highest value to customer on top.
- Product Backlog Item: Item on product backlog specifying what needs to be done on a particular requirement. Usually in form of user stories.
- Sprint Backlog: List of highest priority items from product backlog selected by team to work upon in the next sprint.
- Product Increment: Working product increment at the end of the sprint that meets team’s definition of “done”.
- Estimation: Relative size estimate for tasks in form of ideal hours or story points.
- User stories: Short description of the user requirements containing minimum information needed for developers to estimate it.
- Cross-functional: People from all competencies and domain knowledge work together as a team.
- Self-organizing: Self-manage without externally assigned roles.
- Sprint: It is a short span of time in which product backlog item is converted into shippable product increment.
- Definition of “done”: Definition of done is the list of criteria which when fulfilled a user story can be marked as done.
- Scrum of Scrums: It is a technique used to extend the scope of scrum to large groups. In this large groups are divided into small teams and then the designated person meets with other team designated people to collaborate in scrum of scrums meeting.
- Velocity: Measure of the amount of work a team can produce at the end of the Sprint.
- Sprint Burn-down Chart: Displays total task hours remaining for the team within one sprint.
- Product Burn-down Chart: Tracks progress of the project. Depicts number of sprints on X-axis and story points (work remaining) on Y-axis.