|
Product Manager
|
|
|
The Product Manager
|
|
|
Product Managers, sometimes called Business Analysts or Product Owners, are responsible
for the content and relevance of the software solution being developed. Peter Druker
called this ‘Utility Value.' The best product managers understand that the utility
value of a system is defined by the users of the system, not the designers.
Effective product managers seek the voice of their customers to assemble and prioritize
new features and bug fixes. Effective product managers should be familiar with the
following concepts:
- Minimal Marketable Feature set (MMF)
- The technology adoption lifecycle
- Catering separately to Innovators, Early Adopters, Both Majorities, and Laggard
- Various survey techniques (paper, web, phone, trade-show, in person)
- How to conduct a strategy assessment against a global or widespread user base
- How to validate utility value (conformance to requirements)
- How to validate user acceptance (fitness for use)
- How to validate requirements against business objectives 8. How to identify and
prioritize stakeholders
- How to elicit, analyze, specify, and validate requirements
- Types of requirements
- How to work successfully with technical and non-technical stakeholders
- How to work successfully with the development team
- How to build a business case
- How the organization can perform and benefit from ROI validation
Red Rock Research provides software development best practice seminars that cover
this material.
|
|
|
|
|
|
Business Analyst
|
|
|
The Role of the Business Analyst
|
|
|
Product Managers, sometimes called Business Analysts or Product Owners, are responsible
for the content and relevance of the software solution being developed. Peter Druker
called this 'Utility Value.' The best product managers understand that the utility
value of a system is defined by the users of the system, not the designers.
Effective product managers seek the voice of their customers to assemble and prioritize
new features and bug fixes. Effective product managers should be familiar with the
following concepts:
- Minimal Marketable Feature set (MMF)
- The technology adoption lifecycle
- Catering separately to Innovators, Early Adopters, Both Majorities, and Laggard
- Various survey techniques (paper, web, phone, trade-show, in person)
- How to conduct a strategy assessment against a global or widespread user base
- How to validate utility value (conformance to requirements)
- How to validate user acceptance (fitness for use)
- How to validate requirements against business objectives 8. How to identify and
prioritize stakeholders
- How to elicit, analyze, specify, and validate requirements
- Types of requirements
- How to work successfully with technical and non-technical stakeholders
- How to work successfully with the development team
- How to build a business case
- How the organization can perform and benefit from ROI validation
Red Rock Research provides software development best practice seminars that cover
this material.
|
|
|
|
|
|
|
|