SUGUK Birmingham - Taking the Geek out of SharePoint Governance

1,376 views
1,330 views

Published on

SUGUK Birmingham - Taking the Geek out of SharePoint Governance

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,376
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • Introduce me and 21apps – “changing the way people work and helping our clients realise SharePoint Business Value”
  • Some of the content, particularly around f-laws was from Russell Ackoffand the SharePoint Gov/IA Master Class10% discount off our SharePoint Gov/IA Master Class if you chuck me your business card tonight…
  • Firstly some Context. SharePoint needs two main ingredients to be successful:Assurance – The technical stuff like architecture, backups, resilience, load balancing etc. that ensure that the technology platform is working.Governance – The business stuff like aligning business goals to the technology platform, Information Architecture, user adoption and solution design etc. that ensures the technology delivers measurable business value.
  • Why do we do SharePoint?Because its coolWe have to its our jobBecause your all here on a Wednesday Evening, I’m guessing there not the primary reasons?I guess you are passionate about what SharePoint can doThat it has great potential to deliver value and solve problems within our internal or external customersYes?
  • SharePoint is Awesome!Great platform, broad feature setPotential to deliver great business outcomes and “do good”I’ve seen and been a part of some great implementations, as I’m sure you guys all have?
  • So why do we hear of so many Challenges & Project Failures?Project failure – is not that you haven’t delivered SharePoint project, hit the targets on the Gannt chart – its that you’ve not delivered the expected outcomes of the businessUser Experience isn’t what they wantNot delivering business valuePoor user adoption** ASK - Whats your thoughts?
  • Tell the story of a typical Project in the old worldStrategy – cascaded downProject gets created because - IT want SharePointProject gets created because - Local Business ProblemBusiness see demo of SharePointI “want” rather than “the organisation needs”Requirements based upon SharePoint features – I want a mysite, 5 doc libraries and some workflowThe SharePoint features get delivered as requestedThe project is “in theory” a successBUT….
  • Finish the StoryAnti-climax Project Fails – bad outcomes - lots of reasons Business loose faith in IT and wonder whether we were listeningSharePoint team are wondering what the problem is, they did what was asked of them…
  • Notice I haven’t said that the technology sucksI haven’t said that SharePoint “can’t be made to do that”The technology isn’t the problem here guys…You guys are awesome and we can make SharePoint do ANYTHING… So why is this all so hard?Why are there SharePoint project problems?Why do we have a HUGE SharePoint Business Value problem?
  • Celery contains 6 calories. But the mere act of digesting said stalk burns more like 10 calories, resulting in a negative caloric intake.This is like spending lots of time and effort, licenses, hardware and project time and money, but not delivering anything the business needs¾ of SharePoint projects I was aware of over the past 5 years DID NOT deliver true Business Value** EVERYONE STAND-UP ** Sit down if you’ve seen a “Celery” SharePoint project.
  • There could be any number of reasons for SharePoint project problems, but really common ones I have witnessed are:
  • We’re looking at problems with an IT/Technology focus – SharePoint Knows Nothing…It doesn’t know your business, sector, organisation, business problem
  • No shared understanding between IT and the businessAs an asideI recommend exploring a move away from just using documented requirements and moving to more “Visual Thinking” approach:Visualisations and story-telling are very powerful techniques for gaining a shared understanding between two very different groups of stakeholders:We use and have developed a wide range of techniques that includingIssue MappingSharePoint Project CanvasEmpathy MapsDrawing on the back of a Napkin
  • We allow projects to be specified as SharePoint features not business outcomesSTORYRequirements copied and pasted from the Microsoft web site!Have any of you seen that kind of behaviour from a client?
  • IN Latin means “to steer”It doesn’t mean “Huge Document that no-one wants to read!”Steering a boat you start somewhere and you have a destination, the path you take depends on many factors.STORY - about how I sail etc
  • We have an unhappy baby, our goal is to have a happy baby (otherwise the mum will shout at us) Governance is everything we need to consider to achieve that goalIt’s an on-going process, business want an need continuous improvement (adaptive capacity)
  • Stand upSit down if you think most Governance docs are usually over 100 pages longSit down if you think most Governance docs are usually over 70 pages longSit down if you think most Governance docs are usually over 50 pages longSit down if you think most Governance docs are usually over 30 pages long
  • Microsoft governance overview doc doesn’t talk about users, requirements, value
  • Microsoft governance features doc doesn’t talk about users, requirements, value
  • This is the easy bit, well documented and lots of experts 
  • So why does a typical SharePoint project make so many assumptions about user requirements?
  • Taken from one of Jeff Conklins booksHands up who agree with that approach?There is no definitive statement of “The Problem.” It is a moving target. “they don’t know what they want”The problem is composed of an evolving set of interlocking issues and constraints. Each attempt at creating a solution changes the understanding of the problem. Therefore, the information needed to understand the problem depends on one’s idea for solving it …In order to describe a wicked problem in sufficient detail, one has to develop an exhaustive inventory for all the conceivable solutions ahead of timeA number of designers participated in an experiment in which the exercise was to design an elevator control system for an office building. All of the participants in the study were experienced and expert integrated-circuit designers, but they had never worked on eleva-tor systems before. Indeed, their only experience with elevator systems came from riding in elevators. Each participant was asked to think out loud while they worked on the problem. The sessions were videotaped and analyzed in great detail. The analysis showed, not surprisingly, that these designers worked simultaneously on understanding the problem and formulating a solution. They exhibited two ways of trying to understand the problem: efforts to understand the requirements for the system (from a one page problem statement they were given at the beginning of the session); and mental simulations (e.g. “Let’s see, I’m on the second floor and the elevator is on the third floor and I push the ’Up’ button. That’s going to create this situation....”).
  • **** This is why agile techniques fit better than waterfallThere is no definitive statement of “The Problem.” It is a moving target. “they don’t know what they want”The problem is composed of an evolving set of interlocking issues and constraints. Each attempt at creating a solution changes the understanding of the problem. Therefore, the information needed to understand the problem depends on one’s idea for solving it …In order to describe a wicked problem in sufficient detail, one has to develop an exhaustive inventory for all the conceivable solutions ahead of timeA number of designers participated in an experiment in which the exercise was to design an elevator control system for an office building. All of the participants in the study were experienced and expert integrated-circuit designers, but they had never worked on eleva-tor systems before. Indeed, their only experience with elevator systems came from riding in elevators. Each participant was asked to think out loud while they worked on the problem. The sessions were videotaped and analyzed in great detail. The analysis showed, not surprisingly, that these designers worked simultaneously on understanding the problem and formulating a solution. They exhibited two ways of trying to understand the problem: efforts to understand the requirements for the system (from a one page problem statement they were given at the beginning of the session); and mental simulations (e.g. “Let’s see, I’m on the second floor and the elevator is on the third floor and I push the ’Up’ button. That’s going to create this situation....”).
  • Just like overnight successes don’t ever happen over night they usually take years of failure and learning
  • There are Dark forces at play in your SharePoint projects, lots of things in your “project world” that influence you and challenge the project success
  • Pace of change – project timescales, resource limitationsProblem Wickedness – Can’t define the problem etcTechnical Complexity – What do we need to do to deliver?Social Complexity – people are a pain, they change their minds, they have opinions etc
  • Why are we doing this project, what are we trying to achieve? No reason then the project shouldn’t exists
  • Humffrom Nick Jnr.Look it up in wikipedia!Book - “Built to Last: Successful Habits of Visionary Companies” by James Collins and Jerry PorrasExplain BHAG – There needs to be a bold, big reason for doing the project that the SharePoint project team can believe inShared Understanding and Shared Commitment
  • PlatitudesHomer was rendered infertile from years of radiation exposure and fearing a lawsuit, they created a phony awardSharePoint platitudes:Improved CollaborationBe more ‘social’
  • Homer was rendered infertile from years of radiation exposure and fearing a lawsuit, they created a phony award
  • The power of a Big Hairy Audacious Goal and Outcomes that arent full of platitudes in SharePoint project Governance21shift modelReview of client’s home pageMapping of Vision (non platitude) to what was articulated on the home page – Home Page did not support the Vision at all!
  • Make sure the client, all their stakeholders, all the users and all your SharePoint project team have a shared understanding of the project goal/vision – make sure everyone is going in the same direction
  • Ask whose a SharePoint BA in the room?
  • Why are SharePoint Projects sooooo HARD?Because there solving business problems
  • Dave Snowden (Ex-IBM)Place of Multiple Belongings – multiple influencersSenseMaking model, not a Classification ModelHighlight Analysis versus Facilitation in each zone.SharePoint Projects are typically in the Complex zoneBusiness Problems & SharePoint projects are what I would class as “Complex” ProblemsShow the pronounced ‘canevan’ - Cynefin Matrix… Show where Business & SharePoint is versus a technology problem.Simple Domain - “Everytime you do X you get Y”Complicated Domain - “If you apply method A, on the advice of experts B and C, you will get to Z”Exchange deploymentComplex Domain - “Based on department X feedback, let’s try this new configuration of sites, document libraries, folders and content types”Business projects & SharePointChaotic Domain- “Try method A and see whether it got you any closer to Z. Review whether your understanding of Z has changed as a result”http://www.youtube.com/watch?v=N7oz366X0-8
  • SharePoint gets deployed to solve business problems, which are influenced by the ‘Dark Forces’ which means they are WICKED PROBLEMS
  • If we focus on what does the technology “allow us to do” then we end up with a technology based solution….
  • You need a way to redress the business-technology balance…
  • Use facilitation and visual tools to gain a shared understanding
  • Our solution for this is the 21shift modelGo through the model explaining briefly the purpose of each stageThen show that everything in Delivery must be traced back to support Vision & Outcomes
  • At the start of this session we said that most Technology projects fail to deliver their true valueIf you spend more time focussed on the “what and the why” then you will find your Business Project will DELIVERSharePoint can Rock!
  • Please feel free to feedback on this presentation at the URL above
  • SUGUK Birmingham - Taking the Geek out of SharePoint Governance

    1. 1. Taking the Geek out of SharePoint Project Governancewww.21apps.com @AndrewWoody #spsuk #rwsbs
    2. 2. CodeCamp / SharePoint Saturday, March 26th 2011
    3. 3. acknowledgments Management f-LAWS: Paul Culmsee:How Organizations Really Work www.cleverworkarounds.com CodeCamp / SharePoint Saturday, March 26th 2011
    4. 4. Assurance &Governance
    5. 5. why SharePoint
    6. 6. so why is it like this?
    7. 7. scary-but-true story
    8. 8. I don’t see a tech problem It’s Not Technology Problem
    9. 9. the celery effect..
    10. 10. what’s the cause
    11. 11. SharePoint knows nothing…
    12. 12. no shared understanding
    13. 13. tech features not outcomes
    14. 14. we need a different view
    15. 15. governance = “to steer” CodeCamp / SharePoint Saturday, March 26th 2011
    16. 16. steer where?
    17. 17. f-LAW 1THE MORE COMPREHENSIVE THEDEFINITION OF GOVERNANCE IS, THE LESS IT WILL BE UNDERSTOOD BY ALL CodeCamp / SharePoint Saturday, March 26th 2011
    18. 18. Microsoft’s view..
    19. 19. Microsoft’s “overview” doc
    20. 20. Microsoft’s “features” doc
    21. 21. steer where?
    22. 22. steer where?
    23. 23. f-LAW 2 THERE IS NO POINT IN ASKING USERS WHO DON’T KNOW WHAT THEY WANT, TO SAY WHAT THEY WANTCorollary: There is even less point in thinking that you already know what they want CodeCamp / SharePoint Saturday, March 26th 2011
    24. 24. knowing versus learning Cognexus Institute www.cognexus.org
    25. 25. knowing versus learning Cognexus Institute www.cognexus.org
    26. 26. opportunity driven learning “The truth about Einstein is he didnt arrive at his famous equation by complex mathematical reasoning. In fact, he didnt use mathematical or scientific reasoning at all!” CodeCamp / SharePoint Saturday, March 26th 2011
    27. 27. it took 10 full years! E=MC2 1895 1905
    28. 28. SharePoint dark forces
    29. 29. dark & divergent forces CodeCamp / SharePoint Saturday, March 26th 2011
    30. 30. knowing versus learning Cognexus Institute www.cognexus.org
    31. 31. f-LAW 4 MOST STATED GOVERNANCEOBJECTIVES ARE PLATITUDES –THEY SAY NOTHING BUT HIDE BEHIND WORDS CodeCamp / SharePoint Saturday, March 26th 2011
    32. 32. governance objectives
    33. 33. Big Hairy Audacious Goal
    34. 34. this is a platitude it can’t be measured
    35. 35. this isn’t a platitude We are proving that through better information management, we can improve our customer relationship and trust building without over-burdening our staff” it can be measured
    36. 36. this isn’t a platitude “We are proving that we can grow the organisation while reducing email volumes and centralising document storage” it can be measured
    37. 37. a client “vision” story
    38. 38. key takeaway Ensure a shared understanding of the problem among all participants“The ‘Holy Grail’ of effective collaboration is creating shared understanding, which is a precursor to shared commitment” – Jeff Conklin CodeCamp / SharePoint Saturday, March 26th 2011
    39. 39. f-LAW 12THE MORE ANALYSTS ARE CONVINCED THAT THEY EXIST TO TRANSLATE BETWEEN “I.T” AND “THE BUSINESS”, THE LESS THE PROBLEM WILL BE UNDERSTOOD BY ALL CodeCamp / SharePoint Saturday, March 26th 2011
    40. 40. CodeCamp / SharePoint Saturday, March 26th 2011
    41. 41. Cynefin framework
    42. 42. complex/wicked problems• The problem is not understood until after formulation of a solution• Wicked problems have no stopping rule• You cannot prove that all solutions have been considered• Solutions differ based on interests, values and ideology of participants
    43. 43. analyse tech requirementsfacilitate business outcomes
    44. 44. SharePoint projects are people projects
    45. 45. technical project Ant-idote
    46. 46. stop talking tech features
    47. 47. use facilitation & visual tools
    48. 48. re-focus your efforts
    49. 49. IdentityRealisation Vision SharePoint Business Value Delivery Outcomes Solution
    50. 50. http://bit.ly/Feedback2Ant CodeCamp / SharePoint Saturday, March 26th 2011
    51. 51. Thanks for your time & attentionwww.21apps.com @AndrewWoody #spsuk #rwsbs

    ×