Scrum structures work into development
Posted: Sun Dec 15, 2024 6:59 am
Events cycles known as Sprints, accompanied by specific events that facilitate planning, monitoring and continuous improvement.
Sprint : A fixed period, typically 2 to 4 weeks, during which the team works to complete selected work from the Product Backlog , with the goal of producing a potentially shippable product increment .
Sprint Planning : A meeting at the start of the Sprint where the team decides what work will be done. During this session, Product Backlog items are selected and work for the Sprint is planned.
Daily Scrum : A short daily meeting that allows the development team to synchronize their work and plan for the next 24 hours. It is an opportunity to discuss obstacles and adjust the daily work plan.
Sprint Review : Conducted at the end of each Sprint to inspect the increment and adapt the Backlog if necessary. Stakeholders and the team review what has been accomplished and discuss next steps.
Sprint Retrospective : A meeting after the Sprint Review where denmark telegram data the team reflects on the past Sprint. The goal is to identify and plan improvements to their process.
I invite you to read our article Phases of the Scrum methodology
To create a visual hierarchy of these events, it is helpful to develop a Scrum board. You can use a project management tool like Trello to do this:
SCRUM methodology in trello
4. Artifacts
Scrum artifacts provide key information that all team members can use to understand the product and backlog, as well as the work completed.
Product Backlog : An ordered list of everything needed in the product, managed by the Product Owner. It includes desired features, functions, enhancements, and fixes.
Sprint Backlog : A set of Product Backlog items selected for the Sprint, plus a plan for delivering the product increment and achieving the Sprint Goal. It is managed by the Development Team.
Increment : The set of all Product Backlog items completed during the Sprint, together with the increments from all previous Sprints. It must be in a condition to be delivered to the customer, meeting the acceptance criteria defined by the team.
Scrum Values
We cannot understand what Scrum is, if we do not review the principles that support this methodology. Scrum values form the ethical and behavioral backbone on which the entire Scrum methodology is based .
Introduced in the Scrum Guide in 2016 , these values embody the spirit with which teams should approach their work, interactions, and challenges within the Scrum framework .
Commitment : When discussing what Scrum is, it is important to remember that each team member plays a crucial role in the success of the project. This means committing not only to the assigned tasks but also to the goals of the team and the project as a whole. Open and ongoing communication about progress is essential.
Value : This value drives teams to challenge the status quo and tackle obstacles with courage. Encouraging members to try new solutions and openly address problems ensures that obstacles are handled effectively. Only then can the Scrum Team stay focused on its goals.
Sprint : A fixed period, typically 2 to 4 weeks, during which the team works to complete selected work from the Product Backlog , with the goal of producing a potentially shippable product increment .
Sprint Planning : A meeting at the start of the Sprint where the team decides what work will be done. During this session, Product Backlog items are selected and work for the Sprint is planned.
Daily Scrum : A short daily meeting that allows the development team to synchronize their work and plan for the next 24 hours. It is an opportunity to discuss obstacles and adjust the daily work plan.
Sprint Review : Conducted at the end of each Sprint to inspect the increment and adapt the Backlog if necessary. Stakeholders and the team review what has been accomplished and discuss next steps.
Sprint Retrospective : A meeting after the Sprint Review where denmark telegram data the team reflects on the past Sprint. The goal is to identify and plan improvements to their process.
I invite you to read our article Phases of the Scrum methodology
To create a visual hierarchy of these events, it is helpful to develop a Scrum board. You can use a project management tool like Trello to do this:
SCRUM methodology in trello
4. Artifacts
Scrum artifacts provide key information that all team members can use to understand the product and backlog, as well as the work completed.
Product Backlog : An ordered list of everything needed in the product, managed by the Product Owner. It includes desired features, functions, enhancements, and fixes.
Sprint Backlog : A set of Product Backlog items selected for the Sprint, plus a plan for delivering the product increment and achieving the Sprint Goal. It is managed by the Development Team.
Increment : The set of all Product Backlog items completed during the Sprint, together with the increments from all previous Sprints. It must be in a condition to be delivered to the customer, meeting the acceptance criteria defined by the team.
Scrum Values
We cannot understand what Scrum is, if we do not review the principles that support this methodology. Scrum values form the ethical and behavioral backbone on which the entire Scrum methodology is based .
Introduced in the Scrum Guide in 2016 , these values embody the spirit with which teams should approach their work, interactions, and challenges within the Scrum framework .
Commitment : When discussing what Scrum is, it is important to remember that each team member plays a crucial role in the success of the project. This means committing not only to the assigned tasks but also to the goals of the team and the project as a whole. Open and ongoing communication about progress is essential.
Value : This value drives teams to challenge the status quo and tackle obstacles with courage. Encouraging members to try new solutions and openly address problems ensures that obstacles are handled effectively. Only then can the Scrum Team stay focused on its goals.