1 IT 2403 Software Project Management Prof. Dr. B.Chandramouli.

1

IT 2403Software Project Management

Prof. Dr. B.Chandramouli

2

Syllabus at a glance

• Unit 1 - Introduction» Project basics- Contract management – Activities covered by

SWPM – Project planning

• Unit 2 - Project Evaluation» Strategic assessment – Technical assessment – Cost benefit

analysis – Cash flow – Risk

• Unit 3 - Activity Planning» Sequencing and scheduling – Network planning – Critical path-

Risk management

• Unit 4 - Monitoring and Control» Creating framework – Collect data – Visualise progress – Prioritize

monitoring – Get the project back to target – SCM – Contracts and management

• Unit 5 - People management» Behavior understanding – People selection – Motivation – Team

working – Leadership styles – stress, Health and Safety

3

Books

• Text book• Software Project Management

– Bob Hughes and Mike Cotterell» Tata McGraw Hill, 3rd edition , 2004

• Reference Book• Managing Global Projects

– Ramesh Gopalaswamy» Tata McGraw Hill, 2001

• Adopted Book ( for AU syllabus)• Software Project Management

– B.Chandramouli» Charulatha Publications, 2011

4

Why to study SWPM ?

• Career growth path in an IT org– Programmer – Analyst – Team leader – Module leader – Project

manager – program manager – VP (Program)

• Understanding of scientific methods of managing SW projects

• SW projs – creative – challenging – human involvement

• Project Management Institute (PMI) certifies project managers as “Project Management Professionals” (PMP). PMP certification is the most recognized and respected certification for Project Managers worldwide.

5

How to study SWPM ?

• Concept based subject– Understand diagrams where-ever applicable– Understand & underline keywords– Some simple problems in unit 3

• One book is not sufficient– Read materials from multiple books and websites and

make your own notes

• Introduced this year only– Can’t predict type of questions

6

Unit 1

• Project definition

• Contract management

• Activities covered by software project management

• Overview of project planning

• Stepwise project planning

Dec12/Dec 13 7

Project Definition

• A unique, planned, temporary endeavour with definite start and end dates to achieve one or more goals with the constraints of cost, schedule, quality, performance and resources – Example

• Construction of Chennai Airport• Computerising Apollo Hospital• Conducting unit test for final B.Tech !

Example of Goals

• Money ( Profit)

• Make a product

• Satisfy a customer

• Quality

• Performance

8

9

PM triangle

Cost Schedule

Scope (Resources)

Z (Resources)

X (Schedule)

)

Y (Cost)

)

Quality Product = Target

Target = Quality Product

May 1410

SWPM

• Project Management – discipline of planning, organizing, and

managing resources to bring about the successful completion of specific project goals and objectives

• Software Project Management– Software project management is a sub

discipline of project management in which software projects are planned, monitored and controlled

May 12, Dec 12, May 13, Dec 14, May 15

11

How is SW proj different ?

• The progress not visible immediately• High degree of flexibility expected - customer keeps

changing requirements.• Limited knowledge on application domain • Lack of quality standards and measures • Limited knowledge leads to task delay. When tasks get

delayed, the delivery of the final product delayed• Lack of communication between customers and

contractors due to different levels of domain knowledge and assumptions about the final product

12

SW proj problems

• Project Manager - » poor roles definition,» lack of estimating & planning skills and» lack of decision making skills. » Schedule, budget and quality constraints.

• Developers –» lack of knowledge in the application area,» lack of knowledge about developing standards,» lack of up to date documentations» deadline pressure» changes of application requirements.

• Customers –» monetary constraints» receiving products past the due date» surprises

PM mathematical Tools

• PERT – Program Evaluation and Review Techniques

• CPM – Critical Path Method

13

What is Software Contract ?

• SW contract is a legal document signed by both customer and contractor with following content– Deliverables– Time lines– Finance– Resources from both parties

14

Dec13, May 13,May14, Dec 14

15

CONTRACT MANAGEMENT

• Supervisory role of overseeing the progress of the project as per legal contract

• Software contract modes• Bespoke development

» In house development» Contracted (outsourced)

• Off the shelf» Packages - Ms Word, Ms Excel, Tally etc.» To be bought and used as it is. » No functionality and/or interface is modifiable.

• COTS – customized off-the-shelf » Combination of the above

16

Merits and demerits• Bespoke

• exactly meets the need of the customer• requires a dedicated, well balanced knowledgeable team of

people with resources. • Takes time ( resources may not remain)• Following Int’l standards difficult

• Off the shelf• functions available, they are well tested and proven at multiple

customer sites ( SW quality high)• Best Int’l standards followed• No time loss

• specific needs of a customer cannot be met • COTS

• better than ‘off the shelf’ and falls short of ‘Bespoke’ development.

Dec12, Dec13,May 1317

ACTIVITIES COVERED BY SOFTWARE

PROJECT MANAGEMENT

Initiation Planning Execution

Monitor and control Closing

Project start Project end

18

Project Initiation• Conceiving the concept• Feasibility study

– Present situation– Issues and problems in the present scenario– Proposed solution which would solve the current problems.– Analysis of the proposed solution with respect to

