SPM 1.

Dr.Sushruta Mishra
Dr.Sushruta Mishra
 What is
Project? A Project can be characterized as:

 Every project may has a unique and distinct goal.

 Project is not routine activity or day-to-day operations.
 Project comes with a start time and end time.
A project is well-defined task,
which is a collection of several  Project ends when its goal is achieved hence it is a temporary phase in
operations done in order to achieve
the lifetime of an organization.
a goal (for example, software
development and delivery).  Project needs adequate resources in terms of time, manpower, finance,
material and knowledge-bank.

Dr.Sushruta Mishra
Jobs versus projects

Jobs: repetition of very well-defined and well

understood tasks with very little uncertainty
Exploration: e.g. finding a cure for cancer: the
outcome is very uncertain
Projects: In the middle between Jobs &
Exploration
Dr.Sushruta Mishra
 Software Project
A Software Project is the Software Projects vs Other Projects
complete procedure of
software development
from requirement  Invisibility: With Software, progress is not immediately visible since work is
gathering to testing and logical; however, for physical artifacts like bridges, work progress can be seen
from time to time. In Software Development, there is a level of uncertainty.
maintenance, carried out
according to the execution  Complexity: Software projects contain more complexity than other engineered
methodologies, in a artifacts. For example, in a bridge, there is a clear structural relationship between
parts, whereas software component relationships are much more complicated.
specified period of time to We can't measure the complexity of a software project until we work on it.
achieve intended software
product.  Conformity: Physical systems are governed by consistent physical law, while
Software developers have to conform to the requirements of human clients.

 Flexibility: Software systems are particularly subject to change. A bridge has to

be built in a specific order, whereas we can make Software much more flexibly
and restructure parts quite freely.
Dr.Sushruta Mishra
What is software project management?

 Software project management is an art and discipline of planning and supervising

software projects. It is a sub-discipline of software engineering in which software
projects are planned, implemented, monitored and controlled.

 It is a procedure of managing, allocating and timing resources to develop computer

software that fulfills requirements.

 In software Project Management, the client and the developers need to know the length,
period and cost of the project.

Dr.Sushruta Mishra
Need of Software
Project
Management

It is an essential part of software organization

to deliver quality product, keeping the cost
within client’s budget constrain and deliver the
project as per scheduled.

Dr.Sushruta Mishra
Project Manager:
A project manager is an individual who has the overall responsibility for the planning, design, execution,
monitoring, controlling and closure of a project.

Responsibilities of a Project Manager:

 Managing risks and issues.
 Create the project team and assigns tasks to several team members.
 Activity planning and sequencing.
 Monitoring and reporting progress.
 Modifies the project plan to deal with the situation.

Dr.Sushruta Mishra
 Project Management vs Contract Management
Project Management Contract Management
Focuses on management of particular project till it gets Focuses on management of contract between two
completed successfully. companies, parties, or organizations.

Goal is to achieve desired project goal on time and Goal is to achieve mutual satisfaction among parties or
within budget. organizations or companies whose objectives are not
same but are closely linked.
Project usually involves many parties from one Contract usually binds two different business entities
business entity but mostly involves various related or but if there are more than two entities then there are
unrelated entities. separate sub-contracts.
It involves various processes such as planning, It involves various processes such as managing
organizing, and managing efforts and tasks that are contracts, deliverables, guidelines, deadlines,
made and performed to complete a project execution, analysis
successfully.

It mainly focuses on project constraints i.e. scope, time, It mainly focuses on economic of project and manage
budget, quality as per contract. claims and dispute against contract.
Objective is to predict problems or dangers as many as Objective is to create value for organization.
possible so that such problems can be removed on time
and project can be completed in spite of all problems.
Dr.Sushruta Mishra
 Activities Covered by Project Management
 Project Planning: It is a set of multiple processes, or we can say that it a task that performed before the construction of
the product starts.
 Scope Management: It describes the scope of the project. Scope management is important because it clearly defines
what would do and what would not. Scope Management create the project to contain restricted and quantitative tasks,
which may merely be documented and successively avoids price and time overrun.
 Estimation management: This is not only about cost estimation because whenever we start to develop software, but we
