Managing the Scrum project using IBM Rational Team Concert V2, part 2nd: Planning and managing the sprint

For more than a year, we've been using Ibm®rational team concert™ to support our Scrum teams, enjoy its features, coexist with its shortcomings, and develop its next version. Using the IBM Rational Team concert V2,jazz and the Rational Group concert teams can make significant improvements to Scrum and agile assessment, planning support delivery (not to mention more improved WEB clients and many other new features).

Sprint Planning

As we have used IBM Rational team concert V2 to manage the Scrum project in the first installment of this series, part 1th: Creating projects, teams, and planning chapters to introduce projects from Product Backlog to iterations in each Sprint phase Generation phase, and then until the development team needs to complete the Sprint Backlog task. Despite the results of the Sprint plan, is a collection of estimated tasks that are likely to be assigned to individual team members, but it is important to remember that the goal of Sprint planning is to urge team members to complete the collection of cases and add new and deliverable functionality to the product. Planning and estimating can help the team decide how much work is required to meet the needs of the Sprint.

Create Sprint Backlog

Create a Sprint Backlog iteration plan (see Figure 1):

Similar to the previous guidelines for creating the Product Backlog iteration plan, right-click the Sprint 1 (1.0) on the plans node of the team artifacts view, select New, and then select Plan.

In the dialog box window, enter the Sprint Backlog as the name.

For the plan Type, select the Sprint Backlog and then associate it with the Havannah team area.

Figure 1. Create an iteration plan to maintain Sprint Backlog

On the overview page of the sprint Backlog, record the Sprint's goal (Figure 2).

Figure 2. Record goals for the Sprint phase

Click Save.