Mike Cohn wrote an interesting post where he discusses he allows or even encourages to estimate with story points as large as 20, 40, and 100. He explains that they are useful when you need first and not necessarily precise estimate of the general size of a new project being considered.
Agile estimating and planning in a Scrum software development project will not prevent your boss from asking: “Will you make the date?” This video explains how to use Scrum and the “Cone of Uncertainty” to provide an answer like: “60% probability.”
Your team has adopted the relative story point estimation and you are now ready to jump into your first planning poker session. Where do you start? What is a 1-point story? What is a 3-point story? What is a 13-point story? Your team is looking to you and this process is almost as new to you as it is to them.
In this blog post, Mike Caspar gives a detailed answer to the question: What if your first scrum sprint ends up with zero story points completed?
In this blog post, Mike Treadway explains the technique of using story points for story estimation during agile planning sessions.
This blog post explains why for Scrum it is better to drop the time based approach to estimating and specifically the focus on an individual.
This blog post is about how to improve software project estimations by breaking tasks into sizes no larger than one productive day.