Agile Software Development
Автор: Alistair Cockburn /
CHAPTER 5. Agile and Self-Adapting Becoming Self-Adapting
-
Часть 4
-
Given the mid- and post-increment reflection workshops, I place less emphasis on having a post-project reviews. I feel that the time to reflect is during the project, when the reflection and discussion will do the project some good. After the project, it is too late.
Usually, I find that teams that run post-project reviews did not bother to reflect during the project, and suddenly wants to know how to do better for the next project. If you find yourself in such a meeting, put forward the suggestion that next time, you want to use incremental development, and hold postincrement reviews instead.
Nonetheless, it may be that the post-project review is the only time you get to make statements regarding the staffing and project management used. If this is the case, I suggest getting and using the book Project Retrospectives (Kerth 2001), which describes running a two-day post-project review.
If you hold a post-project review, think about who is going to make use of the information, and what they can really use, as they run their next project. You might draft a short (two-page) set of notes for the next project team to read, outlining the lessons learned from this project.
Of course, you might write yourself a one-page lessons learned reminder after each of your own increments, as a normal outcome of your reflection workshop.
A Reflection Workshop Technique
The tangible output of a mid- or post-increment reflection workshop is a flipchart that get posted on the wall in some prominently visible place and seen by the project participants as they go about their business.
I like to write directly onto the flipchart that will get posted. It is the one that contains the group memories. Other people like to copy the list from the scratched- and scribbled-on flipchart to a fresh sheet for posting. The people who created the one shown in Figure 3-10 decided to use sticky notes instead of writing on the flipchart.
A Sample Reflection Workshop Technique
There are several different formats for running the workshop, and for sharing the results (of course). I tend to run the simplest version I can think of. It goes approximately like this:
A Reflection Workshop
Hi, welcome to this workshop to reflect on how we can get better at producing our software. The purpose of this meeting is not to point fingers, to blame people, or to escape blame. It is to announce where we are getting stuck, and nominate ideas for getting past that stuckness.
The outcome of this workshop will be a single flipchart on which we'll write the ideas we intend to try out during the next increment, the things we want to keep in mind as we work. Let's break this flipchart into three pieces. On the left side, let's capture the things we are doing well, that we want to make sure we don't lose in the next increment.
On the right side, let's capture the new things we want to focus on doing.
On the supposition that the list of what we're doing right will be the shorter of the two, let's write down the major problems we're fighting with, halfway down the left side here (see Figure 6-1).
Let's start with what we're doing right. Is there anything that we're doing right, that we want to make sure we keep around for the next increment?
Figure 6-1. Sample poster from reflection workshop.
At this point some discussion ensues. It is possible that someone starts naming problems, instead of good things. If they are significant, write them down under the Problems section. Allow some time for people to reflect and discuss.
Eventually, move the discussion along:
All right, what are some of the key problems we had this last time, and what can we do to improve things?
Write as little as possible in the Problems section: write as few words as possible, and merge problems together if possible. The point of this poster is to post suggestions for improvement, not to focus on problems.
Collect the suggestions. If the list gets very long, question how many new practices or habits the group really wants to take on during this next period. It is sometimes depressing to see an enormous list of reminders. It is more effective to have a shorter list of things to focus on. Writing on a single flipchart with a fat flipchart pen is a nice, self-limiting way of handling this.
Periodically, see if someone has thought of more good things the team is doing that should be kept.
Toward the end of the workshop, review the list. See if people really are in agreement to try the new ideas, or if they were just being quiet.
After the workshop, post the list where everyone can see it.
At the start of the next workshop, you might bring in the poster from the previous workshop, and start by asking whether this way of writing and posting the workshop outcome was effective, or what else you might try.
Holding this meeting every two to six weeks will allow your team to track its local and evolving culture, to create its own, agile methodology.
The Value of Reflection
The article on Shu-Ha-Ri excerpted in Chapter 2 continues with the following very relevant discussion of reflection:
-
Навигация [ Часть 4. Глава 25. ]
Закладки
The complete discussion about when and where to apply concurrent…
After much coaching for six months, his programs still…
13. (FIRST TECHNIQUE). .. your sword now having bounced…
Using the planning game in this way, the sponsors can properly…
The main question is, if you were funding this project,…
The chart shows the state of the user stories being worked…
Types of Methodologies Rechtin (1997) categorizes methodologies…
Walk around your place of work. Notice · The convection…
1. Project name, job of person interviewed (the interviewee…
Crystal Clear is the most tolerant, low-ceremony small-team…
Accepting program modifications demanded by changing external…
The surprising thing about human success modes is how…
For us as designers, it was possible to express both propositional…
It follows that on the Theory Building View, for the…
Agility implies maneuverability, a characteristic that…
The group of 17 quickly agreed on those value choices.…
We see an example of needing these normalizing rituals in the…
Games are not just for children, although children also play…
Figure 4-1. Elements of a methodology. Roles. Who you…
The industry is littered with projects whose sponsors…