Software Project Management

What is software project management ? What makes it different from management in general? Is software project management different from other types of project management ? To answer these questions we need to look at some key ideas about the planning, monitoring and control of software projects. We will see that project are largely about meeting objectives. Projects to produce software are only worth while if they satisfy real needs. Having identified those objectives, ensuring that they are met is the basis of a successful project. This, however, cannot be done unless there is accurate information and how this is provided will be explored.

Characteristics of Projects

• non routine tasks involved
• planing is required
• specific objectives are to be met or a specified product is to be created
• the project has pre-determined time span
• work is carried out for someone other than yourself
• works involves several specialisms
• work is carried out in several phases
• the resources that are available for use on the project are constrained
• the project is large or complex

Activities covered by the software Project Management

1 - Feasibility Study

This is investigation  into whether a prospective proposed application. The probable developmental and operational costs, along with the values of the benefits of the new system are estimated. The study could be part of a strategic planning exercise examining and prioritizing a range of potential software development.

2 - Planning

If the feasibility study produces results which indicate that the proposed project appears viable, then planning of the project can take place. However, for large projects we could not do all the planning right at the beginning. We would formulate outline plan for the whole project and detailed plan for the first stage. 

3 - Project Execution

The project now can be executed. The execution of a project often contains design and implementation sub phases. There are following sub steps of Project execution:

1. Requirement Analysis
2. Specification
3. Design
4. Coding
5. Verification and Validation
6. Installation
7. User Acceptance
8. Implementation

Reasons of Failure of IT Projects

IT Projects are considered harder to complete, most of the IT Project got failed due to certain reasons. Here we will discuss most common reasons of failure and try to find out the corrective actions.

Weak Project Plan

Most common reason of failure is weak project plan. Project plan must be complete enough to cover all the aspects. It is more important to plan wisely if the projected time of the project is exceeding one calendar year. Generally ignore factors in project plan are:

•    Bad Estimation of time
•    Timely Allocation of Resources
•    Capability of the performers
•    Lack of Detailed Documentation
•    Ignoring Risk Factor
•    Improperly define the Scope of Work

Poor Analysis of Requirements

Detailed and extensive requirements analysis are the base of highly efficient IT system. If the business analyst / Requirement Analyst fails to get the detailed requirements of the user, due to his incapability fails to provide the complete requirement, that project always gone towards failure. Thorough analysis are mandatory for the successful completion of the project.

Incapable Team of Developers

Team of developers, should always, well trained and skillful. 50% of the failures occurred to inefficient staff, who failed to transform the requirements in to the solution. There are many type of incapacity of the teams:

   Lacking in technological Updates

   Lacking in design of the solution

   Lack of coordination among team members

Top Management Interest

Commitment of Top management is mandatory for every successful Project. Regular follow up and weekly / monthly Project follow up meetings should be attended by the Top Management / Stake holders.

Too much Customization

There should be some limit of customization, which must be clearly discussed in the Requirement Analysis document. Once the development has started and after that, if there arises further customization / requirements by the user, it will lead to delayed in the project completion time.