Project Deliverables - Does the Customer Understands its Purpose?
90% of the ERP Projects, we put the Project sign off completion based on either Miles stone based Phase Completion like (Phase 1, Phase 2 or CRP 1 completion, CRP2 Completion, UAT Sign off) or Project Deliverables Sign off based completion (PM Deliverables like Project Plan, As-Is Documents, To-Be Documents, Functional Design, Technical Design, Test Scripts, User Guides etc.,) and Payments are linked to sign off.
We study the Customer background and if they are matured having few systems, Processes and Procedures in place, then we adopt Project Deliverables based sign off, so that they will have some basic understanding of the purpose and meaning of what is Project Deliverable and provide a sign off
On the other hand, if the Customer background is nascent and having more of manual Processes and Procedures, and type of Industries also like Construction Industry, then we adopt Milestone based completion sign off as it is difficult to make them understand the purpose of Project Deliverable and get sign off
In spite of all these, in my experience getting Project Deliverables sign off ended only in following three modes
领英推荐
Another very critical issue is there will be a clause both IT Team and Business needs to sign off the Project Deliverable wherein One will Provide and other will not. This is another headache
Am I making sense?. What is your experience?
Professional Services Manager | Passionate About Helping Real Estate & Property Management Organizations Maximize Success with Yardi Systems
1 年With the adoption of Agile and mostly standardizing each project. Vendors and Partnerrs won’t consume that time analyzing niether the client’s status nor mindset. Else it is mostly projects fixed to certain processes and standard functionalities to start with and promises to enhance once the adoption increases and change management inside the organization is complete.