What is a POC? Why you should do it?
SAP implementations are usually complex and team members run into various road blocks. To minimize risks to projects your implementation should plan to do POC- Proof of Concept to close any gaps between what Business wants (expectation) and what business gets (delivered).
Requirements are captured and scope is locked and it is time for your functional and development teams to work on POC. POC should be done for those requirements completely new and there is no readily available solution in-house or on various SAP community sites. POC should not be confused with building the complete solution. The main purpose of POC is to determine the feasibility. Finding out early in the project if it can be done or not. This reduces the project risk early in the stage.
Inputs and Outputs of a good POC- Proof of Concept
- Requirements are accurately captured and clearly defined
- SAP SME’s driving POC efforts
- Facilitates business to visualize the solution
- Opportunity to tweak solution approach during design phase
- Reduce project risk
- POC closes gaps between what is expected by customer and what is ultimately delivered.
- Do not get into the trap of actual build of solution.
- Facilitates productive decisions making and improve overall project productivity.
POC is to demonstrate feasibility of some aspects of requirement and helps decide if a given requirement can go ahead with fully functional prototyping. POC also reduces build phases and your SAP technical/functional team knows the approach to the solution. With the Agile methodology getting more popular, POC plays even more critical role.