LECTURE 01

SOFTWARE PROJECT MANAGEMENT

Mr. Mubashir Ali [Lecturer]

Department of Computer Science

dr.mubashirali1@gmail.com

Classification

Assignments & Quizzes 6% (6 Marks in Total)

Project, Presentation & Class

Behavior

9% (9 Marks in Total)

Attendance 10% (10 Marks in Total)

Midterm Exam 25% (25 Marks in Total)

Final Exam 50% (5 Marks in Total)

Total 100%

Grading Policy

Note: 10% Marks will be automatically given by Examination

Dept. on Attendance

Academic Honesty

Your work in this class must be your own

If students are found to have collaborated excessively or to have

cheated (e.g. by copying or sharing answers during an

examination), all involved will at a minimum receive grades of

“0” for the first violation

Further violations will result in failure in the course

Few Things to Remember Attendance will be taken with in 15 minutes at the start of class

Students are allowed to enter into class with in 30 minutes at the

starting

of class

Zero tolerance policy on attendance, discipline of class during

lectures!

Assignments must be submitted on time, no late submissions

In case of copied assignment both parties will be given zero!

Projects, Presentation, Quizzes, Assignments, Class participation are

very

important.

Don’t miss your Classes, Quizzes, Presentations, Assignments and

Projects!

Course Synopsis:

This course gives you the overview about what SoftwareProject Management actually is? What tools and techniquesyou will use to manage your project? Similarly, riskmanagement, quality assurance activities, and projectplanning, scheduling activities will also be covered in thiscourse.

Reference:

■ Software Project Management, Bob Hughes, Mike Cotterell, McGraw-Hill Higher Education, 5th Edition

■ Handouts & Research Papers

What is Management?

■ Planning- deciding what is to be done

■ Organizing- making arrangements

■ Staffing- selecting the right people for the job

■ Directing- giving instructions

■ Monitoring- checking on progress

■ Controlling- taking action to remedy hold-ups

■ Innovating- coming up with new solutions

■ Representing- liaising with users, etc.

What is Project Management?

■ Project Management is the art of maximizing the

probability that a project delivers its goals on Time, to

Budget and at the required Quality.

■ Project management is the application of knowledge,

skills, tools, and techniques to project activities to meet

project requirements.

What is Software Project Management?

■ A project is an activity with specific goals which takes placeover a finite period of time.

■ computer programs are not project management: they aretools for project managers to use. Project management is allthat mix of components of control, leadership, teamwork,resource management etc that goes into a successful project.

■ Temporary means that every project has a definite beginningand a definite end.

■ Projects involve creating something that has not been done inexactly the same way before and which is, therefore, uniqueand distinct.

Example of Projects:

■ Developing a new product or service.

■ Effecting a change in structure, staffing, or style of an

organization.

■ Designing a new transportation vehicle.

■ Developing or acquiring a new or modified information

system.

■ Constructing a building or facility.

■ Running a campaign for political office.

■ Implementing a new business procedure or process

Example 1:

Development of a chemical processing plant begins with

process engineering to define the characteristics of the

process. These characteristics are used to design the major

processing units. This information becomes the basis for

engineering design, which defines both the detail plant

layout and the mechanical characteristics of the process

units and ancillary facilities. All of this results in design

drawings that are elaborated to produce fabrication and

construction drawings. During construction, interpretations

and adaptations are made as needed and subject to proper

approval. This further elaboration of the deliverables is

captured in as-built drawings, and final operating

adjustments are made during testing and turnover.

Example 2:

The product of an economic development project may

initially be defined as: “Improve the quality of life of the

lowest income residents of community X.” As the project

proceeds, the products may be described more specifically

as, for example: “Provide access to food and water to 500

low income residents in community X.” The next round of

progressive elaboration might focus exclusively on

increasing agriculture production and marketing, with

provision of water deemed to be a secondary priority to be

initiated once the agricultural component is well under way.

4 Project Dimensions:Four P's have a substantial influence on software project

management-

■ People must be organized into effective teams, motivated

to do high-quality software work, and coordinated to

achieve effective communication.

■ The Product requirements must be communicated from

customer to developer.

■ The Process must be adapted to the people and the

problem.

■ The Project must be organized in a manner that enables

the software team to succeed.

The Players:

The software process is populated by players who can be

