To use Agile or not to use Agile, that is the question. Before addressing that question, some housekeeping: the terms methodology, framework, and even Agile itself are thrown around a lot often with several different meanings. For this post, I will be using the definitions described by the Agile Alliance, a non-profit founded by the original creators of Agile and authors of the Agile Manifesto.
Agile: The Agile Alliance describes Agile as a mindset saying that it is not a concrete set of rules but instead a collection of values or principles emphasizing iterative development cycles, flexibility and adaption to change, and the importance of continuous communication and collaboration throughout the project [1].
Agile Frameworks: These are guidelines providing more structured and concrete project development methodologies that can be implemented by project managers and development teams. This includes frameworks such as Scrum, Kanban, XP (Extreme Programming), AUP (Agile Unified Process), and FDD (Feature Driven Development) to name a few [1] [7].
Agile Methodology: It is an Agile framework that has been modified and adapted to work for a specific team or project [1].
For the sake of readability, from now on I’ll use the word Agile to refer to the collection of frameworks under the umbrella of Agile and specifically state if I am instead referring to the general principles of Agile or an Agile methodology.
Whether or not Agile would be a good fit for your project depends on a myriad of factors but the answers to the following questions can at least indicate whether implementing an Agile methodology could be beneficial for your project.
1: Can your project be developed iteratively?
One of the core aspects of Agile breaking down a project into smaller pieces that can be completed iteratively and creating a semi-working product throughout different stages of development instead of a single finished deliverable product at the end of the project [2].
However, some projects simply cannot be broken down into iterative sections, or have a strict progression of development that cannot be deviated from making iterative development difficult [3] [4].
Take for example the building of a skyscraper: there are strict regulations and safety standards that must be followed and the project must present detailed plans and get them approved before construction can even begin.
2: What are the requirements of your project like?
Another core aspect of Agile is not planning out details too far ahead, thus enabling teams to more quickly adapt to changes and make it feasible for changes to be made to project requirements late into the development of the project. This approach can be very efficient and cost-effective since development teams don't waste time and money doing extensive upfront project planning that ends up being scrapped halfway through development [2].
Additionally, this be incredibly valuable when exact project requirements are unknown or subject to change. This could range from projects where the customer isn’t sure of what they want to projects involving emerging technologies where what is cutting edge at the start of your project might be completely outdated by the time you're ready to implement it into your product [5] [2].
On the other hand, some projects have inflexible requirements or have well-defined requirements that are unlikely to change in which case using an Agile methodology may not be the best option.
Continuing with the skyscraper example; city regulations, safety standards, and structural considerations aren't subject to frequent change, and even small changes to the project requirements midway through would likely be incredibly costly both in terms of time and money [3].
3: How flexible is your project’s timeline?
The iterative approach of Agile encourages the continuous evolution of a project's requirements through testing and customer feedback. This can produce better products that are more tailored to the customer but can also make projects particularly vulnerable to what is referred to as scope creep or kitchen sink syndrome.
With Agile’s cycles of testing and feedback, it’s easy to get caught in a cycle of “yeah this is good but wouldn’t it be even better if we also added this”. As the scope of the project grows can result in extending the project’s timeline [6].
This risk can be mitigated by making sure everyone is aware of hard project deadlines and considering what effect additional features and changes might have before deciding to add them to the project requirements. However, it is still worth considering that this aspect of Agile provides much more frequent opportunities for your project to develop kitchen sink syndrome [7].
4: Will the self-organizing collaborative structure of Agile methodologies be a good fit for you and your team?
For Agile to be used successfully it requires driven, motivated individuals engaging in communication and collaboration continuously throughout the development process. Agile frameworks and by extension methodologies are dependent on the expectation that the development team is made up of individuals who will self-organize and fully commit to following the team’s chosen methodology [1] [5].
This also means the role of the project manager is more to guide and coordinate than directly plan, manage, and direct the project [5]. The fifth principle of Agile based on the original manifest gets to the core of what is expected of an Agile project manager saying to “build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done” [8].
Implementing an Agile methodology can involve a big shift in roles and expectations which will take time and have unforeseen complications that will need to be accounted for if the team is to successfully implement an Agile methodology and complete their project [2] [5].
Summary:
At its core Agile principles and by extension Agile frameworks are built on the idea of iterative development, adaption to change, self-organization, communication, and collaboration.
An Agile methodology might be a good fit for a project if:
It can be broken down into smaller pieces that are mostly independent of each other and can be developed iteratively.
It has unknown project requirements or ones that are subject to change throughout development.
It has a flexible timeline or does not have a set or known end date.
The team working on the project is willing to put in the work to adapt an Agile framework into a methodology that will work for them and the project.
An Agile methodology might not be the best fit for a project if:
Individual parts of the project are highly dependent on each other or outside factors require the project to be developed in a strict linear fashion.
It has known well-defined project requirements that are unlikely to change throughout development.
It has a fixed and immovable deadline that must be met.
The team is currently unable or unwilling to put in the time and effort to create and implement an effective Agile methodology.
Whether or not an Agile methodology would be beneficial is highly dependent on the individual team and project but even if an Agile methodology isn’t suitable one that incorporates some of the principles of Agile.
Sources:
[1] Button, B., Farmer, T., & Musser, H. (2024, January 26). What is Agile Software Development?. Agile Alliance. https://www.agilealliance.org/agile101/
[2] Agile methodology basics. Versatile & Robust Project Management Software. (n.d.). https://www.wrike.com/project-management-guide/agile-methodology-basics/#when-not-to-use-the-agile-project-management-method
[3] When agile can’t be used on projects - PMIS consulting limited. PMIS Consulting. (n.d.). https://www.pmis-consulting.com/when-agile-cant-be-used-on-projects/
[4] What types of projects can agile be applied to?. PMIS Consulting Limited. (2022, October 30). https://www.pmis-consulting.com/what-types-of-projects-can-agile-be-applied-to/
[5] Rigby, D., Takeuchi, H., & Sutherland, J. (2021, August 27). Embracing agile. Harvard Business Review. https://hbr.org/2016/05/embracing-agile
[6] Lynn, R. (2022, September 29). Disadvantages of agile. Planview. https://www.planview.com/resources/articles/disadvantages-agile/
[7] K. Schwalbe, et al, Information Technology Project Management, 9th ed., Boston, MA, USA: Cengage, 2019. [Online]. Available: https://ebooks.cenreader.com/#!/reader/b2aef31a-bf2f-4c23-a0fa-63a64a662287/page/758a39896cdf87baf7a6aadddffd418f Accessed January 28, 2024.
[8] Farmer, T., Musser, H., & Foster, T. (2023, October 18). 12 principles behind the Agile Manifesto: Agile Alliance. Agile Alliance. https://www.agilealliance.org/agile101/12-principles-behind-the-agile-manifesto/
Comments