10. Agile requirements principles
Focus on the goals of the
stakeholders
Bring multiple
perspectives together
Do not commit to details
until necessary
16. THE INCEPTION FRAMEWORK
KICK-OFF
PROBLEM ANALYSIS
SOLUTION DESIGN
SOLUTION DELIVERY PLANNING
CONCLUSION
17. MINIMUM MARKETABLE FEATURES
SYSTEM CONTEXT
BUSINESS PROCESS ANALYSIS
PRAGMATIC PERSONAS
LIKES & DISLIKES
UI DESIGN USER STORY MAPPING
RELEASE THEMES
STAKEHOLDER ANALYSIS
CRITICAL SUCCESS FACTORS
VISION STATEMENT
PAIN POINTS UI WIREFRAMES
NON-FUNCTIONAL REQUIREMENTS
TRADE-OFF SLIDERS USER STORIES
MINIMUM VIABLE PRODUCT
18. VISION
For (target customer)
Who (statement of the need or opportunity)
The (product name) is a (product category)
That (key benefit, compelling reason to buy)
Unlike (primary competitive alternative)
Our product (statement of primary
differentiation)
taken from Geoffrey Moore’s book Crossing the Chasm
20. MMFS
MINIMUM
How small can a product be and still deliver benefit to
someone?
Benefit can be in the form of new information, a marketing
demo or a new feature for end users
MARKETABLE
Each increment should deliver recognisable value
FEATURES
Some features cannot stand alone
Others can be split
24. Deliverables for you
Shared vision
Persona & stakeholder analysis
Roadmap
Release strategy
Product backlog
Technical architecture
UX / UI mock-ups
25. … and the option to have Valtech deliver it
Resource profile
Delivery approach
Adrid
Assumptions, decisions, risks, issues, dependencies
Engagement model
Indicative pricing by stage
26. At what cost
2-3 weeks
Multi-skilled team
Engagement manager
Busness analyst
Technical architect
User experience consultant