Scrum in 14 Steps

• A Product backlog is created and prioritized by the Product Owner.

• Scrum Master will facilitate sprint planning session and will discuss about sizing of each user story.
• Team can ask any number questions to PO during the Sprint planning.
• Once clarify all the questions team can choose stories based on priority.
• While giving the sizing team should think about not only time should think about complexity of the user story.
• The PO selects story cards from the product backlog and adds them to the sprint backlog, deciding what cards get implemented.
• A sprint is a short amount of time to get a significant amount of work done. Usually 2-3 weeks sprint schedule.
• Team meets each day to assess their progress; a “daily scrum”
• The scrum master keeps the team focused on their goals.
• At the end of each sprint, the work that was selected from the product backlog should be released to the customer.
• Every sprint ends with a sprint review and retrospective.
• When a new sprint begins, the team selects another group of stories from the Product Backlog.
• The cycle repeats until there are no more story cards to be implemented in the product backlog or the deadline has passed.
 Roles and Responsibilities
Basically there are 3 roles are defined in any of the Scrum project: The Scrum Team, Scrum Master and Product Owner.
Scrum Teams are small. The ideal size is 7 +/- 2 people.
The Scrum Team/ Core Team Scrum Master Product Owner

All Developers and Testers will be under Core Team. • The Scrum Master is responsible for the Scrum • Create and maintain the product backlog.
Developer: process, facilitate the scrum ceremonies and • Prioritizes and sequences the Backlog according
• Understand the business intent of the story. protect the team from outside noise. to business value.
• Works with PO and tester to come up with an • Remove barriers between the development • Conveys the Vision and Goals at the beginning of
approach on how to provide the value. and the Product Owner. every Release and Sprint.
• Build code to satisfy the tests and conditions of the • Keep information about the team’s progress • Represents the customer, interfaces and engages
story. up to date and visible to all stakeholders. the customer.
• Continually improve the test and code based with • Identify, raise and remove roadblocks • Participates in the daily Scrums, Sprint Planning
refactoring. • Internal team coach and help the team to take Meetings and Sprint Reviews and Retrospectives.
• Help each other to high levels of design and code the right decisions. • Inspects the product progress at the end of every
quality. • Helping the team maintain their burndown Sprint and has complete authority to accept or
Testers: chart and velocity trends. reject work done.
• Their effective communication helps put the • Walking the product owner through more • Terminates a Sprint if it is determined that a
developers and product owner on the same page. technical user stories. drastic change in direction is required .
• They are capable of identifying risks, mitigating • Encouraging collaboration between the Scrum
them where possible, and prioritizing all tasks that team and product owner.
could help deliver a shippable product at the end of • Communicate status internally.
every sprint.
• They give continuous feedback to the entire
development team on the status/progress of the
existing sprint.
• Write the test cases and identify the defects and
upload into Rally.
 Sprint Planning Ceremony
What is it:
The Sprint Planning meeting held at the beginning of each new sprint to break down each of the feature schedule into individual stories. The purpose of the Sprint
Planning meeting is for the team to agree to complete a set of the top-ordered product backlog items. This agreement defines the Sprint Backlog and is based on the
team’s velocity or capacity and length of the Sprint time box.
Duration of the Meeting : Sprint planning is a time-boxed meeting, usually fixed to 4 hours for a 2 weeks Sprint.
Essential:
• Scrum Master : Facilitating the meeting and keeps the team to focus on their goals.
• Product Owner : Product Owner pulls stories from Product backlog and describe the highest priority features of the team. Clarifying the details of the Product
Backlog item and their acceptance criteria.
• Team : Each backlog item would be pick by team members and they can ask any number of questions and clarify all questions before choose the user story.
Sizing:
Once team choose the user stories, we will need to do an estimation. Generally we will follow Story point estimation. Here, team will come together and each of the
member who had identified for the activity for the backlog item. We are following planning poker for user story estimation.
If team feels are too large/complex to complete with in spring should be broken down into smaller/less complex.
Re-estimate when significant new information is uncovered, as it changes complexity.
Re-estimate in the event of team changes.
 Scrum Ceremonies
Daily Scrum:
The daily Stand Up is an Agile Ceremony where the team meets for no more than 15 mins every day. Each team member on the team reports briefly on what they did
yesterday, what they are going to do today and there are any concerns or road blocks they are facing. Scrum Master will refer the Burndown chart during the Daily
scrum to track project health.
Essential: Scrum Master, Product owner and Core team.
Duration of the Meeting : 15 mins in agile room.
Burndown chart: It is used to track project status. X axis is indicating Time and Y axis indicates Scope. At the start of Sprint the team estimates the work for all the
tasks they commit to. The sum of all the hours estimated for all the tasks is the starting point for the graph. The starting point for the burndown chart is created
during the iteration planning. All team members estimate the work for their assigned tasks, and the sum of all these hours is the starting point.
Show & Tell/Demo:
Show and Tell is a demonstration of features completed during a sprint. This provides a forum for team members, customers and other stakeholders to review the
progress, provide feedback. By using show and tell, teams maintain accountability to the customer.
Essential: Scrum Master, Product owner, Core team an business owners.
Duration of the Meeting: Normally 2 hours for 2 weeks sprint.
Retrospectives :
After each sprint we will have retrospective and it is designed to help the team find ways to improve their process and output. In this ceremony basically we will
discuss about what worked and what didn’t worked, suggestions and improvements. We will implement those suggestions in upcoming sprints.
Essential: Scrum Master , Core team and Product Owner.
Duration of the Meeting: Normally 1 hour for 2 weeks sprint.
 Burndown Vs Burnup Charts
It is used to track project status. X axis is indicating Time and Y axis indicates Scope. At the start of Sprint the team estimates the work for all the tasks they commit to.
The sum of all the hours estimated for all the tasks is the starting point for the graph. The starting point for the burndown/up chart is created during the iteration
planning.
Burndown Charts Burnup Charts

• A burn down chart shows how much work is remaining to be done in the • A Burn up chart shows how much work has been completed, and the total
project. amount of work.
• In the burn down chart it appears that the team did not accomplish much in • The burn up chart shows the complete picture - that the scope increased at
the middle of the project but heroically finished everything at the end. the beginning of the project, and some scope was removed to finish the
• A single line racing towards zero as the project is completed. Anyone can project by the deadline, whilst the team made steady progress through the
understand this chart, and it does not need an explanation. However it can entire duration of the project.
hide important information, for example the effects of scope change. • A burn up chart tracks completed work and total work with two separate
lines, unlike a burn down chart which combines them into a single line.
• Burnup chart clearly shows both completed work and project scope. The
project will be completed when the lines meet.
• A burn up chart, tracks progress towards a projects completion. In the
simplest form of burn up chart there are two lines on the chart:
A total work line (the project scope line)
A work completed line