Department of Applied Computational Science & Engg.

Program: BTech CSAI/ CSAIML/

CSDS/ AIML/ AIDS
Course Code: KOE 068
Course Name: Software Project
Management
Lecture No: Unit-4
 Department of Applied Computational Science & Engg.
Course Code: KE068 Course Name: Software Project Management

Course Outcomes :

Program Name: BTech CSAI/CSAIML/CSDS/AIML/AIDS

 Department of Applied Computational Science and Engg.
Course Code068 Course Name: Software Project Management

Course Prerequisites

None

Program Name: BTech CSAI/CSAIML/CSDS/AIML/AIDS

 Department of Applied Computational Science and Engg.
Course Code068 Course Name: Software Project Management

Syllabus

Program Name: BTech CSAI/CSAIML/CSDS/AIML/AIDS

 Department of Applied Computational Science and Engg.
Course Code068 Course Name: Software Project Management

• Lecture Objectives
To introduce the concept of Change Control and Software
Configuration Management

Program Name: BTech CSAI/CSAIML/CSDS/AIML/AIDS

 Department of Applied Computational Science and Engg.
Course Code068 Course Name: Software Project Management

• Lecture Outcomes
At the end of the lecture, a student will be able to
❖ Understand the SCM process
❖ Enumerate steps in SCM
❖ Understand Change Control Process

Program Name: BTech CSAI/CSAIML/CSDS/AIML/AIDS

 Department of Applied Computational Science and Engg.
Course Code068 Course Name: Software Project Management

Change Control
• Change control is a methodology used to manage any
change requests that impact the baseline of your project.
• It’s a way to capture a change from the point where it’s
been identified through every step of the project cycle.
• The purpose of this process is to make sure that you’re not
changing things in the project that don’t need to be
changed.
• Any changes that are approved are then documented.
• The change control process is part of the larger change
management plan.

Program Name: BTech CSAI/CSAIML/CSDS/AIML/AIDS

Program Code: 152/153/154/163/164
 Department of Applied Computational Science and Engg.
Course Code068 Course Name: Software Project Management

Elements of Change Control

• Change Control Board:
– It is a group of representatives from the project team that regularly
meet to approve or disapprove change requests.
• Change Requests:
– It is a formal petition for change in a project.
– It’s a document that explains what are the changes to be made and
the main reasons why they should be implemented.
– Change requests can either be submitted by internal or external
project stakeholders.
– An approved change request turns into a change order.

Program Name: BTech CSAI/CSAIML/CSDS/AIML/AIDS

 Department of Applied Computational Science and Engg.
Course Code068 Course Name: Software Project Management

Elements of Change Control

• Change Orders:
– Once the change control board has approved a change request,
a change order is signed by the board and the clients or
stakeholders.
– This is an agreement from both parties to change the conditions
that were first drafted in the original contract.
• Change Log:
– A change log is a change management tool that’s used to
document all the changes made to a project plan or any contracts.
– It’s a must-have tool for any project manager.

Program Name: BTech CSAI/CSAIML/CSDS/AIML/AIDS

Program Code: 152/153/154/163/164
 Department of Applied Computational Science and Engg.
Course Code068 Course Name: Software Project Management

A Template for Change Log

Program Name: BTech CSAI/CSAIML/CSDS/AIML/AIDS

 Department of Applied Computational Science and Engg.
Course Code068 Course Name: Software Project Management

Steps in Change Control

• 1. Propose Change
– The first thing to do is to identify the change.
– This can come from anyone on the project team, a stakeholder or
even a customer.
– There must be a channel open for these suggestions to flow.
– The change proposal would describe the change and how it would
benefit the project or organization.
– If there are other reasons for the change, outline them on the
change request form. That would then be added to the change log.

Program Name: BTech CSAI/CSAIML/CSDS/AIML/AIDS

 Department of Applied Computational Science and Engg.
Course Code068 Course Name: Software Project Management

Steps in Change Control

• 2. Impact Summary
– Once the change has been proposed, it’s now up to the project manager to
consider it in the larger context of the project.
– Some of the questions to be asked are:
• How will that change impact a number of variables?
• What are the benefits of in terms of cost?
• Are there any legal or regulatory constraints?
• How will the change impact your schedule?
• Will you need to employ more resources?
• Will the change bring new risks or issues to the project?
• 3. Making a Decision
– The project manager makes the recommendation to the change board
– Change board makes the decision to either
• accept the change;
• accept the change, but with notes and conditions;
• reject the change; or defer

Program Name: BTech CSAI/CSAIML/CSDS/AIML/AIDS

 Department of Applied Computational Science and Engg.
Course Code068 Course Name: Software Project Management

Steps in Change Control

• 4. Make the Change
– An approved change moves on to the planning stage and a plan of
action is developed including a schedule with start and end dates
– The plan may include a regression test in case the change proves too
problematic and the project need to revert to its original intent.
– After the change plan is completed, it’s usually followed by a
post-mortem to review any mishaps and successes.
• 5. Closure
– All stakeholders sign off on the change,
– Any outstanding paperwork is completed

