登录查看更多内容

Last updated on 2024年5月29日

How can you handle user stories that are too complex for a single sprint?

由人工智能和领英社区提供技术支持

User stories are one of the key elements of agile methodologies, as they describe the features and functionalities that the customers or users want from a product or service. However, sometimes user stories can be too complex, vague, or ambitious to be completed within a single sprint, which is a short and fixed period of time where a team works on delivering a working increment of the product. How can you handle user stories that are too complex for a single sprint? Here are some tips and strategies to avoid this common user story anti-pattern and ensure that your agile project delivers value and quality.

此文章中的业界达人

由社区从 6 条内容中精选。了解更多

Rob Jago

Associate Salesforce Administrator | Client-focused | Remote | Travel
Gaurav Kumar Mishra

Senior Consultant || Scrum Master ||GIM - Big Data Analytics || Fintech Enthusiast || Machine Learning & Data Analytics…

1 Split the user story

One of the most effective ways to handle user stories that are too complex for a single sprint is to split them into smaller and more manageable chunks. This can help you to reduce the scope, clarify the acceptance criteria, and increase the feedback loop. However, splitting user stories is not a trivial task, and you need to follow some guidelines to avoid creating dependencies, losing value, or creating technical debt. Some of the common techniques to split user stories are: by workflow, by business rule, by data type, by interface, or by test case.

添加您的观点

Rob Jago

Associate Salesforce Administrator | Client-focused | Remote | Travel
举报内容
Splitting user stories can often be a contentious topic within a Scrum team. The biggest thing it needs to be a discussion and collaboration amongst the team (needs to include product owner, QA and client rep). The overall value and priority needs to be considered as well. Other options include happy path only, happy path with minimal (required) data entries, UI with mock data. At the end of the day, this needs to be an open discussion.

已翻译

赞
Gaurav Kumar Mishra

Senior Consultant || Scrum Master ||GIM - Big Data Analytics || Fintech Enthusiast || Machine Learning & Data Analytics ||
举报内容
Splitting of user stories also help scrum team to keep an eye on metrics (Like Say to do ratio, cycle time ,velocity etc ) which are signs of high performing team. Keeping stories short also helps to reduce dependencies which may be hindrance to create increment of value.

已翻译

赞

2 Refine the user story

Another way to handle user stories that are too complex for a single sprint is to refine them with the help of the product owner, the stakeholders, and the team. Refining user stories means to review, discuss, and elaborate on them until they are clear, concise, and testable. Refining user stories can help you to discover hidden assumptions, validate requirements, and prioritize features. Some of the tools and practices to refine user stories are: user story mapping, storyboarding, prototyping, or the INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, and Testable).

添加您的观点

Rob Jago

Associate Salesforce Administrator | Client-focused | Remote | Travel
举报内容
what's often forgotten with user stories is that the user story needs to be a common understanding of what is to be delivered. The methods described here are meant to assist in achieving that. When refining them, you need to ensure that the refined story still has a common understanding even though it may broken down into multiple, smaller user stories.

已翻译

赞

3 Defer the user story

A third option to handle user stories that are too complex for a single sprint is to defer them until they are more feasible, relevant, or valuable. This can happen when the user story depends on external factors, such as market conditions, customer feedback, or technical dependencies, that are not under your control or influence. Deferring user stories can help you to avoid wasting time and resources on features that are not ready or needed. However, deferring user stories also requires careful monitoring and communication, as you need to keep track of the changes, risks, and opportunities that may affect them in the future.

添加您的观点

Rob Jago

Associate Salesforce Administrator | Client-focused | Remote | Travel
举报内容
A definition of ready may help with how to deal with these "stalemates" in a large/complex user story. Setting up a discussion point on the deferred user story a day or so later is best; this gives everyone to think about alternatives and to continue the discussion when its still fresh in everyone's mind is best.

已翻译

赞

4 Reject the user story

A final alternative to handle user stories that are too complex for a single sprint is to reject them altogether. This can happen when the user story is out of scope, unrealistic, or incompatible with the vision and goals of the product or service. Rejecting user stories can help you to focus on the most important and valuable features and avoid scope creep or feature bloat. However, rejecting user stories also requires strong collaboration and negotiation skills, as you need to explain the reasons, provide alternatives, and manage expectations of the product owner and the stakeholders.

添加您的观点

Rob Jago

Associate Salesforce Administrator | Client-focused | Remote | Travel
举报内容
The definition of ready will assist with this scenario. Also, if pre-planning discussions occur, this scenario can be identified well in advance of the planning session and thus resulting in, perhaps, a split up story before the sprint planning session.

已翻译

赞

5 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?

添加您的观点

Rob Jago

Associate Salesforce Administrator | Client-focused | Remote | Travel
举报内容
Splitting user stories is an art and not a science. If the team dynamics/culture is not a psychological safe environment, these discussions can quickly result in a bitter taste for team members. Having an open discussion on the concept BEFORE it occurs becomes a great team agreement and preparation for the eventual occurrence of the scenario.

已翻译

赞

Agile Methodologies

+ 关注

给文章评分

我们借助人工智能创建了此文章。您认为这篇文章怎么样？

很棒不太好

举报此文章

查看全部

How can you handle user stories that are too complex for a single sprint?

1

2

3

4

5

1 Split the user story

2 Refine the user story

3 Defer the user story

4 Reject the user story

5 Here’s what else to consider

Agile Methodologies

给文章评分

感谢您的反馈

更多Agile Methodologies相关文章

更多相关阅读内容

How can you handle user stories that are too complex for a single sprint?

1

2

3

4

5

1 Split the user story

2 Refine the user story

3 Defer the user story

4 Reject the user story

5 Here’s what else to consider

Agile Methodologies

给文章评分

感谢您的反馈

查看其他技能