Professional Documents
Culture Documents
(Desire, determination and a good sense of timing are the common denominations of success)
• Software Project:
– All technical and managerial activities required to deliver
the deliverables to the client.
– A software project has a specific duration, consumes
resources and produces work products.
– Management categories to complete a software project:
• Tasks, Activities, Functions
• Software Project Management Plan:
– The controlling document for a software project.
– Specifies the technical and managerial approaches to
develop the software product.
– Companion document to requirements analysis document:
• Changes in either document may imply changes in the other
document.
Equipment
Project
* Facility
Resource
Fund
* Organi-
Work zation
Breakdown des-
Structure Work
Schedule cribesPackage
con- *
* * sumes *
produces Organizational
Outcome Work respon- Unit
* * sible *
plays
depends for
Role
Set of Work Work
Activity Task Participant Staff
Products Product
Internal Project
Project Function Department Team
Work Product Deliverable
Client Manager Project Team
(Sponsor)
Problem
Statement Software Project
Management Plan
Project
Agreement
Module-1 Introduction
• Examples of Project
1. Building construction
2. Road construction
3. Shutdown Project
4. Wedding ceremony
5. Moving office to a new location
6. Movie making
7. Development of software
History of Project Management
• Projects of all sizes have been undertaken throughout history.
• Early construction projects included the ancient pyramids,
medieval cathedrals, and Indian cities.
• Other large early projects involved waging wars and building
empires.
• In the development of the United States, projects included laying
railroads, developing farms, and building cities.
• Many smaller projects have consisted of building houses and
starting businesses.
• Throughout most of history, projects were conducted, but there
was very little systematic planning and control.
• Some early projects were accomplished at great human and
financial cost.
• Others took exceedingly long periods of time to complete.
History of Project Management
• Project management eventually emerged as a formal discipline to be
studied and practiced.
• In the 1950s and 1960s, techniques for planning and controlling
schedules and costs were developed, primarily on huge aerospace and
construction projects.
• During this time, project management primarily involved determining
project schedules based on understanding the order in which work
activities had to be completed.
• Many large manufacturing, research and development, government, and
construction projects used and refined management techniques.
• In the 1980s and 1990s, several software companies offered ever more
powerful and easier ways to plan and control project costs and schedules.
• Risk management techniques that were originally developed on complex
projects have increasingly been applied in a simplified form to less
complex projects.
History of Project Management
• In the last few years, people have realized more and more that
communication and leadership play major roles in project success.
• Rapid growth and changes in the information technology and
telecommunications industries especially have fueled massive growth
in the use of project management in the 1990s and early 2000s.
• People engaged in banking, insurance, retailing, hospital
administration, and many other service industries are now turning to
project management to help them plan and manage efforts to meet
their unique demands.
• Project planning and management techniques that were originally
developed for large, complex projects can be modified and used to
better plan and manage smaller projects.
• Now project management is commonly used on projects of many
sizes and types in a wide variety of manufacturing, government,
service, and nonprofit organizations.
Project Life Cycle
• All projects go through predictable stages called a project life cycle.
• A project life cycle is “the series of phases that a project goes through
from its initiation to its closure.”
• An organization’s control needs are to be assured that the work of the
project is proceeding in a satisfactory manner and that the results are
likely to serve its customer’s intended purpose.
• The project customer is the person or organization that will use the
project’s product, service, or result.
• Customers can be internal to the organization (that is, part of the
company that is performing the project) or external to the organization.
• Many different project life cycle models are used for different types of
projects, such as information systems, improvement, research and
development, and construction.
Project Life Cycle
• Selecting and initiating—starts when an idea for a project
first emerges and the project is selected and planned at a high
level, and ends when key participants commit to it in broad
terms.
• Planning—starts after the initial commitment, includes
detailed planning, and ends when all stakeholders accept the
entire detailed plan.
• Executing—starts when the plan is accepted, and includes
authorizing, executing, monitoring, and controlling work until
the customer accepts the project deliverables.
• Closing and realizing—includes all activities after customer
acceptance to ensure project is completed, lessons are learned,
resources are reassigned, contributions are recognized, and
benefits are realized.
Project Life Cycle
Characteristics of a project
• Objectives
• Life span
• Single entity
• Team work
• Life cycle
• Uniqueness
• Change
• Successive principle
• Made to order
• Unity in diversity
• High level of sub contracting
• Risk and uncertainty
Characteristics of a project
• Classifying by industry
• Classifying by size
• Classifying by timing of project scope clarity
• Classifying by application
(It is easy to see the faults of others but not so easy to see one’s own faults)
Classifying by industry
• Information Systems
• Project Risk Management
• Consulting Innovation and New Product
Development Requirements Management
• Earned Value Management
• International Development Retail
• E-Business IT and Telecom Scheduling
• Energy, Oil, Gas and Petrochemical
(Desire, determination and a good sense of timing are the common denomination of success)
Classifying by industry
•A third method of classifying projects deals with how early in the project the
project manager and team are likely to be able to determine with a high degree
of certainty what the project scope will be.
•Example, it may be rather simple to calculate the cubic feet of concrete that are
required to pour a parking lot and, therefore, how much work is involved.
•At the opposite end of the spectrum, when developing a new pharmaceutical,
very little may be determined in the project until the results of some early
experiments are reported.
•Only at that time is it possible to begin estimating cost and determining the
schedule with confidence. The planning becomes iterative, with more detail as it
becomes available.
•In the first case, predictive or plan-driven project techniques may work well. In
the second case, adaptive or change-driven methods to iteratively determine
the scope and plan for risks may be more important.
(A successful man is one who can lay a firm foundation with the bricks others have thrown at him)
Classifying by application