Swipe to navigate through the chapters of this book
This chapter provides an introduction to project management for traditional software engineering, and we discuss project estimation, project planning and scheduling, project monitoring and control, risk management, managing communication and change and managing project quality.
Please log in to get access to your license.
Dont have a licence yet? Then find out more about our products and how to get one now:
These are the risk management activities in the Prince2 methodology.
This refers to whether the project is technically and financially feasible.
Organizations have limited resources, and as many projects may be proposed it will not be possible to authorise every project, and so several projects with weak business cases may be rejected.
For example, it may be decided to outsource the development to a third party provider, purchase an off-the-shelf solution, or develop the solution internally.
The project scheduling is usually done with the Microsoft Project tool.
The consequences of under estimating a project include the project being delivered late, with the project team working late nights and weekends to recover the schedule, quality being compromised with steps in the process omitted, and so on.
Unless “Go Ask Fred” is the name of the estimation methodology or the estimation tool employed.
This quotation is adapted from Benjamin Franklin (an inventor and signatory to the American declaration of independence).
The project board in the Prince 2 methodology includes roles such as the project executive, senior supplier, senior user, project assurance, and the project manager. These roles have distinct responsibilities.
The project plan will usually specify a tolerance level for schedule and spending, where the project may spend (perhaps less than 10%) in excess of the allocated capital for the project before seeking authorization for further capital funding for the project.
Often, a colour coding mechanism is employed with a red flag indicating a serious issue; amber highlighting a potentially serious issue; and green indicating that everything is ok.
- Software Project Management
- Copyright Year
- Springer International Publishing