Share
Embed
Slide 1
Slide 1 text
Richie Rump
@Jorriss
www.jorriss.net
Slide 2
Slide 2 text
No content
Slide 3
Slide 3 text
• It’s a framework to get things done.
• Designed for complex projects.
• Iterative process.
• Shippable software, frequently.
• Handles frequent changes.
Slide 4
Slide 4 text
• Embrace Change
• Frequent Delivery of Software
• Better Risk Management
• Greater Team Involvement
• Better Software Quality
Slide 5
Slide 5 text
Source: http://www.mountaingoatsoftware.com/blog/agile-succeeds-three-
times-more-often-than-waterfall
Slide 6
Slide 6 text
• Individuals and interactions over
processes and tools
• Completed functionality over
comprehensive documentation
• Customer collaboration over contract
negotiation
• Responding to change over following a
plan
Slide 7
Slide 7 text
• Product Owner
• Dev Team
• Scrum Master
Slide 8
Slide 8 text
• Sprint Planning
• Daily Scrum (Standup)
• Sprint Review
• Sprint Retrospective
Slide 9
Slide 9 text
• Product Backlog
• Sprint Backlog
• Burndown Chart
Slide 10
Slide 10 text
• One person
• Accountable for product
• Owns Product Backlog
• Responsible for ordering items in Product
Backlog
• Responsible for clearly expressing
Product Backlog items.
Slide 11
Slide 11 text
• Professionals that “Do the work”.
• Self-organizing – Selects what to work
and choses how to do it.
• Cross-functional – the team has all of the
skills necessary to deliver an increment.
• Do not contain sub-teams.
• Accountability is shared
Slide 12
Slide 12 text
• Ensures Scrum is understood and
enacted.
• Facilitates events as needed.
• Removes impediments and blockers.
• Servant leader.
• Serves the Product Owner, Dev Team and
the Organization.
Slide 13
Slide 13 text
• Less than 30 days
• Most are two weeks long
• Has a goal
• No changes are made that would affect
the goal
• Scope may be clarified during the Sprint
Slide 14
Slide 14 text
No content
Slide 15
Slide 15 text
• What will be done this Sprint?
• How will the chosen work get done?
• Creates a Sprint Backlog and a Sprint Goal.
• Forecast the work for the Sprint.
• At the end we will have created shippable
software.
• Define “done”.
Slide 16
Slide 16 text
No content
Slide 17
Slide 17 text
• Fifteen minute meeting
• Held every day
• What has been accomplished since the last
meeting?
• What will be done before the next meeting?
• What obstacles are in the way?
• Inspect and adapt the Sprint Backlog
Slide 18
Slide 18 text
No content
Slide 19
Slide 19 text
• Time boxed; one hour per week of sprint.
• Involves the Scrum Team and
stakeholders.
• Demos the work done.
• Records feedback and places in Product
Backlog
Slide 20
Slide 20 text
• Scrum team only; no outsiders.
• Inspect how the sprint went with regards
to people, process and tools.
• Creates a plan for implementing
improvements.
Slide 21
Slide 21 text
Photo credit: http://sambit-daspatnaik.blogspot.com/2012/03/importance-of-project-management.html
Slide 22
Slide 22 text
• Scrum Guide :
http://www.scrum.org/Scrum-Guides
• Scrum Primer:
http://scrumfoundation.com/library
• Scrum Fundamentals on PluralSight.
Slide 23
Slide 23 text
Richie Rump
@Jorriss
http://jorriss.net
http://slideshare.net/jorriss
http://dotnetmiami.com