Posts Tagged ‘Scrum’


Order Takers versus Advisers

In consulting and outsourcing should we act as order takers or as advisers to our clients? Advisers make observations, provide analysis results, and offer recommendations to the client, which are sometimes not what the client wants to hear. Order takers only provide specifically what the client asks for. As an example, consider a financial planner […]

Scaling Up From One Developer

I have noticed a common problem afflicting small development teams formed to make significant enhancements to an application that was previously maintained by just one developer. Both the original maintenance developer and their management are accustomed to essentially solo development and this culture spills into the enhancement work. Development is treated as individual efforts rather […]

The Mindset of a ScrumMaster

I have been familiar with the Scrum method for developing software for a number of years. Scrum is a simple tool: it defines just a few meetings, artifacts, and roles. So the basic mechanics of scrum are easy to pick up. Using Scrum to its fullest potential, however, requires a much deeper understanding. One area […]

My Definition of Done

I recently wrote about why you need a definition of done, and it only seems logical to follow this up by presenting what I use for a definition of done for developing software. I use two guiding principles as the basis for constructing my definition. Potentially releasable: Ideally the software can be released (or shipped) […]

Why You Need a Definition of Done

Whether you are working on a small task or a large project, do you and your team have a clear understanding of what it takes to complete a piece of work? The Scrum method of software development calls this Definition of Done and touts this as a critical practice for high-performing teams. While I have […]