Seven Reasons Agile Sucks - And What to Do About It

Seven Reasons Agile Sucks - And What to Do About It
      by Greg Smith, CST, PMI ACP, CAPM

We don’t talk enough about all of the limitations of Agile and how many companies choose to not use Agile at all due to the limitations. In this interactive discussion, we will cover the seven biggest reasons why companies say they cannot use Agile, and what can be done to address the constraint and implement a value delivering Agile lifecycle. The case studies presented will be from some of the largest enterprises and organizations in the world. We will cover the following areas:

I cannot use Agile because -

  • My team is not dedicated to the project or is distributed around the world .
  • My team is implementing a Commercial Off The Shelf (COTS) Package which is mostly configuration
  • My project has to go through formal gateways.
  • I must deliver a 90% accurate estimate for the project before development begins
  • I still have to do documentation
  • I must have traceability
  • My project is date driven


Speaker Bio

Greg Smith is an Agile coach and trainer who specializes in the practical adoption of Agile methods. During his career Greg has held positions as a Product Manager, Program Manager, Development Manager, Scrum Master, and Project Manager. Greg has helped several Fortune 500 companies and major institutions move to Agile including Exxon Mobil, JP Morgan Chase, StubHub, Stanford University, First Data Corporation, Fannie Mae, Expeditors International, Lexis Nexis, The Joint Commission, and TD Ameritrade. 

Greg became the instructor for Agile Project Management at Bellevue College in 2005. In 2009 Greg co-authored “Becoming Agile in an Imperfect World.” This book has helped a number of companies move to a more effective development lifecycle, and is often used as a guide for entire project teams. PMI uses his book as part of its curriculum for Agile certification.