Downloaded 60 times
Uploaded byRuven Gotz
SPTechCon - July 2012 - Effective requirements gathering workshops
The document discusses best practices for organizing requirements gathering workshops to implement a SharePoint system, including using tools like Mindjet and Balsamiq to map workflows, documents, and taxonomies, and gathering information on user needs through departmental interviews and examining processes. The goal is to understand organizational goals and user needs to design a system that meets requirements and avoids "kitchen sink" approaches or solutions that do not address real needs.
More Related Content
Similar to SPTechCon - July 2012 - Effective requirements gathering workshops
More from Ruven Gotz
![[BDD 2025 - Full-Stack Development] Agentic AI Architecture: Redefining Syste...](https://cdn.slidesharecdn.com/ss_thumbnails/fs-agenticaiarchitectureredefiningsystemcommunication-251124030838-e6c70cc2-thumbnail.jpg?width=640&height=640&fit=bounds)
![[BDD 2025 - Full-Stack Development] The Modern Stack: Building Web & AI Appli...](https://cdn.slidesharecdn.com/ss_thumbnails/fs-themodernstackbuildingwebaiapplicationswithserverless-251124030844-388cf04f-thumbnail.jpg?width=640&height=640&fit=bounds)
![[BDD 2025 - Artificial Intelligence] Building AI Systems That Users (and Comp...](https://cdn.slidesharecdn.com/ss_thumbnails/ai-buildingaisystemsthatusersandcompanieslove-251124030845-038f7732-thumbnail.jpg?width=640&height=640&fit=bounds)
![[BDD 2025 - Mobile Development] Mobile Engineer and Software Engineer: Are we...](https://cdn.slidesharecdn.com/ss_thumbnails/md-mobileengineerandsoftwareengineerarewestillrelevantsidiqpermana-251127010650-55224ef1-thumbnail.jpg?width=640&height=640&fit=bounds)
![[BDD 2025 - Full-Stack Development] Digital Accessibility: Why Developers nee...](https://cdn.slidesharecdn.com/ss_thumbnails/fs-digitalaccessibilitywhydevelopersneedtoknowandcarein2025-251127011019-0674441d-thumbnail.jpg?width=640&height=640&fit=bounds)
SPTechCon - July 2012 - Effective requirements gathering workshops
- 1. Effective Requirements Gathering Howto organize and run your workshops Ruven Gotz
- 2. @ruveng spinsiders.com/ruveng Toronto ruveng@navantis.com Ruven Gotz
- 3. Effective Requirements Gathering Howto organize and run your workshops
- 4. What makes somethinga requirement? © 2011 Ruven Gotz
- 5. We can dothat for $10
- 6. We can dothat for $1 Million © 2011 Ruven Gotz
- 7. We require ajumbo solution to get to our destination
- 8. © 2011 RuvenGotz
- 9. We require ajumbo solution to get to our destination
- 15. Sometimes, you doneed this
- 16. It’s the destinationthat matters: The outcome © 2011 Ruven Gotz
- 17. Kitchen sink projects © 2011 Ruven Gotz
- 18. Your project willchange over time © 2011 Ruven Gotz
- 19.
- 20. More than halfof “required” features never get used
- 21. Result of akitchen sink project
- 22. Shift gears © 2011 Ruven Gotz
- 23. SharePoint chicken &egg problem © 2011 Ruven Gotz
- 24. Based on real-worldexperience © 2011 Ruven Gotz
- 25. Take away: ToolsYOU can use © 2011 Ruven Gotz
- 26. © 2011 RuvenGotz
- 27. Remaining Agenda © 2011 Ruven Gotz
- 28. DON’T demo SharePoint © 2011 Ruven Gotz
- 29. Initial discovery workshop © 2011 Ruven Gotz
- 30.
- 31. Agenda • About the Project , Our Team & Goals • SharePoint Overview • Department and Role • Document Collaboration • Document Storage and Search • Compliance, Records Management & Off-line • Questions © Ruven Gotz 2011
- 32. About the Project,Our Team & Goals About this Project • Determine the requirements and scope for a SharePoint implementation at ABC Corp. Our Team • Alison Andrews – Project Manager • Bob Baker – Technical Architect • Carol Conrad – SharePoint Analyst • Don Drummond – Infrastructure Analyst Workshop Goals • Set expectations • Gather your input • Keep it to an hour (+ optional half-hour for further questions) © Ruven Gotz 2011
- 33. SharePoint 2007 Overview Server-basedMicrosoft Documents/tasks/calendars, blogs, wikis, e-mail integration, project Office Excel® Business Collaboration management “lite,” Outlook spreadsheets and data visualization, Report Intelligence integration, offline documents/lists Center, business Virtual Teams/Global Teams intelligence Web Parts, KPIs/Dashboards Platform Services OOB workflows, Business Workspaces, Mgmt, Enterprise Portal WF integration, Process Security, Storage, Portal template, Site Topology, Site Model Directory, My rich and Web forms– and Sites, social based front-ends, LOB actions, pluggable Forms networking, privacy SSO control Enterprise Integrated document Content Search management, records Management Enterprise scalability, contextual management, and Web content relevance, rich search for people management with policies and and business data workflow © Ruven Gotz 2011
- 34. Ribbon UI SharePoint 2010 Overview SharePoint Workspace SharePoint Mobile Business Connectivity Services Office Client and Office Web App Integration InfoPath Form Services Standards Support External Lists Intranet, Extranet, Team Collaboration Workflow SharePoint Designer Visual Studio Tagging, Tag Cloud, Ratings API Enhancements Social Bookmarking REST/ATOM/RSS Blogs and Wikis Building complex solutions on top of SharePoint My Sites Activity Feeds Profiles and Expertise PerformancePoint Services Org Browser Excel Services Chart Web Part Visio Services Web Analytics SQL Server Integration PowerPivot Business Intelligence Enterprise Content Types Metadata and Navigation Social Relevance Document Sets Phonetic Search Multi-stage Disposition Navigation Audio and Video Content Types FAST Integration Remote Blob Storage Enhanced Pipeline List Enhancements Search Organizing Information © Ruven Gotz 2011
- 35. Department and Role Pleaseintroduce yourself: • Name • Department • What is your role within your department? • How do you interact with technology to do your job? • How does the current technology help you (or hinder you) from doing your job? © Ruven Gotz 2011
- 36. Document Collaboration • Doyou work on documents with others? • How do you collaborate (e-mail, shared drive) ? • What document types do you create? • Which programs do you use? • Do your documents require multiple reviews and edits? Is approval required? • How do you implement the required workflow? • How do you get the final information out to the audience that needs it? • Do you publish PDF’s? • How are they distributed/posted? © Ruven Gotz 2011
- 37. Document Storage andSearch • Can you find the documents that you need, when you need them? • Does your shared drive folder hierarchy work well? • How long does it take to find a document? At what point do you give up? • When you create a document, do you know where it should be saved? • Are documents saved in more than one location to ease retrieval? • Does search work well? • What features would you like to see in search that would make it better for you and your team. © Ruven Gotz 2011
- 38. Compliance, Records Management& Off-line • Do you have any regulatory requirements that you need to meet? • ISO 9000 • Sarbanes-Oxley – Bill 198 • How are records management policies implemented? • Are there specific policies for document retention and destruction. • Do you have a need for off-line access? • Do you travel off-site for your work • Do you need to work when you are disconnected from the network. © Ruven Gotz 2011
- 39. Questions © Ruven Gotz 2011
- 40. Roadmap © 2011 Ruven Gotz
- 41. OK to demoSharePoint © 2011 Ruven Gotz
- 42. © 2011 RuvenGotz
- 43.
- 44.
- 45.
- 46. Mind Mapping Demonstration © 2011 Ruven Gotz
- 47.
- 48. Navigation workshops © 2011 Ruven Gotz
- 49. Navigational Map © 2011 Ruven Gotz
- 50. Document inventory workshops © 2011 Ruven Gotz
- 51. Explain Metadata © 2011 Ruven Gotz
- 52. Document Inventory Worksheet © 2011 Ruven Gotz
- 53. Build the Taxonomy © 2011 Ruven Gotz
- 54. Document Inventory TaxonomyMap © 2011 Ruven Gotz
- 55.
- 56. Balsamiq © 2011 Ruven Gotz
- 57. Business Process Workshops © 2011 Ruven Gotz
- 58. My Goals forYou © 2011 Ruven Gotz
- 59. Ruven Gotz Tools Mentioned: @ruveng - Mindjet MindManager - Balsamiq Mockups spinsiders.com/ruveng - BizAgi Entry Level - Microsoft Visio ruveng@navantis.com
Editor's Notes
- #2 (Thanks to Richard Harbridge for this title slide.)
- #4 (Thanks to Richard Harbridge for this title slide.)
- #6 Requirements is not the right word!(First heard this distinction from Sue Hanley)
- #7 Requirements is not the right word!(First heard this distinction from Sue Hanley)
- #8 Because I said so, and I’m the customer.If you don’t include my requirement, I’ll shootOne of my biggest jobs as a SharePoint BA is to manage this desire. My three rules of SharePoint: Simplicity, simplicity, simplicity
- #9 Go for it!
- #10 Wait a sec – maybe we can think of some alternatives(Hey! Maybe it’s no longer a ‘requirement’)
- #11 So, what happens when the customer says “I need this”This is the “we need it all” solution – often arrived at before defining the problemThe “Hammer” problem
- #13 So, what happens when the customer says “I need this”This is the “we need it all” solution – often arrived at before defining the problemThe “Hammer” problem
- #14 Think about alternatives:Is it close by?
- #15 How fast do I need to get there – who needs to come with me
- #16 Is a less flexible but more cost-effective solution already out there
- #17 Is the destination specialized and particularly hard to get to?
- #18 Maybe we need to really think outside the box
- #19 Simple is not ALWAYS the best solution: There are times when a complex and expensive solution is the only way to get the required destination
- #20 Bottom line: Arrive at outcomes, not requirements
- #21 The other problem with requirements is that you only have one time to mention them, so you want ALLLLL of them to be met.So, you put everything in that you can think of…SharePoint lets you be ‘agile’Start with the three rules: Simplicity/Simplicity/SimplicityIdeas from: PragPub Feb 2011 – Pragmatic ProgrammersWay of the Agile Warrior - by Jonathan Rasmusson
- #22 But the reality is that most requirements never get used as designed because the landscape changes under your feet.
- #23 And this causes you to change course, sometimes even before that ‘required’ item is even finished being built or tested.
- #24 Leading to a bunch of rusty tools lying around that cause trouble for years.e.g. what happens when you need to upgrade or migrate? Someone has to chip the rust off to see if this stuff is even useful anymore
- #25 The result is wasted money
- #26 So, shifting gears: I’ve explained what we should not be doing. What CAN we do?
- #27 What would you like SharePoint to do?Well, what can it do?Tons! Let me show youWhat do I need that for?Well, it depends… what do you want it for?Well, it LOOKS cool – sure: I want it.
- #28 I’m going to share the tools and techniques that I have built up out of painful experience.
- #29 My goal for you: Ability to move forward confidently, knowing that you have increased your chances of delivering a solution that really works for your customers.
- #30 Favorite phrase: If you don’t know where you’re going, any path will get you there.
- #31 Discovery, Road-mapping, Navigation, Document Inventory/Taxonomy, Wireframing, Business Process
- #32 But First: DO NOT DEMO SharePoint Confuses peopleSets unreasonable expectations
- #33 The focus here needs to be on pain points and outcomes: NOT RequirementsTry to stick to one team at a time3 – 8 people is ideal – up to 12-15 can work.Need to make sure you hear from everyoneDon’t let manager dominateMake SURE you get front-line workers, not just managersBook 1.5 hours – plan on an hour and a bit.People love some extra un-booked time at the end.
- #34 The following slides are a sample deck that I use in workshops
- #44 If you are lucky, you can take the results of these workshops and create a roadmap for a phased, rational approach to SharePoint deployment. Push HARD to do this step.Summarize workshop resultsBuild Gap AnalysisIdentify dependenciesLay out a timeline (not a project plan at this point)
- #45 Use their language, colors, logoShow ‘day in the life’ type scenario
- #46 A little detour into shared understanding
- #47 To achieve success, you need shared commitmentTo get that, you need to get to shared understandingSing from the same song-book: Get onto the same pageIf this area really interests you, speak to Ant Clay of 21 Apps – they run the SharePoint IA Master Class
- #48 What is this a picture of?With a lot of experience, training or imagination, you may figure something out – but the concept is ABSTRACT
- #49 This is something that people understand and agree on.It is concreteVisual tools can help make the abstract into the concrete
- #50 MindManager (from MindJet) is a tool that has changed the way I work. Here is a quick demo of how it works.
- #51 Now lets get back on-track
- #52 Site navigation/Menus
- #53 Using Mind Maps for navigational design makes this process MUCH faster and more efficient.
- #54 First, I do a presentation about what metadata is to a collection of groupsGive them homeworkThen, bring them back to build taxonomy: This needs to be done with just one group at a time
- #55 Folders/Folders/FoldersShow a familiar tool – Excel – to simulate a document library
- #56 This is the homework for the stakeholders: Go and examine your files and, for each type of document, list the potential metadata that may be used.
- #57 Note: Picture of ‘tacks’ is a visual joke – it doesn’t mean anything
- #58 This taxonomy map is built interactively with the client based on the homework that they’ve done
- #59 What is wireframing?Creating page mockups that show the function and structure of the page without the fonts/colors/images, etc
- #60 This tool called ‘Balsamiq’ makes it extremely simple and fast to make wireframes.They look cartoonish, but that makes it easy to focus on what’s important (not color, font, etc.)
- #61 Even without building an automated workflow, it’s essential to understand the business process of your customers.Use BizAgi (which is free to download) or Visio 2010 to map these processes.
- #62 Solve the Chicken and Egg problemAvoid the pain of past mistakesGive you tools that you can learn that will make your projects go better.