class 2003-05-05

Who Reads Methodology and Why
Methodology is used mostly by planners and mostly for reference purposes
How Used
Training Planning
Selling
Roles
Reference 36%
A. Cockburn, Agile Software Development, Addison-Wesley, 2001
SCRUM
K. Schwaber and M. Beedle, Agile Software Development with Scrum, Prentice Hall, 2001.
RUP vs. XP
Attribute Time and Effort Allocation
Architecture
RUP (“Heavyweight”) 2 weeks-6 months
Stabilized during Elaboration phase
XP (“Lightweight”) 2 weeks - 2 months
SE 470 Software Development Processes
James Nowotarski 05 May 2003
Course Map
Week
1
2
3
4
5
6
7
8
9
10
11
Overview . Introduction . History Memorial Day Content . Rational Unified Process . Extreme Programming Implementation . Tools, Training, Roles . CMM, Metrics . Selection & Evaluation Briefings (Term Papers) Assignments Quizzes
15 minutes
30 minutes 45 minutes 10 minutes 45 minutes
• Term Project
• Quiz
10 minutes
40 minutes
Who Reads Methodology and Why
• Study of 1000 practitioners by Prof. Gezinus Hidding, Loyola University (mid-1990’s) • Practitioners seldom “read” the methodology • But when they do, it is to: – learn about something new (training) – look something up that they once knew or want to confirm (reference) • Different needs depending on role
30 minutes 45 minutes 10 minutes 45 minutes
• Term Project
• Quiz
10 minutes
40 minutes
Today’s agenda
Topic Duration
• Recap
• Who reads methodology and why • Deployment, adoption, use • *** Break • Deployment, adoption, use (cont.)
30 minutes 45 minutes 10 minutes 45 minutes
What is XP
Key Features • Pair programming • Test all the time
– unit testing – functional testing – continuous integration
• Short iterations, small releases
What is XP
Key Features
• • • •
40-hour week Coding standards Refactoring and evolutionary design Metaphor to aid in understanding the architecture • Only highest priority tasks are worked • Collective ownership
Today’s agenda
Topic Duration
• Recap
• Who reads methodology and why • Deployment, adoption, use • *** Break • Deployment, adoption, use (cont.)
15 minutes
When Not to Use XP
• Culture – Pointing the car – Big specification – Long hours • 20 or more programmers – though projects are emerging with up to 50 developers • More than 15 months’ duration • More than 50K source lines of code (SLOC) • Fixed price contracts • Technology barriers – Exponential cost curve – Long time needed to get feedback • Geographic separation • Architecture not well established • Developers are low quality and motivation
What is XP
Cost of change
y = axp
Req
Anal. Des. Impl. Test
Prod
Life cycle phase
What is XP
XP purports to change the curve so that the cost to find and repair software problems does not rise dramatically over time
Who Reads Methodology and Why
• Information needs of planners (“crucial target”) – need for speed – summary overviews of processes and artifacts • Information needs of doers – artifact samples – guidelines
15 minutes
30 minutes 45 minutes 10 minutes 45 minutes
• Term Project
• Quiz
10 minutes
40 minutes
Lightweight Methods
Approach XP
Crystal
References
Just enough to support functionality
Scope of Activities and Artifacts
Broad
Narrow Omits: • Business modeling • Deployment Small to Medium
roughly 30
Project size
Adaptive Software Development FDD Agile - General
What is XP
First Principles
• • • • •
Rapid feedback Assume simplicity Incremental change Embrace change Quality work
Artifacts
Small to Very Large
25-30 in small project roadmap
Roles
~ 30 (5 in small project 7 roadmap)
Today’s agenda
Topic Duration
• Recap
• Who reads methodology and why • Deployment, adoption, use • *** Break • Deployment, adoption, use (cont.)
J. Highsmith, Adaptive Software Development, Dorset House, 2000. S. Palmer, A Practical Guide to Feature-Driven Development, Prentice Hall, 2002. /home
Cost of change
Time
When to Use XP
• • • • • Small to medium sized teams Vague or rapidly changing requirements 2-10 programmers Responsible and motivated developers Not sharply constrained by existing computing environment • A reasonable job of executing tests can be done in a fraction of a day • Customer who understands and will get involved