Agile is the only way to go for a fixed price project, because with Agile, a project is 50% complete when 50% of the features have been completed. With non iterative processes that don’t regularly produce a product in a stable state, you just don’t know how complete it is. Completing fixed price projects is a lot about risk management. This presentation explains how to identify and minimize the risk in the bidding, planning and execution stages of a fixed-price, fixed-scope software development project.

Estimating and planning with Scrum will not prevent your boss from asking if you will be able to meet your schedule. This video explains how you can use the Scrum “Cone of Uncertainty” to provide an answer like: “60% probability.”

The first step in creating a useful plan is the ability to estimate reliably. In this session we will discuss how to do this. We will look at various approaches to estimating including unit–less points and ideal time. Mike Cohn presents four specific techniques for deriving reliable estimates, including how to use the popular Planning Poker® technique and other techniques that dramatically improve a project’s chances of on–time completion.
Watch this streaming video from the Norwegian Developer Conference 2010

We are agile, so we don’t have to estimate and have no deadlines, right? Wrong! This session will consist of an overview of the concept of agile estimation and the notion of re-estimation. We’ll learn about user stories, story points, team velocity, how to apply them all to estimation and iterative re-estimation. The lab will consist of an estimation project and doing a round or two of “planning poker”.

This short video explains how to size iterations and applications.