“Cash Can’t Code!” A colleague of mine (Chris Conrad) once told me this. The context of our discussion was about leveraging more resources to complete a large book of work by the end of the year. His main point is clear, having money to throw at the problem wasn’t going…
In this article I want to focus on the distinction between structural and instantiated dependencies. Most of the dependency management recommendations that you encounter deal with instantiated dependencies. However, the larger return on investment will be achieved by…
This blog post is the second in a series of three postings where I discuss eight of the reasons why stakeholders fail to attend sprint reviews and I offer suggestions for how to handle each cause.
In the first posting I focused on two reasons that I categorized as…
When considering your own organization ask yourself this question: “Are you working on too many projects at the same time?” If you are similar to most organizations that I visit, your answer will be a resounding yes! I’m having a hard time remembering the last time that…
Many companies operate with a project-based focus. When a new project is authorized, often times a new team is created to work on that project. Frequently the members of this new team may have limited prior experience working with one another. In those cases, we have to…
Sprints (or iterations if you prefer) are rooted in the concept of timeboxing, a time-management technique that helps organize the performance of work and manage scope. Each sprint takes place in a timeframe with specific start and end dates, called a timebox. Inside…
In previous blogs I introduced the concept of antifragile with a focus on how antifragility helps us deal with risks during agile development. I also blogged about how having flexible scope makes us antifragile. In this post, I explain why limiting work in process (WiP)…