Page 9 - DCAP304_DCAP515_SOFTWARE_PROJECT_MANAGEMENT
P. 9

Unit 1: Introduction to Software Project Management




          Unique Activities                                                                     Notes

          The activities in a project must be unique. A project has never happened before, and it will never
          happen again under the same conditions. Something is always different each time the activities
          of a project are repeated. Usually, the variations are random in nature—for example, a part is
          delayed, someone is sick, a power failure occurs. These are random events that can happen, but
          we never are sure of when, how, and with what impact on the schedule. These random variations
          are the challenge for the project manager.

          Complex Activities

          The activities that make up the project are not simple, repetitive acts, such as mowing the lawn,
          painting the house, washing the car, or loading the delivery  truck. They  are complex.  For
          example, designing an intuitive user interface to an application system is a complex activity.

          Connected Activities

          Connectedness implies that there is a logical or technical relationship between pairs of activities.
          There is an order to the sequence in which the activities that make up the  project must be
          completed. They are considered connected because the output from one activity is the input to
          another. For example, we must design the computer program before we can program it.

          Unconnected Activities

          You could have a list of unconnected activities that must all be complete in order to complete the
          project. For example, consider of developing a payroll system. With some exceptions, the different
          modules of payroll system like, data entry module, updation module, calculation module, etc.
          can be developed separately in any order. But the pay roll system as a whole cannot be completed
          until all its modules are completely developed, but the different modules may be developed in
          any order. So developing a payroll system with various modules in which the modules can be
          developed in any order is not considered a project according to the definition.
          1.1.2 One Goal


          Projects must have a single goal.


                 Example: Consider the development of Management Information System (MIS) project
          for an institute. Each module of the MIS like, Personal information system accounting system,
          administration control system, examination system can be consider  as a subproject, each of
          which is a project in its own right.

          This division makes for better management control. This artificial decomposition of a complex
          project into subprojects often simplifies the scheduling of resources and reduces the need for
          interdepartmental communications while a specific activity is worked on. The downside is that
          the  projects are  now interdependent. Even though interdependency adds another layer of
          complexity and communication, it can be handled.
          1.1.3 Specified Time

          Projects have a specified completion date. This date can be self-imposed by management  or
          externally specified by a customer or government agency. The deadline is beyond the control of
          anyone working on the project. The project is over on the specified completion date whether or
          not the project work has been completed.



                                           LOVELY PROFESSIONAL UNIVERSITY                                    3
   4   5   6   7   8   9   10   11   12   13   14