The document discusses Maslow's Hierarchy of Needs and how it relates to prioritizing software needs. It introduces a Hierarchy of Software Needs that ranks deployability, security/performance, usability, usefulness, successful adoption, and creativity at the top. Lower levels must be satisfied before focusing on higher levels. The document also provides brief instructions for a time-boxed workshop to define specific and measurable software priorities and risks.

1. Hierarchy of Software
Needs
Defining Project Priorities & Risk

2. Gojko Adzic, David Evans & Tom Roden

3. Maslow’s Hierarchy of Needs
Self-actualization
Creativity, Problem
Solving, Authenticity,
Spontaneity
Esteem
Self-esteem, Confidence,
Achievement
Social Needs
Friendship, Family
Safety and Security
Physiological Needs (Survival)
Air, Shelter, Water, Food, Sleep, Sex

4. Facts
When a lower-level need is not met we disregard
higher-level needs.
Satisfying needs on a lower-level brings
diminishing returns.

5. Hierarchy of Software Needs
Successful
Adoption rate,
operating within financial
constraints
Useful
User experience, meets key
production metrics
Usable
Usability metrics, user feedback
Security & Performance
Secure, performant, scalable & available
Deployable
Builds and deploys, functionally OK

6. Workshop Rules
 Time-boxed
 High-level business language
Avoid describing individual test cases
 Items must be specific & measurable
“Must be quick to create accounts”
vs.
“Users must be able to create an new customer account within 3 minutes”