Scribd
Upload
31 views14 pages

Requirements Management, Change Management Policies & Procedures

Requirements management is the systematic process of gathering, documenting, organizing, and controlling requirements throughout the software development lifecycle. It involves identifying, analyzing, prioritizing, validating, and tracing requirements to ensure that a project delivers a product that meets stakeholder needs. Effective requirements management includes requirements identification, analysis, prioritization, traceability, change management, and validation. Change management refers to identifying, evaluating, and controlling changes to project requirements, scope, or objectives. It typically involves assessing impact, evaluating proposed changes, making approval decisions, implementing changes, and controlling changes throughout the project. Change management policies and procedures provide frameworks for decision making and structured processes for requesting, evaluating, and implementing changes.

Uploaded by

Umar Umar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
31 views14 pages

Requirements Management, Change Management Policies & Procedures

Requirements management is the systematic process of gathering, documenting, organizing, and controlling requirements throughout the software development lifecycle. It involves identifying, analyzing, prioritizing, validating, and tracing requirements to ensure that a project delivers a product that meets stakeholder needs. Effective requirements management includes requirements identification, analysis, prioritization, traceability, change management, and validation. Change management refers to identifying, evaluating, and controlling changes to project requirements, scope, or objectives. It typically involves assessing impact, evaluating proposed changes, making approval decisions, implementing changes, and controlling changes throughout the project. Change management policies and procedures provide frameworks for decision making and structured processes for requesting, evaluating, and implementing changes.

Uploaded by

Umar Umar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 14

Requirements Management,

Change Management Policies & Procedures

Engr. Syed Muhammad Ali Imran


Lecture 17 & 18
Department of CS&IT, Superior University Sargodha Campus
Requirements Management
What requirement management is?

Requirements management is the systematic process of gathering, documenting,


organizing, and controlling requirements throughout the software development
lifecycle.

It involves the identification, analysis, prioritization, validation, and


traceability of requirements to ensure that a project delivers a product that meets
stakeholder needs and expectations.
Requirements Management
Requirements Management
Effective requirements management includes the following key activities:

1.Requirements Identification
2.Requirements Analysis
3.Requirements Prioritization
4.Requirements Traceability
5.Change Management
6.Requirements Validation
Stable Requirements
 Stable requirements are those that remain relatively unchanged over
the progression of a project.
 These are typically well-understood, thoroughly documented, and
have minimal ambiguity.
 Stable requirements are the foundation for project planning and
implementation.
Volatile Requirements
 Volatile requirements are those that are subject to frequent changes
or updates.
 They often result from evolving stakeholder needs, market
dynamics, or a lack of initial clarity.
 Managing volatile requirements is a significant challenge in
software development as they can lead to project delays and increased
costs.
Change Management
Change management in software development refers to the process
of identifying, evaluating, and controlling changes to project
requirements, scope, or objectives.

It involves assessing the impact of proposed changes and making


informed decisions about their implementation.
Change Management - I
Change management typically includes the following steps:

1. Change Request: A change request is initiated when stakeholders


identify a need to modify requirements. This request is documented and
submitted for review.

2. Change Impact Analysis: The project team assesses the potential


impact of the proposed change on the project's scope, schedule, cost, and
quality.

3. Change Evaluation: The change request is evaluated based on criteria


such as the value it adds, its feasibility, and its alignment with project
goals.
Change Management - II
Change management typically includes the following steps:

4. Decision Making: The project team, often with the involvement of


key stakeholders, decides whether to approve, reject, or defer the
change.

5. Change Implementation: If approved, the change is incorporated


into the project plan, and appropriate updates are made to requirements,
design, and testing documentation.

6. Change Control: Throughout the project, change control


mechanisms are used to manage and track changes, ensuring they are
properly documented, reviewed, and communicated to stakeholders.
Change Management Policies
Several methods can help prevent errors in requirements:

Change Management Policies


 These are high-level, strategic guidelines like principles of
prioritizing changes, roles, and responsibilities that define how
changes are to be managed across the organization.
 They provide a framework for decision-making and set the overall
direction for change management practices.
Change Management Procedures
Several methods can help prevent errors in requirements:

Change Management Procedures


 Procedures are detailed step-by-step instructions that specify how to
execute the activities related to change management.
 They provide a structured process for requesting, evaluating, and
implementing changes.
Requirements Challenges
As a Business Analyst, there are several challenges that you may face
while gathering requirements from stakeholders. Some of these
challenges include;
 Communication barriers
 Conflicting requirements
 Lack of stakeholder engagement
 Changing requirements
 Managing expectations
THANK YOU
ANY QUERY OF QUESTION?

You might also like