Managing Stakeholders in Software Development Projects

In Chapter 2 (Section 2.1.2), we reviewed some of the key project roles and the responsibilities that go with these roles within the PRINCE2 framework. The concept of a project board was also introduced and its function within a project.
Some practitioners make a clear distinction between project boards and steering committees. I do not, because in practice they tend to be one and the same entity.
The composition and reporting line of this project board will be totally dependent on the nature of the project and the structure of the organization; however it is possible to draw some good practice lessons from my own projects. First keep it small between six and ten people. This committee should not be the device for securing commitment across the organization (although it can be used for communication purposes) this needs to be done by the process itself not by a committee. Depending on the size of the project this project board, should meet at least once a month, and provide direction and oversight to the project manager. It should review the status and plans of each group within the project. This project board should have the responsibility for adjusting priorities and reallocating budgets, when necessary. The chair of the project board is very important. The appointee should be someone who is a driving force behind the project and has the communication channel to top-level management. The other members of the committee will...