Program Name: BTech CSAI/CSAIML/CSDS/AIML/AIDS

 Department of Applied Computational Science and Engg.
Course Code068 Course Name: Software Project Management

Software Configuration Management

• The software configuration management process is a series
of steps designed to track and manage all the defects,
resources, codes, documents, hardware and budgets
throughout a software project.
• It encompasses techniques of initiating, evaluating and
controlling change to software products during and after a
software project.
• Steps in SCM process
– Identification of objects in the software configuration
– Version Control
– Change Control
– Configuration Audit
– Status Reporting
Program Name: BTech CSAI/CSAIML/CSDS/AIML/AIDS
 Department of Applied Computational Science and Engg.
Course Code068 Course Name: Software Project Management

Steps in SCM

Program Name: BTech CSAI/CSAIML/CSDS/AIML/AIDS

 Department of Applied Computational Science and Engg.
Course Code068 Course Name: Software Project Management

Step1: Planning and Identification

• In this step, the goal is to plan for the development of the
software project and identify the items within the scope.
• This step figures out how the project will proceed and
identifies the exit criteria.
• Specific activities during this step include:
– Identifying items like test cases, specification requirements, and code
modules
– Identifying each computer software configuration item in the process
– Group basic details of why, when, and what changes will be made
and who will be in charge of making them
– Create a list of necessary resources, like tools, files, documents, etc.
•
Program Name: BTech CSAI/CSAIML/CSDS/AIML/AIDS
 Department of Applied Computational Science and Engg.
Course Code068 Course Name: Software Project Management

Step 2: Version Control and Baseline

• A baseline is an accepted version of a project with set
attributes.
• This baseline is designated at a specific time in the SCM
process and can only be altered through a formal procedure.
• As the project develops, new baselines are established,
resulting in several versions of the software.
• This step involves the following activities:
– Developing a way to track the hierarchy of different versions
– Establishing various baselines for the product, including
developmental, functional, and product baselines
– Developing a standardized label scheme for all products, revisions,
and files so that everyone is on the same page.
•
Program Name: BTech CSAI/CSAIML/CSDS/AIML/AIDS
 Department of Applied Computational Science and Engg.
Course Code068 Course Name: Software Project Management

Step 3: Change Control

• This method ensures that any changes that are made are
consistent with the rest of the project.
• Having these controls in place helps with quality assurance
and the approval and release of new baseline(s).
• In this step, requests to change configurations are submitted
to the team and approved or denied by the software
configuration manager.
• This procedure includes:
– Controlling ad-hoc changes requested by the client
– Checking the merit of the change request by examining the overall
impact they will have on the project
– Making approved changes or explaining why change requests were
denied.
Program Name: BTech CSAI/CSAIML/CSDS/AIML/AIDS
 Department of Applied Computational Science and Engg.
Course Code068 Course Name: Software Project Management

Step 4: Configuration Status Accounting

• This step tracks each version released during the process,
assessing what is new in each version and why the changes
were necessary.
• It also involves looking at release notes and related
documents to ensure the software meets all functional
requirements according to pre-defined baseline.
• Some of the activities in this step include:
– Recording and evaluating changes made from one baseline to the
next
– Monitoring the status and resolution of all change requests
– Maintaining documentation of each change made as a result of
change requests and to reach another baseline
• Checking previous versions for analysis and testing.
Program Name: BTech CSAI/CSAIML/CSDS/AIML/AIDS
 Department of Applied Computational Science and Engg.
Course Code068 Course Name: Software Project Management

Step 5: Audits and Reviews

• This step looks at the process, configurations, workflow,
change requests, and everything that has gone into
developing each baseline throughout the project.
• Multiple reviews of the software are performed to verify its
integrity and all essential documentation such as release
notes, user manuals, and installation guides.
• Activities in this step include:
– Making sure that the goals laid out in the planning and identification
step are met
– Ensuring that the software complies with identified configuration
control standards
– Making sure changes from baselines match the reports
– Validating that the project is consistent and complete.
Program
• Name: BTech CSAI/CSAIML/CSDS/AIML/AIDS
 Department of Applied Computational Science and Engg.
Course Code068 Course Name: Software Project Management

Recommended Books
Text books:
• Bob Hughes, Mike Cotterell and Rajib Mall: Software Project
Management – Fifth Edition, McGraw Hill, New Delhi, 2012.
Reference Book
• Robert K. Wysocki ―Effective Software Project Management – Wiley
Publication, 2011.
• Walker Royce: ―Software Project Management- Addison-Wesley, 1998.
• Gopalaswamy Ramesh, ―Managing Global Software Projects – McGraw
Hill Education (India), Fourteenth Reprint 2013.
Additional online materials
https://onlinecourses.nptel.ac.in/noc19_cs70/preview

Program Name: BTech CSAI/CSAIML/CSDS/AIML/AIDS

Program Code: 152/153/154/163/164
THANK YOU