Simple Checklist


Access Restricted

Don’t Go Here!

The idea of hybridizing agile evokes all sorts of responses ranging from “do” to “don’t:” (usually with more vehemence). The reaction to the Simple Checklist for Assessing Hybridizing Agile Frameworks or Techniques was no different.  For example, Anthony Mersinso stated, “It has been my experience that the driver for hybridization is ignorance or resistance to change.” John Voris suggested in a comment that acknowledging the usefulness of hybridization fosters experimentation. What neither of these two gentlemen suggested was that the principles in the Agile Manifesto should be ignored and that teams should be transformed into robots locked into ineffective processes. The Simple Checklist spelled out a list of reasons that when all of them were satisfied (with perhaps one or two NAs), hybridization made sense. There are, however, a number of “no-go” scenarios that when recognized should immediately send coaches and practitioners running for the hills or at least for more advice!  The anti-hybridization simple checklist is: (more…)

So the answer is . . .

A minor update for Sprint Planning in late 2019!  At some point planning for planning needs to give way to planning.  Planning identifies a goal and helps to envision the steps needed to attain that goal. In Agile, the planning event also sends a message about the amount of work a team anticipates delivering in an iteration. While every team faces variations based on context and the work that is in front of them, a basic planning process is encapsulated in the following simple checklist. (more…)

Audio Version on SPaMCAST 143

I asked many of my colleagues what they thought were the precursors to beginning a CMMI change program. Almost to a person, they began their list with senior management support, which makes sense as the CMMI has become the top-down process improvement framework of choice, and a prominent attribute of top-down change programs is the need for explicit senior management support. (more…)