产品待办事项：创建和优先级排序 技巧
一个健康的产品待办事项很像是一个健康的人：衣着整齐、做事井井有条、生活公开坦荡。
作者：Dan Radigan
作者：Dan Radigan
开始使用 Scrum 待办事项模板
借助 Scrum 待办事项模板，轻松整理并确定任务优先级、优化时间预估，同时解决各项障碍。
优先级明确的敏捷待办事项列表不仅可以简化发布和迭代规划，还可以宣扬您的团队打算花时间处理的所有内容，包括客户永远不会注意到的内部工作。
这有助于利益相关者和其他团队设定期望，尤其是当他们为您带来额外工作时，并且能够固定工程时间。
什么是产品待办事项？
产品待办事项的优势
A well-managed product backlog can bring numerous benefits to a development team. Some of the key benefits include:
Improved prioritization: A product backlog helps to ensure that the most critical tasks are being worked on first.
Increased efficiency: By prioritizing tasks based on customer feedback and business objectives, teams can ensure they work on the most valuable tasks.
Better communication: A product backlog ensures everyone is aligned and working towards the same goals.
Reduced waste: By prioritizing tasks based on customer feedback and business objectives, teams can reduce waste and ensure that they are not working on tasks that are not valuable.
Improved customer satisfaction: By prioritizing tasks based on customer feedback, teams can ensure they deliver customers' desired features and functionality.
Overall, a well-managed product backlog is essential for agile product development. It ensures that teams are working on the most valuable tasks and that everyone is aligned and working towards the same goals.
以两个“R”开始产品待办事项
A team's roadmap and requirements provide the foundation for the product backlog. Roadmap initiatives break down into several epics, and each epic will have several requirements and user stories. Let's take a look at the roadmap for a ficticious product called Teams in Space.
Since the Teams in Space website is the first initiative in the roadmap, we'll want to break down that initiative into epics (shown here in green, blue, and teal) and user stories for each of those epics.
The product owner then organizes each of the user stories into a single list for the development team. The product owner may choose to deliver a complete epic first (left). Or, it may be more important to the program to test booking a discounted flight which requires stories from several epics (right). See both examples below.
What may influence a product owner's prioritization?
Customer priority
Urgency of getting feedback
Relative implementation difficulty
Symbiotic relationships between work items (e.g. B is easier if we do A first)
Effective product backlog prioritization ensures that the most critical tasks are addressed first, balancing team autonomy with the product owner's demands.While the product owner is tasked with prioritizing the backlog, it's not done in a vacuum. Effective product owners seek input and feedback from customers, designers, and the development team to optimize everyone's workload and the product delivery.
创建产品待办事项
创建产品待办事项是敏捷产品开发的一个关键步骤。它包括制定产品路线图、列出产品待办事项以及与团队沟通。
制定产品路线图
产品路线图是一个高层次的计划，概述了产品的愿景、目标和目的。它是产品待办事项的基础，有助于确保每个人都保持一致，朝着相同的目标努力。
要制定产品路线图，首先要明确产品的愿景和使命。然后，确定需要实现的关键目的和目标。最后，将目的分解为可添加到产品待办事项中的较小的、易于管理的任务。
列出产品待办事项中的项目
产品路线图制定完毕后，就可以开始列出产品待办事项中的项目了。这些项目可以包括功能、用户故事、缺陷、设计变更和技术债务。
在列出产品待办事项中的项目时，应包括每个项目的清晰描述和任何相关细节，如预计时间和所需资源。根据客户反馈、请求和业务目的确定项目的优先级也很重要。
这可确保开发团队致力于完成能带来最大价值的任务。
与团队沟通
在创建产品待办事项时，有效的沟通至关重要。产品负责人应与开发团队密切合作，确保每个人都了解产品待办事项和优先事项。
产品负责人还应与销售和营销等其他团队沟通，以确保每个人都保持一致，并朝着相同的目标努力。定期的会议和更新可确保每个人都保持一致，并有效地管理产品待办事项。还需要指导吗？
请查阅来自 Jira 的免费产品待办事项模板。
如何确定产品待办事项的优先级
Backlog prioritization is essential for ensuring the development team focuses on tasks that deliver maximum impact. Here’s how to approach it:Various backlog prioritization techniques, such as MoSCoW and weighted scoring, can help teams manage and order tasks effectively. The prioritization process involves regularly revising and realigning goals to adapt to a dynamic business environment.
Step 1. Evaluate customer needs
Identify features or fixes that will have the highest value for your users.
Use customer feedback, surveys, or analytics to pinpoint priorities.
Step 2. Assess urgency for feedback
Prioritize items that will generate actionable insights for the team or stakeholders.
For example, testing a new feature early can save time and resources later.
Step 3. Consider implementation complexity
Balance your backlog by including quick wins and more complex, long-term projects.
Weigh the effort-to-impact ratio to ensure resources are spent wisely.
Step 4. Account for dependencies
Identify tasks that must be completed before others can proceed.
Streamline workflows by handling foundational work first.
Reliable tools that support backlog prioritization can streamline product development and enhance efficiency. While the product owner leads prioritization, involving the development team, designers, and stakeholders fosters a shared understanding of priorities. Regular discussions ensure alignment and improve decision-making.
Pro tip: Use prioritization frameworks like MoSCoW (Must-have, Should-have, Could-have, and Won’t-have) or weighted scoring to make objective, data-driven decisions. Teams can implement their own unique prioritization frameworks using the flexible prioritization feature in Jira Product Discovery.
如何有效管理产品待办事项
产品待办事项建立后，定期维护以跟上项目群进度至关重要。产品负责人应在每次迭代规划会议之前审查待办事项列表，以确保优先级正确并纳入上次迭代的反馈。
定期待办事项列表审查在敏捷圈常被称为产品待办事项梳理，它能确保任务与利益相关者的洞察信息保持一致，同时让团队为即将到来的冲刺做好准备。部分团队也会使用待办事项列表梳理这一术语。
当待办事项列表规模变大时，产品负责人需将其归类为近期项目和长期项目。近期项目需要全面完善后，才能归类为此类别。
这意味着要拟定完整的用户故事，完成与设计和开发团队的协作，并获取开发团队的工作量估算。
专业提示
一旦待办事项列表的增长超出了团队的长期能力，就可以关闭团队永远无法解决的事务。为便于今后研究，可在团队的事务跟踪器中标记出这些事务的具体解决方案，如“超出范围”。
长期项目可以保持模糊，但最好能从开发团队那里获得一个粗略的估算，以帮助确定优先级。这里的关键词是“粗略”，因为一旦团队完全理解并开始工作，估算就会发生变化。
待办事项列表充当产品负责人和开发团队之间的联系纽带。产品负责人可以根据客户反馈、逐渐完善的估算和新需求，重新确定待办事项列表中工作的优先级。
但是，一旦工作正在进行中，就应尽量减少变更，因为变更会扰乱开发团队，影响专注度、流程和士气。
应留意的反模式
产品负责人在项目开始时就确定了产品待办事项列表的优先级，但并不会根据开发人员和利益相关者的反馈进行调整。
该团队将待办事项列表限制为面向客户的项目。
待办事项列表作为本地存储的文档保存，很少共享，因此相关各方无法获得更新。
产品待办事项让团队保持敏捷性
Savvy product owners rigorously groom their program’s product backlog to create a reliable and sharable outline of the project's work items.
Stakeholders will challenge priorities, and that’s good. Fostering discussion around what’s important gets everyone’s priorities in sync. These discussions foster a culture of group prioritization, ensuring everyone shares the same mindset about the program.
A well-prioritized agile backlog clarifies what the team intends to spend time on, highlighting visible and internal tasks. The product backlog also serves as the foundation for iteration planning. All work items should be included in the backlog: user stories, bugs, design changes, technical debt, customer requests, action items from the retrospective, etc. This ensures everyone’s work items are included in the overall discussion for each iteration. Team members can then make trade-offs with the product owner before starting an iteration with complete knowledge of everything that needs to be done.
Pro tip: Product owners dictate the priority of work items in the backlog, while the development team dictates its velocity. This can be a tenuous relationship for new product owners who want to “push” work to the team. This article explains work-in-progress limits and flow.
产品待办事项：创建和优先级排序技巧
一个健康的产品待办事项很像是一个健康的人：衣着整齐、做事井井有条、生活公开坦荡。
作者：Dan Radigan
作者：Dan Radigan
开始使用 Scrum 待办事项模板
借助 Scrum 待办事项模板，轻松整理并确定任务优先级、优化时间预估，同时解决各项障碍。
优先级明确的敏捷待办事项列表不仅可以简化发布和迭代规划，还可以宣扬您的团队打算花时间处理的所有内容，包括客户永远不会注意到的内部工作。
这有助于利益相关者和其他团队设定期望，尤其是当他们为您带来额外工作时，并且能够固定工程时间。
什么是产品待办事项？
产品待办事项的优势
A well-managed product backlog can bring numerous benefits to a development team. Some of the key benefits include:
Improved prioritization: A product backlog helps to ensure that the most critical tasks are being worked on first.
Increased efficiency: By prioritizing tasks based on customer feedback and business objectives, teams can ensure they work on the most valuable tasks.
Better communication: A product backlog ensures everyone is aligned and working towards the same goals.
Reduced waste: By prioritizing tasks based on customer feedback and business objectives, teams can reduce waste and ensure that they are not working on tasks that are not valuable.
Improved customer satisfaction: By prioritizing tasks based on customer feedback, teams can ensure they deliver customers' desired features and functionality.
Overall, a well-managed product backlog is essential for agile product development. It ensures that teams are working on the most valuable tasks and that everyone is aligned and working towards the same goals.
以两个“R”开始产品待办事项
A team's roadmap and requirements provide the foundation for the product backlog. Roadmap initiatives break down into several epics, and each epic will have several requirements and user stories. Let's take a look at the roadmap for a ficticious product called Teams in Space.
Since the Teams in Space website is the first initiative in the roadmap, we'll want to break down that initiative into epics (shown here in green, blue, and teal) and user stories for each of those epics.
The product owner then organizes each of the user stories into a single list for the development team. The product owner may choose to deliver a complete epic first (left). Or, it may be more important to the program to test booking a discounted flight which requires stories from several epics (right). See both examples below.
What may influence a product owner's prioritization?
Customer priority
Urgency of getting feedback
Relative implementation difficulty
Symbiotic relationships between work items (e.g. B is easier if we do A first)
Effective product backlog prioritization ensures that the most critical tasks are addressed first, balancing team autonomy with the product owner's demands.While the product owner is tasked with prioritizing the backlog, it's not done in a vacuum. Effective product owners seek input and feedback from customers, designers, and the development team to optimize everyone's workload and the product delivery.
创建产品待办事项
创建产品待办事项是敏捷产品开发的一个关键步骤。它包括制定产品路线图、列出产品待办事项以及与团队沟通。
制定产品路线图
产品路线图是一个高层次的计划，概述了产品的愿景、目标和目的。它是产品待办事项的基础，有助于确保每个人都保持一致，朝着相同的目标努力。
要制定产品路线图，首先要明确产品的愿景和使命。然后，确定需要实现的关键目的和目标。最后，将目的分解为可添加到产品待办事项中的较小的、易于管理的任务。
列出产品待办事项中的项目
产品路线图制定完毕后，就可以开始列出产品待办事项中的项目了。这些项目可以包括功能、用户故事、缺陷、设计变更和技术债务。
在列出产品待办事项中的项目时，应包括每个项目的清晰描述和任何相关细节，如预计时间和所需资源。根据客户反馈、请求和业务目的确定项目的优先级也很重要。
这可确保开发团队致力于完成能带来最大价值的任务。
与团队沟通
在创建产品待办事项时，有效的沟通至关重要。产品负责人应与开发团队密切合作，确保每个人都了解产品待办事项和优先事项。
产品负责人还应与销售和营销等其他团队沟通，以确保每个人都保持一致，并朝着相同的目标努力。定期的会议和更新可确保每个人都保持一致，并有效地管理产品待办事项。还需要指导吗？
请查阅来自 Jira 的免费产品待办事项模板。
如何确定产品待办事项的优先级
Backlog prioritization is essential for ensuring the development team focuses on tasks that deliver maximum impact. Here’s how to approach it:Various backlog prioritization techniques, such as MoSCoW and weighted scoring, can help teams manage and order tasks effectively. The prioritization process involves regularly revising and realigning goals to adapt to a dynamic business environment.
Step 1. Evaluate customer needs
Identify features or fixes that will have the highest value for your users.
Use customer feedback, surveys, or analytics to pinpoint priorities.
Step 2. Assess urgency for feedback
Prioritize items that will generate actionable insights for the team or stakeholders.
For example, testing a new feature early can save time and resources later.
Step 3. Consider implementation complexity
Balance your backlog by including quick wins and more complex, long-term projects.
Weigh the effort-to-impact ratio to ensure resources are spent wisely.
Step 4. Account for dependencies
Identify tasks that must be completed before others can proceed.
Streamline workflows by handling foundational work first.
Reliable tools that support backlog prioritization can streamline product development and enhance efficiency. While the product owner leads prioritization, involving the development team, designers, and stakeholders fosters a shared understanding of priorities. Regular discussions ensure alignment and improve decision-making.
Pro tip: Use prioritization frameworks like MoSCoW (Must-have, Should-have, Could-have, and Won’t-have) or weighted scoring to make objective, data-driven decisions. Teams can implement their own unique prioritization frameworks using the flexible prioritization feature in Jira Product Discovery.
如何有效管理产品待办事项
产品待办事项建立后，定期维护以跟上项目群进度至关重要。产品负责人应在每次迭代规划会议之前审查待办事项列表，以确保优先级正确并纳入上次迭代的反馈。
定期待办事项列表审查在敏捷圈常被称为产品待办事项梳理，它能确保任务与利益相关者的洞察信息保持一致，同时让团队为即将到来的冲刺做好准备。部分团队也会使用待办事项列表梳理这一术语。
当待办事项列表规模变大时，产品负责人需将其归类为近期项目和长期项目。近期项目需要全面完善后，才能归类为此类别。
这意味着要拟定完整的用户故事，完成与设计和开发团队的协作，并获取开发团队的工作量估算。
专业提示
一旦待办事项列表的增长超出了团队的长期能力，就可以关闭团队永远无法解决的事务。为便于今后研究，可在团队的事务跟踪器中标记出这些事务的具体解决方案，如“超出范围”。
长期项目可以保持模糊，但最好能从开发团队那里获得一个粗略的估算，以帮助确定优先级。这里的关键词是“粗略”，因为一旦团队完全理解并开始工作，估算就会发生变化。
待办事项列表充当产品负责人和开发团队之间的联系纽带。产品负责人可以根据客户反馈、逐渐完善的估算和新需求，重新确定待办事项列表中工作的优先级。
但是，一旦工作正在进行中，就应尽量减少变更，因为变更会扰乱开发团队，影响专注度、流程和士气。
应留意的反模式
产品负责人在项目开始时就确定了产品待办事项列表的优先级，但并不会根据开发人员和利益相关者的反馈进行调整。
该团队将待办事项列表限制为面向客户的项目。
待办事项列表作为本地存储的文档保存，很少共享，因此相关各方无法获得更新。
产品待办事项让团队保持敏捷性
Savvy product owners rigorously groom their program’s product backlog to create a reliable and sharable outline of the project's work items.
Stakeholders will challenge priorities, and that’s good. Fostering discussion around what’s important gets everyone’s priorities in sync. These discussions foster a culture of group prioritization, ensuring everyone shares the same mindset about the program.
A well-prioritized agile backlog clarifies what the team intends to spend time on, highlighting visible and internal tasks. The product backlog also serves as the foundation for iteration planning. All work items should be included in the backlog: user stories, bugs, design changes, technical debt, customer requests, action items from the retrospective, etc. This ensures everyone’s work items are included in the overall discussion for each iteration. Team members can then make trade-offs with the product owner before starting an iteration with complete knowledge of everything that needs to be done.
Pro tip: Product owners dictate the priority of work items in the backlog, while the development team dictates its velocity. This can be a tenuous relationship for new product owners who want to “push” work to the team. This article explains work-in-progress limits and flow.