Scrum Development Process

Scrum: A framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.

Hello dear followers and readers,

This is my first article as Scrum Master where I am describing new methodology of software development process.The scrum process is based in two week sprints and include main roles, key artifacts and key meetings with main agenda for each. Usually we don't like to read long articles so I concentrated all process in one picture.

Agenda for Key Meetings

Sprint Planning Meeting - Max 1-2 hour

1. Defining the sprint goal(Lead by Product Owner)
2. Checking team capacity, absences, vacations (By Scrum Master)
3. Describing the requirements to be built (the top priority items from the product backlog)(By Product Owner)
4. Determining the requirements that will be built during the sprint based on velocity of previous sprint. (By Team, Product Owner and Scrum Master)
5. Break down estimated requirements into tasks(By Team and Scrum Master)

Daily Scrum Meeting - Max 15-20 min

During this meeting everyone will focus on answering three questions:

– what did you accomplish yesterday?

– what do you plan on doing today?

– do you have any roadblock/impediment?

It is not a reporting meeting, but a collaboration between team.

Backlog Refinement Meeting - Max 2 hour

Because requirements in Scrum are only loosely defined, they need to revisited and clearly defined before they come into the Sprint. This is done in during the current sprint in a ceremony called Product Backlog Refinement.

1. Analyzing new requirements
2. Splitting large items into smaller ones (epics to user stories, big user story to small user story)
3. Estimation of new items
4. Re-estimation of existing items

Sprint Review Meeting - Max 1-2 hour

1. Introducing all attenders by Scrum Master
2. Sprint Goals (What was planned to achieve)(Lead by Product Owner)
3. Status overview( planned sprint items, finished and unfinished, added and removed items, changed priorities)(Lead by Scrum Master)
4. Live Demo (demonstration of finished functionalities)(Lead by Team)
5. Sprint Statistics (value delivered, velocity chart, burn down chart progress)(Lead by Scrum master)
6. Impediments (Risks identified in the sprint, proposal of solutions)(Lead by Scrum Master)
7. Feedback time(Feedback from every stakeholder ,an information about the next sprint)

Sprint Retrospective Meeting - Max. 1-2 Hour

Main goal of this meeting is improving work of the team.

1. Scrum Master use different techniques.
2. Creating a action list with their owners and due dates.

Here are 10 retrospective techniques for using during the retrospective meeting:

• Liked, learned, lacked, longed for (4 L’s)
• Sailboat
• Speedcar
• Starfish (small, large)
• Stop, start, continue
• Mad, sad, glad
• Token of appreciation
• One word retrospective
• KALM (Keep, add, more, less)
• and when you have no idea what to do…just use lean coffee style

I will come back to you with new articles from my experience as Scrum Master.Focus of this article is to describe shortly scrum process that looks easy to understand but difficult to master.

I look forward to your comments or questions.

Merry Christmas and Happy New Year!