categorized into one of five constituencies:

1. Senior managers who define the business issues that

often have significant influence on the project.

2. Project (technical) managers who must plan, motivate,

organize, and control the practitioners who do software

work.

3. Practitioners who deliver the technical skills that are

necessary to engineer a product or application.

4. Customers who specify the requirements for the software

to be engineered.

Continued….

The people management maturity model defines the

following key practice areas for software people: recruiting,

selection, performance management, training,

compensation, career development, organization and work

design, and team/culture development. Organizations that

achieve high levels of maturity in the people management

area have a higher likelihood of implementing effective

software engineering practices.

The PM-CMM is a companion to the software capability

maturity model that guides organizations in the creation of a

mature software process.

Continued….■ When you build a product or system, it’s important to go

through a series of predictable steps – a road map that

helps you create a timely, high-quality result, The road

map that you follow is called a ‘software process’ .

■ A software process provides the framework from which a

comprehensive plan for software development can be

established.

■ Finally, umbrella activities – such as software quality

assurance, software configuration management, and

measurement – overlay the process model. Umbrella

activities are independent of anyone framework activity

and occur throughout the process.

Project Phases:

■ Organizations performing projects will usually divide each

project into several Project phases to improve

management control and provide for links to the ongoing

operations of the performing organization.

■ Collectively, the project phases are known as the project

life cycle. Software development, just like most other

activities, has a beginning, middle and an end.

■ This view of software development is referred to as the

software development life cycle.

Continued….A project has five phases.

Initiation:

Articulate your vision for the project, establish goals,

assemble your team, and define expectations and the scope

of your project.

Planning:

Refine the scope, identify specific tasks and activities to be

completed, and develop a schedule and budget.

Executing:

Accomplish your goals by leading your team, solving

problems, and building your project.

Continued….

Controlling:

Monitor changes to the project make corrections, adjust

your schedule to respond to problems, or adjust your

expectations and goals.

Closing:

Deliver your project to your audience, acknowledge results,

and assess its success. Take the time to compose a written

evaluation of the project and the development effort.

Continued….■ Each project phase is marked by completion of one or

more deliverables. A deliverable is a tangible, verifiable

work product such as a feasibility study, a detail design, or

a working prototype. The deliverables, and hence the

phases, are part of a generally sequential logic designed

to ensure proper definition of the product of the project.

■ Deliverables from the preceding phase are usually

approved before work starts on the next phase. However,

a subsequent phase is sometimes begun prior to approval

of the previous phase deliverables when the risks

involved are deemed acceptable. This practice of

overlapping phases is often called fast tracking.

Continued….

Project life cycles generally define:

■ What technical work should be done in each phase

■ Who should be involved in each phase

■ Project life-cycle descriptions may be very general or very

detailed.

■ Such detailed approaches are often called project

management methodologies.

■ Cost and staffing levels are low at the start, higher toward

the end, and drop rapidly as the project draws to a

conclusion.

Continued….

■ The probability of successfully completing the project is

lowest, and hence risk and uncertainty are highest, at the

start of the project. The probability of successful

completion generally gets progressively higher as the

project continues.

Concept Phase:■ User Need

■ Initial Investigation

■ User Review

■ System Performance Design

■ Candidate Review

■ Study Phase Report

Requirement Phase:

■ The software requirements specification document

■ The project development plan

■ The software test plan

Design Phase:

■ General System Review

■ Processing Requirements Identification

■ Data Base Design

■ Control Requirements

■ Output Design

■ Input Design

■ Equipment Selection/Acquisition

■ People

Development Phase:

■ Implementation Planning

■ Computer Program Design

■ Equipment Acquisition and Installation

■ Coding and Debugging

■ Computer Program Testing

■ System Testing

■ Reference Manual Preparation

■ Development Phase Report Preparation

■ User Acceptance Review

Operation Phase:

■ System Changeover

■ Routine Operation

■ System Performance Evaluation

■ System Changes/Enhancements

Summary of Lecture

Software Project Management

Project Dimensions

Project Players

Software Development Life Cycle

Project Phases

Readings & References

1. Read and Prepare given Handouts from Page 1 to 20.

2. Revise Your Software Engineering Concepts & Models.

Must Bring Resource Book(Hard Copy) in Next Lecture.

Good Luck