Bachelor of Computer System and

Information Technology (BCS.IT)

Third Semester
Aug/Sep 024
Assignment N0 2

Software Project Management

(CSC 2330)

STUDENTS NAME: BIKRANSHU GUPTA

LECTURER NAME: KUSHAL PAHADI

1) At the start of a project, creating a project charter is essential. Why? Explain using an
imaginary project. How does integration management connect to the project lifecycle?
Clarify.

➔ Creating a project charter at the start of a project is essential because the project
charter serves as a foundational document that outlines the project's objectives, scope,
stakeholders, and overall vision. It acts as a formal agreement among stakeholders and
provides a clear direction for the project team. Let’s explore this concept using an
imaginary project and then discuss how integration management connects to the
project lifecycle.
Importance of Creating a Project Charter
Lets suppose a project: Launching a new mobile app so reasons for creating a project charter:
1. Defines the project objectives: The project charter clearly outlines the primary objectives
of the app, such as user engagement, tracking fitness metrics, and integration with wearable
devices.
2. Establishes scope: The charter helps define what is included in the project and what is not,
thereby setting boundaries and expectations.
3. Identifies stakeholders: The project charter lists key stakeholders, including the project
sponsor, development team, marketing team, and end-users. This ensures that everyone
knows who is involved and their roles.
4. Provides authority and resources: The project charter grants the project manager the
authority to allocate resources and make decisions necessary for project execution.
5. Serves as a reference document: The charter serves as a reference point throughout the
project lifecycle, helping to keep the team focused on the original goals and objectives.
Integration management is a critical aspect of project management that connects various
elements of the project lifecycle to ensure that all parts of a project work together effectively.
Here’s how integration management connects to the project lifecycle:
1. Project Initiation :
Project Charter Development: Integration management begins with the creation of the project
charter, which formally authorizes the project and outlines its objectives, stakeholders, and
high-level requirements. This sets the foundation for all subsequent phases.
2. Project Planning
Developing the Project Management Plan: Integration management involves consolidating all
planning documents into a comprehensive project management plan. This plan includes
scope, schedule, cost, quality, resources, communication, risk, procurement, and stakeholder
management plans, ensuring that all aspects of the project are aligned.
3. Project Execution
Directing and Managing Project Work: Integration management ensures that project activities
are coordinated and executed according to the project management plan. It involves
managing team dynamics, stakeholder engagement, and communication to keep the project
on track.
4. Project Monitoring and Controlling
Tracking Performance: Integration management involves monitoring project performance
against the project management plan. This includes measuring progress, identifying
variances, and implementing corrective actions as necessary.
Integrated Change Control: This process ensures that any changes to the project scope,
schedule, or budget are evaluated and approved in a controlled manner, minimizing
disruptions and maintaining alignment with project objectives.
5. Project Closing
Finalizing All Activities: Integration management ensures that all project work is completed,
deliverables are accepted, and stakeholders are satisfied. This includes formal closure of
contracts and documentation of lessons learned.
From above, integration management serves as the glue that binds all aspects of the project
lifecycle together. It ensures that various processes, stakeholders, and project components are
aligned and coordinated, leading to successful project outcomes.
2) Explain about input, tools and techniques and output of integrated change control.
➔ The input, tools and techniques and output of integrated change control are given below:
Input tools are:
1. Project Management Plan: In project management plan it includes all plans such as scope,
schedule, cost, quality, resource, communication, risk, procurement, and stakeholder
management plans. The project management plan provides the baseline against which
changes are evaluated.
2. Project document: it make the basis of estimate and make the requirment traceability matrix.
Similarly It also make the risk report on the basis of projects.
3. Work Performance Reports: These reports provide information on project
performance, including progress against the project baselines, and can
highlight areas where changes may be necessary.
1. Change Requests: It requests for changes to the project scope, schedule,
or budget must be documented. This can include requests for scope
changes, corrective actions, preven Ddtive actions, or updates to project
documents.
1. Enterprise Environmental Factors: These are external factors that can
influence the change control process, such as organizational culture,
market conditions, regulations, and industry standards.
1. Organizational Process Assets: These include policies, procedures, and
historical information that can assist in the change control process, such
as templates for change requests and lessons learned from previous
projects
Tools and Techniques of the integrated change control are given below:
1. Change Control Tools: Change control Tools is used to to log ,track and access change requests
systematically of the software and systems
2 Expert Judgment: It Involves consulting with experts or stakeholders who have
experience or knowledge relevant to the proposed change. There view can help
assess the impact of changes and make informed decisions.
3 Meetings: Regular meetings with project stakeholders to discuss change
requests and their implications. This helps ensure that all relevant parties are
informed and can provide input.
4 Data Analysis : A technique used to assess the potential effects of a change on
project objectives, including scope, schedule, cost, quality, and resources. This
analysis helps decision-makers understand the consequences of implementing
the change.
5 Decision-Making Techniques: Various methods, such as voting, multi-criteria
decision analysis, or consensus-building techniques, can be used to evaluate and
decide on change requests.
Output of integrated change control are given below;
1 Approved Change Requests: Changes that have been evaluated and formally
approved, leading to updates in project documents and plans. This includes
scope changes, schedule adjustments, and budget modifications.
2 Project Management Plan Updates: The project management plan and its
components (scope, schedule, cost, etc.) are updated to reflect approved
changes. This ensures that all stakeholders are aligned with the latest project
direction.
3 Change Log: A document that tracks all change requests, their status, and the
outcomes of the change control process. This log helps maintain a history of
changes for future reference and accountability.

