1. Project Management

2. Generic Definition.
“...encompasses all of the technical and managerial efforts required to deliver to a customer a product that satisfies the terms of the project agreement.”
..... Fairley
[Software Project]

3. Characteristics. has a specific duration consumes resources
produces deliverables
[Software Project]

4. Constituents. | more Technically speaking… Flowcharts Algorithms
Data Structures
Back end
Front end
…...
[Software Project]

5. Constituents. | more For us People Product Process Project
[Software Project]

6. The Management Spectrum4
P’s
People
Product
Process
Project

7. 4 P’s People — the most important element of a successful project
Product — the software to be built
Process — the set of framework activities and software engineering tasks to get the job done
Project — all work required to make the product a reality

8. People SEI has developed a People Management Capability Maturity Model
Following are some of the KPA’s in PM-CMM
Recruiting
Selection
Performance Management
Training
Compensation
Career development
Organization and work design
Team/Culture development

9. Players Senior managers Project (technical) managers Practitioners
Define business issues
Project (technical) managers
Plan, motivate, organize, and control the practitioners
Practitioners
Deliver technical skills to engineer a product
Customers
Specify requirements
End-users
Interact with software once released for production

10. The Product Software Scope Problem Decomposition Context
Information Objectives
Function and Performance
Problem Decomposition

11. The Process Generic phases characterize the software process
Selection of Model – a wide array exists e.g. the linear sequential model to the formal methods model
Decision should be appropriate for
Customers
People who will do the work
Characteristics of the product
Project environment

12. Project
A project is an undertaking of limited duration in time with a defined outcome.
Characteristics of a Project
One goal
Specified time / finite life
Within Budget
According to Specification
Risk

13. Project efforts must be .....
11/11/2018
Project efforts must be .....
planned
initiated
monitored
controlled

14. Project efforts must be .....
11/11/2018
Project efforts must be .....
To ensure adherence to
schedule
budget
quality

15. Project Management Laws of Project Management!
Why Software Project fail?
Goals of Project Management
Roles played by Project Management
Project Management Activities

16. Laws of Project Management.
No major project is ever installed on time, within budget and with the same staff that started it.
Yours will not be the first.
Projects progress quickly until they become 90 % complete.
Then onwards they remain 90 % complete
[Project Management]

17. Laws of Project Management..
Fuzzy project objectives are advantageous.
They let you avoid the embarrassment of estimating the corresponding costs.
When things are going well, something will go wrong. When things just can’t get worse, they will.
When things appear to be going better, you certainly must have overlooked something.
[Project Management]

18. Laws of Project Management...
If project is allowed to change freely,
Then the rate of change will exceed the rate of progress.
No system is ever completely debugged.
Attempts to debug a system inevitably introduce new bugs that are even harder to find and fix.
[Project Management]

19. Laws of Project Management….
A carelessly planned project will take three times longer than expected.
A carefully planned one will take twice as long.
Project teams detest documenting and progress reporting.
It vividly manifests their lack of progress.
[Project Management]

20. Project Management Concerns

21. Major processes in Project Management
Identify a need for a product or service
Define the goals of the project and their relative importance
Select appropriate performance measures
Develop a schedule
Develop a budget
Develop the technological (process) concept
Integrate into a project plan
Implement the plan
Monitor and control the project
Evaluate project success

22. Characteristics of an Effective Project Manager
Problem solving
Diagnose technical and organizational issues
Managerial identity
Take charge
Achievement
Initiative, accomplishment
Influence and team building
Understand and react; Remain under control

23. Why Software Projects fail.
Some reasons :-(
requirements incomplete, ambiguous, inconsistent, not measurable
success criteria ill-defined or undefined ( not maintainable, unreliable, badly human-engineered, etc.)
poor planning
casual estimates of resource requirements
[Project Management]

24. Why Software Projects fail.
Some more reasons :-( :-(
casual estimates of milestones
poor design techniques
haphazard testing strategies
accidental organizational structures
ill-defined accountability
unavailability of the right tools
poor visibility of project progress
[Project Management]

25. Why Software Projects fail.
Still some more reasons :-( :-( :-(
incompetent manpower
poor management discipline
ineffective environment
hazy process definition
accuracy and definitiveness that apply to physical sciences do not apply to software ……
[Project Management]

26. Goals of Project Management.
deliverables of high quality
use of minimum resources
effective use of resources
meeting targets on time
fool-proof statement of work / contract
skilled & satisfied team members
[Project Management]

27. technical development configuration management
Roles of Project Management.
policies, constraints
management
progress reports
requirements, changes
technical development
reports
customer
reports
work assignments
project management
progress report
work assignment standards
proceduresquality reqmts
configuration management
work assignment change requests
quality assurance
problem reports audit reports quality reports
[Project Management]

28. Project Management’s Role
11/11/2018
Project Management’s Role
customer
requirements, changes
reports
project management

29. Project Management’s Role
11/11/2018
Project Management’s Role
management
policies, constraints
reports
project management

30. Project Management’s Role
11/11/2018
Project Management’s Role
technical development
progress reports
work assignments
project management

31. Project Management’s Role
11/11/2018
Project Management’s Role
project management
work assignment change requests
configuration management
progress report

32. Project Management’s Role
11/11/2018
Project Management’s Role
project management
work assignment
standards
procedures
quality reqmts
problem reports audit reports quality reports
quality assurance

33. Software Project Management
To fail to plan
is to
plan to fail;
but
People make a plan work,
plans alone seldom make people work

34. n individuals assigned to m different functional tasks (m<n) so as to gain informal “earns”
Ad hoc team leader may be appointed
Coordination will be done by a senior manager having diversified workload

35. n individuals are organized into t teams
Each team assigned one or more functional tasks
Team having a specific structure
Coordination controlled both by project manager and team.

36. Mantei Classification of Organizations
Democratic Decentralized (DD)
no permanent leader.
Task coordinator are for shorter duration and are based on task orientation.
Decisions on the basis of group consensus
Communication is horizontal
Controlled Decentralized (CD)
Software Engineering Team has defined permanent and secondary leaders.
Problem solving a group activity with horizontal communication.
Vertical communication along control line also occurs
Control Centralized (CC)
Top Level problem solving.
Communication vertical between team members and team leader.

37. Software Teams The rigidity of delivery date
The following factors must be considered when selecting a software project team structure…
The difficulty of the problem to be solved
The size of the resultant program(s) in lines of code or function points
The time that the team will stay together (team lifetime)
The degree to which the problem can be modularized
The required quality and reliability of the system to be built
The rigidity of delivery date
The degree of sociability (communication) required for the project.