fbpx

Agile Framework – Scrum Part 2

agile framework scrum meetings

In this article, we are going to go deep in the scrum meetings and ceremonies.

Scrum Meetings

Sprint Planning
Sprint planning is a two-parts time-boxed meeting. It must be a maximum of 8 hours allocated for one month of a sprint – anything beyond that is irrelevant, it will not add value.

– Part 1: Defines the deliverables in the increment
* The team selects items from the product backlog and defines a sprint goal.
* The Product Owner explains the requirements to the development team. The PO will clarify any questions they might have and make them understand what value they are getting out of the product item.

– Part 2: Defines how to achieve the increment.
* Items are converted into tasks and estimated.
* The development team has understood what they are going to produce at the end of the Sprint. The team will work the product items and break down into smaller tasks and estimate based on the complexity and maturity of the group, how long they are going to take to complete the tasks.

Tips:
– Everybody should participate in the planning
– Make the planning explicit, i.e., use information radiator

Daily Scrum
The Daily Scrum is a 15 min time-boxed event for the team to synchronize activities and focuses on progress toward the sprint goal. It can be conducted for 5 and 10 minutes if the team has discussed everything, but it should not be over 15 minutes.

There are three questions that everyone in the team should answer during the Daily Standup Scrum:
1) What I did yesterday that help the team to meet the sprint goal?
2) What will I do today?
3) Do I see obstacles that prevent the team or me from achieving the sprint goal?

Tips for performing better the Daily Standup:
– Comply with the given time box
– Be on time
– Focus
– Be nice and kind
– Prepare your questions

Sprint Review
The sprint review is a 4-hour time-boxed meeting. In this meeting, the Product Owner identifies what has been done and determines if the development team completed the tasks correctly. Otherwise, it will go back to the product backlog.
The team discusses what went well, which problems they had and those that were solved, and also demonstrate what it has done in a Product Demo.
If the Product Owner identifies something is not meeting the requirements, they discuss the backlog as it stands and, in the end, the entire group collaborates on what to do next.

Tips:
– Only demonstrate real product increments in a sprint review
– The team showcases the work
– Take new requirements in the backlog

Sprint Retrospective
The goal of a sprint retrospective is to improve the process by collecting feedback.
To do that the team inspects how the last Sprint went with regards to people, relationships, process, and tools. Identify and order the major items that went well and potential improvements and also create a plan for implementing improvements.

Tips:
– Remember: There is no 100% perfect process
– There is always something to improve
– Try to use 1-3 improvements for the next Sprint

Backlog Grooming
The backlog grooming is an opportunity to explain the strategic purposes behind prioritized items in the backlog. In this meeting, the team will break down large users stories into smaller tasks, discuss user stories, answer any related questions to smooth out any ambiguity.

The backlog grooming is also proper to ensure that upcoming user stories meet the team’s “definition of done” by adding critical contextual information and acceptance criteria.