This document summarizes Ben Henderson's presentation on defining requirements through practical approaches like workshops and interviews. The presentation covers standard waterfall and agile development lifecycles, common approaches to gathering requirements, and provides examples of innovation games and exercises that can be used in workshops to help define what to build based on customer needs.

1. SharePoint Saturday
Redmond
Ben Henderson
Measure twice and cut once
A practical approach to defining what to build.

11. Agenda
→ Me
→ Dev lifecycle overview
→ Requirements
→ Approaches
→ Most common approach
→ Example

12. Oxford Brooks
university
(BSC Computing)
KVS/Veritas/Symantec
Software Test Engineer
Capgemini
Business Technology
Consultnat
Capgemini
Enterprise Architect
Colligo
Sales Engineer
Colligo
Client Services
Manager
Colligo
Product Manager
RecordPoint
Solutions Specialist

14. Requirements

15. Standard Waterfall

16. Agile

17. Waterfall
Agile

18. Must get the requirements right

20. Interviews

21. Workshop

22. Effort
Results
Considerations

23. N I H I T Oo
t
h
i
n
g
m
p
o
r
t
a
n
t
a
p
p
e
n
s
n h
e
f
f
i
c
e

24. The Modern Day Workshop
Innovation Games
• Understand your customers needs
• Deliver the right features
• Make better strategy decisions
• Increase empathy for your customers’
experience
• Improve the effectiveness of sales and
services
• Identify the most effective marketing
messages and sellable features
• Uncover breakthrough opportunities
*I am not a certified or trained instructor (yet)

25. Cover Story

26. Product Box
• Build a box that you would
want to sell to your customers.
• It can include pictures, slogans,
offers, etc.
• Enables customers to define
the vision.

27. Prune the Product tree
• Draw a tree on the whiteboard
and use post it notes for
features
• Branches are major themes
• Work to build a balanced tree

28. Buy a feature
• Give features a price
• Distribute cash
• Get people to purchase the
features that they want

29. Interviews

30. InterviewsWhat do you want?
When do you want it?
What should it do?

31. InterviewsWhat are you trying to achieve?
For what reason are you doing it?
What will make this be a success?

32. Don’t ask Questions

33. Road to Success

34. Road to Success

35. Listen

36. Take Notes
& Document

37. Review
Iterate

38. Example

39. Questions to tick off
• Who will use the calculator?
• Who is going to purchase this?
• What's important to them?

40. Process
• Gather Requirments
• Segment
• Weight them ($$)
• Prioritize
• Review
• Adjust

41. Build the amazing Product people want