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.
How do you know if you are developing and maturing as a team? How do you know you are getting good at this agile stuff? Typically agile talks about the soft side of things with a focus on the less tangible aspects such as individuals and interactions. Are there things that teams can tangibly work towards and measure their progress against? This video presents metrics that will help you assess the agile maturity of your team.
To what extent are the implications of agility in software really understood? What does it mean to deliver quality in today’s software systems, and how does that need to be reflected in the development and delivery of software today? In this podcast, Walker Royce describes the core measurements that software delivery teams should focus on in moving to agility
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.
Keith Cerny presents in this blog post, metrics that could be used to measure agile teams performance.