View
218
Download
0
Category
Preview:
Citation preview
Slide 1
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
Slide 2
Agenda A Brief Overview
Scrum Basics
Key Scrum Artifacts
User Stories
Implementing Scrum
2v.6.0 Copyright - Looking Glass Development, All rights reserved.
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
Slide 3
A History Lesson In the beginning there we projects, but
no scientific management.
In the 1950s the engineering world gave us the profession of project management.◦ Discipline
◦ Repeatability
◦ Not real flexible
◦ And the performance…
3v.6.0 Copyright - Looking Glass Development, All rights reserved.
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
Slide 4
4v. 6.0 - © Copyright and all rights reserved – Looking Glass Development, LLC.
1996
2002 & 2009
1996
1996
1996
2002 & 2009
2002
2002
2009
2009
0
10
20
30
40
50
60
1994 1996 1998 2000 2002 2004 2006 2008 2010 2012
Project Results
Successful(%) Challenged(%) Failed(%)
Year Successful(%) Challenged(%) Failed(%)
1994 16 53 31
1996 27 33 40
1998 26 46 28
2000 28 49 23
2002 28 49 23
2004 29 53 18
2006 35 46 19
2008 32 44 24
2010 37 42 21
2012 39 43 18189
45
56
58
59
222
63
84
71
74
1996
2002
2004
2010
2012
Cost & Schedule Overruns
Schedule(%) Cost(%)
74%
69%
2010 2012
Requirements
Completed
Project Results
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
Slide 5
Challenged 57%
Success14%
Failed 29%
5v.6.0 Copyright - Looking Glass Development, All rights reserved.
Waterfall Agile
Success 42%
Challenged 49%
Failed
9%
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
Slide 6
Time Cost
Scope Quality
Risk/Reward
6v.6.0 Copyright - Looking Glass Development, All rights reserved.
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
Slide 7
3 Major Types of Methodologies Waterfall (SDLC the most common type)◦ Oldest◦ Good for non-changing requirements
Spiral◦ All about prototyping◦ Can imbed other methodologies
Agile◦ Is Incremental, focuses on short feedback cycles.◦ 16+ different methodologies including XP, Scrum,
Kanban & APM.◦ Requires most experience & integration of team
7v.6.0 Copyright - Looking Glass Development, All rights reserved.
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
Slide 8
8v.6.0 Copyright - Looking Glass Development, All rights reserved.
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
Slide 9
9v.6.0 Copyright - Looking Glass Development, All rights reserved.
Complicated
Simple Complicated
Complex
Anarchy
Far From
Agreement
Close to
Agreement
Close to Certainty Far From Certainty
Requir
em
ents
Technology
People
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
Slide 10
10v.6.0 Copyright - Looking Glass Development, All rights reserved.
DesignAnalyze
CodeTest
Release
Pla
n
Revie
wAnalyze
DesignCodeTest
Release
Pla
n
Revie
w
Analyze
DesignCodeTest
Release
Pla
n
Revie
w
Analyze
DesignCodeTest
Release
Pla
n
Revie
w
Analyze
DesignCodeTest
Release
Pla
n
Revie
w
Plan Design Code Test Release
Working software is available
Scrum
Waterfall
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
Slide 11
Deliverable 1
Option 1 A A
Option 2 A C A
Deliverable 2
Option 1 B B
Option 2 B B C
Deliverable 3
Option 1 C C
Option 2
11v.6.0 Copyright - Looking Glass Development, All rights reserved.
• In Option 1 the best resource for the deliverable attempts to do each task for the feature and nothing gets delivered.
• In Option 2resourcing is applied based upon availability and two features are delivered.
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
Slide 12
12v.6.0 Copyright - Looking Glass Development, All rights reserved.
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
Slide 13
The Beginning of Agile February, 2001 in Snowbird, Utah
13v.6.0 Copyright - Looking Glass Development, All rights reserved.
Kent Beck Mike Beedle
Arie van Bennekum Alistair Cockburn
Ward Cunningham Martin Fowler
James Grenning Jim Highsmith
Andrew Hunt Ron Jeffries
Jon Kern Brian Marick
Robert C. Martin Steve Mellor
Ken Schwaber Jeff Sutherland
Dave Thomas
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
Slide 14
Agile Development Values... Individuals & Interactions OVER Processes & Tools.
Customer Collaboration OVER Contract Negotiations.
Responding to Change OVER Following a Plan.
Working Software OVER Comprehensive Documentation.
14v.6.0 Copyright - Looking Glass Development, All rights reserved.
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
Slide 15
The 12 Principles of Agile Software 1. Our highest priority is to satisfy the customer through early and continuous delivery of
valuable software.
2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
4. Business people and developers must work together daily throughout the project.
5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
7. Working software is the primary measure of progress.
8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
9. Continuous attention to technical excellence and good design enhances agility.
10. Simplicity--the art of maximizing the amount of work not done--is essential.
11. The best architectures, requirements, and designs emerge from self-organizing teams.
12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
15v.6.0 Copyright - Looking Glass Development, All rights reserved.
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
Slide 16
The Heartbeat of Agility
16v.6.0 Copyright - Looking Glass Development, All rights reserved.
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
Slide 17
Needed
Features, 36%
Rarely Used
Features, 19%
Never Used
Features, 45%
Features
17v.6.0 Copyright - Looking Glass Development, All rights reserved.
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
Review Questions:
1. In what decade was most of the science of project management first created?
A. 1940s
B. 1950s
C. 1960s
D. 1970s
2. What is the average success rate for waterfall projects?
A. 14%
B. 18%
C. 25%
D. 33%
3. What is the average success rate for Agile projects?
A. 25%
B. 33%
C. 42%
D. 55%
4. Which of the following is NOT one of the three major development
methodologies?
A. Agile
B. Compression
C. Spiral
D. Waterfall
5. Which of the following is a problem caused by using a waterfall methodology?
A. Requirements are allowed to flex and adapt to the needs of the
stakeholders
B. Stakeholders are constantly able to see working versions of the product of
the project
C. Stakeholders commonly expect to work with the team on a daily basis to
deliver the project results
D. The process gives the appearance that all the requirements are accurately
defined at the beginning of the project with the expectation of little or no
changes throughout the project
6. Which of the following kinds of projects are best suited to take advantage of Agile
development?
A. Disorganized projects
B. Simple projects
C. Large projects
D. Complex projects
7. Which of the following is a term used to denote an organization’s partially
finished goods waiting for completion and eventual sales, or the value of these
items?
A. Work in process
B. Work in progress
C. Goods in process
D. All of the above
8. Which of the following core Agile values is not correct?
A. Teams & interactions over processes & tools
B. Responding to change over following a plan
C. Working software over comprehensive documentation
D. Customer collaboration over contract negotiations
9. What percentage of software features are never used?
A. 35%
B. 40%
C. 45%
D. 50%
Answer Key:
1. B
The science of project management was first formally created by the U.S. Air
Force, U.S. Navy, Dow and Dupont chemical companies during the 1950s.
2. A
Only about 14% of waterfall projects are deemed successful. 57% are challenged
and 29% are deemed failures.
3. C
Agile development has a success rate of 42% with 49% of projects being
challenged and 9% failed.
4. B
The three (3) major development methodologies include:
- Waterfall
- Spiral
- Agile
5. D
A key concern with using the waterfall methodology is that it often gives the
appearance that all the requirements are accurately defined at the beginning of
the project with the accompanying expectation of little or no changes throughout
the project.
6. D
Agile development is most effective at managing complicated and/or complex
projects.
7. D
In Agile development it is most commonly called Work in Progress, or WIP, but it
can also be called Work in Process or Goods in Process.
8. A
The four core values for Agile development include:
- Individuals & interactions over processes & tools
- Customer collaboration over contract negotiations
- Responding to change over following a plan
- Working software over comprehensive documentation
Recommended