Beruflich Dokumente
Kultur Dokumente
Copyright (c) 2006, Mountain Goat Software, Inc. and Innolution, LLC. All Rights Reserved.
We are about to cover a lot of ground... Please hold your questions until the end.
2 Dec 2009 KeyCorp Public Copyright (c) 2006, Mountain Goat Software, Inc. and Innolution, LLC. All Rights Reserved.
Spring 2008 started a local Agile Users Group that meets bi-monthly.
3 Dec 2009 KeyCorp Public Copyright (c) 2006, Mountain Goat Software, Inc. and Innolution, LLC. All Rights Reserved.
Agile
4 Dec 2009 KeyCorp Public Copyright (c) 2006, Mountain Goat Software, Inc. and Innolution, LLC. All Rights Reserved.
over
Process Process and and tools tools Comprehensive Comprehensive documentation documentation Contract Contract negotiation negotiation Following Following a a plan plan
5
over
over
over
Copyright (c) 2006, Mountain Goat Software, Inc. and Innolution, LLC. All Rights Reserved.
Let the people who add value use their full potential
Build Integrity in
Agile Process
The basic phases of an Agile development project are really no different from those of any other project. You still must define and initiate the project, plan for the project, execute the plan and monitor and control the results. What differs, however, is the manner in which these steps are accomplished.
7 Dec 2009 KeyCorp Public Copyright (c) 2006, Mountain Goat Software, Inc. and Innolution, LLC. All Rights Reserved.
Opportunities for
Strong partnerships between Business/Sponsor and Project Team
9 Dec 2009 KeyCorp Public Copyright (c) 2006, Mountain Goat Software, Inc. and Innolution, LLC. All Rights Reserved.
Scrum
10 Dec 2009 KeyCorp Public Copyright (c) 2006, Mountain Goat Software, Inc. and Innolution, LLC. All Rights Reserved.
What is Scrum?
The term scrum originally derives from a strategy in the game of rugby where it denotes getting an out-of play ball back into the game with teamwork. Scrum is a project management technique based on the principles of agile Scrum consists of processes and measurements to manage the development process.
11 Dec 2009 KeyCorp Public Copyright (c) 2006, Mountain Goat Software, Inc. and Innolution, LLC. All Rights Reserved.
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 Dec 2009 KeyCorp Public Copyright (c) 2006, Mountain Goat Software, Inc. and Innolution, LLC. All Rights Reserved.
Allows us to rapidly and repeatedly inspect actual working software. The business sets the priorities. Development teams self-manage to determine the best way to deliver the highest priority features. (They must agree on the definition of done) Every iteration (Sprint) anyone can see real working software and authorize a release of the demonstrated functionality or continue to enhance for another Sprint.
(Sprints are typically 2wks to 30 days)
13 Dec 2009 KeyCorp Public Copyright (c) 2006, Mountain Goat Software, Inc. and Innolution, LLC. All Rights Reserved.
Sprints
Scrum projects make progress in a series of Sprints (iterations). Target duration is no longer than 30 days:
The team can set the exact duration based on what works the
best for them.
A constant duration leads to a better rhythm (velocity). Do not miss the end of the sprint, the deadline is sacred.
Features are designed, coded, tested and documented during the sprint. Priorities can only change between Sprints, unless the Product Owner terminates the Sprint and starts a new one. Product is potentially shippable after each sprint.
14 Dec 2009 KeyCorp Public Copyright (c) 2006, Mountain Goat Software, Inc. and Innolution, LLC. All Rights Reserved.
Potentially shippable
At the end of each sprint, the team must produce a potentially shippable product increment High quality Tested Complete Done What it does it does well Potentially shippable shippable
15 Dec 2009 KeyCorp Public Copyright (c) 2006, Mountain Goat Software, Inc. and Innolution, LLC. All Rights Reserved.
Scrum Roles
16 Dec 2009 KeyCorp Public Copyright (c) 2006, Mountain Goat Software, Inc. and Innolution, LLC. All Rights Reserved.
Ensures that the team is fully functional and productive Enables close cooperation across all roles and functions and removes
Scrum Master
barriers Shields the team from external interferences Ensures that the process is followed. Participates in daily scrum, sprint review and planning meetings. Servant Leader.
Cross-functional, seven plus/minus two members Selects the sprint backlog Has the right to do everything within the boundaries of the project guidelines
Team
Dec 2009 KeyCorp Public
to reach the iteration goal Organizes itself and its work Demos work results to the Product Owner
17 Copyright (c) 2006, Mountain Goat Software, Inc. and Innolution, LLC. All Rights Reserved.
How Often
1 2 Times per Year 3 4 Times per Year Every Iteration Every Day
Who
Product Owner / Executive Product Owner & Team Product Owner & Team Team
Focus
Product Evolution Over time Features Features Tasks
18 Dec 2009 KeyCorp Public Copyright (c) 2006, Mountain Goat Software, Inc. and Innolution, LLC. All Rights Reserved.
w e i v r e v Sprint O
19 Dec 2009 KeyCorp Public Copyright (c) 2006, Mountain Goat Software, Inc. and Innolution, LLC. All Rights Reserved.
Daily Stand ups 15 min mtg in which team reports to each other: what they
did yesterday, what theyre working on today, whats in the way of their progress. This is NOT a status/problem solving mtg.
Sprint Review Review the sprint goal/deliverable with the product owner
to show accomplishments.
Sprint Retrospective Team meeting held at the end of each sprint to discuss
process improvement within the scope of the project
20 Dec 2009 KeyCorp Public Copyright (c) 2006, Mountain Goat Software, Inc. and Innolution, LLC. All Rights Reserved.
Color Key
21 Dec 2009 KeyCorp Public Copyright (c) 2006, Mountain Goat Software, Inc. and Innolution, LLC. All Rights Reserved.
s t c a f i t Ar
22 Dec 2009 KeyCorp Public Copyright (c) 2006, Mountain Goat Software, Inc. and Innolution, LLC. All Rights Reserved.
Summary of Artifacts
Note: Artifacts can be as simple as an excel doc through commercially available Agile software! The team chooses what they want to use. Product Backlog (All Requirements)
List of tasks to be addressed during the active sprint. Owned and updated frequently by the scrum team
Impediments log (Daily Standup Whats in my way?)
List of impediments identified by that team that require resolution No specific format is mandated for this, teams should determine what
works for them
Creation of additional artifacts becomes a matter of judgment and the requirements of your companys Project Lifecycle.
Dec 2009 KeyCorp Public Copyright (c) 2006, Mountain Goat Software, Inc. and Innolution, LLC. All Rights Reserved.
23
& g n i r u s M ea g n i r o t i n Mo Progress
24 Dec 2009 KeyCorp Public Copyright (c) 2006, Mountain Goat Software, Inc. and Innolution, LLC. All Rights Reserved.
Burndown Charts
Primary method of tracking progress A burndown chart shows how much work remains to be done. Agile focuses on remaining effort vs. completed effort.
Note: Recognize that things such as tracking Financials & Time reporting may still be required PM does that outside of the scrum process.
Burndown charts: Two types of charts: Show net progress Sprint Burndown - report on sprint Raise questions; they
progress against schedule.
dont answer them Facilitate early Product (release) Burndown discussions report on project progress against Make it impossible to hide the truth schedule.
25
Copyright (c) 2006, Mountain Goat Software, Inc. and Innolution, LLC. All Rights Reserved.
The value comes from the team discussing why it looks that way.
26 Dec 2009 KeyCorp Public Copyright (c) 2006, Mountain Goat Software, Inc. and Innolution, LLC. All Rights Reserved.
Hours
450
300
150
2 Sprints
5
27
Copyright (c) 2006, Mountain Goat Software, Inc. and Innolution, LLC. All Rights Reserved.
Wrap Up
28 Dec 2009 KeyCorp Public Copyright (c) 2006, Mountain Goat Software, Inc. and Innolution, LLC. All Rights Reserved.