Software Project Management

Introduction

Some are born to project management, some seek project management and some have project management thrust upon them. This course was originally produced for developers who have had to take up the reigns and manage a software project. It assumes a moderately technical background. Its scope is mainly the software of a project; it would only form part of what would be needed to manage a complete, large project where more than just software has to be engineered.

Duration and Construction

The course lasts two days. Each day will start at 09.30 and finish at 16.30. The delivery is via lecture, exercise and discussion.

The days consist of two morning sessions and three, shorter afternoon sessions, with one hour for lunch. Time will be available after 16.30 for extended discussions or related issues.

Intended Audience

Participants will already have had experience of software development perhaps as developers, designers or architects. They will be considering taking on the job of managing a software development project, or will already have taken up such a job.

Aims

• To understand the roles of the project manager
• To understand the threats and opportunities in project management
• To understand the techniques available with which a project's aims and objectives, timetable, activities, resources and risks can be kept under control
• To understand the social and political problems a project will encounter--against which the technical problems pale into insignificance--and to begin to understand how to approach non-technical problems
• To understand communication

Numbers

We recommend that there are no more than 12 participants, with the best results usually obtained when there are at least 8 participants. It is possible, by negotiation and mutual agreement, for more than 12 participants to be present.

Deliverables

• Lectures
• Facilitation of discussions
• Copies of lecture slides, plus explanatory text and summaries
• Reference list of books and sources

Contents

• The nature of the job
• The nature of the problem
• The SEI capability maturity model
• Process models
• Estimating
• Introduction to project control
• Work breakdown
• Requirements control
• Risk control
• Quality control
• PERT and critical paths
• The opportunities and threats of software tools
• Peopleware
• Communication

Site Requirements

• Data projector of at least 1024 x 768 resolution, and suitable screen
• White-board, preferably not doubling up as the OHP's screen; blackboard and chalk are acceptable
• Flip-chart and easel, with additional flip-chart paper
• It is best if the seating is not fixed. Auditorium style seating, for example, makes it difficult to switch from lecture to group work.

Contacting

Please contact John Deacon by telephone on +44 20 7498 3773; by fax on +44 20 7498 3747; by emailing  jdeacon@jdl.co.uk; or by visiting http://www.jdl.co.uk

[ Home page | Courses List ]

Last modified: Thursday, 08-Feb-2007.
Copyright © 2007 John Deacon. All rights reserved.