1. Best Practices for Collecting User Requirements Gerry Clancy Glenn Berger

2. Requirements Provide direction for program success

3. Why Requirements are Important? Early mistakes lead to costly fixes

4. 64% - Rarely or Never Build for Value Requirements evolve over time Standish Group Study Reported at XP2002 by Jim Johnson, Chairman 20% - Often or Always

5. Where do Requirements fit? Waterfall implementation Months Hours

6. Where do Requirements fit? Agile implementation

7. Where do Requirements fit? Source: Vikas Thange Blog

8. What Benefits? Increase Productivity Streamline Processes Reduce Costs What Benefits? Increase Productivity Streamline Processes Reduce Costs Solution Concept “What?” “How Well?” “What Constraints?” “How Well?” “What Constraints?” Business Meet Goals Derive Benefits Meet Goals Derive Benefits Leverage COTS components Functional Quality of Service What NOT how Clear Define workflow Testable Performance Usability Quality Operational Standards Infrastructure Performance Usability Quality Operational Standards Infrastructure Types of Requirements Business, Functional/Technical, COTS

9. So how do you get there…. Implementing an Enterprise GIS Project9 Discuss similar industries Assess business workflows Prioritize workflows Create a plan Conduct kickoff meeting Add Details

10. Kickoff meeting 10 Bring everyone together Executive leadership important Why is it important to your organization Provide timeline and structure Break into smaller working groups

11. Approach and Agenda 11 Discuss Introductions and overview Organizations in similar industries Assess Business functions and workflows Workflows that could benefit from location information Prioritize Prioritize workflows Summarize Business People Discuss next steps Kickoff meeting Smaller working groups

12. Add a spatial component to the decision making process Get feedback and make informed decisions Get information into and out of the field Provides a common operating picture Turn data into information products Collect organize and exchange data Similar industries …what are the GIS Patterns that apply 12 Asset Management Planning & Analysis Operational Awareness Field Mobility Stakeholder Engagement Location Analytics ArcGIS

13. GIS Solutions 13 CityView Canada Building Permit Management Road Construction Planning Wilson Pym May Philippines District Planning Isovist New Zealand Campus Navigation GISi Washington Meter Data Collection SSP Innovations Tennessee Partner Award Work Orders Trimble Illinois Air Pollution Analysis ARIA Technologies France Air Quality Sensors Valarm California Fire Hydrants Cityworks Oklahoma

14. How to collect business needs… 14 Key business units 5-10 staff in each working group Look at your org chart Who are the primary users What are their business needs

15. Organization overview Organization Business Area 1 Business Function 1 Business Function 2 Business Area 2 Business Function 3 15

16. 16 Replacing Existing System Creating New Opportunity What Value are you adding Who are the Users What are the priorities Focus on the business workflow

17. 17

18. Water Department 18

19. So what should be in your GIS Plan? Vision statement Key workflows Approach – lifecycle, budget and staffing Key things you need from the rest of the organization Schedule – overview of key milestone target dates Assumptions, dependencies and risks Appendices – WBS, roles, key points of contact etc. 19

20. Requirements and Analysis You have a set of preliminary workflows Analyze and flesh out requirements What information is not clear? 20

21. Next Steps – How to add details to your business requirements Evolutionary Refinement of Requirements Tasks Working Increment Working Increment Sprint Cycle <30 Days Daily Review Product Backlog Requirements Who is it for? What is the result? Why is it needed?

22. User Story Simple, brief descriptions of functionality Primarily from a user (role) perspective Sized for planning Testable

23. As a [role], I can [feature] so that [reason]

24. Field Worker Real Estate Manager Public Citizen Analyst Data Provider

25. User Stories Simple and concise As a real estate manager, I need to interact with a map to explore new locations. As an analyst, I need the ability to create a map with pop-ups to build easy-use-maps for management. As a real estate manager, I need to receive information by clicking on potential sites to better understand the property. As a data provider I need to be able to upload my data to the client on a monthly basis, so that I can provide the most up-to-date data for analysis. As a real estate manager, I need interactive map capability on my iPad so that I can travel minimalistic during site visits. As a public citizen, I need to interact with a map to see where new permits are allowed and potential site my new business. As an analyst, I need to the ability to run hurricane models from Provider X and see the results on a map, so that I can better understand the impact on our book of business.

26. User stories facilitate a conversation with the team Product Owner Development Lead The team Stakeholders Hey! Something to look at, talk about, comment on, react to…

27. As a real estate manager, I need to interact with a map to explore new locations. As an analyst, I need the ability to create a map with pop-ups to build easy-use-maps for management. As a real estate manager, I need to receive information by clicking on potential sites to better understand the property. As a real estate manager, I need to be able to see a pie chart of surrounding demographics so that I can match consumer demand with product. As a real estate manager, I need interactive map capability on my iPad so that I can travel minimalistic during site visits. User Stories Progressively decompose your stories

