Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Doing Agile vs. Being Agile

DZone's Guide to

Doing Agile vs. Being Agile

Doing Agile and Being Agile are different.

· Agile Zone ·
Free Resource

See why over 50,000 companies trust Jira Software to plan, track, release, and report great software faster than ever before. Try the #1 software development tool used by agile teams.

Doing Agile and Being Agile are different. Here is a popular infographic that explains what Agile really is and illustrates common misunderstandings about it:

Doing Agile is not Being Agile

Doing Agile

Doing Agile is about the practices: standups, user stories, iterations, etc.

There are significant benefits from using Agile practices. I see it as “common sense” of getting work done. Adopting these practices will lead to benefits; perhaps 20% or more from what I have seen. This is widely reported by industry research such as Version One’s Annual report.

Being Agile

Being Agile is about our Consciousness or way of being. We may also refer to this as Mindset or Organizational Culture. It’s about how we see ourselves. How we relate to each other. How we behave. What we value. A recent post explains more about this: Agile Culture –> Self-managing People.

I put the ROI on this at 3x to illustrate how much impact this has on team and organizational effectiveness. It could be much more. We are talking about reinvention here – not applying a process change.

Acknowledgements

Bob Hartman noticed and coined the concept that Doing Agile is not Being Agile. See his slides.

The Best teams run on Jira. Here's how teams at a few of the world's most recognizable brands are teaming up in Jira to build great software that users love.  Learn More.

Topics:
agile practices

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}