Download - Shepherding User Requirements with TFS
![Page 1: Shepherding User Requirements with TFS](https://reader030.vdocuments.site/reader030/viewer/2022032421/55a783131a28ab2b3e8b48ab/html5/thumbnails/1.jpg)
Shepherding User Requirements with TFSPatrick Tucker
KiZAN Technologies
![Page 2: Shepherding User Requirements with TFS](https://reader030.vdocuments.site/reader030/viewer/2022032421/55a783131a28ab2b3e8b48ab/html5/thumbnails/2.jpg)
About Me
▪ Practice Lead, KiZAN PREP Team (Process, Requirements, Experience & Planning)
▪ 17+ years as a developer, enterprise architect, trainer, speaker and business analyst
▪ TuckersNet.AzureWebSites.net
▪ www.KiZAN.com
![Page 3: Shepherding User Requirements with TFS](https://reader030.vdocuments.site/reader030/viewer/2022032421/55a783131a28ab2b3e8b48ab/html5/thumbnails/3.jpg)
Summary
▪ Tools shouldn’t drive process, but the focus of this discussion is on how requirements live and travel through TFS
▪ We will look at gathering, grooming and protecting requirements using Visual Studio Online, the cloud version of TFS
▪ Our focus will be on Scrum and Agile, so we will be talking about functional and technical requirements related to those process templates
▪ Our focus will tend toward software development projects
![Page 4: Shepherding User Requirements with TFS](https://reader030.vdocuments.site/reader030/viewer/2022032421/55a783131a28ab2b3e8b48ab/html5/thumbnails/4.jpg)
Requirements Are Like Sheep
1.They must be gathered2.They must be guided and groomed3.They must be protected
![Page 5: Shepherding User Requirements with TFS](https://reader030.vdocuments.site/reader030/viewer/2022032421/55a783131a28ab2b3e8b48ab/html5/thumbnails/5.jpg)
They must be gathered…
![Page 6: Shepherding User Requirements with TFS](https://reader030.vdocuments.site/reader030/viewer/2022032421/55a783131a28ab2b3e8b48ab/html5/thumbnails/6.jpg)
Gathering Requirements
▪ What types of requirements do you gather?
▪ Where/How do you currently store requirements?
▪ How do you gather them?
▪ What tools help you gather requirements?
Types Business Functional
Where BRD Excel
How Interviews Wireframes
Tools Use cases User stories
![Page 7: Shepherding User Requirements with TFS](https://reader030.vdocuments.site/reader030/viewer/2022032421/55a783131a28ab2b3e8b48ab/html5/thumbnails/7.jpg)
End in Mind
Once we gather those sheep (uh . . . requirements), where are we going to put them?
Team Foundation
Server
Visual Studio Online
VS Online is FreeWeb based interfaceCan be opened in Visual Studio
What do you first think of when you hear TFS?
![Page 8: Shepherding User Requirements with TFS](https://reader030.vdocuments.site/reader030/viewer/2022032421/55a783131a28ab2b3e8b48ab/html5/thumbnails/8.jpg)
Creating the Project
![Page 9: Shepherding User Requirements with TFS](https://reader030.vdocuments.site/reader030/viewer/2022032421/55a783131a28ab2b3e8b48ab/html5/thumbnails/9.jpg)
TFS Template Options
Scrum
CMMI
Agile
![Page 10: Shepherding User Requirements with TFS](https://reader030.vdocuments.site/reader030/viewer/2022032421/55a783131a28ab2b3e8b48ab/html5/thumbnails/10.jpg)
Gathering and Adding Requirements
Requirement
Add Requirements, User Stories or Product Backlog items under features, depending on the template.
FEATURE
![Page 11: Shepherding User Requirements with TFS](https://reader030.vdocuments.site/reader030/viewer/2022032421/55a783131a28ab2b3e8b48ab/html5/thumbnails/11.jpg)
DemoCreating a Visual Studio Online project and choosing a template
![Page 12: Shepherding User Requirements with TFS](https://reader030.vdocuments.site/reader030/viewer/2022032421/55a783131a28ab2b3e8b48ab/html5/thumbnails/12.jpg)
The BacklogCreating a repository for requirements
![Page 13: Shepherding User Requirements with TFS](https://reader030.vdocuments.site/reader030/viewer/2022032421/55a783131a28ab2b3e8b48ab/html5/thumbnails/13.jpg)
The “Product Backlog”
▪ This is a backlog of all requirements
▪ May contain functional, non-functional, technical, and user interface requirements
▪ May be organized into features and work items
▪ What level of detail is best?
![Page 14: Shepherding User Requirements with TFS](https://reader030.vdocuments.site/reader030/viewer/2022032421/55a783131a28ab2b3e8b48ab/html5/thumbnails/14.jpg)
Zooming In
▪ 2 of 3 Cs – Card and Conversation (Confirmation comes later)
▪ Features (or Epics) create the framework around required areas of functionality
▪ User stories, requirements or PBIs gather initial detail
![Page 15: Shepherding User Requirements with TFS](https://reader030.vdocuments.site/reader030/viewer/2022032421/55a783131a28ab2b3e8b48ab/html5/thumbnails/15.jpg)
Requirements
▪ Requirements, User Stories or Backlog Items
▪ Can be mapped to Features
• Details• “As a business analyst, I can
write user stories so that developers can do work”
• Implementation• Tasks created by developers
• Attachments• Planning
• Story points, risk and ranking• Classification
• When do we do it?
![Page 16: Shepherding User Requirements with TFS](https://reader030.vdocuments.site/reader030/viewer/2022032421/55a783131a28ab2b3e8b48ab/html5/thumbnails/16.jpg)
Sheep Can Be Tagged
▪ Tags can be added as metadata to work items
![Page 17: Shepherding User Requirements with TFS](https://reader030.vdocuments.site/reader030/viewer/2022032421/55a783131a28ab2b3e8b48ab/html5/thumbnails/17.jpg)
Portfolio Backlogs
▪ If you need more than two levels of hierarchy for requirements, additional work item types can be created
![Page 18: Shepherding User Requirements with TFS](https://reader030.vdocuments.site/reader030/viewer/2022032421/55a783131a28ab2b3e8b48ab/html5/thumbnails/18.jpg)
Tools for Requirements Gathering
▪ You can use TFS/VSO and PowerPoint together to create storyboards
![Page 19: Shepherding User Requirements with TFS](https://reader030.vdocuments.site/reader030/viewer/2022032421/55a783131a28ab2b3e8b48ab/html5/thumbnails/19.jpg)
DemoBuilding a backlog of features and work items
![Page 20: Shepherding User Requirements with TFS](https://reader030.vdocuments.site/reader030/viewer/2022032421/55a783131a28ab2b3e8b48ab/html5/thumbnails/20.jpg)
They must be groomed…
![Page 21: Shepherding User Requirements with TFS](https://reader030.vdocuments.site/reader030/viewer/2022032421/55a783131a28ab2b3e8b48ab/html5/thumbnails/21.jpg)
Backlog Grooming
▪ Refinement after conversation; Adding detail and revising effort
▪ In Scrum parlance, Moving from “Product Backlog Item” to “Sprint Backlog Item”
![Page 22: Shepherding User Requirements with TFS](https://reader030.vdocuments.site/reader030/viewer/2022032421/55a783131a28ab2b3e8b48ab/html5/thumbnails/22.jpg)
Areas and Iterations
▪ Part of backlog grooming is deciding what is in or out of the current work
▪ Areas define projects (or manual sub-areas) and iterations define a set of work items to be addressed in a given time frame
▪ In an agile project, when should detail be added to user stories?
![Page 23: Shepherding User Requirements with TFS](https://reader030.vdocuments.site/reader030/viewer/2022032421/55a783131a28ab2b3e8b48ab/html5/thumbnails/23.jpg)
Gotta Find ‘em to Groom ‘em
▪ Queries can help to quickly and repeatedly locate items in the backlog
![Page 24: Shepherding User Requirements with TFS](https://reader030.vdocuments.site/reader030/viewer/2022032421/55a783131a28ab2b3e8b48ab/html5/thumbnails/24.jpg)
Prioritizing and Tracking
▪ A “Kanban” style board is provided
▪ Columns and workflow can be customized
![Page 25: Shepherding User Requirements with TFS](https://reader030.vdocuments.site/reader030/viewer/2022032421/55a783131a28ab2b3e8b48ab/html5/thumbnails/25.jpg)
Get a Room
▪ The conversation around requirements can happen in a TFS “room” when needed
▪ Manually added messages and automated event tracking
![Page 26: Shepherding User Requirements with TFS](https://reader030.vdocuments.site/reader030/viewer/2022032421/55a783131a28ab2b3e8b48ab/html5/thumbnails/26.jpg)
DemoEditing and reorganizing backlog items and using the “Board”
![Page 27: Shepherding User Requirements with TFS](https://reader030.vdocuments.site/reader030/viewer/2022032421/55a783131a28ab2b3e8b48ab/html5/thumbnails/27.jpg)
They must be protected…
![Page 28: Shepherding User Requirements with TFS](https://reader030.vdocuments.site/reader030/viewer/2022032421/55a783131a28ab2b3e8b48ab/html5/thumbnails/28.jpg)
Acceptance Criteria
▪ Scrum demands 100% definition of done
▪ Where does acceptance criteria (Confirmation - the 3rd “C”) go in TFS?
▪ Given/When/Then or A list of “shalls and shall nots”
![Page 29: Shepherding User Requirements with TFS](https://reader030.vdocuments.site/reader030/viewer/2022032421/55a783131a28ab2b3e8b48ab/html5/thumbnails/29.jpg)
Testing
▪ Multiple tests can be associated with each work item
▪ These can be acceptance criteria but also provide a series of steps to guide the developer, user or analyst testing the requirement
▪ Tests can be associated with “automation”
![Page 30: Shepherding User Requirements with TFS](https://reader030.vdocuments.site/reader030/viewer/2022032421/55a783131a28ab2b3e8b48ab/html5/thumbnails/30.jpg)
DemoAdd acceptance criteria and test cases
![Page 31: Shepherding User Requirements with TFS](https://reader030.vdocuments.site/reader030/viewer/2022032421/55a783131a28ab2b3e8b48ab/html5/thumbnails/31.jpg)
Requirements Are Like Sheep
1.They must be gatheredFeatures and User stories added to a backlog in TFS
2.They must be guided and groomedRequirements organized by area and path, presented on a board to show progress
3.They must be protectedConfirmation through acceptance criteria and testing