Planning a project in the context of the BVOP is focused on the following major topics:
- Product research planning
- Major deliverables planning
- Product development planning
- Product validation planning
- Time planning
- Cost planning
- Project release planning
- Product support planning
- Project support planning
Product research planning
Product research planning may include:
- Collecting of all previously collected databases or resources from previous projects and initiatives related to users research practices and analyzing the information.
- Finding proper users for users research practices.
- Scheduling research sessions.
- Preparing tools and environment needed for the product research.
Major deliverables planning
May include planning of the product features or modules, their dependances, relations, and stages of development.
This is also planning of possible sub-products, services, external products and other related initiatives that are related and may be included in the scope of the project.
Planning includes high-level definitions of the deliverables and approximately their desired or estimated completion time presented as quarters of the year, months or other relative time units.
This plan may be helpful for planning other activities related to the product such as marketing campaigns, other parties relationships establishing or estimating high-level cost.
The use of work breakdown structures and other similar tools should not be taken as a method of helping accurate estimates of resources and time needed for project completion as it may lead to errors.
Detailed delivery, time and cost plans need to be considered as an estimate by all stakeholders, and everyone must be aware of a high probability of inaccuracies.
Product development planning
Product development planning may include:
- Choosing development methodologies
- Planning teams
- Planning meetings
- Planning resources
The product development planning characteristics
The planning of the development is recorded in brief documents for approval, discussion, introduction or future reference.
Planning documents should be easy edited and maintained when needed.
All plannings are brief and understandable by anyone involved in the project in any way.
Standard and popular terms and language are used in plans. If team members involved in the project does not understand any term they should quickly get familiar.
All documents are read by all teams and key roles.
When new team members join the project they become acquainted with the planning documentation.
Teams are informed about planning changes.
Teams have quick access to all plans.
Product validation planning
Product validation planning includes a plan of who will validate the product development progress, how and when.
Any idea, wireframe, feature, already developed functionality, and the entire product needs validation.