short description of Software engineering Project Management

1. Copyright @ Deepak 1

2. Project
Management
OverviewWhat is project
management
Who does it
Why is it
important
What are the
steps
Change is good!
Copyright @ Deepak 2

3. The 4 p’s
Copyright @ Deepak 3

4. People :The
StakeholdersSenior managers
Project managers
Practitioners
Customers
End users
Copyright @ Deepak 4

5. People: Team Leaders
Motivation
Organization
Ideas or innovation
Problem solving
Copyright @ Deepak 5

6. People : The Software
Team• Seven project factors
o The difficulty of the problem to be solved
o The size of the resultant program(s) in source lines of code
o The time that the team will stay together
o The degree to which the problem can be modularized
o The required quality and reliability of the system to be built
o The rigidity of the delivery date
o The degree of sociability (communication) required for the project
Copyright @ Deepak 6

7. • Four organizational paradigms
o Closed paradigm
o Random paradigm
o Open paradigm
o Synchronous paradigm
• Five factors that cause team toxity
o A frenzied work atmosphere
o High frustration that causes friction among team members
o A fragmented or poorly coordinated software process
o An unclear definition of roles on the software team
o Continuous and repeated exposure to failure
Copyright @ Deepak 7

8. People : Coordination and
Communication Issues
• Key characteristics of modern software
make projects fail
o scale, uncertainty, interoperability
• To better ensure success
o Establish effective methods for
coordinating the people who do the work
o Establish methods of formal and information
communication among team members
Copyright @ Deepak 8

9. The Product
• The scope of the software development must be established and
bounded
o Context
o Information objectives
o Function and performance
• Software project scope must be unambiguous and understandable at
both the managerial and technical levels
Copyright @ Deepak 9

10. • Problem decomposition
o Also referred to as partitioning or problem elaboration
o Sits at the core of software requirements analysis
• Two major areas of problem decomposition
o The functionality that must be delivered
o The process that will be used to deliver it
Copyright @ Deepak 10

11. The Processo The project manager must decide which process model
is most appropriate based on
• The customers who have requested the product
and the people who will do the work
• The characteristics of the product itself
• The project environment in which the software
team works
o Once a process model is selected, a preliminary project
plan is established based on the process framework
activities
o Process decomposition then begins
o The result is a complete plan reflecting the work tasks
required to populate the framework activities
Copyright @ Deepak 11

12. The Project: A Common Sense Approach
• Start on the right
• Maintain momentum
• Track progress
• Make smart decisions
• Conduct a post mortem
analysis
Copyright @ Deepak 12

13. The Project: Signs it
• Software people don't understand their customer's needs
• The product scope is poorly defined
• Changes are managed poorly
• The chosen technology changes
• Business needs change (or are poorly defined)
• Deadlines are unrealistic
• Users are resistant
• Sponsorship is lost (or was never properly obtained)
• The project team lacks people with appropriate skills
• Managers (and practitioners) avoid best practices and
lessons learned
Copyright @ Deepak 13

14. Project: The W5HH
Principle
• Why is the system being developed?
• What will be done?
• When will it be done?
• Who is responsible for a function?
• Where are they organizationally located?
• How will the job be done technically and managerially?
• How much of each resource is needed?
Copyright @ Deepak 14

15. Summary
Copyright @ Deepak 15
People
Product
Process
Project

16. Reference
o www.projity.c0m
o Wikipedia: Project Management
o Pressman R., Software
Engineering A Practical
Approach, Ch 21
Copyright @ Deepak 16

17. THANK YOU!!
Copyright @ Deepak 17

18. Presented by:
DEEPAK KUMAR
(Shri mata vaishno devi university)
Copyright @ Deepak 18