We’re agile, so we don’t have to estimate and have no deadlines, right? Wrong! This course will dive into the problem with estimation in projects today and then a complete overview of the concept of agile estimation and the notion of re-estimation. We’ll learn about user stories, story points, planning poker , product backlog, team velocity, how to apply them all to estimation and iterative re-estimation. We will then take an alternative approach and look at using real metrics to limit the guesswork in estimating and still run a team that produces predictably and reliably. The course will round out with a discussion on how to “sell” the concept of Agile Estimation in various environments such as consulting or fixed cost projects. Upon completion of this course you will be able to perform Agile Estimation in your organization. This course covers the following PMBOK® Process Groups: Planning. This course covers the following PMBOK® Knowledge Areas: Project Scope Management, Project Time Management.
The Mechanics of Agile Estimation Hello and welcome to the Second Module of the Agile-Estimation course for Pluralsight. In this module we will look at the mechanics of agile estimation. The overview of this module is as follows. First we'll take a look at an introduction to the mechanics of agile estimation. Specifically we'll look at understanding user stories, story points, velocity and the product backlog. Then we'll round out the module by seeing the process in action of re-estimation of the entire backlog after each iteration, let's get started. So just how do you perform agile estimation in your organization. The rest of this module is going to be broken down into six parts, each part is a key feature of agile estimation that you need to understand. The first part we'll be talking about user stories, then we're going to look at decomposing those user stories using something called story points. After that we'll look at a way that the team can get together to perform an estimation called planning poker, it's almost as much fun as playing real poker but not quite. Then we'll look at the concept of the product backlog, if you're already performing an agile methodology you may already be familiar with the product backlog. Then we'll look at a concept called team velocity, this is a key metric that is used in agile estimation. Lastly we'll look at the concept of re-estimating the product backlog after each iteration.
Stop Estimating and use Metrics Welcome to the third and final module of the agile estimation course. In this module we're going to talk about stop estimating and using metrics. The overview of this module is as follows. First we're going to take a look at collecting data, what types of data will you collect, and then using the data and metrics for better estimation. Then we're going to look at some formulas to make your estimation efforts more successful. These formulas will use the data that you'll start collecting. Lastly, we'll round out the module by selling the concept of agile estimation to the business. I put the word selling in quotes because in reality if you are on the technical side and are working with the business, they may want to see Gantt charts and do things the old way. So I'll give you some techniques about how agile estimation can be used in most organizations. Let's get started.