1. Applying Agile Methodology
- Harmeet Sudan, PMP
© 2011 Capgemini. All rights reserved.

2. Waterfall vs. Agile
The Waterfall approach to product development may conflict with the goals of maximum speed and flexibility. Instead a holistic or “rugby” approach – where a team tries to go the distance as a unit, passing the ball back and forth – may better serve today’s competitive requirements. 2

3. The Agile Manifest – a Statement of Values
Process and tools
Individuals and interactions
over
Comprehensive documentation
Working software
over
Contract negotiation
Customer collaboration
over
Following a plan
Responding to change
over 3

4. Sequential vs. overlapping development
Requirements
Design
Code
Test
Rather than doing all of one thing at a time...
...Scrum teams do a little of everything all the time 4

5. Scrum in 100 words
Scrum is an agile process that allows us to focus on delivering the highest business value in the shortest time.
It allows us to rapidly and repeatedly inspect actual working software (every two weeks to one month).
The business sets the priorities. Teams self-organize to determine the best way to deliver the highest priority features.
Every two weeks to a month anyone can see real working software and decide to release it as is or continue to enhance it for another sprint. 5

6. Characteristics of Scrum
Self-organizing teams
Product progresses in a series of month-long “sprints”
Requirements are captured as items in a list of “product backlog”
No specific engineering practices prescribed
Uses generative rules to create an agile environment for delivering projects
One of the “agile processes” 6

7. Potentially shippable
Scrum
24 hours
Sprint
2-4 weeks
Return
Sprint goal
Potentially shippable
product increment
Sprint backlog
Return
Cancel
Coupons
Gift wrap
Cancel
Gift wrap
Coupons
Product backlog 7

8. Putting it All together8

9. The Planning Onion Agile teams plan on the innermost three levels.
Others (on the team in the company) plan on the outer three levels.
Strategy
Portfolio
Product
Release
Iteration
Daily

10. An Agile Approach to Planning
Release
Release planning
Conditions of Satisfaction (scope, schedule, resources)
Iteration
Development
Iteration planning
Conditions of Satisfaction (scope)
Product increment
Feedback

11. Relating the Different Planning Levels
As a frequent flyer, I want to… 3 5 2
Iteration 1
Iteration 2
Product Backlog
Code the UI 8
Write test fixture 6
Code Middle tier 12
Write tests
Automate Tests 4
Iteration Backlog
“Yesterday I started on the UI; I should finish before the end of today.”

12. Sprints Scrum projects make progress in a series of “sprints”
Analogous to Extreme Programming iterations
Typical duration is 2-4 weeks or a calendar month at most
A constant duration leads to a better rhythm
Product is designed, coded, and tested during the sprint 12

13. No Changes During a Sprint
Plan sprint durations around how long you can commit to keeping change out of the sprint 13

14. Scrum framework Roles Ceremonies Artifacts Product owner ScrumMaster
Team
Roles
Sprint planning
Sprint review
Sprint retrospective
Daily scrum meeting
Ceremonies
Product backlog
Sprint backlog
Burndown charts
Artifacts 14

15. Scrum framework Roles Ceremonies Artifacts Product owner ScrumMaster
Team
Roles
Sprint planning
Sprint review
Sprint retrospective
Daily scrum meeting
Ceremonies
Artifacts
Product backlog
Sprint backlog
Burndown charts 15

