Rules for Successful Software Project Management
This article provides provides 65 rules that should help you running successful software development projects. These hints are rooted both in the classic approach to project management and in the new approaches proposed by Agile project management frameworks like Scrum.
Here is what is written at the beginning of the rules’ list: “The promise of a successful project is something we all work harder to achieve, but working harder is not the answer. Software companies need to work smarter before, during, and after development, to ensure that the client gets not only what they want, but what they need. ”
The rules proposed are drawn from the daily project management practice of SSW. Each of them is explained in details with examples. They go from general guidance on relationships to more focused recommendations on specific activities. Here are some examples of their headlines:
* Do you know that Rules are made for the guidance of wise men and the obedience of fools?
* Do you manage clients’ expectations?
* Do you always inform your client how long a task took?
* Do you fix bugs first?
* Do you go beyond ‘Done’ and follow a ‘Definition of Done’?