Open handbook navigation

Appendix

The difference between the project approach and the product

Comparison of project and product approaches: goals, deadlines, responsibilities, financing, metrics and completion criteria.

Project and product approaches solve different management problems. The project is optimized for the agreed volume, time and budget; the product is optimized for a sustainable result for the user and business. In practice, companies often combine both regimes, so it is more important to clearly agree on the criteria for the success of a particular initiative.

ProjectProduct
Specific deadlinesWorking in an uncertain and often changing context
Limitation of requirementsB***** greater liability and risk
Simultaneous participation in two or more projectsFocus on one product, only priorities and metrics can be changed
Specific stakeholdersConstant work with market analytics and search for new sources of information
Expected fast resultResult over long or indefinite time
Frequently changing tasks and communication from project to projectSearch and continual expansion of communications
Continuous generation of new ideas
ParameterProject approachProduct approach
GoalMinimum resources for planned output in timeMaximum value within allocated resource
Team responsibility for the productFor a fragment of the product’s life, its creation with transfer to operational activitiesFor all stages of the product’s life, from hypothesis to its end
Definition of Requirements for the ResultAt an Early Stage (TK, Project), from Project CustomerConstantly (Hypothesis, Prototype, Pilot, Release) by Client
Value deliveryFully, but at the end of the project (as well as the main feedback)Rhythmically in parts, as early as possible for feedback
Task allocation mechanicsStart-up plan, detailed as implemented (equal to team resource)Sliding task portfolio prioritized by product owner (more team resource)
TechnologyManagement of plan, project scope, resources, risksRepetitive short cycle
Success criteriaTimeline and budget, performance requirements, KPIPerformance of product/portfolio metrics (effect)
BenefitsMinimum cost in the required time and result, including: When the first value is not achievable in the short termIncreased effect under uncertainty