1. What is Scrum? Richard Fennell Engineering Director, Black Marble Ltd.
The source version of most of this stack is not from the Scrum Alliance site, but from a slightly modified one from Mike a Scrum Certified trainer
The cartoon characters are copyright Black Marble Ltd
This Stack is based upon the Redistributable Scrum Introduction Stack from the Scrum Alliance
This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike License
Richard Fennell
Engineering Director, Black Marble Ltd.

2. Origins of Scrum
“The New New Product Development Game” in Harvard Business Review by Hirotaka Takeuchi and Ikujiro Nonaka, 1986.
“The… ‘relay race’ 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.”
Wicked Problems, Righteous Solutions by DeGrace and Stahl, 1990.
First mention of Scrum in a software context
The New New Product. Development Game. by Hirotaka Takeuchi and Ikujiro Nonaka
Download from

3. Origins of Scrum Jeff Sutherland Initial Scrums at Easel Corp in 1993
IDX and nearly 600 people doing Scrum
Not just for trivial projects
FDA-approved, life-critical software for x-rays and MRIs
Ken Schwaber
ADM
Initial definitions of Scrum at OOPSLA 96 with Sutherland
Mike Beedle
Scrum patterns in PLOPD4

4. Scrum has been used in… Independent Software Vendors (ISVs)
Fortune 100 companies
Small startups
Internal development
Contract development

5. Scrum has been used for…
Commercial software
In-house development
Contract development
Fixed-price projects
Financial applications
ISO 9001-certified applications
Embedded systems
24x7 systems with % uptime requirements
The Joint Strike Fighter
Video game development
FDA-approved, life-critical systems
Satellite-control software
Websites
Handheld software
Mobile phones
Network switching applications
ISV applications
Some of the largest applications in use
There are no type of project Scum cannot be applied to

6. Characteristics One of the “agile processes” Self-organizing teams
Product progresses in a series of 2 to 4 week 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

7. The Agile Manifesto 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
Source:

8. Project Noise Level Requirements Agreement Technology Close to
Simple
Complicated
Anarchy
Complex
Close to
Certainty
Far from
Technology
Agreement
Requirements
Aims to move the project from the top right to be bottom left by taking ‘small bites’
Source: Strategic Management and Organizational Dynamics by Ralph Stacey in Agile Software Development with Scrum by Ken Schwaber and Mike Beedle.

9. Scrum Process Overview
24 hours
Daily Scrum
Meeting
Backlog tasks
expanded
by team
days
Sprint Backlog
Scrum in a single slide
Potentially Shippable
Product Increment
Product Backlog
As prioritized by Product Owner
Source: Adapted from Agile Software Development with Scrum by Ken Schwaber and Mike Beedle.

10. 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

11. 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
Source: “The New New Product Development Game” by Takeuchi and Nonaka. Harvard Business Review, January 1986.

12. No changes during a sprint
Plan sprint durations around how long you can commit to keeping change out of the sprint

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

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

15. Product owner 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

16. The 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

17. The 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

18. story A chicken and a pig are....
A chicken and a pig are together when the chicken says, "Let's start a restaurant!". The pig thinks it over and says, "What would we call this restaurant?". The chicken says, "Ham n' Eggs!". The pig says, "No thanks, I'd be committed, but you'd only be involved!".
This is the ethos for a Scum team, they are pigs, their neck is on the line in what they have committed to doing. Everyone else is a Chicken, they might be interested in the project but their job is not on the line

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

20. Sprint prioritization
Sprint planning meeting
Team capacity
Sprint prioritization
Analyze and evaluate product backlog
Select sprint goal
Sprint
goal
Product backlog
Business conditions
Sprint planning
Decide how to achieve sprint goal (design)
Create sprint backlog (tasks) from product backlog items (user stories / features)
Estimate sprint backlog in hours
Current product
Sprint
backlog
Technology

21. 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 so I can have a better idea of facilities
Priority 4 [10 Story Points]
Code the middle tier (8 hours)
Code the user interface (4)
Write test fixtures (4)
Code the foo class (6)
Update performance tests (4)

22. 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
Only pigs can speak … does get a little grey which product owner (are they part of the team?)
Fines for people who are late – the fine can be money i.e. to buy cakes for end of sprint, or some penalty such as sing a song, wear a silly hat. Whatever works best for the team

23. Everyone answers 3 questions
What did you do yesterday? 1
What will you do today? 2
Is anything in your way? 3
These are not status for the ScrumMaster
They are commitments in front of peers

