Making the Switch To Agile

Filed Under Mindjet

Making the Switch to Agile

February 29, 2012

The traditional waterfall model consists of long design, implementation, verification cycles that much be completed before any sort of product could be released. Far too often if you are late to market, you are toast. The frightening truth is that consumers are fickle – quickly losing interest in products that are late to market is just a fact of life that we all must deal with. How do companies make sure they don’t lose out? By adopting agile.

Source: Wikipedia

In order to move away from the waterfall model software companies had to begin working in sprints to accommodate for the release of smaller chunks of shippable code that could be planned, built, tested, and shipped within 15-30 days. Given the fast-paced world of business, this seems like a much more successful go to market strategy. By working in sprints and releasing small version updates, companies are putting themselves in a better position to take into consideration their customers’ feedback and requests. They are also better prepared to determine if and when it will be possible to implement these customer requests into future sprints for later releases.

Source: Wikipedia

The premise of agile is based on a few key concepts and roles that include:

Sprint: A specific time period where a team commits to having a given amount of work completed.

Task/User Story: A definitive amount of work that includes specific outcomes for the designated time period – think of it as a difficulty rating for tasks.

Story Points: The amount of effort it will take to get an allocated amount of work done.

Standup: A daily meeting where team members share what they accomplished the day before, their priorities for the present day, and any issues that may impeded future progress.

Sprint Commitment: A meeting that is held to understand what tasks teams are committing to for upcoming sprints.

Sprint Review: Team members review the accomplishments on incompletions from their previous sprints to better understand how teams can improve for the next sprint.

The key to being an agile company is taking this methodology and adapting it in a way that works for your particular industry, company, and team. We all know that no one works in exactly the same way to quote the old cliché “different strokes for different folks”. Becoming an agile company is no different. It is a methodology that needs constant iteration until you find that right mix that works best for your team.

Your Turn

Currently undergoing the switch to Agile? How are you and your company managing it?

Feel like making the change to agile isn’t right for you? Why?


  1.  Health App Development | Pearltrees

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>