AUG 2012INSIGHTAnton Karnaukhov7 min read
Things you SHOULDN'T do in an agile SAP implementation
It's one thing to have the desire to implement SAP software in an agile way, envisioning the benefits of significantly lower cost and much happier end-users . It is a whole other thing to actually make it happen, resisting the constant desire to fall back to the old waterfall ways of doing things. And have no doubt, that desire will be there for quite some time, like a juicy carrot on a stick – if only we could map the entire project in a Gantt chart, if only we could put a deadline on every task no matter how far out that task is, if only we could achieve precise estimates on anything and everything and compare them to actual time spent, then and only then we can take control of the project, determine exact go-live date and keep our executive management properly informed. Falling into this type of thinking in an agile project is very simple. Having the understanding, discipline and commitment to the core principles of agile throughout the entire project is often very difficult.