建立您的產品待處理專案Create your product backlog

Azure Boards |Azure DevOps Server 2020 |Azure DevOps Server 2019 |TFS 2018-TFS 2013Azure Boards | Azure DevOps Server 2020 | Azure DevOps Server 2019 | TFS 2018 - TFS 2013

您的產品待處理項目會對應至專案計劃,即您的 Team 計劃的實施藍圖。Your product backlog corresponds to your project plan, the roadmap for what your team plans to deliver. 您可以藉由新增使用者案例、待處理專案或需求來建立您的產品待辦專案。You create your product backlog by adding user stories, backlog items, or requirements. 如下圖所示,您的待處理專案是由工作專案的一般清單所組成。As shown in the following image, your backlog consists of a flat list of work items.

注意

下圖說明 Azure DevOps Services 的 Scrum 流程的產品待處理專案影像。The following image illustrates the product backlog image for a Scrum process for Azure DevOps Services. 針對 Agile、基本和 CMMI 流程模型, 待處理專案(Backlog )選項會顯示為 案例問題需求For the Agile, Basic, and CMMI process models, the Backlog items selection appears as Stories, Issues, and Requirements.

Scrum 流程產品待處理專案的待處理專案的螢幕擷取畫面。Screenshot of a Backlog of Scrum process product backlog items.

在您定義它之後,您會有已設定優先順序的功能清單和需要建立的需求。After you define it, you have a prioritized list of features and requirements to build. 您的待處理專案也會提供追蹤和與小組共用所需之所有資訊的存放庫。Your backlog also provides a repository of all the information you need to track and share with your team. 而且,您可以透過 互動方式篩選 待處理專案,以將焦點放在工作專案的子集。And, you're able to interactively filter the backlog to focus on a subset of work items.

注意

如需有關設定和自訂專案和小組以支援商務需求的指引,請參閱 Azure Boards 的設定和自訂For guidance on configuring and customizing your project and teams to support your business needs, review Configuration and customization of Azure Boards.

您的待處理專案是由 工作專案清單所組成。Your backlog consists of a list of work items. 您可以使用工作專案來共用資訊、將工作指派給小組成員、追蹤相依性、組織工作等等。You use work items to share information, assign work to team members, track dependencies, organize work, and more. 因為最重要的工作會出現在清單的頂端,所以您的小組一律會知道下一步該怎麼處理。Because the most important work appears at the top of the list, your team always knows what to work on next.

注意

您的產品待處理專案是可供您使用的三種待處理專案類別之一。Your product backlog is one of three classes of backlogs available to you. 如需每個待處理專案的支援功能以及兩種類型的面板的總覽,請參閱待處理專案 、面板和方案For an overview of the features supported on each backlog and the two types of boards, see Backlogs, boards, and plans. 如果您在待處理專案上看不到預期的工作專案,請參閱 設定您的待處理專案和麵板。If you're not seeing the work items you expect on your backlog, review Setup your backlogs and boards.

必要條件Prerequisites

當您建立專案或加入小組時,會自動建立待處理專案(backlog)。Backlogs are automatically created when you create a project or add a team. 每個小組都可以存取自己的產品、組合和短期衝刺待處理專案,如「 關於小組和敏捷式工具」中所述。Each team has access to their own product, portfolio, and sprint backlogs as described in About teams and Agile tools.

  • 您必須連接到專案。You must connect to a project. 如果您還沒有專案,請 建立一個專案。If you don't have a project yet, create one.
  • 您必須將專案加入至專案,做為 參與者project Administrators 安全性群組的成員。You must be added to a project as a member of the Contributors or Project Administrators security group. 若要加入,請 將使用者加入至專案或小組To get added, Add users to a project or team.
  • 若要加入或修改工作專案,您必須被授與專案關係 存取權或更高的許可權。To add or modify work items, you must be granted Stakeholder access or higher. 如需詳細資訊,請參閱 關於存取層級For details, see About access levels.
  • 若要查看或修改工作專案,您必須 在此節點中使用 view 工作專案 ,並將 此節點許可權中的 [工作專案 ] 設定為 [ 允許]。To view or modify work items, you must have your View work items in this node and Edit work items in this node permissions set to Allow. 依預設, Contributors 群組具有此許可權集合。By default, the Contributors group has this permission set. 若要深入瞭解,請參閱 設定工作追蹤的許可權和存取權To learn more, see Set permissions and access for work tracking.