• Business aspects (market trend and need)• Technology used• Financial viability• Strength of the organization in developing such a solution.

– Cost aspects• Development cost including cost of training existing manpower, hiring

additional manpower cost, cost of developing necessary infrastructure.• Operational cost including support and maintenance costs.

– Benefits to the organization.– Risks involved in the process of developing and operating such a

solution and mitigation.– Recommendations

May 12, May 13,May14, Dec 14, May 15

19

Planning and Execution

• In-stream activities ( Framework activities)• Life cycle activities ( any model) – ISO 12207

– Requirement Gathering and analysis– Design– Coding– Integrating– Testing– Installation and implementation– Support and maintenance

May 13,May 14, Dec 1420

Monitor / Control( Umbrella Activities)

• Change management• Project management

– In stream Activities (planning / execution)– Umbrella Activities ( monitor / control)

– Project Planning, tracking and control– Risk Management – Configuration Management – Quality assurance – Formal reviews to ensure process errors are detected early and

corrected. – Work product preparation and documentation. – Reusable components preparation and management– Measurement

21

Project closing

• Customer runs / maintains on his own

• Software becomes obselete

• Contract end date / contract deliverables are complete and accepted

Management of SW projects

• Involves– Planning– Organising– Staffing– Directing– Monitoring– Controlling– Innovating– Representing

Dec 1122

23

Planning

• Outline planning ( MACRO)– Available data– Reasonable assumptions

• Detailed Planning ( MICRO)– More real time data available

Dec11, May 12, Dec 12, May 13, Dec 13, May 14, Dec 14, May 15

24

Stepwise Planning - MACRO

Select Project

Identify Project scope & Objectives

Identify infrastructure

Analyse project characteristics

25

Stepwise project planning – Step 1

MACRO Planning – Select Project

• Projects are essential for the survival of the co.

• Selection of a project - a very crucial and strategic step

– Considerations

• Business ( Strategy)

• Financial

• Technical

• What projects to take up ?

• Who and how this is decided ?

26

Stepwise project planning – Step 1 Stakeholders

• Stackholders are people / Org. directly or indirectly affected by the project

Business organization

Employees Management

Suppliers

Customers

Investors

Competitors

27

Stepwise project planning – Step 1 Various perspectives

• Investors – ‘Return on Investment’ (ROI).

• The Management and employees– Availability of adequate quality and quantity manpower within

the budget.

• Customer– Quality product , satisfies their need and economic cost.

• Suppliers– Availability of products which the project needs.

• Competition's view,– strengths and weaknesses , put forward by Market Analysts.

Risks of project selection

• Can the product /project marketted profitably?

• Can the product be made with good quality ?

• Domain expertise available ?

• Team’s familiarity with technology ?

• Current product extension of existing portfolio ?

28

29

Stepwise project planning – Step 2

Identification of Project scope and Objectives Identify objective

Establish project authority

Identify the stakeholders interest

Modify objectives

Establish communication channel with all stakeholders

Identify all stakeholders

30

Stepwise project planning – Step 2 Project Goal setting

• Must follow SMART approach

• SMART means– Specific– Measurable– Achievable (Agreed upon)– Relevant (Realistic)– Time bound

Difference between scope and objective

• Scope – Sum total of all products, features and requirements– E.g 4 years study, finance reqd, subjects,

pass conditions etc etc

• Objective – End point – E.g To get B.Tech degree

31

32

Stepwise project planning – Step 2 Project Goal – example

• Develop a web based appointment management system for poly clinics deliverable in March, 2012 as per ISO 9000 standards within the budget of Rs.50 Lakhs,

• Here, the objective is – Specific–with respect to application development– Measurable–as per ISO 9000 standards, Below Rs.50

lakhs– Achievable / Realistic– do able appointment system

using available Web Technology (Not something very great or not something never done by anyone before)

– Time bound – Before March, 2012

33

Stepwise project planning – Step 2 Establish Project Authority

• Project – more people / more specialties • Leadership is must for

– Coordinating– Setting the objective– Monitoring the progress towards the objective– Modifying the objectives, whenever needed

• Project Steering Committee, Project management Board, Project coordination committee

34

Stepwise project planning – Step 2 Identify all stakeholders

• WHO ?– A stakeholder is a person who directly or

indirectly influences the project

• Every stakeholder’s interest in the project and perspective of the project is different – Investor -- Supplier– Management -- Customers– Employees -- Competitors

35

Stepwise project planning – Step 2 Identify stakeholder’s Interest

• Each stakeholder’s view is different

• Each stakeholder’s expectation is different

• Difficult to satisfy all

• PM to work towards WIN-WIN for all (!)

36

Stepwise project planning – Step 2 Modify objectives

• To get near to WIN-WIN, some compromises are required

• This results in modifying objectives

• Ex :• Class starts at 8:30 sharp. All students to be

present• Always traffic jam at Sholinganallur esp morning

time all college buses coming same time• Students allowed upto 8:45 due to transport delay

37

Stepwise project planning – Step 2 Establish communication channels

amongst stake holders

