• Skip to main content
  • Skip to primary sidebar
  • Skip to secondary sidebar
  • Skip to footer
  • Home
  • About
    • linkedin
    • twitter
  • Archive
  • Technical youtube Channel
  • Recommended Readings
  • Free Courses
    • Fixed Asset management Course
    • Financial Modules

Ali Raza Zaidi

Musing's of ERP Consultant

Why Story telling is important in ERP implementation.

January 6, 2023 by alirazazaidi

I was at client side.

End user did not going to sign off the functionality. He wants a few more changes. All these changes are very nice to have features.

In go live situation it is not possible to accommodate these. If end user or key person would not sign off and as result no go live. When project is not go live. Then there will no payment release.

As result we are failure. We can not modify things at 11th hour. Who do the enhancement, who test it. And if we deliver not tested things in front of client. his trust will be broken.

EPR implementation is very slow process. When project kick off and now on go live.

There are many people both our and client side already left. The best way to handle this situation is signed Functional Requirement Document. If things varies from this document. We would not do that. That reason it is very important to write functional requirement document will be care. I will write another post. How we have to write functional requirement document and what things we need to care. Any how main point is your functional requirement document must be very good and that is the only thing that help us to close things. Specially when we unable to convince end user or key account holder.

Second way is Story telling. How good you are in Story telling. You can convince him easily.

Human mind did not thing straight. Any how point is simple and straight but it did not understand. It understand, what will happen, if we do that.

Remember, Every project failed not technically, it failed financially. In Project management. There are world triple constraint. Time, scope and cost. Any one increase in it will result in increase other two factors. And Same time Quality is increase. And Most interesting point in this triple constraint is Cost.

So we built a story and share him and he understand our point and project goes to next stage which was in our case go live.

These are seven steps we used to built a story.

  1. A hero ( Certainly a another client )
  2. Has a problem ( many nice to have features)
  3. And meets a guide ( Partner in this case we)
  4. Who offers a solution ( utilize what already we have)
  5. Call hero to action ( Start to use and go live)
  6. help them to avoid failure ( Cost increase, more issues comes, requirement increase and as result System will never go live, no body will use it)
  7. And finish with success. ( They start using the system and we did all those nice to have feature in support. System is in utilization state and it will good in cost saving too).

So what is yours, What you made it help you more client.

Related

Filed Under: Implementations, musings

Primary Sidebar

Categories

  • .net framework 2 (24)
  • Accounts Payable (2)
  • AIF Services (6)
  • Ajax (2)
  • asp.net 1.1 (17)
  • asp.net 2 (42)
  • BAM (2)
  • BizTalk (24)
  • Biztalk 2010 (51)
  • BizTalk Errors (10)
  • Biztalk Tools (6)
  • Biztalk White Paper (2)
  • Books (6)
  • Business Central (1)
  • Business Intelligence (4)
  • c# (28)
  • Certification Guide (3)
  • Channel 9 Video (2)
  • Customization Tips for D365 for Finance and Operations (57)
  • D365OF (53)
  • Data warehouse Concepts (3)
  • Database Concepts (3)
  • Deployment Errors (5)
  • Dynamics 365 (52)
  • Dynamics 365 for finance and operations (119)
  • Dynamics 365 for Operations (137)
  • Dynamics AX (AX 7) (133)
  • Dynamics AX 2012 (274)
  • Dynamics Ax 2012 Forms (13)
  • Dynamics Ax 2012 functional side (15)
  • Dynamics Ax 2012 Reporting SSRS Reports. (31)
  • Dynamics Ax 2012 Technical Side (51)
  • Dynamics Ax 7 (64)
  • ESB toolkit (4)
  • Exam MB-330: Microsoft Dynamics 365 Supply Chain Management (6)
  • Favorites (12)
  • Financial Modules (6)
  • Functional (6)
  • Implementations (1)
  • Lifecycle Services (1)
  • Management Reporter (1)
  • Microsoft Flow (3)
  • MS Dynamics Ax 7 (64)
  • musings (1)
  • MVP summit (1)
  • MVP summit 2016 (1)
  • New Dynamics Ax (19)
  • Non Defined (9)
  • Power Apps (3)
  • Power BI (12)
  • Power BI Desktop (8)
  • Power Platform (6)
  • Procurement (3)
  • procurement and sourcing (3)
  • Product Information Management (1)
  • Product Management (2)
  • Production Control D365 for Finance and Operations (8)
  • regular expression (3)
  • Sale Order Process (8)
  • Sale Order Processing (8)
  • Sales and Distribution (5)
  • Snagit 2021 (1)
  • Software developer (1)
  • SQL Server 2008 (18)
  • SQL Server 2012 (3)
  • SQL Server 2019 (5)
  • SQL Server and TSQL (5)
  • Sql server reporting services (7)
  • SSIS (13)
  • Tips and tricks (275)
  • TSQL (17)
  • Uncategorized (40)
  • Upgrade (1)
  • VB.net (2)
  • Web Cast (7)
  • White papers (4)
  • Windows form (3)
  • X++ (143)

Secondary Sidebar

Footer

Tags

Account receivable AIF Aif Services Apps for Dynamics 365 for Operations asp.net AX 7 AX 7 CTP 8 BizTalk 2010 BizTalk Errors c# Customization in Dynamics 365 d d365 for finance and operations D365 for Operations Dynamic AX 2012 Dynamics 365 for finance and operations Dynamics 365 for Operations Dynamics Ax Dynamics Ax 7 Dynamics Ax 2012 Dynamics Ax 2012 development 2 Dynamics Ax 2012 functional side Dynamics Ax 2012 R3 Dynamics Ax 2012 Reporting SSRS Reports. Dynamics Ax 2102 Dynamics Ax tips and tricks ER Diagrams of Dynamics Ax 2012 tables Exam MB-330: Microsoft Dynamics 365 Supply Chain Management Excel Add ins financial Dimension Microsoft Dynamics 365 for Operations MSDYN365FO New Dynamics Ax Power BI Power BI tutorial procurement in dynamics ax 2012 Product Management Sales and distribution SQL Server 2008 SSRS Tips and tricks Workflow WorkFlow in AX X++ X++ tips

Copyright © 2023 · Magazine Pro On Genesis Framework · WordPress · Log in

Loading…