Agile

- "As a [persona]": Who are we building this for? We’re not just after a job title, we’re after the persona of the person. Max. Our team should have a shared understanding of who Max is. We’ve hopefully interviewed plenty of Max’s. We understand how that person works, how they think and what they feel. We have empathy for Max.
- “Wants to”: Here we’re describing their intent — not the features they use. What is it they’re actually trying to achieve? This statement should be implementation free — if you’re describing any part of the UI and not what the user goal is you're missing the point.
- “So that”: how does their immediate desire to do something this fit into their bigger picture? What’s the overall benefit they’re trying to achieve? What is the big problem that needs solving?
Epic

An epic is a big user story. That’s it. Nothing fancy here. No need to get tied up in knots trying to figure out, “Should this be an epic or a user story?” If it’s something that provides business value and needs to be on the product backlog, it’s a user story. But it may also be an epic, because it’s big.
So what does “big” actually mean? In the years I’ve been using Scrum, the best two definitions I’ve found are:
- An epic is a story that is larger than 8 story points
- An epic is a story that can’t be completed in one sprint
I think the second definition is better, since it doesn’t rely on your use of story points for estimation (though you can read why I love story point estimating) and it’s independent of your particular team’s velocity.

- a large user story, perhaps a few to many months in size […]. Epics are useful as placeholders for large requirements. Epics are progressively refined into a set of smaller user stories at the appropriate time
- The epic will be split into small user stories, and will not “remain”.

posted on 2019-04-08 22:28 迷茫中寻找方向阅读(425) 评论(0) 编辑收藏举报

刷新页面返回顶部

迷茫中寻找方向