![]() ![]() If they have yet to forecast the PBI, then leave it set to the default (root) value.ĭescription Provide as much detail as necessary so that another team member or stakeholder can understand the purpose of the PBI. Iteration Select the Sprint in which the Developers forecast that they will develop the PBI. I will talk about Nexus in Chapter 11, “Scaled Professional Scrum.” For Nexus implementations, each team within a project can have its own corresponding areas as well as a default area. If the PBI applies to all areas your team covers or you aren’t sure of the specific area, then leave it set to its default value. Areas must be set up ahead of time and can represent functional, logical, or physical areas or features of the product. States are covered later in this section.Īrea Select the best area path for the PBI. State Select the appropriate state of the PBI. For example, some Scrum Teams opt not to use the Bug work item type in lieu of the PBI work item type and will simply tag those PBIs with “Bug.” Tags Optionally add tag(s) to help find, filter, and identify the PBI. This will reinforce the fact that the whole team owns the work on the PBI. Title (Required) Enter a short description that succinctly identifies the PBI.Īssigned To Select the Product Owner or leave blank, but don’t assign to a Developer. Later, as more detail emerges, the PBI can be updated to include business value, acceptance criteria, and an estimation of effort, as you can see in Figure 3-3.įIGURE 3-3 Adding detail to a PBI work item.Īs you create or edit PBI work items, consider the following Professional Scrum guidance while entering data in the pertinent fields: In fact, only the title field is required. In Azure Boards, the Product Backlog Item (PBI) work item type enables the Scrum Team to capture all of these various requirements with the least amount of documentation as is necessary. This list can contain new things that don’t exist yet (features), as well as broken things that need to be fixed (bugs). In Scrum, the Product Backlog is an ordered (prioritized) list of the outstanding work necessary to realize the vision of the product. The work items related to Azure Test Plans (test plans, test suites, test cases, etc.) will be covered in Chapter 7. I will focus on just those items that directly relate to planning and executing work. I want to spend some time talking specifically about the work item types in the Scrum process, and how a Scrum Team should (and shouldn’t) use them. We kept this guiding principle in mind as we created the Scrum process, and I still keep it in mind as I write this book. Since you can’t get any lighter weight than that, any prospective software tool would need to be as lightweight as possible. Many Scrum Teams evaluating Azure Boards currently use whiteboards and sticky notes to track their work. In fact, it’s even more lightweight than the Agile process. As you saw in Table 3-1, there are not a lot of extraneous work item types beyond what is needed to plan and track a project using Scrum. ![]() Primarily, they have learned that teams liked it! These teams appreciate its simplicity and straightforward support of Scrum. Over the years, through ongoing collaboration with the Professional Scrum community, Microsoft learned a thing or two about the Scrum process and the community using it. There were over 100,000 downloads of this new process template in the first couple of years. What resulted was a minimalistic process template that followed the rules of Scrum. They also knew that teams using Team Foundation Server and Scrum together wanted a lighter-weight experience, resulting in less friction. ![]() ![]() Everyone knew that Scrum had become the dominant agile framework in software development. It was the result of collaboration between Microsoft,, and the Professional Scrum community. This new template was designed from the ground up to embrace the rules of Scrum as defined in the Scrum Guide. Shortly after Microsoft released Team Foundation Server 2010, they made the Microsoft Visual Studio Scrum version 1.0 process template available for download. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |