SharePoint Saturday UK 2012 - Have pride in your SharePoint business requirements

  • 1,183 views
Uploaded on

SharePoint Saturday UK 2012 - Have pride in your SharePoint business requirements. This session based on the work done in across a number of recent SharePoint projects and co-presented with Paul …

SharePoint Saturday UK 2012 - Have pride in your SharePoint business requirements. This session based on the work done in across a number of recent SharePoint projects and co-presented with Paul Barton from Swisslog a recent client, this session articulates the challenges and pitfalls of current requirement gathering techniques and explains how we ensured our customers were proud and happy with the requirements delivered.

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
1,183
On Slideshare
0
From Embeds
0
Number of Embeds
5

Actions

Shares
Downloads
21
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. WHY AREN’T THE BUSINESS PROUD OF THEIR REQUIREMENTS? HOW WEDELIVERED & PRACTICAL TAKE-AWAYS FOR YOURMADE THEM SHAREPOINT PROJECTS SMILE
  • 2. Buy your copy here:http://bit.ly/SPGovManifesto Discount Coupon: ‘1@nt_SPSUK12’
  • 3. Paul BartonSharePoint ArchitectSharePoint Centre of Excellencepauljrb@gmail.com | t: paulbart0n | www.swisslog.com
  • 4. Scrape away theveneer and get tothe real… Why I’m happy Scrape away the veneer to find the “why?”
  • 5. B.A: So, do you have a need for discussion boards?Stakeholder: Hmmm, discussion boards… Yes we do! BR05: Discussion Boards
  • 6. THE CHAOS REPORT:PROJECT FAILURE FACTORSSource: Chaos Report (1995)http://www.projectsmart.co.uk/docs/chaos-report.pdf
  • 7. 1. LACK OF USER INPUT
  • 8. 2. INCOMPLETE REQUIREMENTS
  • 9. 3. CHANGING REQUIREMENTS & ASSUMPTIONS
  • 10. 4. LACK OF EXECUTIVE SUPPORT
  • 11. 5. TECHNOLOGY INCOMPETENCE
  • 12. 6. LACK OF RESOURCES
  • 13. 7. UNREALISTIC EXPECTATIONS
  • 14. 8. UNCLEAR OBJECTIVES
  • 15. 9. UNREALISTIC TIMEFRAMES
  • 16. 10. NEW TECHNOLOGY
  • 17. SHARE2012REQUIREMENTSPAIN-POINTS BYDUX RAYMOND SY
  • 18. WHERE ARE YOUR REQUIREMENTS?
  • 19. * Make good stakeholders
  • 20. Stakeholder representatives dont work. Chinese whispers might be a fun as a kid. Not when trying to understand stakeholders needs.
  • 21. The right people – mardy stakeholders(NO!) Grumpy stakeholders ruin it for everyone else
  • 22. Analysis?
  • 23. Facilitation?
  • 24. Emergent
  • 25. Collaboration =“The sharing of Information and Knowledge in diverse formats between individuals, teams, departments, projects and across geographic and organisational boundariesto improve efficiencies and learning”
  • 26. Product Tree
  • 27. INFORMATIONARCHITECTURE
  • 28. Thanks for your time and attention…
  • 29. Paul BartonSharePoint ArchitectSharePoint Centre of Excellencepauljrb@gmail.com | t: paulbart0n | www.swisslog.com