Protorative Methodology

588 views

Published on

SAP Implementation in faster and better way.

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
588
On SlideShare
0
From Embeds
0
Number of Embeds
14
Actions
Shares
0
Downloads
43
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • One by one of above points
  • One by one of above points
  • What do you think was the probable outcome of earlier example? Or which result has more probability?
  • Lesser the constraints easier to manage.Every org have constrainst. TOC states that take one constrainst at a time and restructure the methodology, project or org to solve that constraints.After that there may be new constrainsts. Repeat the same process. This way we improve the processes and bring more value for money. If we remove any one constraints, project execution becomes very simple. But unfortunately, we have to live within the intersection of these three constraints.More the overlap area, simpler it is to manage the projectThe goal is to make overlap area as big as possible.
  • Talk abt how constraints are taken care of..
  • Protorative Methodology

    1. 1. 7/5/2010<br />ERP Implementation Methodology<br />1<br />Yashpal Jain, Project Manager-SAP<br />
    2. 2. Agenda<br />Companies without ERP<br />ERP Implementation<br />Current Business situation & Expectation from ERP<br />Reason behind project failures<br />Overview of ASAP methodology & its drawback<br />Theory of Constraints<br />Protorative Methodology – Assumption/Schedule/Advantage<br />Q&A<br />7/5/2010<br />Protorative Methodology<br />2<br />
    3. 3. Companies without ERP<br /><ul><li>Moderate to high number of home grown systems.
    4. 4. Business functions or Systems are not integrated or at best loosely integrated.
    5. 5. MIS reports are generally overdue.
    6. 6. Management decision on market situation is often reactive.
    7. 7. Bird eye view of company’s status is not available to management.</li></ul>7/5/2010<br />Protorative Methodology<br />3<br />
    8. 8. ERP Implementation<br />7/5/2010<br />Protorative Methodology<br />4<br /><ul><li>Implementing ERP is always Top down decision.
    9. 9. Decision to implement ERP is taken by watching market trend and relying on different agencies reports.
    10. 10. With Initial cost of implementation being high, ROI cannot be calculated in short span of time. It is at best over a period of 2-3 years.
    11. 11. Success of system implementation has different meaning to Client and Consulting partner.
    12. 12. Implementation timeline is aggressive and schedule slippage is very costly to business.
    13. 13. ERP systems are sophisticated and not as user friendly as legacy system.</li></li></ul><li>Current Business Situation & Expectation<br />7/5/2010<br />Protorative Methodology<br />5<br />
    14. 14. Current<br />7/5/2010<br />Protorative Methodology<br />6<br />Expectation<br />
    15. 15. End Results??<br />7/5/2010<br />Protorative Methodology<br />7<br />Only two possible outcome<br /> OR<br />SUCCESS<br />FAILURE<br />
    16. 16. Project Success Rate<br />7/5/2010<br />Protorative Methodology<br />8<br />“Studies by Standish Group and others for traditional project management methods, only 44% of projects typically finish on time, projects usually complete at 222% of the duration originally planned, 189% of the original budgeted cost, 70% of projects fall short of their planned scope (technical content delivered), and 30% are cancelled before completion”.<br />“The success rate is even lower in case when companies are going for ERP system for the first time”.<br />
    17. 17. Reasons behind project failures<br />7/5/2010<br />Protorative Methodology<br />9<br />
    18. 18. Definition of Success<br />7/5/2010<br />Protorative Methodology<br />10<br />For Consulting Partner/System Integrator<br /><ul><li>On time Go-Live
    19. 19. In-Budget Go-Live
    20. 20. All open issues are closed before end of stabilization phase</li></ul>For Client<br /><ul><li>On time Go-Live
    21. 21. In-Budget Go-Live
    22. 22. All open issues are closed before end of stabilization phase
    23. 23. Use & leverage the system as intended</li></ul>If we compare the meaning of success of both consulting partner and client, the only difference is using and leverage the system as intended. This is in fact the most ignored success criteria and deciding factor between success or failure of the project.<br />
    24. 24. Issue in Leveraging ERP System<br />7/5/2010<br />Protorative Methodology<br />11<br />Statistics shows that the top 2 reason behind companies not able to leverage or realize full potential of ERP is <br /><ul><li>Not all requirements were met during implementation of ERP.
    25. 25. Users are not comfortable running the system because not all desired functionalities are provided in system and lack of sufficient time spent on the system is hindering them to work as per management expectation.</li></li></ul><li>Project Success<br />7/5/2010<br />Protorative Methodology<br />12<br />With all the discussion and explanation of project’s success or failure, it is very easy to comprehend that on-time and in-budget go live are not the only of the criteria of successful implementation. <br />It is User’s adoptability of ERP system which will decide whether project is success or not.<br />
    26. 26. ASAP Methodology & Drawback<br />7/5/2010<br />Protorative Methodology<br />13<br />
    27. 27. ASAP Methodology<br />7/5/2010<br />Protorative Methodology<br />14<br />
    28. 28. During Project Execution<br />7/5/2010<br />Protorative Methodology<br />15<br /><ul><li>How often requirements are captured inaccurately, insufficiently or missed to be captured at all?
    29. 29. How often changes in agreed business requirement/process are requested by client?
    30. 30. How often we run out of testing time when changes are requested during later phase of the project?
    31. 31. How often client feel inadequately trained at the end of the project?
    32. 32. How often client needs to have extended support to fix all outstanding issues?</li></ul>If most of the answers are in “Very Often” inspite of using ASAP methodology, blaming the poor planning and execution does not sound correct.<br />
    33. 33. Why Do Requirements Change?<br />7/5/2010<br />Protorative Methodology<br />16<br />When we write the initial specification we document the low hanging fruit. The specification will include the most obvious requirements, those that have been discussed before the project started, those which are already documented and those this people think of in the early stages. Yet as the project proceeds, everyone involved will get a more detailed understanding of what is happening both in the software and the company, potentially revealing even greater value in a system. Consequently, it is necessary to reprioritize our work as we go.<br />Requirements changes mainly due to one of the below factors: <br />External changes - changes required to meet some need from outside the organization, say a changed legal requirement. <br />Internal changes - changes required because of company changes such as new products or restructuring. <br />Technical changes - required to meet new technical demands.<br /> Learning - changes resulting from learning by individuals or groups.<br />
    34. 34. Drawback of ASAP Methodology<br />7/5/2010<br />Protorative Methodology<br />17<br />What is the main drawback of using ASAP methodology or for that matter any traditional project management methodology?<br />The answer is “it relies on completing all the activities of a particular phase in that phase itself”. It does not permit us to go back in phase and change something. If we try to go back to some phase and change something, basically we are eating up time of current phase. This often results in project delays.<br />
    35. 35. Theory of Constraints<br />7/5/2010<br />Protorative Methodology<br />18<br />
    36. 36. The five focusing steps in TOC<br />7/5/2010<br />Protorative Methodology<br />19<br /><ul><li>Identify the constraint (the resource or policy that prevents the organization from obtaining more of the goal) .
    37. 37. Decide how to exploit the constraint (make sure the constraint's time is not wasted doing things that it should not do)
    38. 38. Subordinate all other processes to above decision (align the whole system or organization to support the decision made above)
    39. 39. Elevate the constraint (if required or possible, permanently increase capacity of the constraint; "buy more")
    40. 40. If, as a result of these steps, the constraint has moved, return to Step 1. Don't let inertia become the constraint. </li></li></ul><li>7/5/2010<br />Protorative Methodology<br />20<br />3 Constraints of any Project<br />Scope<br />Schedule<br />Cost<br />
    41. 41. Protorative MethodologyPrototype + Iterative<br />7/5/2010<br />Protorative Methodology<br />21<br />
    42. 42. 7/5/2010<br />Protorative Methodology<br />22<br />Configure<br />Protorative Methodology<br />Test<br />Gather<br />Close<br />Prototype<br />Configure<br />& <br />Train<br />
    43. 43. Protorative Phases & Milestones<br />7/5/2010<br />Protorative Methodology<br />23<br />
    44. 44. Differences<br />If most of the answers are in “Yes” inspite of using ASAP methodology, blaming the poor planning and execution does not sound correct.<br />7/5/2010<br />Protorative Methodology<br />24<br />
    45. 45. Assumptions<br />7/5/2010<br />Protorative Methodology<br />25<br /><ul><li>Client will ensure the dedicated users are available during complete life cycle of the project.
    46. 46. List of would be SAP users are finalized with their respective roles in Organization before project starts.
    47. 47. All the hardware (At least Dev and Quality servers) are procured and ready to be setup before project starts.
    48. 48. Consulting Project team is finalized and ready to be deployed.
    49. 49. Standard SAP user manuals are available to give it to the users.
    50. 50. Consulting team is experienced and ready to work extra hours from the day one of the project.
    51. 51. End users to have good excel knowledge. If not, a 5 day workshop will help the project in long run.</li></li></ul><li>Activity Schedule<br />7/5/2010<br />Protorative Methodology<br />26<br /><ul><li>Weekly Activity Schedule for Protorative Methodology</li></li></ul><li>Advantages<br />7/5/2010<br />Protorative Methodology<br />27<br /><ul><li>4-6 weeks of time saving (and cost) for both client and Implementation partner.
    52. 52. Testing of the system is done by user himself.
    53. 53. Both client and implementation partner become equally responsible for success of the system.
    54. 54. Consultants will be working more during initial phase of the project instead of later part. This way they can be more productive when it matters most.
    55. 55. Post Go Live issues will be very few as user has tested and approved the system.
    56. 56. Separate window for Training is not required as user get hands on training from week 2.
    57. 57. Data collection is almost error free and smooth.
    58. 58. User adopts & use the system as per management expectations.</li></li></ul><li>7/5/2010<br />Protorative Methodology<br />28<br />Thank you<br />Yashpal.v.Jain@gmail.com<br />

    ×