24. 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

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

26. Start / Stop / Continue Start doing Stop doing Continue doing
Whole team gathers and discusses what they’d like to:
Start doing
Stop doing
Interesting idea to do this before the project starts as a hypothetical planning projects to see what people think could be problems.
See Clarke Ching’s blog for some thought’s on this
This is just one of many ways to do a sprint retrospective.
Continue doing

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

28. 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

29. A sample product backlog
Priority
Backlog item
Story Point Estimate 1
Allow a guest to make a reservation 3 2
As a guest, I want to cancel a reservation. 5
As a guest, I want to change the dates of a reservation. 4
As a hotel employee, I can run RevPAR reports (revenue-per-available-room) 8
Improve exception handling 6
... 30
The estimates are in story points, these give a relative estimate between the items, not a fixed one in hours

30. 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.

31. 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

32. 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
We can see how the sprint backlog goes down over the sprint

33. A sprint burndown chart
Hours
The daily estimates are used to plot the sprint burndown, the work remaining

34. Tasks Mon Tues Wed Thur Fri Code the user interface 8 4 12 16 8 10 167 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

35. Team Velocity
Over a number of sprints you will see how many story points you can achieve – the velocity
This allows you to predict delivery times based on number of story points outstanding
REMEMBER – one team’s story point is not the same as anothers

36. 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

37. Scaling through the Scrum of scrums
The person sent to the scrum of scrums is the most appropriate – this is not always the scrum master
e.g. if a teams was doing DB design the DBA might be a better choice. This choice could alter over time .

38. Scrum of scrums of scrums
The scrum of scrums process can be repeated to further grow a project.

39. Tools for Scrum Postcards & Post-Its Scrum board
As with Extreme Programming the product backlog and sprint backlog can be managed on paper cards, most other things add complexity
These can be displayed in a notice board or whiteboard with a manual burn down chart.
Image Source:

40. Tools for Scrum Often need to record the sprint progress
Digital Camera
Excel
However we also want to
Link to development tools such as TFS
Support remote development teams
Commonly the Scrum master will record the revised estimates at the end the daily scrum into Excel and maybe photograph the scrum board.
However this alone may not provide the support needed for a distributed project where staff can be in different countries.

41. Scrum and TFS
There are at least three Scrum Process Guidance Templates
Conchango’s Scrum for Team System
Microsoft’s eScrum
VSTS Scrum Process Template from CodePlex
They all do basically the same, customise work items to scrum names and provide reports

42. demo
eScrum
I like eScrum as I find the web based user interface a quick easy way to capture the sprint progress.
As the sprint items are TFS work items source code can be checked in against them.

43. Screenshot from demo
On the product screen you can add the product backlog items

44. Screenshot from demo
You can enter all the product feature details

45. Screenshot from demo
In the sprint page you can add the team members and the time they have committed to the sprint

46. Screenshot from demo
In the sprint page you can add the team members and the time they have committed to the sprint

47. Screenshot from demo
Every day the team alter the hours completed and the estimate of the remaining.

48. Screenshot from demo
The daily scrum page, were tasks can be updated

49. Screenshot from demo
A sprint burn down, one of many reports available

50. 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.

51. Where to go next www.scrumalliance.org www.controlchaos.com

52. A Scrum reading list
Agile and Iterative Development: A Manager’s Guide by Craig Larman
Agile Estimating and Planning by Mike Cohn
Agile Project Management with Scrum by Ken Schwaber
Agile Retrospectives by Esther Derby and Diana Larsen
Agile Software Development Ecosystems by Jim Highsmith
Agile Software Development with Scrum by Ken Schwaber and Mike Beedle
Scrum and The Enterprise by Ken Schwaber
User Stories Applied for Agile Software Development by Mike Cohn
Lots of weekly articles at

53. For Further Information
My random thoughts ‘But it works on my PC!’
You can also get in touch via: –
WebSite –

54. Copyright notice You are free: Under the following conditions
to Share―to copy, distribute and transmit the work
to Remix―to adapt the work
Under the following conditions
Attribution. You must attribute the work in the manner specified by the author or licensor (but not in any way that suggests that they endorse you or your use of the work).
Nothing in this license impairs or restricts the author’s moral rights.
For more information see
Based on Presentation by: Mike Cohn
(720) (office)
Amended and the cartoon characters added by Black Marble Ltd