Thank you to the kind messages, the PoC team is inspired by them. There are so many reasons to use PoC in many areas. One example is its use by Software Developers early on in the development cycle of a software or to sell the concept of the software. Validation of technical feasibility, identification of the possible expectations from a platform, identification of potential stumbling blocks and determination of the scope and customization level required necessarily to complete a project are some of the concepts of early development cycle of a software where PoC can be used. By tokenizing PoC, it allows for this process to be open and adjusted to necessary input of an emerging PoC platform.
Fascinating!
I am interested in PoC with regard to project planning on a blockchain.
There are 4 aspects to consider while planning and executing any project like this
1. Effort and duration of the PoC.
2. Project scope
3. Choosing the resources
4. Finalizing Acceptance Criteria
I will send you a PM with my thoughts on these applied to blockchain technology.
Look forward to your response.
I would be fascinated by your thoughts on these applied to blockchain technology.
My own point of view is that these four aspects can be broken down like this (in brief terms):
Effort & Duration:
Typically a PoC should not take more than 2 weeks to be executed as then it becomes something more than a proof of concept.
We should also have 2 people working on POC so that 2 brains can work on thoughtful evaluation without any personal biases towards a certain technology or a solution (blockchain).
Project Scope:
It is important to make sure that you are defining the scope thats actually well-suited to the concept, otherwise it is a recipe for getting skewed results. Restrict the scope to find a resolution of a specific blockchain related problem rather than trying to get everything done.
Choosing the resources:
Blockchain care should be taken to ensure that the people taking part in the PoC represent the right mix of skills in order to make the project as successful as possible. While having a person to work on a completely new technology is okay but there has to be someone who can mentor and guide the POC. In the absence of which, it becomes a Research without having any tangible end point.
Finalizing Acceptance Criteria:
-Ask questions to the client.
-Do your best to lay out these questions at the outset of your evaluation, based on some defined goals for the project.
-It is important that once PoC development effort has completed you re-focus on the high-level goals in a practical manner.
-Non-functional blockchain considerations will generally be ignored unless specifically requested.
Great!!!!
A Proof of Concept (POC) is used to demonstrate the feasibility and practical potential of any blockchain project in any field such as Energy, Communication, Services, Insurance and Healthcare. A POC can either be a prototype without any supporting code or any MVP (Minimum Viable Product) with bare featureset. A POC is a prototype that is used for internal organization who can have a better understanding of a particular project.
Any project will need viable theoretical cases so that the productivity and feasibility of the product will be cleared to the potential end-users, stakeholders, etc. Create a set of proposals that will explain the parameters of the project. This proposal will be the cynosure of the forthcoming discussions.
The Theoretical process has been completed and all the stakeholders involved in the project have said their word. Now the theory will be put to test by creating a working prototype to be presented with the decision makers. It may contain information architecture, code, sketches, mockups, design and tested product.
This stage is to create a product with a minimum set of optimum features that will be actually used in the long run. A MVP is done to test the product's hypothesis on the project and see what will be feasible in the product. This stage is where the end-users might try to use it.