[L5][21/10/2025][S1 2025-26] SE440 Software Project Management

Change Requests in Project Management

Understanding Change Requests

• The discussion begins with an introduction to change requests, which are formal requests for modifications in a project. These can arise from various stakeholders, particularly customers.

• Change requests often involve adjustments to project requirements or scope, such as adding or removing features based on customer feedback.

Types of Change Requests

• The first category of change requests is those initiated by the customer, typically related to project requirements or staffing changes. For example, if a university (the customer) requires modifications to their system.

• Changes may also involve replacing team members if the customer is dissatisfied with current staff performance. This necessitates assessing the impact of such changes on project timelines and costs.

Impact Assessment

• Any modification can affect several aspects of the project:

• Cost: Additional expenses may arise due to new resources or extended timelines.

• Timeline: Adjustments could delay project completion.

• Quality: New components might require re-evaluation of quality standards and analyses.

Communication with Customers

• Transparency with customers is crucial when discussing potential impacts of requested changes. If a new component like a search engine increases resource demands, this should be communicated clearly.

• Agreements regarding changes can be informal (gentleman’s agreement) or formalized through contract amendments that document any alterations in scope or timeline.

Documentation and Formalization

• When customers request changes verbally (e.g., during meetings), it’s essential for project managers to document these discussions formally through notes or emails for accountability.

• Written documentation serves as protection for the project manager and ensures clarity about what was agreed upon regarding any modifications.

Handling Verbal Requests

• Even verbal requests must be treated seriously; documenting them helps maintain professionalism and clarity in communication with clients.

• After conducting an impact assessment on costs, quality, and timelines due to change requests, results should be communicated back to the customer formally via email or written reports.

Finalizing Amendments

• Once assessments are shared with customers, their approval is necessary before proceeding. This includes agreeing on additional costs and time extensions resulting from requested changes.

• A formal amendment document should outline all agreed-upon changes and their implications on existing contracts.

Managing Team Dynamics During Changes

• Project managers must navigate team dynamics carefully when issues arise during execution without alarming customers about potential problems discovered by team members.

• It’s important for managers to address internal issues discreetly while ensuring that the final product meets quality expectations without compromising client satisfaction.

Understanding Customer Communication and Change Requests

Importance of Customer Assurance

• It's crucial for customers to feel confident in the quality of work being delivered. Transparency is key, as any issues that arise should be communicated effectively without causing discomfort or distrust.

Types of Change Requests

• There are various types of change requests from customers, which can significantly impact project management.

Project Accountant's Role

• The project accountant acts as a gatekeeper, reviewing all expenses to ensure they align with the budget. They play a vital role in managing financial aspects when unexpected costs arise due to staff changes.

Budget Adjustments

• If new employees have higher salaries than those who left, it may strain the project's salary budget. This necessitates discussions about reallocating funds from other budget items to cover these increased costs.

Managing Change Requests Effectively

• The most significant type of change request comes from customers. Project managers must convince clients that certain changes could negatively affect the project's budget or system integrity.

Risk Management Strategies

Simplified Risk Classification

• Risks can be classified into three levels: low impact (minimal effect), moderate impact (harmful but not catastrophic), and high impact (severe consequences).

Example Scenario: Power Outage

• A power outage at a university can serve as an example of risk management. The impact varies based on the experience level of the instructor; seasoned instructors may adapt easily while novices might struggle without their presentation tools.

Proactive vs Reactive Planning

• Proactive planning involves preparing for potential risks before they occur, such as advising inexperienced instructors to bring backup materials like laptops for lectures in case of power failure.

Identifying Risks Early

• Recognizing risks ahead of time allows for effective planning and implementation strategies before issues arise, ensuring smoother operations during unforeseen events.

High Impact Risks in Medical Settings

• In medical facilities, risks like power outages can lead to severe consequences if critical equipment fails. Proactive measures such as installing backup generators are essential for safeguarding expensive medical supplies and procedures.

Project Management Approaches and Lean Principles

Overview of Project Management Phases

• The speaker introduces a method for risk management, summarizing the remaining slides with a chart that outlines key project management approaches.

• The five phases of project management are detailed: Initiation, Planning, Execution, Monitoring & Control, and Closure. Each phase must be followed sequentially without skipping any steps.

Lean Project Management Concepts

• Lean principles in project management emphasize efficiency; for example, reusing resources can reduce costs while maintaining quality.

• A case study is presented where refurbished computers are offered to customers at a lower price point than new ones, demonstrating how lean practices can enhance competitiveness.

Software Development and Agile Methodologies

• The concept of reusing software components from previous projects is discussed as a way to accelerate development timelines and save costs.

• Agile methodologies like iterative and incremental development allow for early deployment of components (e.g., student application systems), enabling immediate use rather than waiting for full project completion.

Planning Challenges in Project Management

• The importance of integrating each component during delivery is highlighted; successful integration ensures that all parts work together effectively.

• Constraints such as resource availability must be considered when planning projects. For instance, if subcontractors are only available at specific times, this affects the overall schedule.

Traditional vs. Modern Approaches in Project Management

• Traditional methods focus on product output; defining what products need to be produced helps establish production lines and plans accordingly.

• Standards like ISO 21500 provide frameworks for managing project phases effectively. Understanding these standards is crucial for modern project managers.

Success Factors in Project Management

• Key success factors include customer satisfaction and stakeholder involvement throughout the project's lifecycle. Engaging users as partners enhances outcomes.

• Competence of the project manager is essential; their expertise directly influences project success rates.

Evolution of Project Management Practices

• Historical context shows that earlier project management relied heavily on individual manager styles. Formal training has become necessary to standardize practices across the industry.

Defining De Facto Standards

Understanding De Facto Standards

• The speaker discusses reaching a consensus on a concept referred to as "de facto," which implies an agreement among a large group of individuals.

• After gaining confidence in the de facto standard, the speaker plans to elevate it to ISO (International Organization for Standardization) for formal recognition.

• The discussion includes the potential involvement of project managers who may be asked to utilize this standard, allowing for ongoing feedback and improvements.

• The aim is to refine the standard until it reaches a satisfactory level of quality, ultimately leading to its official establishment with a number and release date.