16. Scrum Roles Role Description Product Owner ScrumMaster Team
Define the features of the product
Decide on release date and content
Be responsible for the profitability of the product (ROI)
Prioritize features according to market value
Adjust features and priority every iteration, as needed
Accept or reject work results
ScrumMaster
Represents management to the project
Responsible for enacting Scrum values and practices
Removes impediments
Ensure that the team is fully functional and productive
Enable close cooperation across all roles and functions
Shield the team from external interferences
Team
Typically 5-9 people
Cross-functional:
Programmers, testers, user experience designers, etc.
Members should be full-time
May be exceptions (e.g., database administrator
Teams are self-organizing
Ideally, no titles but rarely a possibility
Membership should change only between sprints

17. Scrum framework Roles Ceremonies Artifacts Product owner ScrumMaster
Team
Roles
Sprint planning
Sprint review
Sprint retrospective
Daily scrum meeting
Ceremonies
Product backlog
Sprint backlog
Burndown charts
Artifacts 17

18. Sprint Planning
Team selects items from the product backlog they can commit to completing
Sprint backlog is created
Tasks are identified and each is estimated (1-16 hours)
Collaboratively, not done alone by the ScrumMaster
High-level design is considered
As a vacation planner, I want to see photos of the hotels.
Code the middle tier (8 hours)
Code the user interface (4)
Write test fixtures (4)
Code the foo class (6)
Update performance tests (4) 18

19. The Daily Scrum Parameters Not for problem solving
15-minutes
Stand-up
Not for problem solving
Whole world is invited
Only team members, ScrumMaster, product owner, can talk
Helps avoid other unnecessary meetings 19

20. Everyone Has Three Questions
What did you do yesterday? 1
These are not status updates for the ScrumMaster
These are commitments in front of peers
What will you do today? 2
Is anything in your way? 3 20

21. The Sprint Review Team presents what it accomplished during the sprint
Typically takes the form of a demo of new features or underlying architecture
Informal
2-hour prep time rule
No slides
Whole team participates
Invite the world 21

22. Sprint retrospective
Periodically take a look at what is and is not working
Typically minutes
Done after every sprint
Whole team participates
ScrumMaster
Product owner
Team
Possibly customers and others 22

23. This is just one of many ways to do a sprint retrospective.
Start / Stop / Continue
Whole team gathers and discusses what they’d like to:
Start doing
Stop doing
This is just one of many ways to do a sprint retrospective.
Continue doing 23

24. Scrum framework Roles Ceremonies Artifacts Product owner ScrumMaster
Team
Roles
Sprint planning
Sprint review
Sprint retrospective
Daily scrum meeting
Ceremonies
Product backlog
Sprint backlog
Burndown charts
Artifacts 24

25. This is the product backlog
The requirements
A list of all desired work on the project
Ideally expressed such that each item has value to the users or customers of the product
Prioritized by the product owner
Reprioritized at the start of each sprint
This is the product backlog 25

26. A Sample Product Backlog
Backlog item
Estimate
Allow a guest to make a reservation 3
As a guest, I want to cancel a reservation. 5
As a guest, I want to change the dates of a reservation.
As a hotel employee, I can run RevPAR reports (revenue-per-available-room) 8
Improve exception handling
... 30 50 26

27. The sprint goal
A short statement of what the work will be focused on during the sprint
Life Sciences
Support features necessary
for population genetics studies.
Database Application
Make the application run on SQL Server in addition to Oracle.
Financial services
Support more technical indicators than company ABC with real-time, streaming data. 27

28. Managing the Sprint Backlog
Individuals sign up for work of their own choosing
Work is never assigned
Estimated work remaining is updated daily
Any team member can add, delete or change the sprint backlog
Work for the sprint emerges
If work is unclear, define a sprint backlog item with a larger amount of time and break it down later
Update work remaining as more becomes known 28

29. A sprint backlog Tasks Mon Tues Wed Thur Fri Code the user interface
Add error logging 8 10 16 8 16 12 4 12 16 8 4 11 8 8
Code the middle tier
Test the middle tier
Write online help
Write the foo class 29

30. A sprint burndown chart
Hours 30

31. Tasks Mon Tues Wed Thur Fri 8 4 12 16 8 10 16 7 11 8 16 8 12 50 40 30
Code the user interface 8 4 12 16 8 10 16 7 11 8
Code the middle tier 16
Test the middle tier 8
Write online help 12 50 40 30
Hours 20 10
Mon
Tue
Wed
Thu
Fri 31

32. Scalability Typical individual team is 7 ± 2 people Factors in scaling
Scalability comes from teams of teams
Factors in scaling
Type of application
Team size
Team dispersion
Project duration
Scrum has been used on multiple 500+ person projects 32

33. Scaling through the Scrum of scrums33

34. Scrum of scrums of scrums34

35. Recap

36. Product Owner explains the Scope

37. Team estimates the complexity and task details

38. Sprint Review

39. Sprint Demo

40. Daily Scrum

41. Daily Scrum – Contd…

42. Product Backlog

43. Sprint Backlog

44. Typical Scrum Board

45. Typical Scrum Board – Contd…

46. Agile Tool Demo

47. Enterprise Product Tour Video – VersionOne
elease=11.3&page=MainMenu.MyHome

48. Next Steps

49. Presentations and Discussion
Effective User Stories for Agile
Requirements
Estimation Techniques
Agile for Testing
Agile for Program Management
Office

50. Appendix

51. Sources www.mountaingoatsoftware.com/scrum www.agilemanifest.com
“The New New Product Development Game” by Takeuchi and Nonaka. Harvard Business Review, January 1986.

52. Product Backlog Template
Release No
Sprint No
Req No
Functional/Non-Functional
Feature Name
User Description
Priority
Business Value (BV)
Estimate
Estimation Risk
Error Severity
Originator
Creation Date
Created By
Status
Closed Date
Total Points

53. Sprint Planning from 5-Oct-2009 to 30-Oct-2009
Sprint Plan Template
Sprint Planning from 5-Oct-2009 to 30-Oct-2009
Week1
Onsite Team
Offshore Team
Sl.No
Phase Name
Task Description
PSD
PED
Assigned To
Efforts
Status T1 T2 T3 T4 T5 T6 T7 T8 T9
T10
T11
T12
T13
T14
T15
T16
T17
T18
T19
T20
T21
T22
T23
WEBSITE REDESIGN - DESKTOP VERSION - POST DEPLOYMENT TASKS
Total Efforts 1 8 24
39.5 17 35
Design
SEO
22-Oct-09
26-Oct-09
ALL 20
Closed 2
Progress bar, Button and Form design for User registration 3
Roll Out
Virginia and Tenesse zips not launching those site
5-Oct-09
6-Oct-09 4 5
Change Label Coler from Red to Blue
7-Oct-09
Shows Incorrect in Safari on Mac
In Progress 6
Sometimes get error on page warning when going back 32 12 7
Copyright should be Changed to Copyright(mark) 2009 Alfa Mutual Insurance Company 16
2.5
Requirement missed as part of project execution
21-Oct-09 80 9
Need to be able to press enter instead of clicking execute button 10
FAQ, if you click on multiple FAQ's - Error on Page 11
Tracking Script is Commented Out
Billmatrix page is centered in IE7 but is left aligned in other browsers
8-Oct-09 30 13
The mouse pointer no longer changes when you mouse over the action button
12-Oct-09
13-Oct-09 14
All banners have to load before site starts
14-Oct-09 64 15
If you select as state then do agent locator and come back text is gone? 40
All tickers have to load before site starts
Application urls and s need to be looked UP From Table by Environment, Not Hard Coded. For example customer stories 18
These are high maintenance, need to pull from common file
28-Oct-09 19
"FARMS" to be re-located from under Home to Top of the menu list. Should reflect in all pages which has left handside navigation menu. "Auto, Home, Life, Farm" to be the order. "Farm" to be renamed as "Farms" - Will confirm this
15-Oct-09 60
Review efforts on Roll Out tasks
30-Oct-09
100
WEBSITE REDESIGN - MOBILE SITE 45 21
Creation of iPhone New Application design
29-Oct-09 22
Construction
iPhone to Non-iPhone HTML Migration for New design
16-Oct-09