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

bit.ly/BuySPGovManifesto

SharePoint

Rocks!

what‘s the problem?

SharePoint Projects are

Broken

we get lost

we get wrapped up in tech

the celery effect..

SharePoint knows nothing…

tech features not outcomes

It’s Not Technology Problem

I don’t see a tech problem

we’re not focussing right

Source: Chaos Report (1995)http://www.projectsmart.co.uk/docs/chaos-report.pdf

THE CHAOS REPORT:PROJECT FAILURE FACTORS

1. LACK OF USER INPUT

2. INCOMPLETE REQUIREMENTS

3. CHANGING REQUIREMENTS & ASSUMPTIONS

4. LACK OF EXECUTIVE SUPPORT

5. TECHNOLOGY INCOMPETENCE

6. LACK OF RESOURCES

7. UNREALISTIC EXPECTATIONS

8. UNCLEAR OBJECTIVES

9. UNREALISTIC TIMEFRAMES

10. NEW TECHNOLOGY

WHERE ARE YOUR REQUIREMENTS?

Analysis?

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 off er?Free text type here

What don’t you like about it?

Free text type here

How can we improve it?

Free text type here

Facilitation?

Play?

Emergent

context

context

context

context

requirement

requirement

priority

priority

priority

Beware

Work out loud

create an evolving story

“I will not deliver SharePoint celery !”

Thanks for your time

and attention…

bit.ly/BuySPGovManifesto