Aug 21

When to be agile, and when not to be

My opinions:

When to be agile

  • When you’re dealing with constantly changing requirements
  • When there’s a lot of uncertainty about how to build the system
  • When there’s a lot of variability – priority changes, multiple projects, etc
  • When you want the team to “gel” quickly
  • When you want the team to take ownership of their projects and tasks
  • Pretty much all the time except the following:

When not to be (too) agile:

  • When you’re building “infrastructure”
    • Protocols/APIs
    • Frameworks/Platforms
  •  When your client expects and is paying for a thorough analysis and extensive documentation
  • When you’re building something “mission critical”

I’ll address these in more detail in follow-up posts.

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>