Agile Software Development
Автор: Alistair Cockburn /
CHAPTER 6. The Crystal Methodologies And What Should I Do Tomorrow?
-
Часть 1
-
Whether you use Crystal or not, increase morale and communication on your project so that the people trade information a little bit better. This applies for any base methodology.
Mistakes are discussed and suggestions for improvements have been made at every meeting, supporting the learning culture we are creating. The quality of code going live has improved greatly as the testing team has a veto power, to prevent bad code from going live (and this can be embarrasing). The SWAT team, dedicated to eliminating live bugs have also made great strides in responding to customer and call centre queries.
Focus time is still adhered to (and we still ring a bell every morning at ten). If I go a single day without these two hours I now start panicking, so useful has it proven to be.
Some things that did not survive was the habit of posting current priorities/ work progress on a board. Maybe interruptions are less of an issue now, as people work from home or maybe relationships between business owners and developers have stabilised. Maybe people are just lazy.
Most developers have a maximum of three tasks at any given time, except for the two key people working on the back end, who may easily have a list of 15 each. Moreover they are still interrupted by live issues, which interfere with their completion of tasks and lead to much frustration by other developers and business. The issue here is lack of skilled resources. It is the age-old problem that training employees to assist, while undoubtedly the right medium term solution, takes longer than simply doing it yourself. "
In those comments, what I notice with some satisfaction is that the team still uses the core elements of the process: heartbeat with learning, and have found ways to modify even that heartbeat to fit their needs.
I notice the discussion of talent and skills as being critical to the project, and I notice the drifting away from what probably was embellishment in the methodology.
Get your experienced developers at Level 2 in methodology design. If your project doesn't have anyone at that level, do two things: Study your base methodology.
Start holding reflection workshops so that someone Compare what your team is doing with the three gets up to Level 2 soon. methodology samples given in this chapter. Choose a few ideas to apply on your own project.
-
Навигация [ Часть 1. Глава 28. ]
Закладки
Agility implies maneuverability, a characteristic that…
Types of Methodologies Rechtin (1997) categorizes methodologies…
The group of 17 quickly agreed on those value choices. Developing…
The surprising thing about human success modes is how nebulous…
The chart shows the state of the user stories being worked on…
Crystal Clear is the most tolerant, low-ceremony small-team…
It follows that on the Theory Building View, for the primary…
We see an example of needing these normalizing rituals…
After much coaching for six months, his programs still…
In arguing for the Theory Building View, the basic issue…
Games are not just for children, although children also play…
The third problem is absence of feedback from the downstream…
Figure 4-1. Elements of a methodology. Roles. Who you employ,…
That it is people who design software is terribly obvious.…
Accepting program modifications demanded by changing external…
The main question is, if you were funding this project,…
While writing, reading, typing, or talking, we pick up traces…
Walk around your place of work. Notice · The convection…