Using Agile on Large Software Package Implementations

I've been doing large software package implementations for years now. The ones that use an Agile approach always come out better, faster, cheaper. But, that requires educating the business folks as the entire experience is different. I always write a few slides to help them understand the difference, putting the main two here.

Caveat emptor: These are just the kernel of what you should discuss. Every single company will need more than just these 2 slides to properly orient the business. The specific nature of the extra information varies from company to company. Some may need more initial context before these slides. Some may need a slide on roles & responsibilities to illustrate to how business resources act and work differently in an Agile implementation. Others may be concerned about governance as its inherently different. And, they're context sensitive, so not a lot of value in me taking a crack at that. If you need help rounding out your presentation consult your favorite tall, dark and handsome management consultant :-)

(Note: I'm also going to put these up on my website, TheBhatiaGroup.Com, as it seems LinkedIn doesn't render slides too well. I realize the font is tiny here, nothing I can do)

Slide 1: set the context by showing them what they're used to seeing. Lengthy paper documents, business resource peaks and valleys, arguments over whether a late discovery is a defect or a change request, and problems not found until far too late.

Slide 2: Show them what an Agile world looks like. Little to no paperwork, parallel teams, consistent business resource involvement providing fast feedback. And in a package implementation, vendors often supply sample data so clients can even more quickly see a functioning system, as conversion/migration inevitably takes weeks to months based on complexity of the data.

I need until 3/17/19 to put this up on my website. If you want the raw slides before then, PM me.