Recently I have been asked that how do I deliver small projects or tasks? What is my approach to solve a problem/task?
Well I said POC (Proof of Concept) because I think it is a one of cost effective way to tackle small projects and tasks, Also it helps to deliver 80 percent functionality or requirements asked by users. It also backs KISS (Keep it Simple Stupid!) rule. Most often stack holders are not so clear with their ideas or concepts, or not able to put a business cases against the benefits over ROI, which I think its fair on them, POC can rescue it. I see it as a tool that try before you buy in. I consider this as maximum throughput of Return on Investment. Also it will give a chance to refine complex processes to more normal forms.
Right so let us understand what is POC?
Proof Of Concept
A Proof of concept (POC) is a realization of a certain method or idea to demonstrate its feasibility, whose purpose is to verify that some concept or theory has the potential of being used. A proof of concept is usually small and may or may not be complete.
A proof of concept in software aims to determine the solution to some technical problem or to demonstrate that a given configuration can achieve a certain throughput.
The Proof of Concept approach – A Time Travel to a successful Project
The Proof of Concept approach is practiced for various client requirements to provide the customer with the opportunity to “test drive” core processes in order to validate its needs are met as expected. The value proposition for a customer doesn’t end there-by investing a part of the total project cost up-front customers are able to identify and circumvent complex challenges that could become showstoppers later. In this way, a Proof of Concept would act as the first step of the blueprinting phase – very much like a conduit or bridge to a successful project launch. By leveraging the POC approach, we were able to rapidly prototype core business processes as requested by the customer.
p align=”justify”>The Proof of Concept approach Benefits
Clarity in need/problem formulation;
Number/quality of new ideas;
New ways of thinking;
Level of planning;
Management of time;
Efﬁciency of execution;
Low in budget;
Low in risk;
Right so we understand the POC and its process but actually can you explain it with an example?
A Successful Client Consulting
Yes sure Let us say for an example, As an admin I want a dashboard which allows me to monitor who has login to the system and reports on their action lists such as assigned, pending and completed tasks.
I have estimated the work involved in it was around 6 days and budget was around £1500.
So with a POC approach, I have created a web application which has functionality of above and simple report on action lists of the user and user management functions such as CRUD. Now with an exception of no need of prettiness on look and feel wise but signed off on a condition if approved then they will allocate more fund on further development.
After It was demonstrated successfully and stack holders has given further requirements to enhanced functionality and user experience.
The technologies I have used was MVC, ASP.NET and SignalR (which gives me real time update on who is logged in).
Consultant engagements beyond simply purchasing expertise require the development of a relationship between the consultant and the client.
Consultants add value by addressing both content and process issues based on expertise, methodology and general problems solving skills.