0% found this document useful (0 votes)
68 views8 pages

Understanding Software Project Management

This document provides an introduction to software project management. It discusses why project management is important, with large amounts of money being spent on software projects and many projects failing or going over budget. It defines what constitutes a project and compares projects to jobs and exploration. The key characteristics of projects are described. While software projects are similar to other projects, factors like invisibility, complexity, conformity and flexibility make software more challenging to develop. The document also distinguishes between in-house and outsourced projects, and the differing roles of a contract manager versus a technical project manager.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
68 views8 pages

Understanding Software Project Management

This document provides an introduction to software project management. It discusses why project management is important, with large amounts of money being spent on software projects and many projects failing or going over budget. It defines what constitutes a project and compares projects to jobs and exploration. The key characteristics of projects are described. While software projects are similar to other projects, factors like invisibility, complexity, conformity and flexibility make software more challenging to develop. The document also distinguishes between in-house and outsourced projects, and the differing roles of a contract manager versus a technical project manager.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd

Software Project Management

An Introduction &
Importance of Software Project
Management
Outline of talk
In this introduction the main questions to be
addressed will be:
– What is software project management? Is it really
different from ‘ordinary’ project management?
– How do you know when a project has been
successful? For example, do the expectations of
the customer/client match those of the
developers?

2
Why is project management important?

• Large amounts of money are spent on ICT e.g. UK government in 2003-4


spent £2.3 billions on contracts for ICT and only £1.4 billions on road
building
• Project often fail – Standish Group claim only a third of ICT projects are
successful. 82% were late and 43% exceeded their budget.
• Poor project management a major factor in these failures

3
What is a project?
Some dictionary definitions:
“A specific plan or design”
“A planned undertaking”
“A large undertaking e.g. a public works
scheme”
Longmans dictionary
Key points above are planning and size of task

4
Jobs versus projects

‘Jobs’ – repetition of very well-defined and well


understood tasks with very little uncertainty
‘Exploration’ – e.g. finding a cure for cancer: the
outcome is very uncertain
Projects – in the middle!
Characteristics of projects
A task is more ‘project-like’ if it is:
• Non-routine
• Planned
• Aiming at a specific target
• Carried out for a customer
• Carried out by a temporary work group
• Involving several specialisms
• Made up of several different phases
• Constrained by time and resources
• Large and/or complex

6
Are software projects really different from other
projects?
Not really …but

• Invisibility
• Complexity
• Conformity
• Flexibility
make software more problematic to build
than other engineered artefacts.

7
Contract management versus technical project
management
Projects can be:
• In-house: clients and developers are
employed by the same organization
• Out-sourced: clients and developers
employed by different organizations
• ‘Project manager’ could be:
– a ‘contract manager’ in the client organization
– a technical project manager in the
supplier/services organization

Common questions

Powered by AI

Customer or client expectations often differ from those of developers due to varying priorities and perceptions of project requirements. Customers may prioritize features that solve their specific problems, while developers may focus on technical excellence and feasibility. Aligning these expectations is crucial for project success because it ensures that the final product satisfies customer needs and is delivered efficiently. Misalignment can lead to dissatisfaction, increased costs, and project failure due to unfocused development efforts .

Size and complexity are defining characteristics of a project because they necessitate comprehensive planning, resource management, and coordinated execution, distinguishing projects from simpler tasks or ongoing operations. In ICT projects, managing these aspects effectively is critical for success because they are large and complex by nature, requiring specialized skills and significant coordination across different phases. Failure to manage these characteristics can result in delays, budget overruns, and ultimately project failure .

Differentiating between jobs and projects is essential in ICT project management because it influences the approach to resource allocation and overall management. Projects, being large, complex, and non-routine, require more detailed planning, diverse expertise, and cross-functional collaboration, thus demanding more sophisticated management practices. This differentiation ensures that resources are allocated efficiently, risks are managed effectively, and objectives are clearly defined, unlike jobs which involve repetitive and well-defined tasks needing minimal resource variation or strategic planning .

A project is distinguished from ordinary jobs or ongoing tasks primarily through its definition and planning. A project involves a specific plan or design aimed at achieving a particular target and often operated by a temporary work group. It is characterized by being non-routine, involving several specialisms, and comprising different phases. This distinction is crucial as it mandates a structured approach with clear objectives, timelines, and resource allocations, unlike ordinary jobs which are repetitive and well-defined tasks with minimal uncertainty .

In in-house software projects, both clients and developers are employed by the same organization, which can streamline communication and align goals more naturally. The project manager often functions as a technical project manager overseeing day-to-day operations. In contrast, outsourced projects involve clients and developers from different organizations, likely requiring a contract manager in the client organization to handle oversight, contract adherence, and coordination across organizational boundaries. This adds complexity due to differing organizational cultures and potential communication barriers .

Poor project management is a major factor in the failure of ICT projects, as it can lead to inadequate planning, resource allocation, and risk management. According to the Standish Group, only a third of ICT projects are successful, with 82% being late and 43% exceeding their budget. This highlights the critical role of effective project management in meeting project deadlines and budget constraints .

Beyond typical management practices, key factors contributing to the success of a software project include effective communication among stakeholders, alignment of customer and developer expectations, adaptability to changing requirements, and the ability to integrate specialized skills effectively. These factors help mitigate the unique challenges posed by the characteristics of software projects, such as their complexity and flexibility. Successful projects typically exhibit a high degree of stakeholder engagement and continuous feedback loops to ensure alignment and adaptability .

To improve the success rate of ICT projects, organizations can implement robust project management practices focusing on early identification and management of risks, realistic planning, and setting achievable deadlines. Encouraging effective communication and collaboration among team members, stakeholders, and customers is crucial. Frequent monitoring and iterative development help to adapt to changes quickly. Training and developing project managers to handle both technical and managerial challenges can also mitigate issues leading to late delivery and budget overruns .

The characteristic of conformity in software projects presents challenges as these projects must adhere to existing standards, regulations, and technological constraints. Unlike other engineering projects, which often deal with physical components and established practices, software projects must frequently integrate with legacy systems and meet evolving technological standards. This can hinder innovation and complicate development, as developers must balance conforming to requirements with achieving optimal functionality and performance .

Software projects are particularly problematic compared to other engineered artifacts due to four main characteristics: invisibility, complexity, conformity, and flexibility. Invisibility refers to the fact that software products are intangible, making their progress difficult to assess. Complexity arises from the numerous potential interactions and dependencies within software systems. Conformity reflects the pressure software projects face to adhere to existing standards and regulations. Flexibility pertains to the frequent changes in requirements that software projects experience, which can complicate development and management processes .

You might also like