Agile Software Development
Автор: Alistair Cockburn /
CHAPTER 4. Methodologies And What Should I Do Tomorrow?
-
Часть 1
-
Start by recognizing that no single methodology definition can possibly suit all projects. Don't even think that the Rational Unified Process, Unified Process, or the Something Else methodology will fit your project out of the box. If you follow a methodology out of the box, you will have one that fits some project in the world, but probably not yours.
Practice noticing how the seven principles of methodology design relate to your project:
· Look for where your team could benefit from using warmer communications channels and where cooler ones are needed.
· Identify the bottleneck activities on your project.
· Track them as they change.
· Invent ways to utilize some other group's excess capacity to streamline the bottleneck group's work or to reduce uncertainty.
· Reduce the internal deliverables on your project:
· Arrange for higher-bandwidth communication channels between the developers and opportunities for rapid feedback, and you will find that some of the promissory notes are no longer really needed.
· Find the bottleneck activities, and see if you can trade efficiency elsewhere for increased productivity at the bottleneck station.
· Find a place where lightening the methodology would actually cause damage. Think about what might be an alternative.
· Review the list of purposes of a methodology. Evaluate the purpose of your group's methodology, and then rank its effectiveness with respect to that purpose.
· Practice naming the scope and elements of your methodology and other methodologies. Observe how much they differ due to addressing different scopes or different priorities.
· Look at the different methodologies in use on different projects, and evaluate them according to how they address their different project sizes.
· Experiment with the difference between problem size and project size.
· Can you think of a project that had more people than it needed?
· Can you think of a difficult problem that was turned into an easy problem through the application of some particular point of view?
Level 2 readers:
· Add these ideas to your bag of tricks.
· Learn where to apply, adjust, and drop them. Level 3 readers: See if you can explain these ideas to someone else.
-
Навигация [ Часть 1. Глава 22. ]
Закладки
Agility implies maneuverability, a characteristic that is…
For us as designers, it was possible to express both propositional…
Walk around your place of work. Notice · The convection…
The main question is, if you were funding this project,…
The industry is littered with projects whose sponsors did…
The chart shows the state of the user stories being worked…
The complete discussion about when and where to apply concurrent…
While writing, reading, typing, or talking, we pick up traces…
13. (FIRST TECHNIQUE). .. your sword now having bounced upward,…
Crystal Clear is the most tolerant, low-ceremony small-team…
The surprising thing about human success modes is how nebulous…
That it is people who design software is terribly obvious.…
Figure 4-1. Elements of a methodology. Roles. Who you employ,…
After much coaching for six months, his programs still…
Accepting program modifications demanded by changing…
On a new project, I would use Crystal Orange as a base methodology…
Using the planning game in this way, the sponsors can properly…
1. Project name, job of person interviewed (the interviewee…
We see an example of needing these normalizing rituals in…