Agile pros and cons: should CEOs embrace agility?

Agile pros and cons: Should CEOs embrace agility?

To be agile or not to be? That is the question. More and more organizations and departments are adopting Agile methodologies for both project and portfolio management. However, is Agile made for everyone? Is it always justified that CEOs and company executives push Agile methodologies at all costs, without considering the pros and cons of its implementation?

The CEO says: “We need Agile”

CEOs like the latest technology. CEOs like continuous improvement initiatives. CEOs like to be at the cutting edge of technology whenever possible. They like to make decisions. But are those decisions always in the best interest of the organization? Or are The latest tech, the latest processed, the best buzzwords this week. Whatever is hot now – that’s what they want. They’re pretty sure that’s what will solve whatever problem or change how the organization is going through right now.

Agile. It’s the latest corporate buzzword making the rounds. One survey last year found that over half the organizations who were implementing it were doing so because the CEO said so, not because of the value it adds. When done well it can transform individuals and organizations, but when done badly it can suck the life out of everyone involved.

So, when the CEO orders a change or champions something like this… what do you do? This topic brings to mind what I would consider an appropriate or applicable quote from the late Steve Jobs… “In weak companies politics win. In strong companies, best ideas do.” Strategic planning is a must – we must avoid falling into the trap of just adapting to the whims of leadership or the latest technology.

See the Triskell platform in action in a personal demo​

What is Agile? A brief definition

Agile is an iterative type approach where phases (requirements/design/build/test) needed to complete a project are generally done in parallel together. There are many Agile frameworks but each effectively has the same empirical structure where tasks are broken down into small planning cycles. Requirements and solutions are continually evolving and based on priority and discipline.

Generally, the Agile pros outweigh the Agile cons, but let’s consider a few…

Agile advantages

  • Agile is great for creative, innovative and more uncertain projects. These types of projects often have changing or evolving requirements and that’s a perfect fit for Agile.
  • Agile encourages active involvement and interaction from key project stakeholders which allows for product build based on priority and accuracy. Continual ‘show and tell’ sessions allow for product agreement.
  • The Agile framework is great for teams because it generally allows for more team interaction. Constant team involvement and structured communication channels allow for the discovery of progress, impediments and collaboration.
  • Agile forces continuous improvement. Lessons are learned and ultimately used to better the next iterations.
Pros and cons of Agile

Agile cons

  • Scalability may become an issue. Agile is really useful in software development projects, especially small ones with team size up to 10 people. Above that the question how to scale agile practices comes into play.
  • Agile methodologies don’t always work as well for predictable projects. if the project is predictable and plannable – use traditional PM approach.
  • Planning can be difficult because the actually deliverable delivery dates may become moving targets. Agile can cause the delivery dates to move and that may be an issue with the organization, leadership or project.
  • Business representation may become an issue. Time and efforts will be continually required from product resources. This is crucial to cycle planning and success.
  • Team members must be highly skilled and cross-skilled. Team members must be highly skilled and competencies as core teams are small. They must also be up-skilled on the Agile framework chosen.


The bottom line is this – Agile can be great for the organization and can be the right software development life cycle (SDLC) to follow. But it must be well adopted among the dev staff and is not necessarily the end all best for everyone and every situation. And it certainly should not be rolled out and forced on a mature development staff just because the CEO heard about it and decided to force it on the organization.

I know that would have been a complete disaster back when I was a younger application developer working with a dev staff that averaged 20 years older than me. The idea would have crashed and burned fast and many projects would have suffered irreparable damage in budget and timeframe.

What are your thoughts? Have you had major changes or processes forced on you by the Ceo’s desire to implement something “just because”? What pushback was done there? Did it work? Please share and discuss.

Subscribe to our Newsletter

Get stories like this in your inbox

Request a demo of Triskell Software

Want to learn more? Request a free demo of Triskell Software and you will discover the PPM software that best suits your business needs.

FAQs about pros and cons of Agile


  • Adaptability to changing requirements: Agile thrives in environments with evolving needs, allowing for adjustments throughout the project lifecycle.
  • Improved focus and prioritization: Agile emphasizes working on high-priority features in short iterations, promoting better focus and delivering value early.
  • Enhanced collaboration and communication: Agile practices encourage active stakeholder involvement and frequent communication, leading to better alignment.
  • Faster time-to-market: By delivering features iteratively, Agile methodologies can accelerate product launch and time-to-market.


  • Difficulty in planning for long-term projects: Agile’s focus on short iterations can make long-term planning challenging for some projects.
  • Potential for scope creep: The ability to adapt requirements can lead to scope creep if not carefully managed.
  • May not be suitable for all projects: Highly predictable projects with well-defined requirements might benefit more from traditional project management approaches.
  • Requires a shift in company culture: Agile methodologies often require a cultural shift towards collaboration, flexibility, and self-organizing teams.

Agile is a good fit for projects with:

  • Uncertain or evolving requirements.
  • A need for rapid delivery and feedback.
  • A focus on innovation and creativity.
  • A collaborative and adaptable team environment.

However, if your project has:

  • Clearly defined and static requirements.
  • A strong emphasis on long-term planning and predictability.
  • Limited stakeholder involvement.
  • A more hierarchical team structure.

Then a traditional project management approach might be more suitable.

If Agile isn’t the best fit for your project, here are some alternative project management approaches:

  • Waterfall: A traditional, sequential approach where each project phase (like requirements gathering, design, development, testing, deployment) is completed before moving to the next. This offers a clear structure but can be inflexible for changing requirements.
  • Critical Path Method (CPM): A project management technique that focuses on identifying the critical tasks that must be completed on time for project success. CPM helps prioritize tasks and manage dependencies effectively.
  • Project Management Institute (PMI) methodologies: PMI offers various project management frameworks, such as PMBOK, that provide structured approaches for project planning and execution. These methodologies can be helpful for complex projects requiring a high degree of control.
  • Phase-Gate: A project management approach that utilizes defined stages with specific criteria that projects must meet before progressing to the next stage. This provides clear decision points and helps ensure projects stay on track.
  • Hybrid Project Management: A combination of Agile and traditional project management methodologies. This allows for flexibility while maintaining some level of control. Hybrid approaches can be customized to fit the specific needs of a project.

Here are some tips to mitigate the potential cons of Agile:

  • Clearly define project scope and goals: While Agile allows for adaptation, a strong foundation with clear goals helps manage expectations and prevent scope creep.
  • Maintain strong communication and stakeholder involvement: Regular communication with stakeholders keeps everyone aligned and ensures requirements are well-understood.
  • Establish a solid project management process: Even within Agile, a defined project management process ensures effective workflow and risk management.
  • Invest in Agile training: Equipping your team with Agile principles and practices fosters better adoption and higher effectiveness.

Related Content


2024 Market Guide for Enterprise Agile Planning Tools

Get access to the Gartner® Market Guide ‘Enterprise Agile Planning Tools’ for 2024 and discover why they are key to manage strategies, investments, and outcomes effectively.