I talked about why I was creating this page here. It was as a response to this post that I decided to collect everything together on a single, permanently visible page that I could expand and grow over time.
If anyone has any suggestions then I’d love to hear them. Let me know in the comments below.
Firstly, make sure you understand the need for estimation and the costs of doing so:
- Software estimation considered harmful? by Peter Seibel
If you are going to estimate, then the best approach I’ve seen so far is Evidence Based Scheduling:
- Evidence Based Scheduling by Joel Spolsky
Project Progress and Status updates
You can’t get much better than Dan Pink:
However, Joel talks specifically about motivating a software team:
- Three Management Methods by Joel Spolsky
Other Aspects to Consider
As well as the Agile Manifesto, the management adjunct that accompanies it is well worth a read:
- Alistair Cockburn –The Declaration of Interdependence for Modern Management. This really gets to the heart of the problems with traditional project management and software development and proposes principles and practices to work in an agile environment.