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.
- first of all thank you for answering my question, so just so that I understood what you meant is - the info I get from user story will be basis for my estimate of complexity - it's better to parallelly create with UI design so a user can give a better feedback on the productanoop francis– anoop francis2022-03-03 10:51:28 +00:00Commented Mar 3, 2022 at 10:51
- Also what happens I realize that the particular user story UI has a lot of animation and flashy stuff that throws out my estimation, is it recommended that I change my estimation on user story or to better phrase the question as a developer, how can I better inform team that my estimation of the complexity of the work changed in light of new info and it will affect the sprint?anoop francis– anoop francis2022-03-03 10:56:42 +00:00Commented Mar 3, 2022 at 10:56
- The preferred approach would be take the ticket into the sprint on the basis on building a basic UI. "Make fancy UI" is then a separate ticket which can be prioritised appropriately.Philip Kendall– Philip Kendall2022-03-03 11:04:42 +00:00Commented Mar 3, 2022 at 11:04
- so by ticket do you mean as a new user story or a subtask of the user story 1. if we are making it into a user story shouldn't it be completed in the same sprint and hence testers can test based on the UI given 2. if ticket mean a sub task will the story points be increased so velocity measurement is accurate Again thank you for taking time answering the questionanoop francis– anoop francis2022-03-03 11:21:58 +00:00Commented Mar 3, 2022 at 11:21
- New user story, and I see no reason it should necessarily be completed in the same sprint. The functionality can be tested with the basic UI, the improved UI can be tested when it's ready.Philip Kendall– Philip Kendall2022-03-03 11:26:47 +00:00Commented Mar 3, 2022 at 11:26
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**
- indent code by 4 spaces
- backtick escapes
`like _so_` - 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. design-patterns), 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