Course Name : Software Project Management

Course Code : CoSc-614

Credit Hour : 3, (Lecture - 2)

Introduction
To
Software Project Management
 • Good Morning!
• Welcome you all to the first virtual Class

Audio Check if you use mobile phone for this class

Use Ear phone or head phone with your mobile when you join

Then Do the audio setting.

1. Open Zoom app

2.Click setting (Curled double circle) at top-left screen
3.Select meeting
4.select the option on auto connects to audio
5. change to use internet.
6. join to meeting with the same id : 640 852 7369
***************************************************
 Topics to be covered.
Chapter -I Introduction to Software Project Management
.
CHAPTER – II Project Evaluation

CHAPTER – III Life-Cycle Phases & Artifacts of the Process

CHAPTER – IV Project Monitoring & Control

CHAPTER – V Managing People and Team Organization

Tuesday, May 12, 2020 3

 Syllabus of SPM
• CHAPTER - I
• , Earned Value with base line budget, Prioritizing and
• Introduction to Software Project Management: What monitoring, Change Control.
is Software Project Management, General Project and
Software Project, Need of Software Project Management, •  
Characteristics of Projects, Activities covered by project • CHAPTER - V
management, An overview of project planning (Step • Managing People and Team Organization:
Wise). Introduction, Understanding Behavior, Organizational
•   Behavior with Background, Selecting the right person
• CHAPTER - II for the job, Instruction in the best methods,
• Project Evaluation: Introduction, Strategic Assessment, Motivation, Working in the Group, Becoming a Team,
Technical Assessment, Cost benefit analysis, cash flow Decision Making, Leader Ship and organizational
forecasting, Cost Benefit evaluation techniques and Risk Structures.
evaluation.
•  
• Brief information about Project Estimation
Techniques. •  
•   • Text Books:
• CHAPTER - III • 1. Software Project Management, Bob Hughes and
• Life-Cycle Phases & Artifacts of the Process: Life- Mike Cotterell: Tata McGraw-Hill Edition.
Cycle Phases-Inception, Elaboration, Construction, • 2. Software Project Management, Walker Royce:
Transition. The artifact sets – Requirement Set, Design Pearson Education, 2005.
Set, Implementation Set, Deployment Set, About
•  
Management Set and its planning’s, Management
artifacts, Engineering artifacts, pragmatic artifacts. • References:
•   • 1. Software Project Management, Joel Henry, Pearson
• CHAPTER - IV Education.
• Project Monitoring & Control: Introduction, Creation • 2. Web Resources of www.nptel.in
of Frame work, Collecting Data, Visualizing Progress, • 3. Software Project Management in practice, Pankaj
Cost Monitoring, Earned Value with base line budget, Jalote, Pearson Education.2005.
Prioritizing and monitoring, Change Control.
• 4. All other online related web recourses and papers.
•   May 12, 2020
Tuesday, 4
 1.Project Success
Su
b
Pr
oc

K
ess
RIS

RIS
K
SCOPE TIME
Tuesday, May 12, 2020 5
 2. Examples of 10 Application Areas

1 2 3 4 5 6
YOUR SOFTWARE PROJECT IS NOT 100 PERCENT COMPLETE UNLESS
THE DEVELOPER UNDERSTANDS THOROUGLY OF THE APPLICATIONS
Tuesday, May 12, 2020 6
2. EXAMPLE – 10 APPLICATION AREAS..
DIFFERENT PROJECTS HANDLED BY ECIL

10
8
ECIL

Tuesday, May 12, 2020 7

……………….
 Project of JAWAHAR port