注意

具有公用專案之專案關係 存取權的使用者,就像是具有 基本 存取權的使用者,具有待辦專案和麵板功能的完整存取權。Users with Stakeholder access for a public project have full access to backlog and board features just like users with Basic access. 如需詳細資訊,請參閱 關於存取層級For details, see About access levels.

  • 您必須連接到專案。You must connect to a project. 如果您還沒有專案,請 建立一個專案。If you don't have a project yet, create one.
  • 您必須將專案加入至專案,做為 參與者project Administrators 安全性群組的成員。You must be added to a project as a member of the Contributors or Project Administrators security group. 若要加入,請 將使用者加入至專案或小組To get added, Add users to a project or team.
  • 若要加入或修改工作專案,您必須被授與專案關係 存取權或更高的許可權。To add or modify work items, you must be granted Stakeholder access or higher. 如需詳細資訊,請參閱 關於存取層級For details, see About access levels.
  • 若要查看或修改工作專案,您必須 在此節點中使用 view 工作專案 ,並將 此節點許可權中的 [工作專案 ] 設定為 [ 允許]。To view or modify work items, you must have your View work items in this node and Edit work items in this node permissions set to Allow. 依預設, Contributors 群組具有此許可權集合。By default, the Contributors group has this permission set. 若要深入瞭解,請參閱 設定工作追蹤的許可權和存取權To learn more, see Set permissions and access for work tracking.

開啟您的待處理專案Open your backlog

