1. An Introduction to Scrum

2. 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. Our teams self-manage 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 for another iteration.

3. Characteristics 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”
Scrum

4. Agile Manifesto – a statement of values
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:

5. Overview
Scrum

6. Sprints Scrum projects make progress in a series of “sprints”
Analogous to XP iterations
Target duration is one month
+/- a week or two
But, a constant duration leads to a better rhythm
Product is designed, coded, and tested during the sprint
Scrum

7. Sequential vs. Overlapping Development
Scrum
Requirements
Design
Code
Test
Source: “The New New Product Development Game”, Hirotaka Takeuchi and Ikujiro Nonaka, Harvard Business Review, January 1986.

8. No changes during the sprint
Inputs
Tested Code
Change
Scrum
Plan sprint durations around how long you can commit to keeping change out of the sprint

9. Scrum Framework Roles : Product Owner, ScrumMaster, Team
Ceremonies : Sprint Planning, Sprint Review, Sprint Retrospective, & Daily Scrum Meeting
Artifacts : Product Backlog, Sprint Backlog, and Burndown Chart
Scrum is a simple "inspect and adapt" framework that has three roles, three ceremonies, and three artifacts

10. Scrum Framework Roles : Product Owner, ScrumMaster, Team
Ceremonies : Sprint Planning, Sprint Review, Sprint Retrospective, & Daily Scrum Meeting
Artifacts : Product Backlog, Sprint Backlog, and Burndown Chart
Scrum is a simple "inspect and adapt" framework that has three roles, three ceremonies, and three artifacts

11. 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.
He/She is the driver, car driver analogy

12. The Scrum Master 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
Scrum
SM has no authority

13. The Scrum Team Typically 5-10 people Cross-functional
QA, Programmers, UI Designers, etc.
Members should be full-time
May be exceptions (e.g., System Admin, etc.)
Teams are self-organizing
What to do if a team self-organizes someone off the team??
Ideally, no titles but rarely a possibility
Membership can change only between sprints
Scrum
Selects the Sprint goal and specifies work results
Has the right to do everything within the boundaries of the project guidelines to reach the Sprint goal;
Organizes itself and its work; and  Demos work results to the Product Owner.

14. Scrum Framework Roles : Product Owner, ScrumMaster, Team
Ceremonies : Sprint Planning, Sprint Review, Sprint Retrospective, & Daily Scrum Meeting
Artifacts : Product Backlog, Sprint Backlog, and Burndown Chart
Scrum is a simple "inspect and adapt" framework that has three roles, three ceremonies, and three artifacts

15. Sprint Planning Meeting
Scrum
Product Owner
Scrum Team
Customers
Management
Product Backlog
Sprint Planning
Meeting
Team Capabilities
Sprint Goal
Business Conditions
Sprint Backlog
Technology
Current Product

16. Daily Scrum meetings Parameters Three questions:
15-minutes
Stand-up
Not for problem solving
Three questions:
What did you do yesterday
What will you do today?
What obstacles are in your way?
Chickens and pigs are invited
Help avoid other unnecessary meetings
Only pigs can talk
Scrum

17. Daily Scrum – Pigs and Chickens
The joke is meant to point out the difference between those who are committed on a project and those who are only involved.
Scrum affords special status to those who are committed and many teams enforce a rule in which only those who are committed are allowed to talk during the daily scrum.

18. Questions about Scrum meetings?
Why daily?
“How does a project get to be a year late?”
“One day at a time.”
Fred Brooks, The Mythical Man-Month.
Can Scrum meetings be replaced by ed status reports? No
Entire team sees the whole picture every day
Create peer pressure to do what you say you’ll do
Scrum

19. Sprint Review Meeting
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
Participants
Customers
Management
Product Owner
Other engineers
Scrum

20. Sprint Retrospective Meeting
Scrum Team only
Feedback meeting
Three questions
What was good?
What could have been better?
What would they like to do different in next sprint?
Don’t skip for the first 5-6 sprints!!!
This should not be a blame session.

21. Scrum Framework Roles : Product Owner, ScrumMaster, Team
Ceremonies : Sprint Planning, Sprint Review, Sprint Retrospective, & Daily Scrum Meeting
Artifacts : Product Backlog, Sprint Backlog, and Burndown Chart
Scrum is a simple "inspect and adapt" framework that has three roles, three ceremonies, and three artifacts

22. Product Backlog A list of all desired work on the project
Usually a combination of
story-based work (“let user search and replace”)
task-based work (“improve exception handling”)
List is prioritized by the Product Owner
Typically a Product Manager, Marketing, Internal Customer, etc.
Scrum

23. Sample Product Backlog
Scrum

24. Eksempel på et Backlog item

25. Planning Hver post-it svarer til en task inden for et Backlog item

26. Planning (Real-life)

27. The Sprint Goal A short “theme” for the sprint:
Scrum
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.”

28. From Sprint Goal to Sprint Backlog
Scrum team takes the Sprint Goal and decides what tasks are necessary
Team self-organizes around how they’ll meet the Sprint Goal
Manager doesn’t assign tasks to individuals
Managers don’t make decisions for the team
Sprint Backlog is created
Scrum

29. Sample Sprint Backlog
Scrum

30. Sprint Backlog format/Taskboard

31. Sådan benyttes et Taskboard

32. Et real-life Sprint Backlog Taskboard

33. Sprint Backlog during the Sprint
Changes
Team adds new tasks whenever they need to in order to meet the Sprint Goal
Team can remove unnecessary tasks
But: Sprint Backlog can only be updated by the team
Estimates are updated whenever there’s new information
Scrum

34. Sprint Burndown Chart
Scrum

35. Some conclusions about pair-programming (Henrik Kniberg, Crisp)
Pair programming does improve code quality.
Pair programming does improve team focus (for example when the guy behind you
says “hey is that stuff really necessary for this sprint?”).
Pair programming is exhaustive and should not be done all day.
Shifting pairs frequently is good.
Pair programming does improve knowledge spread within the group. Surpisingly fast too.
Some people just aren’t comfortable with pair programming. Don’t throw out an
excellent programmer just because he isn’t comfortable with pair programming.
Code review is an OK alternative to pair programming.
The “navigator” (the guy not using the keyboard) should have a computer of his own
as well. Not for development, but for doing little spikes when necessary, browsing
documentation when the “driver” (the guy at the keyboard) gets stuck, etc.
Don’t force pair programming upon people. Encourage people and provide the right
tools but let them experiment with it at their own pace.