Hello Alexzandria,
First, I would like to compliment you on how you compared and contrasted each unit of work in
Scrum for this discussion, it is well organized, and you provided a definition and an example for
each.
I would just like to add that Features, Epics and User Stories are considered as a valid Product
Backlog Item (PBI) and that Tasks are generally not considered as a valid PBI. "Tasks, along
with their associated PBIs, constitute the Sprint Backlog" (hundhausen, 2021). Features and
Epics are managed on their own backlog. Additionally, one thing to mention with User Stories is
that to properly comlete a user story, communication between the Scrum Team and
knowledgeable stakeholders is required. User Stories are what make up the Product Backlog.
Great job on your discussion and the examples that you presented helped me better understand
each unit of work. After getting through the third week of the course I can't say that I am a Scrum
expert, however, I can now discuss the framework compared to before this class. I look forward
to using the Scrum framework for one of my future projects. The last thing I can say is that it is
one thing to understand Scrum and its another to actually use it. The example you pointed out
about categorizing a task based on its unknown and which one would be harder, in that example,
I would prioritize the easier task first. However, it made me question the priority of tasks. What
if the harder one is required before you can even attempt the easier one?
Respectfully Sent,
Christian M.
References
Hundhausen, R. (2021, March 26). Professional Scrum Development with Azure DevOps.
