在Scrum中,细节在哪里?

时间:2023-01-14 08:07:11

We've been using Scrum on a few projects now with varying success and I now have a query relating to documentation.

我们现在已经在一些项目上使用Scrum并取得了不同的成功,现在我有一个与文档相关的查询。

In Scrum, you obviously have the product backlog ("The application begins by bringing up the last document the user was working with.") and the sprint task backlog ("Implement forgot password screen"). However, in all the examples I have seen, these two items are fairly high level in terms of detail (being designed on fit on a post-it note).

在Scrum中,你显然有产品积压(“应用程序首先打开用户正在使用的最后一个文档。”)和sprint任务积压(“实现忘记密码屏幕”)。然而,在我看到的所有例子中,这两个项目在细节方面都是相当高的水平(根据便利贴设计)。

So, where does the detail sit? Let's say the client has some very specific requirements for a stock management screen, or has a complex API that needs to be integrated with on the back end, where is this documented, how and who captures this information? Is it seperate to the backlog but populated on a just-in-time basis or some other way?

那么,细节在哪里?假设客户对库存管理屏幕有一些非常具体的要求,或者有一个复杂的API需要在后端集成,在哪里记录,如何以及谁捕获这些信息?它是否与积压分开,但是在准时制或其他方面填充?

4 个解决方案

#1


8  

Sprint backlog

The sprint backlog is a greatly detailed document containing information about how the team is going to implement the requirements for the upcoming sprint. Tasks are broken down into hours with no task being more than 16 hours. If a task is greater than 16 hours, it should be broken down further. Tasks on the sprint backlog are never assigned, rather tasks are signed-up for by the team members as they like.

sprint backlog是一个非常详细的文档,其中包含有关团队如何实现即将到来的sprint的要求的信息。任务分为几个小时,任务不超过16小时。如果任务超过16小时,则应进一步细分。 sprint backlog上的任务永远不会被分配,而是由团队成员按照自己的意愿注册任务。

#2


3  

Detail can sit in a wiki available to the whole team and editable by the whole team.

细节可以放在整个团队可用的维基中,并由整个团队编辑。

#3


2  

Not sure if this is as simple as it sounds. We've seen challenges with the detail part as well. Lets say if we're developing on a story that requires capturing simple contact information for lets say a CRM system. I now have the stories from the PO and we went through the sprint planning meeting and understood the first 5 stories that meets our velocity. However its always a struggle on capturing all the details of the conversation, for example how the screen needs to be laid out, what are the 20+ fields you need to have on the screen, can some of these fields lookup information from other tables/views etc. Who captures those details, should it be the PO or developer and whats the best practice for storing these details. We're right now trying to use wiki's for this, however it becomes an overhead in trying to maintain the action items on who needs to update which details and by when.

不确定这是否像听起来那么简单。我们也看到了细节部分的挑战。让我们说如果我们正在开发一个故事,需要捕获简单的联系信息,比如说CRM系统。我现在有PO的故事,我们参加了sprint计划会议,并了解了满足我们速度的前5个故事。然而,它总是很难捕获对话的所有细节,例如屏幕需要如何布局,你需要在屏幕上显示的20多个字段,这些字段中的一些可以从其他表中查找信息/如果是PO或开发人员,那么谁捕获这些细节,以及存储这些细节的最佳实践。我们现在正在尝试使用wiki,但是在尝试维护需要更新哪些细节以及何时更新的操作项时,它会成为一种开销。

#4


-1  

My understanding is that specific requirements such as this are handled by the product owner. They will liase with the client during Sprint Planning 2 and update the tasks with specfic requirements as needed - hence why the Product Owner is a optional attendee of the Sprint Planning 2 meeting. This gives you a hybrid of Just-in-Time and Sprint Planning 2 population of the specifics. Anything that isn't satisfied by the time you come to work on the task will be an impediment and should be dealt with a the daily scrum, by the product owner.

我的理解是这样的具体要求由产品所有者处理。他们将在Sprint Planning 2期间与客户联系,并根据需要更新具有特定要求的任务 - 因此产品负责人为什么是Sprint Planning 2会议的可选参与者。这为您提供了Just-in-Time和Sprint Planning 2特定群体的混合体。当你开始完成任务时,任何不满意的事情都将成为障碍,应该由产品所有者处理每日争议。

As the development is Agile when using Scrum you shouldn't find too much of an issues getting requirements just in time.

由于在使用Scrum时开发是敏捷的,因此您不应该找到太多的问题及时获得需求。

#1


8  

Sprint backlog

The sprint backlog is a greatly detailed document containing information about how the team is going to implement the requirements for the upcoming sprint. Tasks are broken down into hours with no task being more than 16 hours. If a task is greater than 16 hours, it should be broken down further. Tasks on the sprint backlog are never assigned, rather tasks are signed-up for by the team members as they like.

sprint backlog是一个非常详细的文档,其中包含有关团队如何实现即将到来的sprint的要求的信息。任务分为几个小时,任务不超过16小时。如果任务超过16小时,则应进一步细分。 sprint backlog上的任务永远不会被分配,而是由团队成员按照自己的意愿注册任务。

#2


3  

Detail can sit in a wiki available to the whole team and editable by the whole team.

细节可以放在整个团队可用的维基中,并由整个团队编辑。

#3


2  

Not sure if this is as simple as it sounds. We've seen challenges with the detail part as well. Lets say if we're developing on a story that requires capturing simple contact information for lets say a CRM system. I now have the stories from the PO and we went through the sprint planning meeting and understood the first 5 stories that meets our velocity. However its always a struggle on capturing all the details of the conversation, for example how the screen needs to be laid out, what are the 20+ fields you need to have on the screen, can some of these fields lookup information from other tables/views etc. Who captures those details, should it be the PO or developer and whats the best practice for storing these details. We're right now trying to use wiki's for this, however it becomes an overhead in trying to maintain the action items on who needs to update which details and by when.

不确定这是否像听起来那么简单。我们也看到了细节部分的挑战。让我们说如果我们正在开发一个故事,需要捕获简单的联系信息,比如说CRM系统。我现在有PO的故事,我们参加了sprint计划会议,并了解了满足我们速度的前5个故事。然而,它总是很难捕获对话的所有细节,例如屏幕需要如何布局,你需要在屏幕上显示的20多个字段,这些字段中的一些可以从其他表中查找信息/如果是PO或开发人员,那么谁捕获这些细节,以及存储这些细节的最佳实践。我们现在正在尝试使用wiki,但是在尝试维护需要更新哪些细节以及何时更新的操作项时,它会成为一种开销。

#4


-1  

My understanding is that specific requirements such as this are handled by the product owner. They will liase with the client during Sprint Planning 2 and update the tasks with specfic requirements as needed - hence why the Product Owner is a optional attendee of the Sprint Planning 2 meeting. This gives you a hybrid of Just-in-Time and Sprint Planning 2 population of the specifics. Anything that isn't satisfied by the time you come to work on the task will be an impediment and should be dealt with a the daily scrum, by the product owner.

我的理解是这样的具体要求由产品所有者处理。他们将在Sprint Planning 2期间与客户联系,并根据需要更新具有特定要求的任务 - 因此产品负责人为什么是Sprint Planning 2会议的可选参与者。这为您提供了Just-in-Time和Sprint Planning 2特定群体的混合体。当你开始完成任务时,任何不满意的事情都将成为障碍,应该由产品所有者处理每日争议。

As the development is Agile when using Scrum you shouldn't find too much of an issues getting requirements just in time.

由于在使用Scrum时开发是敏捷的,因此您不应该找到太多的问题及时获得需求。