Page 58 - DCAP304_DCAP515_SOFTWARE_PROJECT_MANAGEMENT

Software Project Management

Notes An organization needs to put in place processes in order to bring some uniformity to the way in
which projects are managed. There will always be a need to tailor the process but the aim of the
process is to ensure there is a minimum “reinventing of the wheel”. It also means the organization
has a clear understanding of what is happening because it has happened that way on previous
projects. Projects don’t exist in a fog.
Tools

We have seen organizations with a number of tools to do the same job. Almost surely this will result
in problems. For example, one organization used both Artemis and Microsoft Project to create
schedules. Those with Project could not integrate with the Artemis schedules. They didn’t even have
access to Artemis. There were lots of lists of dependencies maintained manually in spreadsheets.
Having a steady set of tools is fundamental to the creation of a project infrastructure. Tools may
include:
 Scheduling tools
 Risk and issue management tools

 Financial management tools
 Document management tools
 Action Item management tools

 Databases for recording anything from benefits, to progress reporting, to resources.
Techniques

Techniques are the general, reusable process that an organization expands, or that an organization
subscribes to. For instance, an organization may use JAD sessions. There are a number of
techniques around JAD that need to be applies in a steady way. People should be trained to
apply the techniques, and participants will become familiar with the techniques. It makes life
much easier if people can quickly slot into an environment because they have undertaken a
similar activity previously.
One exacting area where techniques are important is in the development of requirements.
It should not be up to the project manager or business analyst as to what method they use to
gather requirements. The organization should make a decision as to the technique they will use
and every project uses the same techniques.
We have seen many association use a range of techniques such as UML, Data Flow diagrams,
Functional Definition etc. to document system requirements. Each new project required a learning
curve for participants where they had to become familiar with a new technique. Another factor
was where people preferred another technique so you end up with resistance, or a blended
technique. Typically it results in a new set of problems.

Training

Communication does not take place by osmosis. There needs to be a training program in place
to communicate the way in which projects should be assumed. Training will likely range from
classroom to CBT (Computer Based Training) to “one on one” training for new project managers.
The training should not end at project managers. It is significant that project participants also
receive training so they can understand how the project will be managed and what they are
expected to contribute.

52 LOVELY PROFESSIONAL UNIVERSITY