Installation and implementation
• India’s 11th major port (A class) located in New Mumbai.
Co-ordinated by IPA (Indian Port Authority)
• Constructed by a Consortium –-----Klockner, Hyundai, ABB, `
Tarmate,Siemens, L&T- in 1990
(Investment-01 Billion Rupees including 20 Million Rupees for Automation)
Slno Equipments/Activities Company
1 4 Layers control system A B B (Asia Brown
Top Layers : Workstations/DEC3100,- Client/Server Bovery)-Switzerland
3rd Layer : Computer systems (Micro VAX3500
(Real Time Computer)
Middle Layer: PLC-Programmable Logic Control and
Bottom layer : Mechanized Equipment(Semi Auto)
2 Motors ,Relays , Electrical Panels ABB , Germany
3 Structures, Sheds/Shallown, Rails, Hyundai, Korea
4 Roads, infrastructutre Tarmate , Japan
5. Bagging System Klockner , Germany
6 Electrical Distributed System
Tuesday, May 12, 2020
Siemens, L&T 8
 Characteristics of projects
A task is more ‘project-like’
if it is:
-Non-routine(one start and one end)
-Planned
-Aiming at a specific target Project
-Work carried out for a customer IT Project
-Involving several specialism Software
Projects
-Made up of several different phases
-Constrained by time and resources
-Large and/or complex
Tuesday, May 12, 2020 9
 Projects’ Activities

1. Project -- Product , Services & Results

e.g, Garments/Shirts,Ethiotel/Transport & Universities
2. Project Management (measurement & metrics, estimation of time and
budget,risk analysis, and track and control)
3. Portfolios, Programs, Project
4. Progressive Planning
5. Project and Strategy Planning (Framework)
6. Operation Management (Machine operation/works in shifts)
7. Enterprenership Environment Factor (against/Pro by local
conditions)

Tuesday, May 12, 2020

Continue ……next slide 10
 Project Activities
8. Life Cycle & Organization
9. Organization process assets(technical guidelines)
10. Process groups(5 different groups.InPlExMoCl)
11. Projec Mapping with Knowledge Areas
12. Project Management Processes
13. Buyer and Seller Relationship (SCM&CRM)
14. PERT/CPM
(Project Evaluation Review Technique/Critical Path Method)

Tuesday, May 12, 2020 11

Activities covered by project management

Feasibility study
Is project technically feasible and worthwhile from a business
point of view?
Planning
Only done if project is feasible
Execution
Implement plan, but plan may be changed as we go along
12
 Projects‘ Phases
( Life Cycle of Software Engineering )

1.Data Collection 2.Data Analysis

3.Specification analysis 4.Design
5.Development 6.Testing
7.Implementation 8.Maintenance
9.Reengineering

The way of Execution ..

I .Single source (Proprietary)

II Split project into area wise…

Contractors -1+2+ 3 +…(consortium) for execution-- Arbitration.at the
end

III. Methodology: Traditional water falls , RAD, Iterative Incremental…etc,

IV. Resources.. Creativity by Right Brain and analytical –left brain

V. Constraints and Quality

Tuesday, May 12, 2020 13
 KNOWLEDGE AREAS -9 ELEMENTS

Tuesday, May 12, 2020 14

 Organizational Culture & Styles
Generally refers to norms how to approach, what is
acceptable, who is influential in facilitating for
getting the work done.
Work ethics, work hours, dress code,
communication styles and structures.
This is part of EEF(Enterprises Environment Factors)
EEF refers to environmental factors that surround or influences
project success.
It could be internal or external and can come from all
enterprises involved in the projects

Tuesday, May 12, 2020 15

 What is management?
*This involves the following activities:

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 solutions when problems emerge
Representing – liaising with clients, users, developers and other
* This list is based on one that can be found in Introduction to Software
stakeholders
Project Management and Quality Assurance
by Darrel Ince, Helen Sharp and Mark Woodman, McGraw-Hill, 1993.

Tuesday, May 12, 2020 16

 What is Software Project Management?
Project management is not just a crucial element in successful
software and IT development, but is also a fascinating topic in its
own right.
Software project management, while incorporating all the key
elements of generic project management, also has to deal with
the peculiar problems associated with creating software.
The peculiar problems include the relative intangibility of
software, its extreme malleability, the intimate relationship it has
with the systems within which it is embedded, and its sheer
complexity(encapsulation).
SWOT analysis is not applicable to software Project but for other
projects

Tuesday, May 12, 2020 17

 Need of Software Project Management,(why)
SPM techniques enable the translation of a
problem statement into a solution that
satisfies all stakeholders
Primary target readers are decision makers.
Those people who authorize investment and
expenditure of software related budgets

Example. 1.Organization managers, 2.Project managers,

3.Software acquisition officials and their staff.

Tuesday, May 12, 2020 18

 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!
19
 Difference between
General Project and Software Project
Sl Attributes General Projects Software Project
n
o

1 Visiblility when a bridge or a road is Progress is not immediately visible

constructed the progress is
actually seen.

2 Nature of Not so as software Complexity

bindings

3 Flexibility Difficult job Changes can be made easily

Software Management is full of

Maximum is well planned gray areas, situation dependencies
4. Construction and ambiguous trade offs,
It is difficult to provide an accurate
depiction of many concepts and
to retain precision of the
presentation across a broad range
of domains
Tuesday, May 12, 2020 20
 How is SW project different from other projects ?

1. Limited knowledge on application domain

2.Lack of quality standards and measures
3.Limited knowledge leads to task delay. When
tasks get delayed, the delivery of the final
product delayed
4.Lack of communication between customers
and contractors due to different levels of
domain knowledge and assumptions about the
final product

Tuesday, May 12, 2020 21

 Software Project Problem
• 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

Tuesday, May 12, 2020 22

The software development life-cycle (ISO 12207)

23
 Objectives should be SMART
S – specific, that is, concrete and well-defined
M – measurable, that is, satisfaction of the objective can
be objectively judged

A – achievable, that is, it is within the power of the

individual or group concerned to meet the target

R – relevant, the objective must relevant to the true

purpose of the project

T – time constrained: there is defined point in time by

which the objective should be achieved
Tuesday, May 12, 2020 24
 Project Success-12 Golden Rules
Rule #1 Gain Consensus on Project outcome
Rule #2 build the best team possible
Rule #3 develop a comprehensive , viable plan and keep it up to date
Rule #4 determine how much stuff you really need to get things done
Rule #5 have a realistic schedule
Rule #6 won’t try to do more than that can be done
Rule #7 remember that people count
Rule #8 gain the formal and ongoing support of management and stakeholders
Rule #9 must be willing to change
Rule #10 must keep others informed of what you are up to
Rule #11 must be willing to try new things
Rule #12. must become a leader

Tuesday, May 12, 2020 25

 Which situation is worse?

• Successfully building and implementing a

system that provides little or no value to the
organization
OR
• Failing to implement an system that could
have provided value to the organization , but
was poorly developed or poorly managed.

Tuesday, May 12, 2020 26

 Goals/sub-objectives
Often a goal can be allocated to an individual.
Individual may have the capability of achieving goal,
but not the objective on their own e.g.

Objective – user satisfaction with software product

Analyst goal – accurate requirements

Developer goal – software that is reliable

Tuesday, May 12, 2020 27

 Measures of effectiveness
How do we know that the goal or objective has been
achieved?
-By a practical test, that can be objectively assessed.

e.g. for user satisfaction with software product:

1. Repeat business – they buy further products from s/w
companies
2. Number of complaints – if it is low etc .

Tuesday, May 12, 2020 28

 Stakeholders
These are people who have a stake or interest in the project
In general, they could be users/clients or
developers/implementers

They could be within the project team or

Outside the project team, or
within the same organization or
Outside both the project team and the organization

Tuesday, May 12, 2020 29

 CPM/PERT
• Critical Path Method(CPM): emphasis on the trade off
between the cost of the project and its over all
completion time .The path connects nodes which have
zero slake factor
• .e.g, for certain activities it may be possible to decrease
their completion times by spending more money.
• Project Evaluation Review Technique(PERT) emphasis
on completing the project in shortest possible time
• .e.g. For a particular activity the most likely
completion time is 4 weeks but it could be anywhere
between 3 weeks and 8 weeks)
Tuesday, May 12, 2020 30
 An overview of Project Planning (Step Wise).
Step 0: Select a project
Step 1: Identify the project scope and objectives

Step 2: Identify project infrastructure

Step 3: Analyze Project characteristics
Step 4: Identify project product and activities

Step 5: Estimate efforts for each activities

Step 6: Identify the activity risks

Step 7: Allocate resources

Step 8: Review/Publicize view
Step 9: Execute Plan
StepTuesday,
10:May 12, 2020 Lower levels of Planning 31
An overview of Project Planning (Step Wise).

Tuesday, May 12, 2020 32

 Example for a project PERT chart
problem

Tuesday, May 12, 2020 33

 Software Cost Model
• Most of the software cost models can be abstracted into a
function of FIVE basic parameters
1.SIZE- no. of source instructions, number of function points
2.PROCESS-to produce the end product and ability to avoid
rework, bureaucratic delays and communication overhead
3.PERSONNEL-software engineer skill, experience in
computer science
4. ENVIRONMENT- Tools and Techniques

5.QUALITY- its feature , performance , reliability and

adaptability

Tuesday, May 12, 2020 34

 Estimated cost

Efforts= (Personal)X (Environment) X( Quality)X ( Size process)

The Per-line cost for smaller application much less than
for the larger application
Example given in text book. Comparing 10,000 lines application with
100,000 line application .assume all parameters are constant

10,000 lines 100,000 lines

Man Month/staff 62 900
Lines/man month 175 111
hours per line 0.87 1.37
Less no of lines cost less, less memory and fast process
Tuesday, May 12, 2020 35
 Summary
• Projects are non-routine - thus uncertain
• The particular problems of projects e.g. lack of
visibility
• Clear objectives are essential which can be
objectively assessed
• Stuff happens. Not usually possible to keep precisely
plan – need for control
• Communicate, communicate, communicate!

Tuesday, May 12, 2020 36

 .
References
1.Chapter 6-Activities & Time Planning by Dr. Daniel Keret
2.Chapter 1- Introduction to SPM by Robert Hughes and Mike
Cotterell.
3. PMBOK 4th edition. by Project Management Institution , America
 End of Chapter 1

Tuesday, May 12, 2020 38

 Individual Assignment
A write up for the Topics given
Marks: Reports (10) + Presentation(10) -submission : before 3 weeks

I.Introduction includes
1. Where is it built/Location ?
2. Who/Contractor executed?
3. How much money / investment made and by whom(sponsorship)?
4. When it was completed /who inaugurated?..span of the project. Possible get scheduled execution
5. How much money spent on Software?
6. Goal or purpose or intention of the project
II. Execution includes
7. Identify the infrastructure available /are made during the project execution
8. What are the activities they have carried out?
9. What is the software application used for project monitoring ?
10. What are the software used in machineries of the projects to execute it?
11.What are the resources Utilized to build up the project.
III. Challenges includes
.12.If it is incomplete What are the challenges/risks?
Stake holders includes
13. Who are the beneficiaries’ /end users?
IV. Conclusion
14. Its features and disaster?
15. is itMay
Tuesday, really achieved/success?
12, 2020 39
 Tentative Titles for assignment
Sl no Title for Write up Name of students
1 Blue Water Island,Dubai Leta
2 Dubai water front projects Chaltu Tesfaye
3 Jewel of the creek,UAE Amanuel
4 Coastal railway ,Nigeria Tesfaye
5 Bagamoyo Port , Tanzania Andualem
6 Standard Gauge railway , Kenya Robe
7 Ethiopian Electric Power-Ashegoda Wind Farm
Ethiopia Debelo
8 Yamarna GAS Pipeline Project,Australia Diriba
9 Metropolitan Real Estate Addis Ababa Dinka
10 Koga Irrigation And Watershed Management Project Akarbayo
11 DARPA’s Integrated Sensor Is Structure
warship(Defense Advanced Research Projects Agency) Hailu
12 Werkin van De Maeslantkering –ocean Surge
Arrester ,Rotterdam. Tashale
13 TIDAL LAGOON SWANSEA BAY,UK MESERET
14 Leningrad Nuclear Power Plant, Russia Chali
Tuesday, May 12, 2020 40
1. Wrapping page should have the usual phrases
and include

“Individual Assignment”
A study on “…………………..name of the Project”
2. Table of contents
3. Last page will have “Conclusion” and Reference

Tuesday, May 12, 2020 41