Agile Software Development
Автор: Alistair Cockburn /
CHAPTER 5. Agile and Self-Adapting And What Should I Do Tomorrow?
-
Часть 1
-
Consider "agile" as an attitude, not a formula. In that frame of mind, look at your current project and ask, "How can we, in this situation, work in an agile way? "
"As you learn a technique, and as it asymptotically approaches your mental model of the technique as you see others practicing it, you can begin to reason about the technique. It seems the important questions to ask are:
1. How does this technique work?
2. Why does this technique work?
3. How is this technique related to other techniques that I am practicing?
4. What are the necessary preconditions and postconditions to effectively apply this technique in the combatitive situation? .. .
As you develop a reasonable repertoire of techniques that you can perform correctly, you will need to expose yourself to as broad a range of practitioners as possible. As you watch others, you need to ask and answer at least three questions:
1. Which other practitioners do I respect and admire?
2. How is what they do different from what I do?
3. How can I change my practice (both mental model and attempts to correspond to it) to incorporate the differences that I think are most important? .. . The questions you need to ask yourself about a competition in your post mortems are:
1. Were you able to control the pace and actions of your opponents.
2. Were you able to keep calm and make your techniques effectively with an unhurried frame of mind.
3. Does your competition look like those of the practitioners you admire. .. .
Throughout all of this, you must honestly evaluate the results of each 'test'. Cycle back to Shu through Ha and then Ri as you go down dead end paths. "
I couldn't say it better.
Look for how far you are from the sweet spots in your development team. See how creative you can be in getting closer to, or simulating them. Look for where your team can lighten its methodology. Look for where it is not-yet sufficient. Perform one project interview as described. Get several people to perform one each, and share results. Find the common thread in your interview results. Hold a one-hour reflection workshop within your project. As you encounter difficulty in this, reflect on which aspects of people are showing up; compare them to the list I gave in Chapter 3. Look for antidotes and extend my list. Post the reflection workshop flipchart, and check how many people ever look at it. See what it takes to hold a second one. Learn how to get people to complain less and make more positive suggestions a these workshops. . Develop yourself into a Level 2 methodology designer. Yes, it is part of your profession.
-
Навигация [ Часть 1. Глава 26. ]
Закладки
While writing, reading, typing, or talking, we pick up…
The main question is, if you were funding this project,…
On a new project, I would use Crystal Orange as a base methodology…
Accepting program modifications demanded by changing…
We see an example of needing these normalizing rituals in the…
Using the planning game in this way, the sponsors can properly…
Types of Methodologies Rechtin (1997) categorizes methodologies…
After much coaching for six months, his programs still…
The surprising thing about human success modes is how…
The third problem is absence of feedback from the downstream…
The industry is littered with projects whose sponsors did not…
That it is people who design software is terribly obvious.…
1. Project name, job of person interviewed (the interviewee…
The complete discussion about when and where to apply concurrent…
In arguing for the Theory Building View, the basic issue…
The group of 17 quickly agreed on those value choices. Developing…
Walk around your place of work. Notice · The convection currents…
13. (FIRST TECHNIQUE). .. your sword now having bounced…