Loading presentation...

Present Remotely

Send the link below via email or IM


Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.


Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks


Redistributable Intro To Scrum by Mountain Goat Software, LLC

Maria Goldberg

on 26 November 2012

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of RedistributableIntroToScrum

Artifacts: Product backlog
Sprint backlog
Burndown charts Roles: Financial Services 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 Analyze and evaluate product backlog
Select sprint goal Sprint prioritization Sprint planning meeting Sprint planning
Sprint review
Sprint retrospective
Daily scrum meeting Roles: Product owner
Team Artifacts: Ceremonies: Product backlog
Sprint backlog
Burndown charts Sprint planning
Sprint review
Sprint retrospective
Daily scrum meeting Ceremonies: Artifacts: Product owner
Team 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 www.scrumalliance.org A sample product backlog 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 Where to go next www.mountaingoatsoftware.com/scrum
scrumdevelopment@yahoogroups.com Scalability Typical individual team is 7 ± 2 people
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 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 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 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 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 99.999% uptime requirements
the Joint Strike Fighter Video game development
FDA-approved, life-critical systems
Satellite-control software
Handheld software
Mobile phones
Network switching applications
ISV applications
Some of the largest applications in use An Introduction
to Scrum <your name here>
<date> Copyright notice You are free:
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 http://creativecommons.org/licenses/by/3.0/ Sprint retrospective Periodically take a look at what is and is not working
Typically 15–30 minutes
Done after every sprint
Whole team participates
Product owner
Possibly customers and others 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 Putting it all together Image available at www.mountaingoatsoftware.com/scrum Scrum has been used by: Microsoft
Electronic Arts
Lockheed Martin
Capital One
BBC Intuit
Nielsen Media
First American Real Estate
BMC Software
John Deere
Lexis Nexis
Time Warner
Turner Broadcasting
Oce A sprint burndown chart Hours The sprint review Team presents what it accomplished during the sprint
Typically takes the form of a demo of new features or underlying architecture
2-hour prep time rule
No slides
Whole team participates
Invite the world The daily scrum Parameters
Not for problem solving
Whole world is invited
Only team members, ScrumMaster, product owner, can talk
Helps avoid other unnecessary meetings Scrum origins Jeff Sutherland
Initial scrums at Easel Corp in 1993
IDX and 500+ people doing Scrum
Ken Schwaber
Scrum presented at OOPSLA 96 with Sutherland
Author of three books on Scrum
Mike Beedle
Scrum patterns in PLOPD4
Ken Schwaber and Mike Cohn
Co-founded Scrum Alliance in 2002, initially within the Agile Alliance We’re losing the
relay race Hirotaka Takeuchi and Ikujiro Nonaka,
“The New New Product Development Game”, Harvard Business Review, January 1986. Contact information Presentation by: Mike Cohn
(720) 890-6110 You can remove this (or any slide) but you must credit the source somewhere in your presentation. Use the logo and company name (as at bottom left, for example) or include a slide somewhere saying that portions (or all) of your presentation are from this source. Thanks. 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 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
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)
Code the user interface (4)
Write test fixtures (4)
Code the foo class (6)
Update performance tests (4) No changes during a sprint Plan sprint durations around how long you can commit to keeping change out of the sprint Change Roles Start / Stop / Continue Whole team gathers and discusses what they’d like to: Start doing Stop doing Continue doing This is just one of many ways to do a sprint retrospective. Scrum framework Roles: 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. <you>
<date> Presented by An Introduction to Scrum The team Typically 5-9 people
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 Everyone answers 3 questions These are not status for the ScrumMaster
They are commitments in front of peers What did you do yesterday? 1 What will you do today? 2 Is anything in your way? 3 Source: “The New New Product Development Game” by Takeuchi and Nonaka. Harvard Business Review, January 1986. Rather than doing all of one thing at a time... ...Scrum teams do a little of everything all the time Requirements Design Code Test Project noise level The Agile Manifesto–a statement of values Process and Tools Individuals and Interactions over Following a Plan Responding to Change Source: www.agilemanifesto.org Comprehensive Documentation Working Software over Contract Negotiation Customer Collaboration over The sprint goal A short statement of what the work will be focused on during the sprint Support features necessary
for population genetics studies. Support more technical indicators than company ABC with real-time, streaming data. Make the application run on SQL Server in addition to Oracle. Scaling through the Scrum of scrums Scrum Sprint
2-4 weeks Sprint backlog Potentially shippable
product increment Coupons 24 hours Sprint
goal Sprint
backlog Business conditions Team capacity Product backlog Technology Current product Scrum of scrums of scrums “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.” Scrum in 100 words over Sprint Goal Coupons Return Cancel Gift wrap Productbacklog Sequential vs.
overlapping development Product backlog
Sprint backlog
Burndown charts Sprint planning
Sprint review
Sprint retrospective
Daily scrum meeting Product owner
Team Scrum framework Roles: Artifacts: Ceremonies: Product backlog
Sprint backlog
Burndown charts Scrum framework Ceremonies: Sprint planning
Sprint review
Sprint retrospective
Daily scrum meeting Product owner
Team Scrum framework Database Application Database Application Life Sciences By:
Full transcript