Creating a PERT estimate for a single task is both easy and straightforward. Creating an estimate for a set of tasks is still easy, but requires a little bit of math. Combining PERT estimates for tasks is easy, but not as obvious. Roll up your sleeves and dive in.
Flashback: This Week in the Past on Tyner Blain [Apr 19]
A look back at the best from this week in the past.
Why Your Project Plan Will Fail
You’ve written a project plan. Your team is ready to start. Here’s the bad news – you’re going to fail. But why? How can you avoid failure?
Flashback: A Year Ago This Week on Tyner Blain [2006-04-28]
A look back at the best from a year ago.
Flashback: A Year Ago This Week on Tyner Blain [2006-04-14]
A look back at the best from a year ago.
Project Scheduling – 80% Done, 80% Remaining
Johanna warns us that there is “no such thing as percent complete” when it comes to tracking status on a project. Your managers and customers want to know percent complete – and there is a way to report it. Project planning and scheduling involves walking this fine line.
Foundation Series: Basic PERT Estimate Tutorial
PERT is a technique for providing definitive estimates of how long it will take to complete tasks. We often estimate, or scope, the amount of time it will take us to complete a task or tasks. PERT allows us to provide not only an estimate, but a measure of how good the estimate is. Good estimates are a critical element in any software planning strategy. In this post, we will present an introduction to using PERT, explain how it works and how to interpret PERT estimates.