Why Agility Matters: The Real Advantages of Agile Methodology.
For software development professionals, working with “agile” development methodologies (agile methods) such as Scrum or Kanban is an easy-to-understand and obvious choice. For business professionals who may not be experts in development practices, this may be less obvious, so we thought we’d take a few minutes to explain.
Twenty years ago, software developers invented agile methods, which have since become the dominant method used by technology firms. A number of methodologies preceded agile methods, most notably the “waterfall” process. To explain the value of agile, you need to understand the limitations of what it replaced.
The waterfall method follows a set path to defining, building, testing, and releasing software that includes distinct phases for:
Defining product requirements - the features and functions, as well as non-functional requirements such as scalability - that the software should support;
Creating designs for the product that meet the requirements;
Writing the code to support the requirements and designs;
Testing the product and fixing any problems - referred to as defects or “bugs” - in the software;
Releasing the software.
The waterfall process centers on a contract-like agreement among stakeholders regarding the requirements defined in phase one. All parties - the head of product is responsible for defining the requirements, the head of software development is responsible for writing the code, the head of quality responsible for testing the software, the head of marketing responsible for generating demand, the head of sales responsible for achieving a revenue target - would all (quite literally in many cases) sign off an agreement that the requirements were “right,” and everyone was committing to achieve their intertwined goals based on those requirements.
This forced the organization to stick to the agreed-upon requirements set out at the beginning of the project and NEVER make changes or additions to the plan along the way, otherwise those changes/additions would cause a release delay. Because waterfall prioritized bringing an entire product to market, it could require a year or more to complete a release.
During that time, the software release frequently underwent changes in response to shifts in the nature of the need being addressed. It causes the software release to not align with the actual need when the software is completed. For the software customer, this implies potentially waiting for many years to address critical business needs. For the development organization, this means continually introducing products to the market that do not genuinely meet customer needs or, in some cases, abandoning projects to avoid delivering a destined-to-fail product.
Agile methods break development down into smaller, shorter increments. All phases in the waterfall are completed, but on a MUCH smaller, more frequent basis. Under the most common version of agile development, called “Scrum”, product increments are anywhere from a week to four weeks, and, in my experience, two weeks seems most common. During that short interval, the team designs, builds, tests, and releases a small set of features so that, at the end of EVERY increment - referred to as a "sprint" - they can release the features developed during the sprint.
This reduced the delay between identifying a need and delivering functionality to address it. The result:
Faster delivery of value to customers;
Ability to improve features more quickly by listening to customers after they use a feature and incorporating improvements into subsequent sprints in an effort to optimize the customer experience;
Fewer products failing in the market;
Ability to release individual features without necessarily having to wait for a complete software release.
Read: What Are the 12 Principles of Agile Project Management?
Under the waterfall model, an architect and designer spend months creating a detailed plan for the house. This plan includes everything from flooring to countertops to paint colors. Then, the contractor begins building the house. It takes a year or more before you finally get to see it for the first time. But what if six months into the build, you discover you’re pregnant and should have added another bedroom? Should you have to wait until the house is finished and then build an addition? Or what if you decide that the shade of paint doesn’t quite look right? Shouldn’t you say something after the painters finish the first room instead of after they paint all the rooms?
With an agile approach, you’d see the house every week during development. So, looking at the hardwood flooring in your living room may prompt you to reconsider the paint color or bathroom tile choice. You would have an opportunity to adjust the plan. Also, look at the paint color after one room is painted and change your mind. You may need to pay extra to repaint that room, but at least you avoided having an entire house full of colors you dislike.
In summary, agile methodologies deliver to the businesses that use them:
A greater likelihood that your product actually addresses the needs of your customer, and you find a market fit;
Software that your customers enjoy using because you were able to listen to their feedback and improve incrementally.
In a no-risk discovery we look at your CRM, finance and operations systems and who owns each part, and show what a connected system would do differently. You pay only if you proceed. Or see how we approach it.
More on the same problem:
It needs an engaged business owner every sprint, which many organizations cannot sustain. Long-range cost and date forecasts are less precise, which makes fixed-price contracts awkward. Without discipline, flexibility becomes scope creep. And teams can mistake the ceremonies for the method, running every meeting while shipping nothing. Agile works where the requirements genuinely evolve; for a fully specified project with no uncertainty, its overhead buys little.
Two weeks is the most common choice, long enough to finish meaningful work and short enough to course-correct. One-week sprints suit teams with very frequent feedback and small stories; three or four weeks suit work with heavy testing or external dependencies. The length should stay fixed once chosen, because the predictability of a regular rhythm is where much of the benefit comes from.
By making the riskiest assumptions testable early. The first sprints build the parts most likely to be wrong, technically or commercially, and users or stakeholders see them within weeks. If an assumption fails, the cost is a sprint rather than a year. Waterfall discovers the same failure at the end, when the whole budget is spent. Agile does not remove risk; it moves the discovery of it to the cheap end of the project.
Attend the sprint review and give direct feedback on working software. Keep the backlog prioritized so the team always knows what matters most. Answer questions within a day rather than a week. Accept that scope will shift as learning arrives, and make the trade-offs when it does. The time commitment is a few hours a sprint, and it is the single biggest predictor of whether the project delivers something useful.
Yes, through a vendor that runs it and a business owner who participates. The owner's role is to prioritize, review and decide. The vendor supplies the process, the estimates and the engineering. What the small business should insist on is seeing working software every sprint and being able to change direction between sprints, because those two things are the benefit; the terminology is not.
"Something isn't working." "We're outgrowing our tools." "We're afraid to make the wrong move." No-Risk Discovery is a short, practical conversation that gets you clarity before you commit to anything big. We'll tell you if we're a fit. If we're not, we'll tell you that too.
Say who you are and ask. A person replies within one business day.