Roadmap to Product Management

Requirements
are the backbone of successful product development

Eliciting Requirements:
- investigative process: need vs want
  - asking the right question
  - actively listening
- uncover underlying requirements
Expressing Requirements
- identified, then framed
  - use cases
  - user stories
  - storyboards
- effectively communicate & document
Prioritizing Requirements
- must be vs should be completed
- understand critical needs
  - allocate resources
  - focus on the most impactful aspects
Analyzing Requirements
- ongoing process
- ensures clarity, completeness, consistency
- scrutinize the listed requirements
  - identify ambiguities/gaps
  - refine requirements to make them more effective
Managing Requirements
- address changes/evolving requirements
  - as the project progress
- organizing
- re-organizing
- potentially reusing subsets of requirements in different stages

Each serves a unique purpose in the product development lifecycle.

Business requirements
- business objectives & strategic directions
Business rules
- rules & constraints
User requirements
- specific needs
- expectations
- preferences of the end-users
Functional requirements
- defines: functions, features, capabilities
Non-functional requirements
- focus on the quality attributes of the product
  - performance,
  - security, and
  - usability.
Developmental constraints
- specify any limitations or restrictions
- e.g., technology or resource constraints