12/16/2023 0 Comments Epic meaning in product management![]() The scope of this action helps to classify the size of the story. The action is the actual functionality that the story describes, this is ultimately what will be expanded into either more detailed stories (in the case of epics) or detailed acceptance criteria. Would set a different context than: As a corporate executive user. Defining the user helps the whole development team understand who will be using the feature, and what their motivations and needs are. The user type should describe a class of the application user, these should typically map back to the either the personas we created or specific application roles. Each of the lines is necessary to form a good user story or epic: User Type: The Who You should decide early on in a project what your format is and stick to it. Some organizations prefer to focus first on the user involved, some prefer to focus on the value derived. This can be just as correctly written user first: As a _user type_ There is a specific format used to write user stories, they don't need to be long and involved, they only need three parts: In order to _achieve some value_ It is a way to describe application functionality in a way that focuses on the end user and the benefits they derive from the feature. In the context of Agile software development, a user story (or epic) is a very specific thing. In order for the software developers to continuously deliver working, valuable software, we must first continuously deliver detailed specifications. A large idea is broken into several smaller ones, then one of those is further divided and so forth. You'll notice that this breakdown process is very similar to the process overview we discussed earlier. Each will need to be continuously broken down into smaller and smaller parts before the development team can start working on those parts. Just as new boulders will arrive at the gravel factory, so too will new user scenarios, wireframes, and storyboards be generated as the product or application grows. When we talk about the breakdown process, we are talking about a continuous process, but one that does indeed begin when a project kicks off. Similarly while breaking down our artifacts, we try to do so such that we can deliver Stories to the development team just-in-time for them to work on them. ![]() Why? Well that would take a lot of time, and our customers need the gravel now! Also what if one customer wanted a finer or coarser grade of gravel? If we did all the processing at once we could only provide one type. Note that we specifically did not explode all of the boulders to rocks at once, nor grind all the stones to gravel.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |