Essential Agile Processes Part 5: Sprint Capacity Planning Sheet

Resource allocation is a critical process on both Agile and traditional projects. Even the best-planned projects can’t be carried out if there are not enough people to do the project activities, or if they are too busy. Agile values teams delivering working software at the end of each sprint, collaborating closely with the customer, and managing their own output. To accomplish these goals, the team needs must be able to accurately assess its own capability based on reality rather than best guesses. The sprint capacity planning sheet is a powerful tool for teams to discover their capacity and deliver more realistic assessments of their ability to execute what is needed to finish a sprint.
Essential Agile Processes Part 4: Sprint Backlog

Backlog management in Agile needs to occur at three levels. First, the product backlog contains the prioritized list of epics, features, stories, and tasks. Second, the release backlog separates the features in the product backlog into time-phased chunks, with the first release containing as many high-priority features as possible in a working piece. The granularity differs in that the release backlog only contains prioritized and estimated stories. Finally, there is the iteration or sprint backlog (hereafter referred to as sprint backlog), which is organized into stories, broken down into tasks and estimated in terms of hours, that the team can implement within the span of each sprint. In this post, we describe the sprint backlog and best practices and pitfalls for its use.
Essential Agile Processes Part 3: User Stories

Strong communication between the customer and the project team is a fundamental ideal of Agile that helps to produce quality results that the customer can use right away. For strong communication to happen, there needs to be common ground; otherwise, the two sides are coming from different cultures and speaking what may sound like two different languages, and this makes communication difficult. User stories fill this gap by framing requirements in a way that facilitates communication between the customer and the project team, and for this reason, they are a critical piece of any Agile project. Keep reading to learn more about what a user story is, how it is structured, and how to write one effectively.
Essential Agile Processes Part 2: Product Backlog

The product roadmap is a high-level vision for where you want your product to go. The product backlog follows up on the roadmap by serving as a list of features and requirements that help shape the product goal. Mike Griffiths (2012) defines the product backlog as “the ordered list of everything that might be needed for the product” (PMI-ACP Exam Prep, p. 38) and lists several categories of items typically found in a product backlog, including features to be built, functions, requirements, quality attributes, enhancements, and fixes. Building and maintaining the product backlog is key to realizing the high-level project goal, and takes the combined effort of the product owner, development team, and ScrumMaster. In this blog post, we will look further at how the product backlog fits into an agile project and how to successfully create and maintain it.
Essential Agile Processes Part 1: Product Roadmap

One of the starting points of an Agile project is to develop the product roadmap. The product roadmap documents the long-term vision of the product: it explains how the product is expected to launch and evolve. While the Agile process, and the Scrum process in particular, revolves around short-term periods of working product delivery in the form of iterations, or sprints, the product roadmap provides the long-term outlook that helps drive each of the sprints.
Eight Powerful Project Management Processes Part 8: Performance Reporting

With this look at performance reporting, we end our ongoing series on “Eight Powerful Project Management Processes” series. These processes are also included in our toolkit, Essential Gear for Project Managers. We hope you have enjoyed this look at eight critical processes to project success.
Eight Powerful Project Management Processes Part 7: Risk Register

In the next to last part of our series on “Eight Powerful Project Management Processes” series, we take a look at a very critical process, the risk register. These processes are also included in our toolkit, Essential Gear for Project Managers.
Eight Powerful Project Management Processes Part 6: Communication Plan

In Part Six of our “Eight Powerful Project Management Processes” series, we examine the communication plan. These processes are also included in our toolkit, Essential Gear for Project Managers.
Eight Powerful Project Management Processes Part 5: Project Schedule

This is Part Five in our series on the “Eight Powerful Project Management Processes,” a look at the project management processes that we have found to be most crucial to project success.
Eight Powerful Project Management Processes Part 4: Resource Allocation

This is Part Four of our series on the “Eight Powerful Project Management Processes,” a look at the project management processes that we have found to be most crucial to project success. These processes are also available in our toolkit, Essential Gear for Project Managers. Last time, we looked at the Work Breakdown Structure (WBS). Now, we examine resource allocation.