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
Sponsoring software projects can be very overwhelming. Understanding and documenting initial problems, business requirements, prepare RFP/RFQ, deciding vendor/product and so on. Throughout this process there is often one major concern, “Can we deliver the project under the approved budget?". Organisations often try to mitigate this risk by opting for ‘Fixed price’ quote. But, does that … Continue reading ‘Fixed Price’ ERP/COTS Projects Advise
In my previous post, I put together some information to help you understand your business needs before procuring Enterprise software. I hope information was helpful! Once you know what you need, you go out and buy it! Right? But, it is not true for purchasing Enterprise software. Assuming your business needs Commercial-Off-The-Shelf (COTS) software (Software package). Then, … Continue reading Software Vendor Selection – Steps To Find Initial Vendor List