Most ERP projects have to be delayed without much warning. It has a negative impact on team morale, project cost and business case. Let us see some leading indicators of project delay: Executive Leadership: No sense of urgency: Project sponsor and board do not communicate importance of the project. There is no carrot, no stick. … Continue reading Early Indicators Of Project Delay!
Scrum is like a religion. Religion has values and rituals. Rituals support values. Without values, rituals are meaningless. Scrum sucks because we follow its rituals (Daily Scrum, Sprint Reviews etc.) without living the values (Focus, Courage, Openness, Commitment and Respect) and the three pillars of Scrum (Transparency, Inspections and Adaptation). If the basic Scrum values … Continue reading Why Scrum Sucks?
Uh - Finally, ERP implementation project is over! Business-As-Usual now! But, have you thought of servicing your ERP? If not, then read carefully! Your ERP is a business tool (Information processing machine). Like all other complex machines, your ERP needs service. So, get your ERP logbook now! But why? Here are few points to consider: … Continue reading How Often You Service Your ERP?
Do you agree that COTS/ERP implementations makes your business mediocre at best? One of the main value propositions of the packaged software (COTS/ERP) is relatively quicker implementation. Business processes are standardised. Your business receives so called 'best practice' implementation. But is it a good thing? The so called 'best practice' is really a best practice? … Continue reading COTS/ERP Bringing Mediocrity At Best!
As a Project Sponsor, you are responsible for project governance. You ensure that the project is steering in right direction. You are ultimately responsible for the business case and success of the project. Typically, more than one vendors, subcontractors, consultants are involved in ERP implementations. These resources may not have worked together before. There are strong … Continue reading How to Govern ERP Project?
Every project initiates with preliminary planning followed by Analysis/Design. But, why we do analysis? What is the actual purpose of requirements elicitation, documentation, identifying solution options, providing estimates and so on? Why instead of spending time on analysis, we just build the required product and iteratively improve it? Well, it may sound revolutionary idea, however, the reality is the … Continue reading Why Do We Do Analysis?
Requirements for ERP / COTS projects are documented in all shapes and sizes. There is no standard method. It is left on consultants, Business Analysts, Business Users (Subject Matter Expert) discretion. The result is - requirements are all over the place. Sometimes requirements: are collection of vague wish list are replica of existing system and processes include solution (big mistake) include … Continue reading How To Document ERP / COTS Requirements – Tell Stories
Our ERP is very old: Check your ERP software version. If it is ‘ancient’ version, consider option of upgrading to latest version rather than changing the ERP. Our ERP never really worked: Check if software was implemented poorly. Therefore, end-users have no choice but to get creative and device manual workarounds. There is no one … Continue reading 10 Reasons Not To Change ERP!
ERP Implementations are complex! So many moving variables among which key decisions are to be made. One of the challenges is to get good visibility on breakdown structure of Total Cost of Ownership (TCO). Following diagram will help you. You can use this during various stages of the project (Initiations/discovery - developing business case, Vendor … Continue reading ERP Implementation – Estimate Breakdown Structure