Mike Lyons argues that constraints like sprint deadlines and WIP limits fuel creativity and focus in Agile work, while unrealistic deadlines and rigid processes kill it. He shows how to identify risks early, assign owners to them, and run small experiments to turn threats into opportunities.
What's the difference between a good constraint and a bad constraint? While these might seem like obstacles, they can actually be powerful tools for innovation and creativity when they're approached correctly. I've worked on many projects with extremely tight deadlines and really tight budgets, and initially I used to get overwhelmed by that. But I've come to see these constraints as forcing functions really that help teams think creatively. Constraints help us focus on what's truly important. They force us to prioritize and be strategic in our decision making. For instance, in the Scrum framework, we have a constraint of delivering a potentially shippable increment at the end of every sprint. Well, this self imposed constraint helps the teams deliver value incrementally and it forces them to think creatively about how to break down work into manageable chunks. When we don't have constraints, particularly time constraints, we often fall victim to Parkinson's law, which states that work expands to fill the time allocated for its completion. Without a deadline as a constraint, there's no sense of urgency. And that can lead to procrastination or inefficient uses of time. What's the reason for your truancy? Just couldn't make it on time. Another example of this is the use of work in progress or WIP limits in Kanban. These limits restrict the number of tasks a team can work on simultaneously. By constraining the amount of work in progress, teams are forced to focus. They're forced to collaborate and complete tasks before starting new ones. And this seemingly simple constraint, it can lead to improved productivity, higher quality and faster delivery times. When teams manage risks and constraints well, they'll find innovative ways to deliver value within those limitations. This is where creativity thrives. For example, a tight budget might lead to the discovery of a more cost effective solution or the development of a minimum viable product that still meets core user functionality. That said, a project with zero constraints might find itself drifting aimlessly. Clark, I think we're lost. On the other hand, too many or unrealistic constraints can stifle the delivery of value or worse, put a project on a course that's doomed from the start. And I want to consider some examples of unrealistic constraints. Setting unreasonable deadlines that don't account for complexity or team capacity, mandating rigid adherence to a specific methodology without consideration for project context, or expecting comprehensive documentation for rapidly changing requirements. These types of constraints, they can be detrimental to a project's success. I want to talk about de risking and tracking risk. Exposure can be a type of constraint, and managing them is an essential part of how we use constraints creatively. So active de risking it involves identifying potential risks early in the project, prioritizing these risks based on their potential impact and likelihood, developing strategies to mitigate or avoid high priority risks, and continuously monitoring and reassessing risks throughout the project lifecycle. Tracking risk exposure? Well, that just means keeping a close eye on how our risk profile changes as the project progresses in Managing risk exposure is an ongoing process in Agile project management. Well, hey, got any suggestions on how we might do that? Mike? I'm glad you asked. It begins with regular risk identification sessions where teams openly discuss potential threats and opportunities. These risks are then quantified based on their probability and potential impact, often visualized using a risk matrix. For high priority risks, teams develop response strategies whether to avoid, transfer, mitigate or accept them, and they assign risk owners for monitoring. Continuous monitoring is key, with risks regularly reviewed in daily standups and sprint reviews, and overall exposure tracked using tools like risk burn down charts. Teams must be prepared to adapt their strategies as new risks emerge or existing ones evolve. Pro tip here, Transparency is crucial. I know sometimes with risks we get a little scared or nervous or whatever, but I found that the old adage bad news is like spilt milk. It doesn't get better with age holds true here. So make sure you're communicating your risk status and mitigation efforts clearly to all of your stakeholders. By actively managing risks, we can often turn potential threats into opportunities for innovation. For example, if we identify a risk related to a new technology integration, we might decide to run a small proof of concept project. This not only reduces the risk, but could also lead to discovering new and more efficient ways of working. Remember, risks and constraints are not roadblocks but guideposts. They direct our creation, creativity, focus our efforts, and often lead to the most innovative solutions.
