Using Stakeholder Analysis in Software Project Management
Bas de Baar · 2006
If you look at training material on software project management, you often find what I will call classical techniques: how to list every task that should be performed, to create the schedule of the project, to control its progress, to recognise the associated risks, etc... In addition, agile approaches have put in evidence some techniques or tools like short iterations, daily meetings or burndown charts. With this situation, you can have the impression that project management is mainly a technical issue. Don't get me wrong: all these technical considerations are important and they are useful tools for the project manager, but I think that the most essential skills for a successful project are beyond those technical aspects.