In fact that’s what benefits point to as that post describes:īenefits are the outcomes or results that users will (hopefully) experience by using your product or service I like this definition better because it provides a nicer tie in with outcome based thinking. Benefits: What’s the Difference & Why It Matters and has much more of a marketing slant to it. That definition is taken from the article Features vs. Since I wrote Beyond Requirements, I’ve refined my view of features and now think of feature in these terms: That definition is written from the context of business analysis so it is inevitably going to relate to requirements. In Beyond Requirements, I used the Guide to the Business Analysis Body of Knowledge (BABOK Guide) v3 definition of feature: “A distinguishing characteristic of a solution that implements a cohesive set of requirements and which delivers value for a set of stakeholders.” I need to start by clarifying the use of this particular word, because some of the other definitions depend on it. You can sign up for a free trial, purchase a subscription to Linked In Learning, or just purchase the course. Want to know more about Themes, Epics, Features, and User Stories from a different perspective, take a look at this video (Affiliate link) from Angela Wick’s Linked In Learning Course Agile Product Owner Role: Foundations. Keep your product backlog hierarchy to two levels. User stories are for the team.ĭon’t use themes for prioritization.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |