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?
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
Let us first understand about project scope: Client: “I have a block of land. I want to build a standard one-story house according to this plan. Can you please give some pricing?” Builder: “Why not sir! Looking at your house plan. It will cost you $250,000 for standard fittings. Note that it does not include tiles, … Continue reading How to define project scope