3) What is WBS? Why is it important to design WBS? Illustrate a WBS for a project
of
inventory management system of a college.
WBS mean Work Breakdown Structure. It is a hierarchical decomposition of the
total scope of work to be carried out by the project team to accomplish the
project objectives and create the required deliverables.The WBS organizes and
defines the total scope of the project and represents the works specified in the
current approved project scope statement. It breaks down the total scope of
work into smaller, more controllable parts, allowing project managers to organize
and define the total work requires to complete a project.

WBS is important to design due to the following reasons:

➢ WBS provide a clear structure for the project, making it easier for team members to
understand the project scope and their responsibilities.
➢ It helps in defining and controlling the project scope by ensuring that all work
required to complete the project is included
➢ It allows better estimation of time and costs associated with each work package,
leading to more accurate project planning.
➢ It provide a framework for monitoring and controlling projects progress.
➢ It make the better communication between the stakeholder by providing a common
understamding of the project.
➢ It mitigate the risk of the project by the early project detection.

The WBS project of inventory management system of a college is shown below:

4 Why project integration management is termed as umbrella of rest of other knowledge areas?
Explain with examples.
Project integration management involves coordinating all of the other project managementknowledge
areas throughout a project’s life cycle. This integration ensures that all the elements of a project come
together at the right times to complete a project successfully. Project integration management involves
coordinating all elements of a project, including tasks, resources, stakeholders, and deliverables.
Hence, it is called Umbrella of rest of other knowledge area. Project integration management
activities is to develop, review, analyze and understand the scope of the project. It transform the
collected project information into a project management plan using a structure approach. It monitor
and measure the project progress. It take appropriate action to meet project objective.
1.Develop the project charter
The process of developing a document that formally authorizes the existence of a
project and provides the project manager with the authority to apply organizational
resources to project activities.

2. Development the project management plan

The process of defining, preparing, and coordinating all plan components and
consolidating them into an integrated project management plan.
3. Monitoring and controlling project work
The process of tracking, reviewing, and reporting overall progress to meet the
performance objectives defined in the project management plan.
4. Monitoring and controlling project work
The process of tracking, reviewing, and reporting overall progress to meet the
performance objectives defined in the project management plan.
5.Performing integrated change control
It involves identifying, evaluating, and managing changes throughout the project
life cycle. The process of reviewing all change requests; approving changes and
managing changes to deliverables, organizational process assets, project
documents, and the project management plan and communicating the decisions.

Example in Practice:
Scenario: Launching a New Product
• Scope Management defines the features of the product.
• Schedule Management plans the timeline for development, testing, and
marketing.
• Cost Management estimates and tracks the budget for materials, labor,
and marketing.
• Risk Management identifies risks like supplier delays or market
competition.
Through Integration Management, the project manager ensures:

• The approved product features (scope) align with the allocated budget
(cost).
• Changes in timeline due to delays are communicated and resolved.
• Risk mitigation plans are updated across relevant areas.
Without Integration Management, the project risks misalignment, inefficiencies,
and failure to meet overall objectives. so it acts as the umbrella that unites and
coordinates all knowledge areas for project success.

5. Why ongoing scope management is necessary? Illustrate a WBS for a project of e-

commerce site.
Ongoing scope management is essential in project management for several reasons. It ensures
that the project remains aligned with its objectives, maintains stakeholder satisfaction, and
effectively utilizes resources. Here are some reasons why ongoing scope management is
necessary:
1. Prevention of Scope Creep: Scope creep refers to the uncontrolled expansion of project scope
without adjustments to time, cost, and resources. Ongoing scope management helps identify and
control changes to the project scope, ensuring that any additions or modifications are properly
evaluated, documented, and approved.

2. Adapting to Changing Requirement: Stakeholder needs and external conditions may

change over the project lifecycle. Regular scope reviews ensure these changes are
documented, assessed, and integrated appropriately.
3. Stakeholder satisfaction: Regularly reviewing and managing the project scope allows for
better communication with stakeholders. It provides opportunities to gather feedback and
address concerns, ensuring that stakeholders' expectations are met throughout the project
lifecycle.
4. Risk Management: Changes in project scope can introduce new risks or exacerbate existing ones.
Ongoing scope management helps identify these risks early and allows for proactive risk management
strategies to be implemented.
5. Improved Change Control: Ongoing scope management facilitates a structured change control
process. It provides a framework for evaluating proposed changes, assessing their impact, and making
informed decisions about whether to proceed with them.
The WBS for a project of e-commerce site is shown below;