| Channel | Publish Date | Thumbnail & View Count | Download Video |
|---|---|---|---|
 |  0 Views |
However, if you have not worked on agile projects before, the terms “epics”, “user stories” and “story points” may be confusing to you.
Let me explain.
User Stories
A user story describes something a user wants.
It is a simple description of a product requirement in terms of what the product must be able to do… and for whom.
They represent functions that a customer or user expects from the project. Together, user stories that were not created by the project team form the product backlog.
They are usually documented on maps that typically include:
• A title
• A unique ID
• An estimate of the work required
(usually in story points)
• A description of what the function is intended to achieve
• Perhaps a list of tasks (such as WBS items) required to create the product or feature
The description usually defines the scope and quality requirements and can often be formulated in a form like this:
• As … (user/persona)
• I want to … (action)
• So that … (benefit)
And they may also have a validation test like this:
• If I … (action)
• This happens … (Result)
Epics
An epic is nothing more than a large user story. They are often called "oversized" user stories because they are too large to complete in one sprint or iteration. It is a higher-level story that is actually a group of closely related user stories. Epics are therefore usually broken down into user stories that represent smaller product features. There is no clear boundary to distinguish a large story from a small epic.
subjects
A theme is a collection of user stories that somehow fit together – they have a “thematic” connection to each other.
Action points
Story points are unitless measures of the effort required to complete a user story. What matters is not the magnitude of the effort in story points, but the relative values between the sizes of the individual user stories.
Estimates of the relative number of story points most often depend on the following factors:
• The amount of work
• The complexity of the work required
• The risk or uncertainty of this work
One way to estimate story size is Planning Poker – I made a video about it a while ago. https://youtu.be/cm3DbFo5bxY
recommended videos
Carefully curated video recommendations for you:
What is…
Agile project management? https://youtu.be/D5FoRXGa8ic
the Agile Triangle – Value, Quality and Constraints https://youtu.be/QDExsKePcd0
Crowd? https://youtu.be/CVmNgMxe0rk
Scrumban? https://youtu.be/kiI3IweyAeQ
Planning potter? https://youtu.be/cm3DbFo5bxY
A while ago I asked project managers in some forums what material things they needed for their work as project managers. The answers were great. I compiled their answers in a kit list.
https://kit.co/MikeClayton/what-a-project-manager-needs
Please note that the links are affiliate links.
For more great project management videos please subscribe to this channel: https://www.youtube.com/channel/UCMZfp1_wquyegVY9SoER0Nw?sub_confirmation1
All of our great articles and resources on project management can be found on the OnlinePMCourses website: https://onlinepmcourses.com/
Basic Management Courses – free training on YouTube with 2 new management lessons per week – can be found on our sister channel Management Courses: http://youtube.com/c/managementcourses
You can find more of our project management videos in thematic collections in our free academy of project management: https://onlinepmcourses.com/free-academy-of-project-management/
#Epics #UserStories #StoryPoints
Please take the opportunity to connect with your friends and family and share this video with them if you find it useful.
