The Scrum Journey

Scrum is an agile approach to developing and releasing software products
Scrum starts with three key roles namely - Product Owner, Scrum Master, and Scrum team / Feature team / Development team

The creation of requirements and the determination of development timing and delivery are undertaken by the Product Owner, who is also tasked with maintaining the overall vision of the product.

The Scrum master works with the scrum team to help the team understand the importance of scrum principles, values, and processes. They coach the team, along with acting as a facilitator. A critical responsibility of the scrum master is to ensure the team is not blocked with anything and protect the team from any interferences that might impact the delivery.

The scrum / Development team comprises folks with cross-functional, diverse skill sets that can help release the agreed-upon sprint goals. The whole team works as one to deliver value

The Journey starts with the Product owner writing down the high-level requirements as the product backlog, which are broken down further into small user stories and tasks based on the discussion with the scrum team. This process is also called backlog grooming, which is prioritized.

A sprint begins with sprint planning, where items from the backlog are pulled into the sprint backlog based on priority and discussion with the product owner. The user stories are estimated based on various estimate strategies like planning poker and others. The team as a whole agrees on what will be delivered as part of the sprint.

Once spirit is started, the team pulls user stories that will be worked upon daily and updates progress. Daily scrum meetings would be conducted to talk about the progress that is being made and also discuss any roadblocks. The user stories should meet the defination of done defined which is very vital. At the end of the sprint a potential shippable product feature will be ready which will be demoed to all stakeholders which might include customers as well.

A Sprint retrospective is an activity to inspect what is working, what is not working, what went fine and did not go fine, and discuss and brainstorm, which can lead to embracing and applying changes as necessary for the betterment of the upcoming sprint.

The Scrum team invests in wirting Good user stories that should meet the INVEST criteria

Various metrics like burnup, burndown, and sprint velocity are monitored to track the progress of the sprint.

The Scrum Journey

Source: :point_down:

1 Like