Post on 30-Nov-2014
description
Copyright @ Deepak 1
Software Project Management
Copyright @ Deepak 2
Project Management Overview
What is project
management
Who does it
Why is it important
What are the steps
Change is good!
Copyright @ Deepak 3
People
Product
ProcessProject
The 4 p’s
Copyright @ Deepak 4
People :The StakeholdersSenior managers
Project managers
Practitioners
Customers
End users
Copyright @ Deepak 5
People: Team LeadersMotivation
Organization
Ideas or innovation
Problem solving
Copyright @ Deepak 6
People : The Software Team
• Seven project factorso The difficulty of the problem to be solvedo The size of the resultant program(s) in source lines of
codeo The time that the team will stay togethero The degree to which the problem can be modularizedo The required quality and reliability of the system to be
builto The rigidity of the delivery dateo The degree of sociability (communication) required for
the project
Copyright @ Deepak 7
• Four organizational paradigmso Closed paradigm
o Random paradigm
o Open paradigm
o Synchronous paradigm
• Five factors that cause team toxityo 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 8
People : Coordination and Communication Issues• Key characteristics of modern software
make projects failo scale, uncertainty, interoperability
• To better ensure successo Establish effective methods for
coordinating the people who do the work
o Establish methods of formal and information
communication among team members
Copyright @ Deepak 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 10
• Problem decompositiono Also referred to as partitioning or problem elaboration
o Sits at the core of software requirements analysis
• Two major areas of problem decompositiono The functionality that must be delivered
o The process that will be used to deliver it
Copyright @ Deepak 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 workso Once a process model is selected, a preliminary
project plan is established based on the process framework activities
o Process decomposition then beginso The result is a complete plan reflecting the
work tasks required to populate the framework activities
Copyright @ Deepak 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 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 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?
Summary
Copyright @ Deepak 15
People
Product
Process
Project
Copyright @ Deepak 16
Referenceo www.projity.c0mo Wikipedia: Project
Managemento Pressman R., Software
Engineering A Practical Approach, Ch 21
Copyright @ Deepak 17
THANK YOU!!
Copyright @ Deepak 18
Presented by:DEEPAK KUMAR(Shri mata vaishno devi university)