Software Engineering-II. Software Project Management. Software Project Management!!!. IT Projects have a terrible track record A 1995 Standish Group Study found that only 16.2% of IT projects were successful
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
Software Project Management
Project is a planned activity. Being planned it assumes that
we can determine how we are going to carry out a task before we start.
A project is a specific(non-routine), finite task to be accomplished. It carried out in several phases and the resources available are constrained. Any activity that results in a deliverable or a product.
Projects always begin with a problem. The projects is to provide the solution to this problem.
When a project is finished it must be evaluated to determine whether it satisfies the objectives and goals.
with software progress is not immediately visible
per dollar software products contain more complexity
software developers have to conform to the requirements of clients.
the ease with which software can accommodate changes.
what work must be done to satisfy the customer that deliverables meets the requirements.
what is the project’s schedule?
The objective of any project is to complete the scope within the budget by a certain time to the customer’s satisfaction
Management can be defined as all activities and tasks undertaken by one or more persons for the purpose of planning and controlling the activities of others in order to achieve objectives or complete an activity that could not be achieved by other acting independently.
Management functions can be categorized as
predetermining a course of action for accomplishing projects objectives
arranging the relationship among work units for accomplishment of objectives and the granting of responsibility and authority to attain those objectives
selecting and training people for completing tasks
creating an atmosphere that will assist and motivate people to achieve desired end result
establishing, measuring, and evaluating performance of activities towards planned objectives
Project management is a system of management procedures,
experience that are necessary to successfully manage a project.
Yours will not be the first
Effective software project management focuses on the four P’s
Software process is populated by players who can be categorized into followings:
The Selection of team occurs early in the life cycle of a software development project.
Common characteristics of effective team members
Some important tools and techniques for team development
A legendary sports manager once said
“it’s easy to get the players. Getting them play together , that’s the hard part”
Team building- developing a group of individuals to accomplish the project’s objectives- is an ongoing process.
Team building helps to create an atmosphere of openness and trust. Members feel a sense of unity and a strong commitment to accomplish the project objectives
Once the project is selected, the next step for the senior management is to choose a Project Manager
When the team is formed, choose a leader
It is the PM’s job to make sure that the project is properly planned, implemented and completed.
It is the People - not the procedures and techniques - that are critical to accomplishing the project objectives.
Facilitator (Virtual Project Manager)
Many projects are international and team members may be geographically dispersed. Many projects may be carried out by different organizations at different location.
PM is responsible to the project team, to senior management, to the client, to anyone else who may have a stake in the projects performance and outcome.
To the Organization
• Timely and accurate communication of project’s progress
• Competent project management
To the Project Team
• Competent human resource management
To the Client
• Acceptable delivery of project’s product
• Timely and accurate communication of project’s progress
To the Project
• acquisition of resources and personnel
• dealing with obstacles arising during the course
of the project
• exercising the leadership needed to bring the
project to a successful conclusion
• trade-offs between budget, schedule, and
specifications to ensure successful completion of
§ Supply of large and small technical solutions
§ Political sensitivity
§ Much of Project Management involves politics and power
§ Solution oriented
§ Goal oriented
§ Results rather than activity focused
Openness through high self-esteem
§ No hiding errors, No witch hunts, No shooting the managers
The Best Project Manager is the one who can get the job done
A Reasonable understanding of the base technologies the
The Aim is to
• Client, Senior Management, Functional Managers
• Power base must be sufficient to get what you want
• Detect and resolve conflicts between team members
Detecting when technical experts are not telling everything
• Covering up their own failures
• Hiding doubts
Def: Interpersonal influence, exercised in situations and
directed through the communication process, towards the attainment of a specified goal.
Enthusiasm, Optimism, Energy, Courage, Maturity
• When to reward, when to punish
• When to delegate , when to step in
• When to communicate, when to remain silent
• How to capitalize on people’s strengths and cover their
– this is the PM’s fault
Software Engineers shall
1. act consistently with the public interest
2. act in a manner that is in the best interest of their client and employer
3. ensure that their products and related modifications meet the highest
professional standards possible
4. maintain integrity and independence in their professional judgement
5. subscribe to and promote an ethical approach to the management of
software development and maintenance
6. advance the integrity and reputation of the profession consistent with
7. be fair and supportive of their colleagues
8. participate in lifelong learning regarding the practice of their profession
Bossing/dictatorship Coaching & apprising/collaboration
Error hiding Error admitting
To make profit To hold the customer
giant steps Baby steps
Worker supervision Mentoring and profit sharing
Management in Past Future Management unique purpose.
Do it yourself Ask for help
Play safe Take risk and initiative
Crises management Prevention and contingency
Planning Adhoc decisionPlanned decision
Top downTop down & bottom up
Management competitive Collaborative and cross functioning
Kraul and Streeter examine a collection of project coordination techniques that are categorize in following manner.
A product breakdown structure (PBS)
Ten signs that indicates that information system project is in jeopardy
Five-part commonsense approach to software projects:
Barry Boehm suggested w5HH principle
Our Concern unique purpose.
Identify known and predictable risks
What characteristics of this product may threaten our project plan?
for software development ?
design, code and test?
1 2 3 4 5