Ready, Set, Action Agility

Bart has been in ecommerce for over 20 years, and can't imagine a better job to have. He is interested in all things agile, or anything new to learn.

  Agile   Strategy   ProjectsAtWork  

Agile anticipates being wrong, or at least not exactly right, and the same principle applies to any organization becoming agile. The best approach is to simply get started and commit to the fundamentals: prioritize, re-plan, release frequently, seek constant feedback, and trust enough in the cycle to continue.

How does an organization become Agile? It gets started! — on one project and then another. Of course, truly becoming Agile isn’t easy, but committing to the process and understanding that it was built to withstand the common problems that all initiatives face is the first step toward getting your organization’s teams, executives and customers on the Agile track.

Let’s take a look at the fundamental components of the Agile process — from prioritizing and reprioritizing, to frequently releases and constant feedback, to trusting and continuing the cycle.

Decide and Prioritize

One of the key differentiators of Agile is the reliance upon prioritization. In more traditional projects, the product owner or customer comes up with a long list of requirements, and the project isn’t done until all of them are complete. This leads to teams creating a project plan that includes all the items, all at once. The “critical path” to the project is found, that being the longest dependency path of the project that will complete all …

Please log in or sign up below to read the rest of the article.