also figure out their size(line of code), efforts, time as well as cost.
 Scheduling Management: Scheduling Management in software refers to all the activities to complete in the specified
order and within time slotted to each activity. Project managers define multiple tasks and arrange them keeping various
factors in mind.
 Project Resource Management: In software Development, all the elements are referred to as resources for the project. It
can be a human resource, productive tools, and libraries.
 Project Risk Management: Risk management consists of all the activities like identification, analyzing and preparing the
plan for predictable and unpredictable risk in the project.
 Project Communication Management: Communication is an essential factor in the success of the project. It is a bridge
between client, organization, team members and as well as other stakeholders of the project such as hardware suppliers.
 Project Configuration Management: Configuration management is about to control the changes in software like
requirements, design, and development of the product.

Dr.Sushruta Mishra
 • Feasibility study: Is project technically feasible and
worthwhile from a business point of view?
• Planning: Only done if project is feasible
• Execution: Implement plan, but plan may be
changed as we go along

Dr.Sushruta Mishra
Software Development Life-cycle
 Requirements analysis starts with requirements
elicitation or requirements gathering which
establishes what the potential users and their
managers require of the new system.

 Architecture design The components of the new

system that fulfi l each requirement have to be
identified. Existing components may be able to
satisfy some requirements. In other cases, a new
component will have to be made. These
components are not only software: they could be
new hardware or work processes.

 Detailed design Each software component is

made up of a number of software units that can
be separately coded and tested. The detailed
design of these units is carried out separately.

Dr.Sushruta Mishra
 Code and test refers to writing code for each software unit. Initial testing to debug
individual software units would be carried out at this stage.

 Integration The components are tested together to see if they meet the overall
requirements. Integration could involve combining different software components, or
combining and testing the software element of the system in conjunction with the
hardware platforms and user interactions.

 Qualification testing The system, including the software components, has to be tested
carefully to ensure that all the requirements have been fulfilled.

 Installation This include activities such as setting up standing data (for example, the
details for employees in a payroll system), setting system parameters, installing the
software onto the hardware platforms and user training.

 Acceptance support This is the resolving of problems with the newly installed system,
including the correction of any errors, and implementing agreed extensions and
improvements. Software maintenance can be seen as a series of minor software
projects.

Dr.Sushruta Mishra
 Plans, Methods and Methodologies
Methodology = a set
of methods  Method relates to a type of activity
 Plan takes that method and converts it to
a real activities
 Its start and end dates
 Who will carry it out
 What tools and materials (also
information) will be needed

The output from one method might be the input to

another. Group of methods or techniques are
often grouped into methodologies such as
object-oriented design.

Dr.Sushruta Mishra
 Some ways of Categorizing Projects

Would an operating system on a computer be an information system or an ernbedded

system?
Dr.Sushruta Mishra
 Stakeholders in a Software Project

• Internal to the project team This means that they will be under the direct managerial
control of the project leader.

• External to the project team but within the same organization For example, the project
leader might need the assistance of the users to carry out systems testing. Here the
commitment of the people involved has to be negotiated.

• External to both the project team and the organization External stakeholders may be
customers (or users) who will benefit from the system that the project implements. They
may be contractors who will carry out work for the project.

Dr.Sushruta Mishra
CASE STUDY #1

Unity College is a higher education institution which used to be managed by a local

government authority but has now become autonomous. Its payroll is still
administered by the local authority and pay slips and other output are produced in the
local authority's computer centre. The authority now charges the college for this
service. The college management are of the opinion that it would be cheaper to obtain
an 'off-the-shelf' payroll package and do the payroll processing themselves.

What would be the main stages of the project to convert to independent payroll
processing by the college?

Dr.Sushruta Mishra
 Planning::: The transfer to local processing that is to be carried out needs proper planning with the participation of all those
concerned. Some detailed planning would need to be deferred until more information was available, for example which
payroll package was to be used.

 Requirements elicitation and analysis::: This is finding out what the users need from the system. To a large extent it will
