You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
- again, clearly my plane example wasn't the best. Let't try this one: "As a customer (in an online shop) I want to be able to pay my cart using MasterCard so that I don't need to get a Visa". This is a very concrete and precise feature but the technical work required may exceed the sprint length and add no value until it's actually done. Did I explain myself better?Lezka– Lezka2014-09-01 15:38:15 +00:00Commented Sep 1, 2014 at 15:38
- @Lezka: "Again?" Your question didn't mention anything about your example not being adequate. As to your comment... What makes the technical work level so high? Is it because the feature is actually composed of smaller features, or because there are all kinds of unnecessary technical hurdles in place? If the latter, it sounds like there's another problem to be solved before features can be added. Does the system already have credit card payments? Adding MasterCard as an option to an existing payment gateway sounds simple. If there isn't a gateway, adding one has multiple steps/features.David– David2014-09-01 15:44:54 +00:00Commented Sep 1, 2014 at 15:44
- sorry, I said again because I edited my original question too as a user said that wasn't software related. Anyway, so your view on this one is that if we have so much technical work behind a simple feature, there is probably a problem somewhere else in the code, and if the feature requested is not so simple, the PO is probably note making an effort to simplify it, would that be right?Lezka– Lezka2014-09-01 15:52:08 +00:00Commented Sep 1, 2014 at 15:52
- 1@Lezka: Well, I can't be very specific with contrived examples. There is no one single answer, every product/feature/story/team/etc. is different. The overall team should collaboratively make an effort to decompose the work into smaller components. Epics, features, stories, tasks. Stories and tasks shouldn't cross sprints, but epics and features certainly can. QA would validate stories, the PO might only validate features.David– David2014-09-01 15:55:52 +00:00Commented Sep 1, 2014 at 15:55
Add a comment |
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. ms-project), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you