The following article is part of the self-preparation for the modern BVOP® Product Management Certification program.
Product development practices in the context of BVOP are focused on crafting concepts, designing prototypes, testing results, creating artifacts and final usable end-results.
- Creating concepts
- Concepts validation by users with product knowledge
- Creating functional prototypes
- Prototype testing by users with product knowledge
- Creating a usable end result
- End-result testing by users with product knowledge
Whatever practices are used for product development, the BVOPDM office needs to implement practices that ensure valid and actual end-results. Recommended steps include:
- Creating concepts.
- Validation of the concepts by users with product knowledge.
- Creation of functional prototypes.
- Users with product knowledge testing the prototypes.
- Creation of a usable end-result.
- Users with product knowledge testing the end-result*.
Users with product knowledge may be considered:
- Real users already using or intending to use the product or using a similar product
- Potential users
- Representatives with extensive product knowledge
*End-result: feature, part of a product, module or current version
The concept in the context of the BVOP is not a functional prototype or any other piece of work that requires extensive time or resource consumption. Concepts may be drawings, videos, sketches, paper prototypes, wireframes, charts, explanatory text materials, or any other materials that can present an early idea and vision about the future product or parts of the product.
The sources for the creation of the concepts are the product vision, the previously gathered information from internal organizational assets and external third parties or other users and sources with product and market knowledge.
Concepts have to be created fast to avoid time wastes and their ideas have to be presented clearly.
They present realistic user needs, solutions, and values.
After a concept is created, a validation process needs to confirm its value and authenticity or reject it.
Users with product knowledge evaluate the concept during a validation session. Users point out the weak and strong features.
Validation session requires the participation of more than one individual because rejecting or accepting the concept is a group process.
If a concept is fully rejected, a new concept, presenting a clear idea, should be created as soon as possible.
If a concept has some value, its positives are documented, and the following concepts are based on them.
After a concept is validated and approved, creating a functional prototype may provide a more valuable and precise vision of the end product or some of its features.
A functional prototype in the context of the BVOP is the result of a concept, which has been validated, accepted and includes a more realistic presentation of the product. It may be a physical model or very early-stage version of a software or other digital product.
The product features are usually only visually presented, simulated where applicable, or implemented at some working level with minimum efficiency and quality.
Testing the prototypes ensures a level of confidence in the future development. After a functional prototype is built on some satisfactory level, it should be validated against the real user needs, experience, expectations, and usability issues.
Users with product knowledge test the functional prototype, and their feedback is recorded for future use in the prototype improvements and development.
Testing the prototypes for usability issues may be conducted with any popular user testing protocol, such as “Cognitive walkthrough”, “Think-aloud protocol”, “Wizard of Oz”, or any other suitable method.
Modifications, combinations, and creating custom testing protocols are also recommended.
After the test sessions, some issues are usually documented, and improvements on the prototype may be implemented.
After the prototype is validated and agreed upon as satisfactory, the teams develop the real product or parts of it. At this stage, all the product concepts and prototypes are evaluated as accurate and reliable. The product development continues to the end-goals.
This stage is usually the longest and requires massive amounts of time, resources, communications, a collaboration between many teams inside the organization.
Just like the prototypes, the end-result needs to be tested regularly against real user needs, experience, expectations, and usability issues.
A test and validation session after every major update of the end-result prove that the product is being developed according to the precise needs and business direction.
It is good practice to create and maintain a brief record during product development that can help with all testing and validation in the future.
When the end-result is released, and it is in a real-world environment, it is strongly recommended to track, record and analyze the behaviour of a large number of real users.
The following issues related to chapter "Product development practices" are included in the certification exam. The sequence of questions is presented in the table.
The data is current as of February 25, 2021, 12:23 pm
|0||Creating concepts||60 sec||PDM, PM|
|1||End-result testing by users with product knowledge||60 sec||PDM, PM|
|2||Prototype testing by users with product knowledge||60 sec||PDM, PM|
|3||Creating functional prototypes||60 sec||PDM, PM|
|4||Creating a usable end result||60 sec||PDM, PM|
|5||Concepts validation by users with product knowledge||60 sec||PDM, PM|