Disclaimer – While this may appear to be an article about a software development methodology, I’ve been using many components that are considered “agile” in non-software projects for over a decade. For the software folks out there, this is an article on the pieces of “Agile” that I find value in – your mileage may vary. After exceeding 2,000 words, I decided that I would need to kick out posts outlining details of the Agile components as separate components.
At a recent meeting of the folks involved in the PMI Southern Alberta Chapter (PMI-SAC) mentorship program, a discussion started around “Agile” since one of the people involved had been informed that their team would be using agile. A number of side discussions arose around this, including questions like:
- What kind of Agile will you be using?
- That seems like a project better suited to a traditional methodology – why are you using Agile?
- What sort of projects are suited for Agile methodologies?
- Why do IT projects continually fail / over-scope / finish late / …