As a consultant, I get to see a lot of different organizations and work with a variety of teams. By now, virtually everyone has at least heard of agile and read the manifesto. We also seem to have, in technology adoption terms, crossed the chasm, and so adoption by more traditional, sometimes slower moving, global scale organizations is well under way. Agile has finally been vetted by the early adopters and is now becoming mainstream. I, like others, talk about the difference between “doing Agile” and “being agile”—differing the big “A” agile and the little “a” agile is intentional[BC1] . From…read more
Adopting agile is never 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.
As companies grow sometimes they slow down and lose the ability to innovate. Agile can help you get back your competitive edge.
Delivering on time is only important if you are delivering the right product. Agile can help you get the feedback you need.
We start by helping you take a look at what your company values from a planning perspective and comparing that against what your customer values from a delivery perspective. Organizations often find themselves operating in ways that don’t align with the goals of their customers. They might try to adopt agile to get things in sync, but end up out of alignment with how the rest of their company does business. Getting everyone working together is a process that can be planned and executed with clearly defined goals and measurable outcomes.
Far too often agile is sold as a predefined set of roles, artifacts, and ceremonies, and when those roles, artifacts, and ceremonies don’t work in your organization, it’s somehow your fault. The problem is that adopting agile is more about creating the conditions for agile to thrive rather than simply teaching people a new process or a new way of thinking. Adopting agile is about forming teams, building backlogs, and regularly producing working tested product increments. Transformation is about systematically removing barriers to making that happen.
Making the journey involves defining a team based organizational structure, a governance model to coordinate value, and a metrics strategy to guide and shape your transformation activities. We help you craft a pilot approach to exercise the structure, validate the framework, and challenge any assumptions made during planning. Metrics guide and inform our progress and help to shape the remainder of the transformation. Finally, we prepare your team with the knowledge and skills necessary to sustain the changes after our consultants have moved on.
LeadingAgile facilitates the process by providing a unique blend of service offerings designed to help you define, implement, and sustain your agile transformation. Consulting and Media provide the foundation to implement the LeadingAgile change management approach. Training and Talent help you build the necessary infrastructure to find, hire, and develop your people as the organization grows. Studios and Labs work side by side with you to sustain the change, build products, and create innovative new solutions for your market.
Our consultants will guide your company along the path to agility.learn more
From principles to practice, training helps guide your journey with agile.learn more
Acquiring and hiring the best talent is a challenge for any size organization.learn more
From vision to release, we help organizations create new products with speed and agility.learn more
Companies know they need a strong brand. Sometimes they need help building one.learn more
Innovation labs fuel your enterprise to create new products and services.learn more
latest field notes
The LeadingAgile Blog
You’d think that once I’ve blogged about something, everyone in the universe would be on board with it immediately. I mean, like, obviously, right? So, I wrote about the differences between information radiators and information vaults, and yet many people still assume that the use of tactile tools in a team room for process visualization conflicts with the use of electronic tools as systems of record, or that the two represent duplicate effort for the same value. Go figure. The bad news is a close family member had to get surgery recently. The good news is the hospital staff uses…read more
Where were we? Part 1: Command-line utilities and wrapper scripts Part 2: Guard (with Ruby) and SBT (with Scala) Part 3 (this): Infinitest (with Java and IntelliJ IDEA) In Part 1, we looked at some simple continuous checking solutions based on shell commands and wrapper scripts. In Part 2, we climbed up the pile of tools a bit and tried out guard (Ruby) and sbt (Scala). Now we’ll have a look at Infinitest for Java, with JetBrains IntelliJ IDEA. Infinitest was one of two continuous checking tools for Java that came out in the early 2000s; the other was Kent…read more
Where were we? Part 1: Command-line utilities and wrapper scripts Part 2 (this):Guard (with Ruby) and SBT (with Scala) Part 3: Infinitest (with Java and IntelliJ IDEA) In Part 1, we looked at some simple continuous checking solutions based on shell commands and wrapper scripts. Let’s start climbing the tool pile and see what we find. Guard for Ruby Guard exemplifies the next level “up” from plain command-line tools. In the Ruby world there are several continuous unit testing tools, of which two are significant and widely-used: ZenTest and guard. ZenTest is a suite of four tools, of which autotest…read more
Part 1 (this): Command-line utilities and wrapper scripts Part 2: Guard (with Ruby) and SBT (with Scala) Part 3: Infinitest (with Java and IntelliJ IDEA) Back in the day, we used to run compile, link, and execute steps separately and manually (after walking 15 miles to and from school in a snowstorm, uphill both ways). As integrated development environments (IDEs) matured, they wrapped those steps so that we needn’t do them manually over and over again. That was a great step forward, as we could maintain our focus on solving the problem at hand without being distracted by mechanical details…read more
Ready to Go?
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, Dennis, or Jim 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 to talk and explore our approach in more detail.