分類: User Story

如何使用100分法來優先處理您的產品待辦事項清單？

Your product backlog items need to be structured, organized and prioritized to identify the most important things for your team. In this article, I will introduce 100-point method for product backlog refining activities. (您的待办事项需要进行结构化，组织和优先排序，以确定您的团队最重要的事情。在本文中，我将介绍100点方法为产品积压细化活动。)

Continue reading

使用者故事範本：作為／我希望／以便——如何撰寫有效的故事

The most common technology is the role-feature-reason template, which is used by teams and product owners to start writing user stories in three parts: (1) As a (role); (2) I want (feature); So that (reason). (最常见的技术是角色 – 特征 – 理由模板，用于团队和产品所有者开始编写用户故事，分为三个部分：（1）作为 As a（角色）; （2）I What 我想要（特征）; So that（理由）。)

Continue reading

Scrum：誰負責創建產品待辦事項或使用者故事？

The Product Owner (PO) “owns” the product backlog on behalf of the stakeholders, and is primarily responsible for creating it. He or she may instruct the development team and/or the Scrum Master to help him/her in defining the backlog items and in estimating them. (产品所有者（PO）代表利益相关者“拥有”产品积压工作，并主要负责创建积压工作。他或她可以指示开发团队和/或Scrum主控来帮助他/她定义积压项和估计它们。)

Continue reading

什麼是敏捷估算？

Agile teams use collective estimation methods to estimate their workload. Group estimation usually uses planning poker as a tool, and teams perform group estimation by playing estimation games. Planning poker is considered to be the most effective and interesting technique for workload estimation in agility. (敏捷团队的估计工作量使用了集体估算方法。集体估算通常使用规划扑克作为工具，团队通过玩估计游戏进行集体估算。规划扑克被认为是在敏捷中进行工作负荷估算的最有效和最有趣的技术。)

Continue reading