Professional Documents
Culture Documents
Scrum
www.sonata-software.com
Agenda
www.sonata-software.com
Agile Manifesto
www.sonata-software.com 4
Scrum Terminology
• Scrum Roles
o Product Owner
Represents all stakeholders, secures funding, defines overall
requirements, determine ROI & Release Plan
o Development Team
Develops functionality, self managed, self organized, cross functional,
collectively responsible for success of each iteration
o Scrum Master
Facilitator and responsible for scrum processes, training
o Users, other stake holders
• Product Backlog: A prioritized list of User stories to be worked on in project.
• User Story : A high level requirement to be delivered during a Release.
• Release: A fixed set of time that will focus on delivering a set of prioritized
features with relevant value to the business
www.sonata-software.com 5
Scrum Terminology contd.
• Release Planning Session: A one day planning session to define product features to
be delivered for the release.
• Sprint: One of several 2-4 week development iterations occurring within a release.
• Sprint Backlog: Prioritized list of stories to be worked over the sprint.
• Sprint Planning Session: A half a day planning session to request and commit to
stories to be worked over the sprint.
• Scrum Meeting/Standup Meeting: 15 minute meeting facilitated by Scrum Master.
Team members report what they did yesterday, what they are going to do today, any
obstacles they are facing. Focus is work remaining not accomplished.
• Retrospection: Held at the conclusion of a sprint to determine what worked well and
what didn’t to identify process improvements
• Sprint Review/Demo: Held at the end of the sprint to demo the new stories developed
in the sprint
www.sonata-software.com 6
Scrum Terminology contd.
• Story Point: A unit of measure that defines the relative work effort estimated for
completing a story.
• Task: A unit of work, typically between 4 and 16 hours, broken down from a story.
• Team Velocity: Calculation to show the available work capacity of the team and
individuals during a sprint. Estimated at the beginning of a sprint, measured during and
after the sprint.
www.sonata-software.com 7
Agile Vs Waterfall
www.sonata-software.com 8
Agile Vs Waterfall
Iteration
• Requirements
• Design
• Development
n • Testing
• Release
www.sonata-software.com 9
Risk Analysis: Agile Vs Waterfall
Time
Waterfall Methodology Agile Methodology
www.sonata-software.com 10
Delivered Value – Waterfall Method
100%
70-80%
50% 60-70%
0%
www.sonata-software.com 11
Delivered Value – Agile Methodology
150%
100 % 140%
10% 125%
15%
110%
50 % 25%
5%
5%
5%
20%
0% 15%
1 2 3 H1 4 5 6 H2 7 8 9 10 H3 11 12 H4 13 14 15 H5 16 17 18 H6 19 20
• Project Stages
Release Planning
Prioritize Product Backlog
Write User Stories
Develop High level Estimates
Develop Release Plan
Sprint Development
Sprint Planning
Sprint Execution
Daily Stand up meetings
Demonstration
Sprint Retrospection
Release Retrospection
Closure
www.sonata-software.com 13
Release Planning
www.sonata-software.com 15
Estimation
• Key Principles
• Estimate, get feedback on accuracy. Don’t estimate too far into the future
• If requirements are not clear, develop multiple estimates
• Validate estimates by comparison/experience
• Agile is continuous improvement, this applies to estimation also.
• Key Methods
Coarse grained Estimation / Triangulation
o Measure in Story Points (say 1,2,3,5,8,13,20 and 40)
o Principle: Relativity. (A 8 point story takes twice as much as a 3 point story)
o Convert Story point size to effort (say 1 story point = 3 days)
o Apply factors for the team for example:
Adjusted Estimate = Actual Estimate * (1+ Knowledge of Technology +Knowledge of Domain +
Work Environment + Complexity Factory + Team Togetherness)
Adapted Delphi Wideband Approach
o Developers ask questions about a story to Product owner
o Each developer separately gives out an estimate
o If estimates differ largely, discuss, do it again
Estimations are done as games to increase motivation.
www.sonata-software.com 16
Sprint Development
• Sprint Planning
Input People Activity Process Output
Resource Plan, Scrum Master, Availability of Guidelines for Sprint
Product Backlog, Product Owner, resources, Story Sprint Backlog,
Sprint Velocity, Dev Team Success criteria, Break Planning Sprint Burn
Review Notes stories into Tasks, down Chart,
Estimate Task size, Product
Create Initial Burn Backlog
down chart
• Complete Tasks
Input People Activity Process Output
Sprint Dev Team, 1. Test Plan & Test Guidelines for Dev: Sprint
Backlog Tech Lead Cases 1.Test Driven Backlog,
2. Tested Software Development Sprint Burn
3. Documentation 2.Design Docs down Chart,
4. Integration 3.Unit Test cases Tested
testing 4.Testing Strategy Software
5.Builds
6.Deployments
www.sonata-software.com 17
Sprint Development
www.sonata-software.com 18
Sprint Development
www.sonata-software.com 19
Sprint Development
• Daily Standup meetings
Input People Activity Process Output
Sprint Product 1. Update task Guidelines for Meeting: Sprint
Backlog, Owner, Dev status in Sprint 1.15 min. max Backlog,
Sprint Team, backlog 2.No elaborate tech Sprint Burn
Burn Scrum 2. Identify discussions down Chart
down Master bottlenecks 3.What is accomplished?
Chart 3. Plan for 4.What is planned for
Resolving today?
5.Any obstacles?
• Demonstrate
• Sprint Retrospection
Input People Activity Process Output
Feedback Product 1. Assess sprint Guidelines: Team
from Owner, Dev performance 1.What went well? Velocity***,
Demo, Team, 2. Gather metrics if 2.What went wrong? Learning,
Ideas Scrum required 3.Areas for Improvement Metrics
Master 3. Sprint Velocity
www.sonata-software.com 20
Sprint Development
• Key Aspects
o Team member picks up the story: he ‘owns’ it
o Team member commits to the time
o Daily standup meetings:
No detailed discussions that takes hours
o Handling Sprint Backlog exceptions
Tasks identified during sprint
Tasks that could not be completed in sprint (deferred)
o Retrospection: No personal attacks, discuss metrics like defects
o Retrospection: A performance assessment sheet with relevant
process areas can be filled
Product Owner’s Presence
Daily standup meeting code of conduct
Unit testing, build, testing timelines, deviations
www.sonata-software.com 21
Release Retrospection
www.sonata-software.com 22
Close Project
• Close Project
Input People Activity Process Output
Metrics, Feedback, Scrum 1. Hand holding Guidelines Lessons Learnt,
Product Backlog, Master 2. Document key metrics Metrics,
Retrospection 3. Discuss Lessons Communication
outcome, Revised learnt
Estimates
www.sonata-software.com 23
Advantages
www.sonata-software.com 24
Key Issues
www.sonata-software.com 25
Summary
www.sonata-software.com 26
Thank you
Questions?
Contact:
Kalyan Chakravarthy V
Ext: 5632
www.sonata-software.com 27