28. ~~~~~~~~~~~ ~~~~~~~~~~~~~ ~~~~~~~~ ~~~~~~~~~ ~~~~~~~~~~~ ~~~~~~~~~~~~~ ~~~~~~~~ ~~~~~~~~~ ~~~~~~~~~~~ ~~~~~~~~~~~~~ ~~~~~~~~ ~~~~~~~~~ ~~~~~~~~~~~ ~~~~~~~~~~~~~ ~~~~~~~~ ~~~~~~~~~ ~~~~~~~~~~~ ~~~~~~~~~~~~~ ~~~~~~~~ ~~~~~~~~~ ~~~~~~~~~~~ ~~~~~~~~~~~~~ ~~~~~~~~ ~~~~~~~~~ ~~~~~~~~~~~ ~~~~~~~~~~~~~ ~~~~~~~~ ~~~~~~~~~ ~~~~~~~~~~~ ~~~~~~~~~~~~~ ~~~~~~~~ ~~~~~~~~~ ~~~~~~~~~~~ ~~~~~~~~~~~~~ ~~~~~~~~ ~~~~~~~~~ ~~~~~~~~~~~ ~~~~~~~~~~~~~ ~~~~~~~~ ~~~~~~~~~ ~~~~~~~~~~~ ~~~~~~~~~~~~~ ~~~~~~~~ ~~~~~~~~~ ~~~~~~~~~~~ ~~~~~~~~~~~~~ ~~~~~~~~ ~~~~~~~~~ ~~~~~~~~~~~ ~~~~~~~~~~~~~ ~~~~~~~~ ~~~~~~~~~ ~~~~~~~~~~~ ~~~~~~~~~~~~~ ~~~~~~~~ ~~~~~~~~~ ~~~~~~~~~~~ ~~~~~~~~~~~~~ ~~~~~~~~ ~~~~~~~~~ ~~~~~~~~~~~ ~~~~~~~~~~~~~ ~~~~~~~~ ~~~~~~~~~ User Stories Consider grouping them into themes

29. As a user interface, I need to look like the following image so that I can be intuitive to use Not always about [a user] Capture key concepts

30. Use Paper Cards Keep them simple and concise

31. Example – Leak Management – Isolation Trace Decomposing work into manageable pieces 31 As a Field Engineer I need to run an Isolation Trace to identify network leaks, and improve the quality of water service to all customers. Locate Leak Locate by address Configure Options Pick Trace Starting Point Select from map Summary Report Run Trace Display Trace Results Locate with Map Execute Trace Detail Report “Trace Map” Save Trace User Story Use Cases Most Detailed – Test Case Titles Field Crew Launch Mobile App Locate Leak Run Isolation Trace Notify Customers Fix Leak

32. Keep user stories visible Focus of daily meetings

33. JIRAMicrosoft Team Foundation Server (TFS) Requirement Management Tools Licensed and Open Source

34. Requirements Process Things to avoid Avoid long lists of requirements Do not be judgmental Prepare for conflicting requirements Avoid requirements that are ambiguous Avoid requirements that describe HOW (unless you are using COTS approach) Don’t forget to prioritize Requirements must have a “reason”

35. Requirements THE most important part of a project Solid requirements gathering leads to successful projects Consider solution, COTS capabilities before collecting additional requirements Involve the right people in the process Pick a methodology that fits your project Focus on the level of detail that is appropriate Important to prioritize and allocate Invest plenty of time to secure customer approval

36. References Agile & Iterative Development: A Manager’s Guide by Criag Larman, Addison-Wesley,2003 Software Requirements (2nd Edition) by Karl Wiegers, Microsoft Press, 2003 Use Case Driven Object Modeling with UML by Doug Rosenberg and Matt Stephens, Apress, 2008 Writing Effective User Cases, A Cockburn, Addison-Wesley, 2001 Agile Development with ICONIX Process by Doug Rosenberg, Matt Stephens, and Mark Collins, Apress, 2005

37. References www.agilemanifesto.org http://alistair.cockburn.us/ http://www.iconixsw.com/ http://www.pmi.org/default.aspx

38. Where to go From Here? TuesdayTimeRoom Managing an Enterprise GIS Project: What You Need to Know from the Start *8:30-9:45am08 Establish an Initial Operating Capability for Your Enterprise10:15-11:30am06C Managing an Enterprise GIS Project: Best Practices for Collecting User Requirements*10:15-11:30am08 Enterprise GIS: Security Strategy10:15-11:30am06E Enterprise GIS: Performance and Scalability1:30-2:45pm06E Managing an Enterprise GIS Project: Create a Manageable Plan3:15- 4:30pm06C WednesdayTimeRoom Managing an Enterprise GIS Project: What You Need to Know from the Start*1:30-2:45pm06E Deploying Apps in the Cloud3:15-4:30pm17A Inject GIS into your Business Systems3:15-4:30pm06E Enterprise GIS: Performance and Scalability*3:15-4:30pm06C ThursdayTimeRoom Enterprise GIS: Database Planning8:30-9:45am04 Enterprise GIS: Architecture Deployment Options1:30-2:45pm06E Managing an Enterprise GIS Project: Best Practices for Collecting User Requirements *1:30-2:45pm15B Deploying Apps in the Cloud*3:15-4:30pm06C Enterprise GIS: Security Strategy*3:15-4:30pm06E * Repeat Sessions

39. Gerry Clancy – gclancy@esri.comgclancy@esri.com Glenn Berger – gberger@esri.comgberger@esri.com Thanks