Here is the deck from my Agile2014 talk on why many folks are struggling to adopt agile in larger, more complex enterprises. The presentation explores many themes persistent on this blog. Why agile works, why agile fails, what gets in the way, and how to systematically and pragmatically begin to refactor your legacy organization into an effective agile enterprise? If you came to the talk, I appreciate it. If you have any questions, please let us know. Thanks! Why Agile Is Failing in Large Enterprises, And What You Can Do About It from Mike Cottmeyerread more
LeadingAgile takes the mystery out of leading an agile transformation. We can explain why you may have struggled with agile in the past and what you can do differently next time to get better results. We believe in safe, incremental, pragmatic change and we are passionate about improving the business drivers executives repeatedly tell us are behind their desire to adopt agile in the first place.
Agile tends to focus on adaptability, but predictability is most often cited as the reason for an agile transformation.
As organizations scale, product quality often suffers. Agile focuses on quality from requirements through implementation.
Many organizations struggle with 18 month delivery cycles. Agile helps your team accelerate time to market and revenue.
Cost savings are tough to promise, but agile can help make sure you are only spending money on the features most likely to generate revenue.
the road map
Executives hire us because we have a credible point of view and a plan. We don’t start with culture and we don’t leave it up to you to figure out everything by yourself. We work with your team to develop a scaled agile delivery model specific to your organization, a pilot strategy to exercise the model and validate any assumptions, and a transformation plan for leading and sustaining change.
We offer a package of coaching, training, and staff augmentation services wrapped within our cutting edge framework for leading large scale enterprise agile transformations. Our Compass and Our Roadmap make all the difference in how those services are brought to bear within your organization. Our team is always focused on business outcomes and leading sustainable change.
Take a look around and see what we have to offer.learn more
let your journey begin...
If you’re ready to get started, or even if you’d just like more information, the first step is to reach out and let us know you’d like to talk. Our team will setup a quick call to learn more about your organization and what you’d like to accomplish. Next we’ll put you on the phone with Mike or Dennis to dive a little deeper. If we both think their is an opportunity to help, next step is to get in a room and talk.
The people that bring it all together.
companies we have guided
latest field notes
The LeadingAgile Blog
Lots has been written about backlog refinement (what we in the US used to call grooming), and a lot of it is good. There is lots to say about this practice. However, I’ve not seen any treatment on whether you should do it differently for your initial backlog. Therefore, I’m setting out in this post and in the next to answer these questions: How do you refine and estimate the initial backlog? How do you refine and estimate additional stories or subsequent backlogs for work that comes along later? Wouldn’t those approaches be the same? Usually, when I spin up…read more
What is the ROI of Your Event? Now that I’ve had a week to reflect and let the experience sink in, I wanted to share my thoughts of our first official Baltimore Lean Coffee event. I’ve participated in ALN DC events and even helped organize a PMI Agile meetup. So, where did our new event fall on a scale compared to the others? Did I feel like attendees received value and did I feel like we got a good return on our investment? Let me give a little comparison. Lots of effort – Too much process – Formal – Minimum ROI…read more
Validation is an engineering activity. In many ways it’s very much how engineers tell a product, “you’re awesome!” Unfortunately, many people don’t really understand what engineering validation really is. They think it’s something that happens at the end of all the other work. Often people who don’t understand validation think it’s performed on the finished product. Specifically that it’s only performed on the finished product in the form of “testing.” Yes, you test the product at the end, but how do you know the product will work when placed into service in the users’ environments? As they intended to use…read more
I started out this blog post writing about shared accountability for agile program teams. Accountability is an interesting, large topic that gets skipped over quite often in our agile community. In fact, I found, in my writing, a realization that we don’t have a great track record for defining it. So here’s my take. Caution! I am trying to pair down my mindmap of points to discuss in this blog. Apparently, I am not doing a great job, and I’ll own that. The way that I’ll own it is by committing to write to conclusion about: •What accountability means…read more