Back to Insights

Creating a Smarter Velocity Chart – Part 2

ShareLinkedInEmail

In my previous blog entry, I explained what a velocity chart is and why it is an effective tool for communicating project information to stakeholders. In this write-up, I'll provide a true-to-life IT scenario to detail the steps for creating velocity charts.

Estimating Effort

Developing a velocity chart starts with effort estimation. We do this by working with the project team to identify the critical quantitative project deliverables, weigh the amount of effort required and assign points values to each.

Building the Velocity Chart

After determining the effort estimate, we begin building the velocity chart per the T2 Tech Group methodology. Several key sections are included: Original Scope, Original Forecast, Current Scope, Current Forecast, and Completed.

Tracking Progress Over Time

As the project progresses and work is completed, continuously update the Current Scope, Current Forecast and Completed cells in the table to reflect current total project weight, including scope changes and the effort points earned.

The Power of Velocity Charts

Most of the effort required to create a velocity chart is invested in the initial effort estimation. Once this is completed, periodic updating of the chart after each iteration can be accomplished quickly. If you're an IT project manager, you'll find this velocity chart can be a great tool for showcasing project completion status in a meaningful way.

Ready to explore a partnership?

Let's Connect

We use cookies. View our Privacy Policy