SharePoint Evolution 2013 - Business Track - BUS616 - Gamestorming your way to awesome requirements

1. Gamestorming Your Way to
Awesome Requirements
BUS616
Ant Clay

4. Get it here: (Discount code: ‘SPEvo13_Rocks!’)
http://bit.ly/SPGovManifesto

5. WHY TRADITIONAL REQUIREMENTS
TECHNIQUES ARE BROKEN
KEY ELEMENTS TO
ENSURE YOUR
PROJECT DELIVERS
THE RIGHT THINGS
INSIGHTS INTO THE TECHNIQUES
YOU CAN USE TOMORROW TO
FACILITATE AWESOME BUSINESS
OUTCOMES
WELCOME

8. what‘s the problem?

9. the celery effect..

11. SharePoint knows nothing…

12. tech features not outcomes

13. It’s Not Technology Problem
I don’t see a tech problem

14. we’re not focussing right

15. Source: Chaos Report (1995)
http://www.projectsmart.co.uk/docs/chaos-report.pdf
THE CHAOS REPORT:
PROJECT FAILURE FACTORS

16. 1. LACK OF USER INPUT

17. 2. INCOMPLETE REQUIREMENTS

18. 3. CHANGING REQUIREMENTS
& ASSUMPTIONS

19. 4. LACK OF EXECUTIVE SUPPORT

20. 5. TECHNOLOGY
INCOMPETENCE

21. 6. LACK OF RESOURCES

22. 7. UNREALISTIC EXPECTATIONS

23. 8. UNCLEAR OBJECTIVES

24. 9. UNREALISTIC TIMEFRAMES

25. 10. NEW TECHNOLOGY

32. WHERE ARE YOUR REQUIREMENTS?

34. Analysis?

35. Spreadsheet / Survey?
Lame questions to ask to improve a platform
Do you like using it?
Yes No
How often do you use it?
Daily Weekly Monthly
Does it do what you want it to do?
Yes No
If no then why?
What other features should it offer?
Free text type here
What don’t you like about it?
Free text type here
How can we improve it?
Free text type here

36. Facilitation?

37. Play?

38. Emergent

51. Beware

52. Work out loud

55. create an evolving story

57. Thanks for your time
and attention…

58. Get it here: (Discount code: ‘SPEvo13_Rocks!’)
http://bit.ly/SPGovManifesto

59. Thank you for attending…
You all rock!