1.2.5: Doing Agile vs Being Agile

Agile Project Management · LibreTexts

0%

Contents

    Text

    Size
    100%
    Theme
    Typeface
    Line length
    Spacing

    Read aloud

    How

    Speed: 1×
    Light up
    Highlight

    Symbols: Mulberry Symbols, © 2018–2026 Steve Lee, CC BY-SA 4.0 (licence, the set), the site's own copies.

    From LibreTexts, under CC BY 4.0, as the source states it; its equations are written in TeX, which the PDF shows typeset. This page at LibreTexts.

    1.2.5: Doing Agile vs Being Agile

    Doing Agile vs. Being Agile

    Many organizations say they are adopting Agile. They introduce Scrum teams, sprint planning, daily standups, retrospectives, story points, Kanban boards, and Agile job titles. On the surface, it may look like Agile is happening. But an important question remains: is the organization truly becoming Agile, or is it only performing Agile ceremonies?

    Doing Agile vs. Being Agile

    Doing Agile means using the practices. Being Agile means living the values behind the practices.

    This is the difference between "Doing Agile" and "Being Agile". Doing Agile means using Agile practices and terminology. Being Agile means internalizing the values, principles, and mindset behind those practices. A team can have sprints, standups, and story points and still not be truly Agile. True agility shows up in trust, feedback, adaptation, collaboration, and continuous delivery of value.

    Starting with Why

    Agile adoption should begin with the question “Why?” Why does the organization want to move toward Agile? Is it trying to respond faster to change? Improve customer feedback? Reduce waste? Increase transparency? Deliver value sooner? Build stronger teams?

    If an organization starts only with “what,” Agile becomes a checklist of activities. The team is told what meetings to attend, what tools to use, what roles to adopt, and what reports to produce. But without understanding the purpose behind Agile, the practices become mechanical. People may follow the process, but they may not believe in it.

    A better approach is to start with the reason Agile is needed. The “why” creates meaning. The “how” explains the behaviors needed to support that purpose. The “what” becomes the visible practices that help the team work in an Agile way. In other words, Agile should not begin with ceremonies. It should begin with the business need for adaptability, learning, and value delivery. 

    Doing Agile starts with practices or what; Being Agile starts with purpose or why.
    Figure \(\PageIndex{1}\): Being Agile starts with “Why”; Doing Agile starts with “What.”. (CC BY 4.0; Guha Janakiraman). Accessible text description of Figure \(\PageIndex{1}\)

    When Organizations Only Do Agile

    Organizations often struggle with Agile because they focus too much on mechanics and not enough on mindset. They introduce standups, sprint planning, backlogs, retrospectives, and Agile tools, but they do not change how leadership behaves or how decisions are made.

    For example, a team may have a daily standup, but every update is really a status report to the manager. A team may work in sprints, but leadership may still force fixed scope into every sprint. A team may hold retrospectives, but people may not feel safe enough to discuss real problems. A team may maintain a backlog, but priorities may still be driven by politics instead of customer value.

    This creates frustration. Teams begin to feel that Agile is just more meetings. Managers may conclude that Agile does not work. Traditionalists may use the failed adoption as evidence that Agile is a bad idea. But often the real problem is not Agile itself. The problem is that the organization adopted Agile practices without adopting Agile thinking.

    What It Means to Be Agile?

    Being Agile means embracing the mindset behind the methodology. It means teams are trusted to solve problems, leaders remove impediments, customers provide feedback, and plans are adjusted when new evidence appears. It also means transparency is encouraged, even when the news is uncomfortable.

    An Agile organization values learning over pretending to be certain. It understands that complex work cannot always be fully planned upfront. Instead of punishing change, it creates a system for responding to change responsibly. Instead of measuring success only by whether the original plan was followed, it measures whether value was delivered.

    Being Agile also requires leadership change. Leaders must move away from command-and-control behavior and toward servant leadership. They clarify direction, protect the team’s focus, remove blockers, encourage collaboration, and create an environment where people can be honest about risks and problems.

    The difference between Doing Agile and Being Agile is very important. Often describe teams that are using Agile labels but still behaving in traditional ways. In those cases, the better choice usually supports empowerment, collaboration, servant leadership, transparency, customer feedback, and adaptation.

    A team is not Agile just because it has a sprint board. A team is Agile when it can deliver value, learn from feedback, and adapt responsibly.


    This page titled 1.2.5: Doing Agile vs Being Agile was last modified on Thu, 27 Aug 2026 21:59:37 GMT and is shared under a CC BY 4.0 license and was authored, remixed, and/or curated by Guharaman Janakiraman.