From the course: Getting Started with Azure DevOps for Non-Programmers

Unlock the full course today

Join today to access over 24,900 courses taught by industry experts.

Specifying development with the user story

Specifying development with the user story - Azure Tutorial

From the course: Getting Started with Azure DevOps for Non-Programmers

Start my 1-month free trial Buy for my team

Specifying development with the user story

“

- [Instructor] Azure DevOps runs on what's called User Stories. It's a funny name for a piece of work really. You can see it listed here at the bottom. They're meant to be user-centric descriptions of functionality. They're a way for the business analyst who's working with the business to specify to the developer what needs to be done. So they represent individual pieces of work but from an end-user perspective. The developer actually has to code these things though. So although the user story should be focused on the end user, the split of work between them, the grouping of stories and their placement into sprints, should be done very much with the developers in mind. No matter how much the business might want it, you do have to build your applications in a certain order. So within the Create canvas epic, and by the way, if you can't see this, if you can't see all of the things you've just created, it may be that my…

Contents