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.
Scoping objectives with Epics - Azure Tutorial
From the course: Getting Started with Azure DevOps for Non-Programmers
Scoping objectives with Epics
- [Instructor] An Epic is the biggest piece of work that a DO offers. It might be a completely new section of software, for example. An Epic is just a container for smaller pieces of work and you might have a whole team of developers working towards achieving the Epic. Your entire project that is to build the website should probably be between 5 and 10 Epics. At least I tend to see about between 5 and 10 active Epics on any given project. The big question is how to structure them. You need to think as a developer would or consult your coders. Epics should be structured in line with the development. Now I'm going to delete all the work items that you can see in a DO, and start again. And I'm going to make, create one Epic for the navigation and sort of blank landing pages, so that we've got the skeleton website created at the end of that Epic. So by the time that Epic is finished, I can click around and all the other…
Contents
-
-
-
-
(Locked)
Introducing StyleMyYard4m 45s
-
(Locked)
Scoping objectives with Epics9m 44s
-
(Locked)
Giving yourself permission to make a feature4m 16s
-
(Locked)
Creating work containers with features6m 11s
-
(Locked)
Specifying development with the user story7m 56s
-
(Locked)
Estimating story points3m 22s
-
(Locked)
Implementing and fixing with tasks and bugs6m 31s
-
(Locked)
-
-
-