Scrum is a subset of Agile. If you’re not familiar with the term agile. Here is a little Intro into the Term Agile.
Scrum is a light process framework for agile development, and the most widely-used one. A “process framework” is a particular set of practices that must be followed in order for a process to be consistent with the framework. (For example, the Scrum process framework requires the use of development cycles called Sprints) “Light” means that the overhead of the process is kept as small as possible, to maximize the amount of productive time available for getting useful work done.
A Scrum process is distinguished from other agile processes by specific concepts and practices, divided into the three categories of Roles, Artifacts, and Time Boxes. These and other terms used in Scrum are defined below. Scrum is most often used to manage complex software and product development, using iterative and incremental practices. Scrum significantly increases productivity and reduces time to benefits relative to classic “waterfall” processes.
Scrum processes enable organizations to adjust smoothly to rapidly-changing requirements, and produce a product that meets evolving business goals. An agile Scrum process benefits the organization by helping it to Increase the quality of the deliverables Cope better with change (and expect the changes) Provide better estimates while spending less time creating them Be more in control of the project schedule and state
Roles in Scrum
Product Owner
The Product Owner is sometimes referred to as the “voice of the customer,” though the role entails more than that. The Product Owner is responsible for determining what the team might work on and ordering the items so that the highest-priority items are done first.
Scrum Master
The Scrum Master removes impediments, or blockers, allowing the Scrum team to proceed with their work smoothly and effectively.
Development Team
The Scrum ideal is that development team members are cross-functional, meaning they are flexible in the kind of work they can do to contribute to the team.
Scrum Events
Scrum event: Scrum team meeting that recurs during each Sprint
Sprint Planning: Scrum event where the team gathers to plan a new sprint
Daily Stand-up Meetings: Daily check-ins where each team member reports progress, next tasks, and issues impeding progress
Backlog Refinement: Product owner reviews product backlog items with the team for clarification and revision. The team estimates the effort of each item.
Sprint Review: Team gathers with stakeholders to demonstrate working software in the form of the Sprint Product
Retrospective: Team gathers to reflect on the work of the Sprint and identify something they can attempt to improve in the next sprint
The Product Backlog and Sprint Backlog
The Product Backlog feeds into the Sprint Backlog. Items are taken from the top of the Product Backlog, where they have the highest priority, and are accepted into a Sprint.
The Taskboard
A taskboard provides an easy way to communicate about work during the course of the Sprint.
Scrum Wrap-up
You now have a much better understanding of what Scrum is and how people work together to make Scrum work.
Definition of “Done” and the Sprint Product
Effective agile teams have clear standing agreements regarding how they will work together. Part of this is the artifact known as the definition of “done.”
Definition of Done
- Tasks are complete
- Code is reviewed
- Item is tested
- Reviewed with stakeholders
- Product Owner reviews Conditions of Acceptance
Key Terms
Product Backlog Item (PBI): A description of a unit of work that is a candidate for a sprint. These often include User Stories, defects, and technical items.
Product Backlog: A prioritized list of Product Backlog Items that are candidates for sprints
Sprint Backlog: A group of Product Backlog Items that have been accepted into the current sprint.
Burn Rate: the rate of completion of tasks in a sprint
Taskboard: a tool for communicating the progress on tasks within a sprint
Stakeholder is someone outside the Scrum team who has a say in what the product should be, such as a manager, client, or customer
Product Owner is the “voice of the customer” and is responsible for developing, maintaining, and prioritizing the items in the product backlog.
Scrum Master is responsible for making sure the work of the team goes smoothly by facilitating Scrum and removing impediments.
Development Team Members are the members of the team who write and test code.
Ressources:
Liftoff: Launching Agile Teams & Projects, Diana Larsen and Ainsley Nies