often consist of finding out the functionalities of the current system and whether to assume the new system to provide the
same functions as the old. The users might have additional requirements, however, or there might even be facilities that are
no longer needed.

 Specification::: This involves documenting what the new system is to be able to do.

 Design/coding::: As an 'off-the-shelf'package is visualized, these stages will be replaced by a package evaluation and
selection activity.

 Verification and validation::: Tests will need to be carried out to ensure that the selected package will actually do what is
required. This task might well involve parallel running of the old and new systems and a comparison of the output from
them both to check for any inconsistencies.

 lmptementation::: This would involve such things as installing the software, setting system parameters such as the salary
scales, and setting up details of employees.

 Maintenance::: This will include dealing with users'queries, liaising with the package supplier and taking account of new
payroll requirements.
Dr.Sushruta Mishra
 Setting objectives
Objectives focus on the desired outcomes of the project
rather than tasks within it. They are the post condition
of the project.
Objectives should be
Answering the question ‘What do we have to do to SMART
have a success?’
Need for a project authority
Sets the project scope
Allocates/approves costs
Could be one person - or a group
Project Board
Project Management Board
Steering committee

Informally, the objective of a project can be defined by

completing the statement:
The project will be regarded as a success
if……….
Rather like post-conditions for the project
Focus on what will be put in place, rather than how
activities will be carried out Dr.Sushruta Mishra
 Goals/sub-objectives
• These are steps along the way to achieving the objective.
Often a goal can be allocated to an individual.
• Informally, these can be defined by completing the sentence. Individuals might have the capability of achieving
goal on their own, but not the overall objective e.g.
• To reach objective X, the following must be in place
A…………… Overall objective – user satisfaction with software
B……………
product
C…………… etc
Analyst goal – accurate requirements
Developer goal – reliable software

Any project plan must ensure that the business case is kept intact. For example:
● that development costs are not allowed to rise to a level which threatens to exceed the value of benefits;
● that the features of the system are not reduced to a level where the expected benefits cannot be realized;
● that the delivery date is not delayed so that there is an unacceptable loss of benefits.

Dr.Sushruta Mishra
Project success/failure

Other success criteria

are::::::
• Improved skill and knowledge
• Creation of assets that can be used on
future projects e.g. software libraries
• Improved customer relationships that
lead to repeat business

Dr.Sushruta Mishra
Project objectives and Business objectives:::::

A computer game could be delivered on time and

within budget, but might then not sell.

A commercial website used for online sales could be

created successfully, but customers might not use it to
buy products, because they could buy the goods more
cheaply elsewhere.

Dr.Sushruta Mishra
 What is
Management
?
 Planning – deciding what is to be done
 Organizing – making arrangements
 Staffing – selecting the right people for the job
 Directing – giving instructions
 Monitoring – checking on progress
 Controlling – taking action to remedy hold-ups
 Innovating – coming up with solutions when problems emerge
 Representing – liaising with clients, users, developers and other stakeholders

Dr.Sushruta Mishra
Management Control
 Data: the raw details
e.g. ‘6,000 documents processed at location X’

 Information: the data is processed to produce

something that is meaningful and useful
e.g. ‘productivity is 100 documents a day’

 Comparison with objectives/goals:

e.g. we will not meet target of processing all
documents by 31st March

 Modelling: working out the probable outcomes of

various decisions
e.g. if we employ two more staff at location X how
quickly can we get the documents processed?

 Implementation: carrying out the remedial actions

that have been decided upon

Dr.Sushruta Mishra
Much of the project manager’s time is spent on only three of the eight
identifi ed activities, viz., project planning, monitoring, and control.

Dr.Sushruta Mishra
 Traditional versus Modern Project Management

Characteristics Modern approach Traditional approach

Organizational structure Iterative Linear
Scale of projects Small and medium scale Large scale
User requirements Interactive input Clearly defined before implementation
Involvement of clients High Low
Development model Evolutionary delivery Life cycle
Customer involvement Customers are involved from the time Customers get involved early in the project but not once
work is being performed the execution has started
Escalation management When problems occur, the entire Escalation to managers when problem arise
team works together to resolve it
Test documentation Tests are planned one sprint at a time Comprehensive test planning

Dr.Sushruta Mishra
END

Dr.Sushruta Mishra