Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Scrum in 100 Scrum is an agile process that allows us to words delivering the highest business focus on
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.
Mountain Goat Software, LLC
Scrum origins
Jeff Sutherland Ken Schwaber
Initial scrums at Easel Corp in 1993 IDX and 500+ people doing Scrum ADM Scrum presented at OOPSLA 96 with Sutherland Author of three books on Scrum Scrum patterns in PLOPD4
Mike Beedle
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
Characteristics
Self-organizing teams Product progresses in a series of two
week 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 others Mountain Goat Software, include XP, Kanban, LEAN LLC
over
over
over
over
Scrum
Sprint goal Return Cancel Return Gift wrap Coupons Gift wrap Cancel Product backlog
Mountain Goat Software, LLC
24 hours
Sprint 2 weeks
Sprints
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.
Scrum framework
Roles
Product
owner ScrumMaster Ceremonie Team s Sprint planning Sprint demo Sprint retrospective Daily scrum Artifacts meeting Product backlog Sprint backlog Burndown charts
Mountain Goat Software, LLC
Product owner
Beresponsible for the profitability of the Prioritize features according to market Adjustfeatures and priority every
iteration, as needed
The ScrumMaster
Responsible for enacting Scrum values
and practices sprints
With team consensus, sets velocity for Removes impediments Ensure that the team is fully functional
and productive and functions
Mountain Goat Software, interferences LLC
Enable close cooperation across all roles Shield the team from external
The team
administrator)
Scrum framework
Roles
Product
owner ScrumMaster Ceremonie Team s Sprint planning Sprint demo Sprint retrospective Daily scrum Artifacts meeting Product backlog
Mountain Goat Software, LLC
Sprint prioritization Analyze and evaluate product backlog Select sprint goal Sprint planning
Sprint goal
sprint goal (design) Create sprint backlog (tasks) from product backlog items (user stories / features) Estimate sprint backlog
Sprint backlo g
Sprint planning
Code the middle tier (8 hours) Code the user interface (4) Write test fixtures (4) Code the foo class (6) Update performance tests (4)
Definition of Done
Code checked in Successful build Pass all automated unit and
All manual tests executed and passed Complete Documentation Accepted by the product owner
Mountain Goat Software, LLC
No discussions of issues until breakouts Whole world is invited Only team members, ScrumMaster,
meetings
1 2 3
during the sprint Typically takes the form of a demo of new features or underlying architecture Informal
demo) Mountain Goat Software, GXS will have a consolidated demo LLC
Sprint retrospective
Periodically take a look at what is and
is not working Typically 1530 minutes (Timebox it) Done after every sprint (or just before
planning)
Continue doing
Scrum framework
Roles
Product
owner ScrumMaster Ceremonie Team s Sprint planning Sprint review Sprint retrospective Daily scrum Artifacts meeting Product backlog Sprint backlog Burndown charts
Mountain Goat Software, LLC
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
Estimate
3 5 3 8
8 30 50
Story Points
Fibonacci Series 0,.5,1,2,3,5,8,13,20,40,100, inf Measures complexity, not Time
Support features necessary for population genetics Database Application studies. Make the application run on SQL Server in addition Financial services to Oracle. Support more technical indicators than company ABC with real-time, streaming data. Mountain Goat Software,
LLC
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
Mountain Goat Software, LLC
A sprint backlog
Code the user interface Code the middle tier Test the middle tier Write online help Write the foo class Add error logging
Tasks
Code the user interface Code the middle tier Test the middle tier Write online help
Tasks
Scalability
Typical individual team is 7 2 people Factors in scaling
Scalability comes from teams of teams Type of application Team size Team dispersion Project duration
person projects
Where to go next
www.mountaingoatsoftware.com/scru
m
Scrum and The Enterprise by Ken Schwaber User Stories Applied for Agile Software Mountain Goat Software,
LLC
Copyright notice
You are free:
to Shareto copy, distribute and transmit the work to Remixto 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).
Contact information
Presentation by: Mike Cohn mike@mountaingoatsoftware.c om www.mountaingoatsoftware.co m (720) 890-6110
You can remove this (or any slide) but you must credit the source somewhere in your d presentation. Use the logo an 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.