Sometime it can be really hard to structure a Proof of Concept. To acknowledge the time for implementation, to define the goals or the learnings we want to reach by the end of the implementation are often difficulties. So a PoC must have a clear, small and reachable scope within the upon agreed small period of time. This post is all about the logic I follow to support my decisions to structure a PoC.
Sometimes when we are requested to present a Product Road-map it is hard to start… Start from where? Which features? Which inter-dependencies? How to define priorities? Priorities in the order of the tasks or in the features to enhance product value?