Before we get into the specifics of estimating software, first we cover some theory. This lesson covers why estimating software is so hard, the different ways you can estimate software, and the theory of how you can estimate software, along with a discussion around whether it is possible to estimate without requirements, and what skills you need represented in your estimating team.
This lessons discusses the multitude of approaches to software development, their history, and which one is best suited for your team. It then takes a look at how you can own your own Way of Working, and how to talk to people about the Waterfall approach.
There are all sorts of risks that come with building a software project. In this lesson, we look at why so many software projects fail and the top risks which contribute to these. We also discuss how you can handle different risks, and how to manage expectations when discussing the estimation with someone.
Risk is not the only thing which can blow out a project's time. This lessons takes a look at the other factors which you need to make allowances for, including: worker productivity, polishing time at the end, and time to research and explore potential solutions while developing.
This lesson takes a look at the actual way you calculate the estimation. It discusses using hours vs. story points, how to calculate the estimate, and then, once you have finished the estimation, how to the reduce development costs that come from that estimation.