external end-users, internal end-users, partners, etc. ![]() End-users can be anyone who comes into contact with your product, e.g. User stories are lightweight requirements phrased in a way that focuses on the end-user and the desired outcome. But first, let's make sure we have a good understanding of where each term comes from and really means. the implications the difference in size has on how product teams work with epics and stories respectively. Basically someone making sure everything is on track.īoth have acceptance criteria (yes or no)…scrum has definition of done for a feature…traditional pm has success criteria for a deliverable.īasically the same, just wrapped up differently.Now that we have gotten that out of the way we can focus on what matters, i.e. – Traditional PM has weekly meetings…scrum, kanban has sprint review, or replenishing. – A workpackage/user story is around 8hrs work (no more than 40hrs) I find it helpful to compare scrum/kanban to traditional project management using work breakdown structure (wbs). I have found that splitting stories into tasks encourages teams to split work horizontally, whereas we try to slice work vertically.Īn example task: “Put ‘Add to wishlist’ button on each product page.” However, many teams don’t break their stories down into tasks. Tasks often follow the SMART acronym: specific, measurable, achievable, relevant, time-boxed (although what the letters stand for seems to be hotly debated). Stepping stones to take the story to ‘Done’. My view is that everything should have a goal (otherwise why are you doing it?!) However, interestingly, one group thought that themes should refer to business goals. By its nature, an epic can also be a theme in itself. delivering working software frequently, early continuous delivery, regular reflection).Īn example epic: “As a customer, I want to be able to have wishlists so that I can come back to buy products later.”Ī collection of stories by category. This helps them support the agile principles (e.g. Epics need to be broken into smaller deliverables (stories). A requirement that is just too big to deliver in a single sprint. I think this is a smart idea as everything should be done for a valid business reason: starting with explaining the benefit certainly makes sense to me.Īn example story: “As a customer, I want to be able to save a product in my wishlist so that I can view it again later.”Īn epic is a big story. One team stressed that they alter the above format to put the “So that …” first. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |