In my previous post, Replacing Backlog Grooming, I wrote about leveraging a Product Owner (PO) Team instead of the “Scrum” team in Progression Workshops (backlog grooming). To clarify, the members of the PO teams are mainly populated by a Product Owner (Product Lead) and facilitator (could be a Scrum Master), but from there we’ll include others like a development lead, a testing lead, and an architect. We use the team construct over a single person because we’re operating at scale, with multiple delivery teams. The Leads and Architects are thinking bigger-picture strategy and are aware of external dependencies that need to be…read more
Adopting agile is never about about adopting agile practices. It’s not even about adopting an agile culture. While those things are important, if you don’t achieve better business outcomes, adopting agile is not worth the investment. Your journey toward greater business agility starts by identifying what outcomes are most important to your company’s success. This knowledge helps you lay a foundation for making decisions about how to tailor your approach and guide your transformation to measurably show progress toward your critical business objectives.
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 LeadingAgile compass helps us visualize what your company values from a planning perspective and compare that against what your customer values from a delivery perspective. Many organizations find themselves oriented in opposition to the needs of their customers, and when they try for greater alignment, they find themselves out of sync with the processes governing fiscal responsibility in their own organization. Getting your company and your customers in alignment is a process that can be planned and executed in a measurable and controllable way.
the road map
We don’t start with culture and we don’t leave it up to you to figure out everything by yourself. We help you develop an organizational structure, a governance model, and a metrics strategy designed to guide all your transformation activities. We help you craft a pilot approach to exercise the strategy, validate the framework, and challenge any early assumptions. Metrics guide and inform the outcomes and we prepare your team to sustain the new organization after the coaches are gone.
LeadingAgile offers training, but we are not a training company. Engagements are always a mix of consulting, classroom training, hands-on coaching, and sometimes even staff augmentation delivered exclusively in the context of our cutting edge framework for leading large-scale enterprise agile transformations. Our Compass and Our Roadmap make all the difference in how our services are brought to bear within your organization. Our team is consistently focused on business outcomes and can tie every day-to-day activity to specific business goals we are helping you achieve.
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, what you’d like to accomplish, as well as your budget and how soon you’d like to get started. Next we’ll put you on the phone with Mike or Dennis to dive a little deeper into your goals and current challenges. If we both think there is an opportunity to help, next step is to get in a room and talk. We'll fly almost anywhere for a face-to-face meeting to begin building our relationship with your team.
The people that bring it all together.
companies we have guided
latest field notes
The LeadingAgile Blog
Sustainable pace is all about keeping positive energy flowing on your teams. It doesn’t mean taking it easy. It doesn’t mean struggling to achieve a constant pace. It means expending your energy in a positive way, on the right things, for the right amount of time. It means allowing you and your team to feel the exhilaration of completing valuable work. And it means stopping at the right time to allow that exhilaration buoy your team along so they can all reach the finish line together. This week, I was re-reading one of my favorite books called “What I Talk…read more
The Problem Over the last few years, I’ve worked with numerous teams. One thing they all struggle with is backlog grooming. They all know they need to do it. Unfortunately, they all seem to struggle with when to do it or who should do it. The most interesting struggle with backlog grooming happened two years ago. The “story time” meetings took place at the beginning of a month-long sprint. The manager stated, the work to be completed and delivered during that sprint had to be refined within the same sprint. This helped explain why the team thought they needed month-long sprints. When…read more
As usual… I’ve gotten a little sidetracked on my Agile 101, 102… series of posts. I’ve got the 201 post half finished, but haven’t been able to spend the time getting over the hump. That said, I want to divert just a little and talk about agile in general, explore some of what it is, and a little about where it’s going. I think we have created a bunch of confusion in the marketplace. I am under no illusions that this post will be the definitive explanation, but I spend a TON of time talking to people and level setting…read more
Code Smell A code smell is a hint that something may have gone wrong somewhere in your source code. Martin Fowler included the term smell in his book Refactoring way back in 2000, referring to something that may not be right. Just because something smells, it does not mean there is a problem; it does mean, however, that there should be further investigation. Agile Smell Similar to a code smell, Agile smell is a hint that something may have gone wrong somewhere in your Agile practices. Be it a variation in the length of iterations, volatility in velocity, or having teams where the…read more