You will be hard-pressed to find any Silicon Valley companies these days that aren’t using the agile methodology. Agile has become the most popular approach to development because it’s effective , and it’s effective because it expects and orchestrates change throughout the development process . By the numbers, — but you already know that. 71% of organizations use agile today as opposed to the traditional waterfall approach
What you might not know is that agile often does not play nicely with enterprise processes. A gile scrum purists believe it is important to “never deviate from pure agile” and “never blend styles.” But those people probably haven’t had to make agile development work within the confines and constraints of a large company. That’s where the rubber meets the road and success requires the agility to take a blended approach, as opposed to Agile orthodoxy.
Comparing Methodologies
For the uninitiated, here’s the elevator summary on agile vs the waterfall method . Agile generally employs short (1–2 week) incremental development cycles called “sprints” to continuously release software and deliver business value in a short period, embracing changes along the way. Traditional software development uses a waterfall methodology, which starts with creating a detailed schedule, defining and freezing requirements, development, testing, then finally implementing — months or even years after capturing the initial requirements.
There are hybrid methods as well. For example, Disciplined Agile Delivery (DAD), is a blended Agile approach (with a fun acronym) where the team gets to choose what best practices they will implement within guidelines. DAD recognizes that not all projects, teams, stakeholders, and companies are alike — often requiring different methods to support effective project delivery.
Another notable example is Rapid Application Development (RAD). RAD and Agile share similar values with respect to flexibility, shorter delivery time, and high customer interaction . RAD is more prototype-driven , while Agile breaks down a project into features which are then delivered in various sprints over the development cycle. There are advantages and disadvantages to each. What’s important is flexibility (or agility) to accommodate the needs of the project and the client because real-world limitations sometimes necessitate a blend of traditional project management practices in order to be very successful.
What Enterprises Need
While large enterprises are now embracing collaboration, transparency, and rapid progress over perfectionism, they are generally more constrained than a truly pure Agile process allows. Enterprises need to consider timelines, fixed budgets, audits, and IT security requirements. Embracing a hybr id of the waterfall and agile methodologies allows teams to execute projects successfully , while accounting for all stakeholder demands and enterprise constraints .
One of the keys to a successful blended strategy is when and how you blend. Anyone familiar with cooking will find this concept very easy to understand. Have you ever tried to make hollandaise sauce? Timing and temperature and ingredient ratios are everything. Blended agile is a bit like that.
Project initiation , or how you start you r project, will w eigh heavily on the outcome. If you get it right, then so many issues are avoided. Rapid application development may be best suited for this phase , however, if you are digitaliz ing a well known process , th a n elements of the waterfall method are usef ul . Starting a new project with a high-level scope document, risk assessment, and discovery process (“Sprint 0”) supports the iterative agile process along the way. This is just one of many ways to pursue a blended strategy.
Originally published at https://10pearls.com on September 11, 2020.
