What is Agile ERP Implementation Methodology? | Agile vs. Waterfall Digital Transformation

Agile ERP implementations may be the latest flavor of the month used by SAP S/4HANA, Oracle ERP Cloud, Microsoft Dynamics, and other ERP vendors in their implementation methodologies. But the agile approach is generally a bad idea for those looking for successful ERP and digital transformation initiatives. This whiteboard video explains why.

——————————————————————
DOWNLOAD MORE RESOURCES BELOW
——————————————————————

————————————————————
CONNECT WITH ME:
————————————————————

CONTACT ME TO BRAINSTORM IDEAS FOR YOUR DIGITAL TRANSFORMATION:

[johnjhope]

Fantastic video and message Eric. I'm amazed you don't have more subscribers at this point. You have a lot of good content on here.

[fsaetre]

Such an important point and it is a foot in the door, and customers need to know about the future comitment it leads to.
The overarching process has to be waterfall as the steps has to be locked in a given sequence to acheive alignment.
SureStep was a waterfall methodology and had an agile subset that could be used if needed. Microsoft has for the last three years suggested Conference Room Pilot.

[srk]

@Eric Looks like there is some misunderstanding on what Agile is all about and I don't see what needs to be on left and probably right as well. But fundamental concept of Agile is all about building whats right and at the right proportion and right time. and Risks/ Issues I heard about the last point is supposed to be unveiled if Agile practices used right. Glad to explore and discuss on more if you are open! Agile started for one single project team initially, but its no more for small teams and no more built in silos. Hope you've also heard about several scaling practices/ guidelines quite useful for Larger organizations!

I also believe we should do the same for other methodologies like waterfall as well to understand how we solve ERP related issues/ problems for the current world!

[munshianisulislam]

I agree with your opinion (last 2 minutes of this video). I want to add one point, wherever coding is involved to customize ERP feature, some agile practices can be introduced. For example, one of my ERP projects I used Kanban and TDD for customization (where coding required) and 3rd party software integration.

[emviarockkapak]

What an amazing explanation!! Thanks a lot Eric. Keep it up!

[nicolasdeflassieux]

Very interesting but in real life I have never seen such a project starting with just one small module, and not considering the global requirement right from the start. The Agile approach as such, is only used for the "build" phase, it's a good method because the customer (project sponsor or application owner) is regularly involved in the project, which reduces the risk of gaps between user requirement and the final solution.

[TheAlloway]

Great channel! Very helpful and well presented information. Every profesional in the industry would benefit. Thank you!

[HelgeHabenicht]

Thank Eric for the video and comments. I thought I was on the wrong train with the project I am engaged in at the moment. Apparently not. The agile approach has lead to the dismantling of the silos, but lead now to even more silos and everybody is sprinting alongside in its own lane. And I see a huge wall across the finishing line.

[elenar]

I am watching this video to learn about ERP implementation, this is for an assignment. I am a Supply Chain Student. Thank you, very helpful information. Gracias guapo!

[Jadeddave]

This is a great video. I can identify with a lot of the downsides raised here in our own implementation, specifically the point on "let us start with Finance".

[nalinipatil]

Excellent! I find your videos so full of information and so helpful. Thank you so much

[odedasouline]

I see your point, but I think the agile minset for a business goal of "creating an enterprise system" is not to do one full all the way erp model at a time (e.g. finnance). it would more likely be to make the minimum needs in all required modeles first so that in case of project faliure (to meet the buisness goal) the cost will be at a minimum. agile is about reducing uncertinty, if there is low uncertinty in the rollout a more classical project approch may be better i guess

[someoneelse]

Agile is based around the work structure originally used for the terracotta warriors. One major difference at the end of the sprinter if it wasn't perfect the person responsible was beheaded. Back then it worked perfectly!

[hectorballinas]

Its both. For the “out of the box” side of the implementation use waterfall, for all of the customizations use agile. From my perspective, ERP implementations are the conceptual modeling of processes, to be successful the business processes need to be documented, made lean, integrated and coherent before even speaking about any sort of automation. No single business is like another, in other words there is no cookie cutter approach, so unless the business agrees to radically change its processes to the vendors way (which almost never happens) then customizations with agile methodologies like Scrum make somewhat certain sense.
But even with the fanciest most expensive solution and methodologies in the world if the processes are crooked (what i believe you mention as misalignment) then the chances of success are quite minimal if at all, waterfall or agile alike.

[amrc]

excellent video and explanation. I have been saying these point to so many partners :) Good to see someone out there thinks the same

[crazyjawnllc]

This is awesome. I’m so happy when people much smarter than me, make statements that align with thoughts I’ve had during meetings.

[jurijusmirosnicenko]

Can you comment more the point where U say that cloud solutions are not so mature as on premises are?

[mrd]

Thanks for an excellent video Master Eric. I use my own hybrid model the include the framework and the context definition at the beginning and the agile development with countinusly releases after that similar to what you explained at the end of your video. Therefore I am against pure agile model for ERP implementation that includes a number of ISV products and Integration points.

[dorphus]

I believe scaled agile methods can deal with most of the problems you have pointed... So its not Agile the problem but the way it is getting done... Problems will always be faced in both sides... But I got your point and it is a great video! Brings a lot of reflection. Thank you!

[psvanguri]

We are using a mixed approach of Agile and Waterfall - Our Build activity is being broken down into multiple sprints and after the build we are blending into Waterfall methodology.