• Required right information at the right time

• During smooth run, periodic updates

• Man is information hungry – Go ahead and satisfy ego

38

Stepwise project planning – Step 3

Identify project infrastructure

• Mapping the project to organization’s strategic planning – how the proposed project maps onto the

organizations strategic planning.• E.g HIS co can take stock management system

NOT student management suystem

• Freezing procedures and standards • Project team organization

39

Stepwise project planning – Step 3 Freezing procedures and standards

• Life cycle model to be followed• Work products at each stage• Design standards• Development standards• Testing standards• Security standards• Installation standards• Maintenance standards• Change control procedures• Configuration management standards• Measurements for statistics purposes.• Project management and control standards

40

Stepwise project planning – Step 3 Project team organization

• Org chart of a typical SW proj co.Strategic apex

Technical support

HW & Networking, SW support,

Training, DB,design,

testing, Integration,

Domain expertise

Logistic support

Middle management

Core operation

Logistic support to the entire project ,

HR, Finance, Admin, Stores etc

Technical support to core

operations

SW development

Convert directions to plans

for execution

Execution of plans

To set direction

May12, 41

Stepwise project planning – Step 4

Analyse Project characteristics • Every project is very unique

• Uniqueness reveals its characteristics• HIS -- saves human life• GSLV - huge cost / Nation’s prestige• Tally – product for multiple customers in India• Oracle Apps / SAP - product for multiple customers

worldwide• AIIMS – Joint Commission International (JCI), USA

» - National Accreditation board of Hospitals ( NABH), India

42

Stepwise Planning - MICROIdentify

products & activities

Estimate effort

Estimate risk

Allocate resources

Review/

Publicize plan

Execute the planLower level

planning

May 1243

Stepwise project planning – Step 5 Identify the products and activities

• Identification of Deliverables • Document the product flow • Identify product instances • Draw activity network diagram • Identify parallel activities and milestones• Draw the base plan

44

Stepwise project planning – Step 5 Identification of Deliverables

• Product breakdown structureProject products

Module productSystem product Management product

Work products such as

-Software specs

-Design specs

-Test plan-Integration test cases

etc…

All submodules(codes) such as

-Master

-Various types of transactions

etc…

Management reports such as

-Periodic progress report

-Progressive cost sheet

-Milestone reportetc…

45

Stepwise project planning – Step 5 Document the product flow

• Documentation min. reqd for

– Software requirement specs– Design specs– Codes– Test plan/Test cases

46

Stepwise project planning – Step 5

Product flow diagram

Software requirement specs

User requirements

Various module design

Integration test cases

Module code/Test

Tested software

47

Stepwise project planning – Step 5 Identify product instances

• Weekly reports on every Monday– number of instance for this report = Number

of Monday’s in the given project period.

• No. of modules/sub modules– Master, Savings transactions, Fixed deposit

transaction, - product instance = 3.

48

Stepwise project planning – Step 5

Draw activity network diagram

Software requirement

specs

‘Module master’ design Code/Test

Test integrated software

‘Module savings trx’ design

Code/Test

‘Module fixed deposits’ design Code/Test

Design integration test cases

49

Stepwise project planning – Step 5

Identify parallel activities and milestones

• Master first

• Trx parallally

• Establish milestones

50

Stepwise project planning – Step 6

Estimate effort • Cost of components

– Cost of all non human resources.– Cost of human resources (including hiring and

training cost)– Cost of various activities.

• Total cost = Sum total of all above costs

51

Stepwise project planning – Step 7

Identify and Estimate risks • Many people involved

• Many specialties involved

• Project is interdependant

• Effect of Risk– Time overrun– Cost Overrun

• Keep investors in knowledge loop

52

Stepwise project planning – Step 8 (Prepare the project plan)

1 Define specifications

1.1 Identify customers

1.2 Interview 10 customers

1.3 Interpret requirements

1.4 Benchmark products

1.5 Define target PDS

1.6 Target PDS Released

2 Generate concepts

2.1 Review comp products

2.2 Search patents

2.3 Brainstorm concepts

3 Select top 2 concepts

4 MQ Presented

5 Profile motor power

5.1 Design test stand

5.2 Build test stand

WBS Task name3 6 9 12 2 512 15 18 21 24 27 8 11 14 17 20

January February

30

1/7

1/8

1/12

1/14

1/19

1/19

1/20

1/20

1/29

1/14

1/28

1/7

1/11

1/13

1/18

1/21

1/21

1/22

1/28

2/8

1/27

2/5

1/21

2/2

53

Stepwise project planning – Step 9 Broadcast/Review/Freeze plan

• Circulate to all stakeholders

• Stakeholders look from their perspective

• Get their feedback

• Modify plan, if necessary

• Freeze plan ~ called ‘Base Plan’

• Any future modification on this plan only

54

Stepwise project planning – Step 10

Execute / low level plan• Kick start activities as per plan• When proj progresses….more accurate data comes in• Update base plan judiciously and recirculate to all stake

holders• Allocate resources

– Skill / competency– Experience– Salary– Requirement availability– Personal traits

55

End of Unit 1

56

Q & A