從您的網頁瀏覽器開啟您的產品待處理專案(backlog)。From your web browser, open your product backlog.

  1. (1) 請確認您已選取正確的專案, (2) 選擇 [面板] > 待處理專案],然後 (3) 從 [team 選取器] 功能表中選取正確的小組。(1) Check that you have selected the right project, (2) choose Boards>Backlogs, and then (3) select the correct team from the team selector menu.

    開啟小組的工作、待處理專案(Backlog)Open Work, Backlogs, for a team

    若要選取其他待處理專案,請開啟選取器,然後選擇不同的小組,或選取 [ View 待 處理專案目錄] 選項。To select another backlog, open the selector and then choose a different team or select the View Backlog directory option. 或者,在 [搜尋] 方塊中輸入關鍵字,以篩選項目的小組待處理專案清單。Or, enter a keyword in the search box to filter the list of team backlogs for the project.

    選擇另一個小組Choose another team

    提示

    選擇 星號圖示,即可將小組待處理專案加入最愛。 加入最愛構件 ( 加入最愛圖示) 出現在 [team 選取器] 清單上方。

  2. 請確認您已選取 Agile) 的 案例 (、基本) 的 問題 (、Scrum (的 待處理專案) ,或 CMMI (做為待辦專案層級的 需求) 。Check that you have selected Stories (for Agile), Issues (for Basic), Backlog items (for Scrum), or Requirements (for CMMI) as the backlog level.

    選擇產品待處理專案層級、待處理專案、案例或需求Choose product backlog level, Backlog items, Stories, or Requirements

  3. (選擇性) 選擇應顯示的資料行和順序,請選擇 [ 動作] 圖示,然後選取 [資料 行選項]。 若要深入瞭解,請參閱 變更資料行選項To learn more, see Change column options.

    開啟資料行選項Open Column Options

  1. 檢查您選取的是正確的專案,然後 選取 [ 面板待處理專案] > ****。Check that you selected the right project, and select Boards > Backlogs. 然後從 [小組選取器] 功能表中選取正確的小組。Then select the correct team from the team selector menu.

    開啟小組的 > 待處理專案(Backlog)

    若要選取其他待處理專案,請開啟選取器,然後選擇不同的小組,或選取 [ 流覽所有 待處理專案] 選項。 或者,在 [搜尋] 方塊中輸入關鍵字,以篩選項目的小組待處理專案清單。Or, enter a keyword in the search box to filter the list of team backlogs for the project.

    選取另一個小組Select another team

    提示

    選取 星號圖示,讓小組待處理專案成為我的最愛。 我的最愛構件 (我的最愛 圖示) 出現在 [team 選取器] 清單上方。

  2. 請確認您選取了 Agile 的 故事、Scrum 的基本 、待處理專案(backlog ),或 CMMI 的 需求 做為待處理專案(backlog)層級的 問題Check that you selected Stories for Agile, Issues for Basic, Backlog items for Scrum, or Requirements for CMMI as the backlog level.

    選取產品待處理專案層級、待處理專案、案例或需求Select product backlog level, Backlog items, Stories, or Requirements

  3. (選擇性) 若要選取哪些資料行要顯示和排列順序,請選取 [ 動作] 圖示,然後選取 [資料 行選項]。 若要深入瞭解,請參閱 變更資料行選項To learn more, see Change column options.

    開啟資料行選項Open Column options

在您的網頁瀏覽器上,開啟小組的產品待處理專案,並從專案和小組選取器選取小組。On your web browser, open your team's product backlog and select the team from the project and team selector. 然後選取 [工作待處理 專案] > ****。Then select Work > Backlogs. 選取產品待處理專案,這是 Scrum 的 待處理專案 、Agile 案例 或 CMMI 的 需求Select the product backlog, which is Backlog items for Scrum, Stories for Agile, or Requirements for CMMI.

開啟 [面板 > 待處理專案] 頁面Open the Boards > Backlogs page

若要選取另一個小組,請開啟專案和小組選取器。To select another team, open the project and team selector. 選取不同的小組,或選取 [ 流覽] 選項。Select a different team, or select the Browse option.

選取另一個小組Select another team

在您的網頁瀏覽器上,開啟小組的產品待辦專案。On your web browser, open your team's product backlog. 選取 [ 面板待處理專案] > ****。Select Boards > Backlogs.

面板 > 待處理專案,TFS 2015,2013 web 入口網站

追蹤待處理專案的 bugTrack bugs on your backlog

您可以選擇要如何管理 bug。You can choose how you want to manage bugs. 有些小組喜歡追蹤 bug,以及待處理專案的需求。Some teams like to track bugs along with requirements on the backlog. 其他小組(例如,在支援需求時所執行的工作)上追蹤 bug。Other teams like to track bugs as tasks performed in support of a requirement. Bug 接著會出現在其 工作面板上。The bugs then appear on their taskboard.

在決定之前,請先參閱 設定和自訂,將 Bug 視為需求或工作, 以取得指導方針。Before deciding, review Configure and customize, Treat bugs as requirements or tasks for guidance. 或者,直接在待處理專案 和麵板上顯示 bugOr, go directly to Show bugs on backlogs and boards.

將構想轉換成待處理專案Convert ideas into backlog items

您的待處理專案會顯示您打算進行或已開始處理的工作。Your backlog shows work that you plan to do or have started to work on. 當工作專案的狀態設定為 [完成] 或 [已完成] 時,工作專案就不會再顯示在待處理專案上。As soon as the state of a work item is set to Done or Completed, the work item no longer shows up on your backlog. 您可以使用待處理專案 (backlog)控制項 來篩選或變更您的觀點。You can use the backlog controls to filter or change your view.

提示

如果您已定義一長串的專案,就不需要一次重新輸入一個。If you already defined a long list of items, you don't have to reenter them one at a time. 相反地,請使用 Microsoft Excel 快速將它們匯入您的待處理專案中。Instead, use Microsoft Excel to quickly import them to your backlog.

具有專案關係 存取權的使用者,只能將工作專案加入至待處理專案的結尾。Users with Stakeholder access can only add work items to the end of the backlog. 如需詳細資訊,請參閱 關於存取層級For details, see About access levels.

  1. 在您加入工作專案之前,請先選取 [ 視圖選項] 圖示,然後將 項的滑杆和 預測 轉換為 [ 關閉]。 (選擇性)開啟或關閉 進度專案Optionally, turn In Progress Items on or off.

    新增產品待處理專案Add a product backlog item

  2. 若要加入工作專案,請選取 [ 新增工作專案],然後輸入標題。 然後按 Enter 鍵,或選取 [ 新增至頁首]。Then press Enter or select Add to top.

    加入工作專案。Add the work item.

    注意

    如果您有專案關係人存取,您只能將工作專案加入至待處理專案的底部。If you have Stakeholder access, you can only add work items to the bottom of the backlog.

  3. 重複此步驟,將您所有的想法視為工作專案。Repeat this step to capture all your ideas as work items.

若要建立您的待處理專案,請輸入標題,然後選取 [ 新增]。To build your backlog, enter a title and select Add. 如果您沒有看到 [新增 ] 連結,請選取 [ 新增 ] 以開啟快速新增面板。If you don't see the Add link, select New to open the quick add panel. (選擇性)設定要 顯示隱藏****的進度專案Optionally, set In progress items to Show or Hide.

將工作專案加入至待處理專案

注意

如果您有專案關係人存取,您只能將工作專案加入至待處理專案的底部。If you have Stakeholder access, you can only add work items to the bottom of the backlog.

重複此步驟,直到您掌握所有的主要構想為止。Repeat this step until you capture all your main ideas.

注意

根據您是否使用 基本AgileScrumCMMI建立您的專案,您的待處理專案(backlog)中的專案可能會被稱為問題、使用者案例、pbi 或需求。Depending on whether you create your project with Basic, Agile, Scrum, or CMMI, the items in your backlog might be called issues, user stories, PBIs, or requirements. 這三個都很類似。All three are similar. 它們描述要傳遞的客戶價值,以及要執行的工作。They describe the customer value to be delivered and the work to be performed.

根據預設,使用者案例會出現在 Agile 待處理專案上、基本待處理專案的問題、Pbi 和 bug 會出現在 Scrum 待處理專案上,而需求則出現在 CMMI 待處理專案By default, user stories appear on Agile backlogs, issues on Basic backlogs, PBIs and bugs appear on Scrum backlogs, and requirements appear on CMMI backlogs.

重新排列待處理項目順序Reorder your backlog

在待處理專案中有某些專案之後,您可以重新排列它們,以建立優先順序的工作清單。After you have some items in your backlog, you can reorder them to create a prioritized list of work. 經常檢查待處理專案並排定其優先順序,以協助您的小組瞭解下一步最重要的專案。Review and prioritize your backlog frequently to help your team know what's most important to deliver next.

提示

您無法在資料行上排序待處理專案。You can't sort your backlog on a column. 若要查看已排序的清單,請選取 [ 建立查詢]。To view a sorted listed, select Create query. 儲存並開啟查詢,然後排序查詢結果。Save and open the query, and then sort the query results. 若要深入瞭解查詢,請參閱 使用查詢編輯器列出和管理查詢To learn more about queries, see Use the query editor to list and manage queries.

若要重新排序待處理專案,請拖曳工作專案。To reorder your backlog, drag the work items. 或者,如果您想要使用鍵盤,請按住 ALT 鍵並使用向上和向下箭號。Or, if you prefer to use the keyboard, hold down the Alt key and use the up and down arrows.

重新排列工作專案Reorder work items

注意

若要重新排序待處理專案,您必須擁有基本或更高層級的存取權。To reorder a backlog, you must have Basic or higher level access. 如需詳細資訊,請參閱 關於存取層級For details, see About access levels. 如果您有專案關係人存取權,則無法重新排列待處理專案的順序。If you have Stakeholder access, you can't reorder backlog items.

參與組合管理或包含嵌套相同類型子專案的待處理專案,可能無法讓您重新排序專案。Backlogs that participate in portfolio management or that contain nested same-type child items might not allow you to reorder the items. 如需詳細資訊,請參閱下列文章:For more information, see these articles:

新增詳細資料和預估Add details and estimates

建立您的待處理專案並排定其優先順序,可提供您高階的藍圖。Building and prioritizing your backlog provides you with a high-level roadmap. 不過,在您的小組可以開始處理任何專案之前,他們需要更多詳細資料。Before your team can start work on any item, however, they need more details. 您可以在工作專案表單中捕捉這些詳細資料。You capture these details within the work item form.

若要開啟每個專案,請按兩下或按 Enter 鍵。To open each item, double-click or press Enter. 然後新增您要追蹤的所有資訊。 變更一或多個域值、加入描述或在 討論 區段中記下。Then add all the information you want to track. Change one or more field values, add a description, or make a note in the Discussion section. 您也可以選擇 [ 附件 ] 索引標籤,然後拖放檔案,以與其他人共用檔案。

輸入小組需要的詳細資料:Enter as much detail as the team needs to:

  • 瞭解範圍。Understand the scope.
  • 估計所需的工作。Estimate the work required.
  • 開發測試。Develop tests.
  • 確定最終產品符合接受準則。Ensure that the end product meets acceptance criteria.

注意

您只能將工作指派給單一使用者。You can only assign work to a single user. 如果您需要將工作指派給多個使用者,請為每個使用者新增工作專案,並區分標題和描述所要完成的工作。If you need to assign work to more than one user, add a work item for each user and distinguish the work to be done by title and description. 指派至欄位只接受已 新增至專案或小組的使用者帳戶。The Assigned To field only accepts user accounts that have been added to a project or team.

例如,在這裡,我們將案例指派給 Raisa Pokrovskaya,並新增討論筆記(提及 Raisa)。For example, here we assign the story to Raisa Pokrovskaya and we add a discussion note, at-mentioning Raisa.

使用者案例工作專案表單,加入詳細資料User Story work item form, add details

完成時,選擇 [ 儲存 & 關閉 ]。Choose Save & Close when done.

提示

若要規劃短期衝刺,請至少預估執行每個待處理專案的工作。To plan a sprint, at a minimum, estimate the effort involved to implement each backlog item. 若要在工作專案表單中取得投入時間,請針對基本或 Scrum、Agile 的 故事點 或 CMMI 的 大小 使用 投入 時間。To capture effort in the work item form, use Effort for Basic or Scrum, Story Points for Agile, or Size for CMMI.

欄位Field

使用量Usage

提供完成 PBI 所需工作量的相對估計。Provide a relative estimate of the amount of work required to complete a PBI. 針對使用者案例和需求,您可以在本文 點數大小中捕捉估價。For user stories and requirements, you capture estimates in Story Points and Size.

大部分 Agile 方法建議您根據工作的相對大小,設定待辦專案的估計值。Most Agile methods recommend that you set estimates for backlog items based on relative size of work. 這類方法包含 2 (1、2、4、8) 的電源,以及 (1、2、3、5、8等的1、2、3、5、8等 ) 。Such methods include powers of 2 (1, 2, 4, 8) and the Fibonacci sequence (1, 2, 3, 5, 8, etc.). 使用您的小組慣用的任何數位測量單位。Use any numeric unit of measurement your team prefers.
您針對 投入 時間、 大小故事點 所設定的估計值,會用來計算 速度預測短期衝刺The estimates you set for Effort, Size, or Story Points are used to calculate velocity and forecast sprints.

指定 PBI 相較于其他 Pbi 的相對值,可捕獲的優先權。Specify a priority that captures the relative value of a PBI compared to other PBIs. 數字愈高,商務價值愈大。The higher the number, the greater the business value.
當您想要捕捉與可變更待處理專案堆疊排名不同的優先順序時,請使用此欄位。Use this field when you want to capture a priority separate from the changeable backlog stack ranking.

提供足夠的詳細資料,以建立範圍的共用理解,並支援預估工作。Provide enough detail to create shared understanding of scope and support estimation efforts. 專注于使用者、他們想要完成的工作,以及原因。Focus on the user, what they want to accomplish, and why. 請勿描述如何開發產品。Don't describe how to develop the product. 請提供足夠的詳細資料,讓小組可以撰寫工作和測試案例來實作項目。Do provide sufficient details so that your team can write tasks and test cases to implement the item.

藉 " " 由描述小組用來驗證是否已完全實行 PBI 或 bug 修正的準則,來定義完成的意義。Define what "Done" means by describing the criteria for the team to use to verify whether the PBI or the bug fix is fully implemented.

開始處理 PBI 或 bug 之前,請盡可能清楚地描述 客戶接受準則Before work begins on a PBI or bug, describe the criteria for customer acceptance as clearly as possible. 在小組與客戶之間進行對話,以決定接受準則。Have conversations between the team and customers to determine the acceptance criteria. 這些準則有助於確保小組內部的普遍理解,以符合客戶' 的期望。These criteria help ensure a common understanding within the team to meet customers' expectations. 此外,此資訊也提供接受度測試的基礎。Also, this information provides the basis for acceptance testing.

影響評 量 (僅限 CMMI) Impact Assessment (CMMI only)

描述不實施需求的客戶影響。Describes the customer impact of not implementing the requirement. 您可能會從 Kano 模型包含此需求是屬於意外、必要或明顯類別的相關詳細資料。You might include details from the Kano model about whether this requirement is in the surprise, required, or obvious categories.

顯示/隱藏正在進行中的專案Show/hide In progress items

您可以從 [ View options ] 選取器中,選擇顯示或隱藏 正在進行的專案From the View options selector, you can choose to show or hide In Progress items. 如果您將 [ 進行中 ] 控制項開啟,則待處理專案(backlog) 中的 [ 作用中]、[已 認可] 或 [已解決] 或 [ 已解決 ] 狀態或狀態的專案 將不會 出現在待處理專案中If you turn the In Progress control off, then items that are in the Active, Committed, or Resolved states or states that map to the In Progress category state won't appear in the backlog.

查看選項選取器,進行中控制項

查看選項選取器,進行中控制項

選擇 進行中的專案 顯示或隱藏 進行中的 待處理專案(backlog)。Choose In progress items show or hide In Progress backlog items. 如果您將 [ 進行中專案 ] 控制項關閉,則待處理專案(backlog) 中的 [ 作用中]、[已 認可] 或 [已解決] 或 已解決 [] 狀態或 狀態中的專案將不會出現在待處理If you turn the In Progress items control off, then items that are in the Active, Committed, or Resolved states or states that map to the In Progress category state won't appear in the backlog.

當您想要預測工作時,通常會選擇隱藏 正在進行的專案You usually choose to hide In Progress items when you want to forecast work. 若要深入瞭解,請參閱 預測您的產品待辦專案。To learn more, see Forecast your product backlog.

顯示/隱藏已完成的子專案Show/hide Completed child items

您可以從 [ 視圖選項 選取器] 選擇顯示或隱藏 已完成的子專案From the View options selector, you can choose to show or hide Completed Child items.

視圖選項選取器、完成的子專案控制項

當您想要 查看匯總資料行時,通常會選擇顯示已完成的子專案。You usually choose to show Completed child items when you want to view rollup columns.

當您想要預測工作時,通常會選擇隱藏已完成的子專案。You usually choose to hide Completed child items when you want to forecast work. 若要深入瞭解,請參閱 預測您的產品待辦專案。To learn more, see Forecast your product backlog.

接下來嘗試這個Try this next

既然您已備妥待處理專案,您的小組就可以開始處理最高優先順序的專案。Now that you have a working backlog in place, your team can begin work on the top-priority items. 從這裡開始決定您要如何以小組的形式工作。From here, it's time to decide how you want to work as a team. 您要使用 Scrum 或看板嗎?Do you want to use Scrum or Kanban? 您可以單獨或一起使用這些方法。You can use these methods independently or together.

在追蹤和估計方面,需要最少額外負荷的小組可能會偏好使用看板。Teams that want the least overhead in terms of tracking and estimating might prefer Kanban. 想要以穩定步調工作並繪製其短期衝刺計畫詳細資料的小組,可能會偏好採用 Scrum 和短期衝刺計畫。Teams that like to work at a steady cadence and plot the details of their sprint plan might prefer Scrum and sprint planning.