Here is an article to understand the agile scrum method. What could be better than an example to understand?
Let’s take a subject for our example
To start, I want to create a new blog dedicated to the agile scrum method called scrum.sg.
Here are what this blog will present:
- all the elements defined by the scrum framework
- will only present elements from the guide scrum
- will offer clear illustrations
The subject is simple but it will allow us to properly lay the foundations of our example.
How do we start our agile scrum method?
Indeed, it is not easy to start a project with the agile scrum method without any preparation.
Start with a preparation phase
For my part, I recommend to prepare a first vision of the backlog; for that, don’t hesitate to go and see the agile framing which is a 100% agile product launch framework.
It will allow to:
- align the team around the mission and objectives
- have a vision of the product that we want to make
- view the risks and the product roadmap
- define the organization and governance of the team
Link: Agile framing website
At the end of your agile framing, you will have defined a first backlog with some elements “ready” to be developed and many elements not yet detailed.
The team will have taken the time during the agile framing to define the definition of done which determines the set of criteria which will validate that an item is completed is potentially publishable in production.
Article: Definition of Done (DOD)
Start your first sprint
As a reminder, a sprint begins with a sprint planning and ends with a sprint review and a retrospective. The scrum master will help the team become independent throughout the sprints.
Agile scrum method: sprint planning
During this sprint planning, the scrum team will define its sprint backlog with the following elements:
- the sprint goal
- items meeting the sprint goal
- the implementation plan for these items (technical subtasks, scheduling, etc.)
Here’s what the scrum team defines together for our blog example:
Sprint objective: “display a first version of the blog scrum.sg”
items selected by the team:
- As a visitor, I want to see the home page with the latest blog posts
- (and) As a visitor, I want to be able to obtain the RSS feed for articles
- As a visitor, I want to be able to read an entire article
To meet the requirements of the scrum guide, the product owner had completed the items with:
- gherkin tests to explain how to test them
- the value of each of them
- the estimate of each of them previously purposed by the development team.
Then the development team and the product owner agree on the “how” to meet these needs during this sprint planning. This is the famous “plan” expected during the sprint planning. And indeed, this part is often underestimated.
The team must talk about the solution
Solution purposed by the development team: put a wordpress that meets the 3 needs with the installation of wordpress and some configurations.
The product owner decides to validate the solution. The development team will then suggest to the product owner to add items because they are convinced that they can do more during the sprint.
Moreover, they also indicate to the product owner, that certain items will also have been made thanks to this solution:
- As an author, I want have the capacity to write an article on the blog
- As an author, I want that my administration part of the blog to be secured by login / password access
So, As you can see, depending on the purposed and / or validated “plan”, the development of this plan can compel the team to review all the sprint backlog. The sprint planning is not just about choosing the items to realize but talking about how the development team will do them.
And I have taken this example because it shows how the “plan” can change the whole physiognomy of a sprint imagined upstream.
The team must split into technical subtasks
As the user stories are not technical, the development team will split each of the user stories into technical subtasks.
As a visitor, I want to see the home page with the latest blog articles
The development team will define the technical cuts adapted to the chosen solution, knowing that this will be the first user-story to be dealt with by the team:
- install a development environment
- set up a testing environment
- install wordpress
- setup wordpress for “scrum.sg”
- configure the home page to display the latest articles
- make fake articles to properly check the display
The development team will also define the order of development of user-stories (at least for the first ones).
Agile scrum method: realization begins
At the end of the sprint planning, the development team will start the realization phase.
Each time that one item is developed, one (or more) member of the development team will check that the item meets all the criteria of the definition of done before defining it as “done”.
Please note, the product owner doesn’t do this work, just the development team!
Agile scrum method: daily scrum
Each morning the team will do a classic daily scrum. Each member of the development team will explain:
- what I have been done since the last Daily
- then what I plan to do until the next Daily
- If I have an alert to communicate, I explain it quickly to inform the others members of the team
Agile scrum method: sprint review
The product owner invites the development team and the stakeholders to review the sprint.
He will remind the objective of the sprint: “display a first version of the blog scrum.sg”.
Then, the development team will explain all the finalized items and the items that the team couldn’t finish in the backlog sprint. The team will take the opportunity to explain the obstacles encountered and to indicate if the sprint’s objective has been reached.
When it’s done, the team will present the first version of the blog (objective achieved) in order to obtain feedback from all of the participants in this sprint review. With these feedback, the product owner will add new items that are not detailed in the product backlog.
All participants will define together how to continue the development of the product during the next sprint.
Agile scrum method: retrospective sprint
The scrum team will isolate itself at the end of the sprint review to do a sprint retrospective in order to look for axis of improvement that it could implement during the next sprint.
The team define these:
- improve the visual management
- analyze wordpress plugins to avoid to redo the work
- analyze the security aspect of wordpress
I hope this example of sprint will help you to better understand how scrum takes place. You could find a lot of interesting articles about scrum in this blog.