a blogblogest 2013

Field Notes

Posts by Dennis Stevens

Having the Right Answer is Not Enough


I’ve often been involved in conversations exploring the right way to build software in large organizations. Very commonly, clients are exploring Agile versus Waterfall. Recently, at a significant conference in our industry various people were representing different “best ways” to build software. Different people held options like Scrum, XP, SAFe, LeSS, and Disciplined Agile Delivery […]

read more

How to Achieve Shared Understanding When Scaling Agile


Agile practices as described in the literature are suitable for small co-located teams focused on a single product. These small co-located teams quickly and efficiently establish a shared understanding of a project, the customer and the architecture within which they are working. As organizations scale Agile, teams aren’t working in the same room, they are […]

read more

Stop Writing Code You Can’t Yet Test


Most of the organizations we engage with have more work to do than they can possibly get done. So, developers are writing code as fast as they can to get done trying to maximize their capacity. Typically, we see developers running way ahead of testing. Often, testing is still working on the prior release while […]

read more

Agile vs. Waterfall


Agile versus Waterfall These words have become completely overloaded when discussing product development. Lots of conversations about helping organizations improve their product development processes go sideways based on individual perspectives about the meaning of Waterfall and Agile. At this point these words don’t provide a distinction that is helpful when we are trying to figure […]

read more

Making Work Ready


Teams moving to Agile often abandon planning and documentation. Some coaches claim that any planning or estimating is waste. Some teams hear that we don’t do any planning or documentation in Agile. The concept of not developing “The Plan” upfront comes to mean we don’t plan in Agile and we don’t document in Agile. Planning […]

read more