[L19][16/12/2025][S1 2025-26] SE440 Software Project Management

Understanding the Scrum Process

Overview of Phases and Processes

• The lecture discusses the final phase of a project, highlighting that there are 8 processes remaining after previous phases have been completed.

• Emphasis is placed on three critical processes: Implementation Phase, Creation, and Delivery. These are essential for producing deliverables during each sprint.

User Stories and Deliverables

• Each sprint includes a set of user stories, with each story expected to yield specific deliverables. Some user stories may serve as inputs for others.

• The planning stage involves selecting high-priority user stories from the product backlog to include in the current sprint based on its capacity.

Sprint Backlog and Scrum Board

• The Sprint Backlog is created by taking top priority user stories and placing them into the current sprint's workload.

• A Scrum Board is utilized for transparency, allowing team members and stakeholders to track project status without interrupting the team.

Release Planning and Dependencies

• Release planning is crucial for determining when to implement each user story based on dependencies; for example, one story may depend on another being completed first.

• Recommendations from Scrum guidelines help teams navigate dependencies effectively throughout the project lifecycle.

Daily Stand-ups and Review Processes

• Daily stand-up meetings facilitate communication among team members about progress and obstacles encountered during implementation.

• At the end of each sprint, a review process occurs where deliverables are assessed before implementation at customer sites.

Coordination Among Multiple Scrum Teams

Managing Multiple Teams

• When projects require more than nine members, multiple Scrum teams are formed. Each team has its own Scrum Master and Product Owner to ensure effective coordination.

• Coordination between different teams is managed through established processes that facilitate collaboration while maintaining focus on individual team goals.

Review and Retrospective in Scrum

Overview of the Review Process

• The review process involves delivering completed deliverables for approval, where a team conducts a demonstration for the Product Owner to ensure everything is satisfactory.

• After approval, the deliverables are prepared for deployment to the customer. Feedback from customers is gathered during sprint retrospectives to learn and improve future sprints.

Sprint Retrospective Insights

• Each sprint goes through various phases, with most phases being iterative except for the initial setup phase, which is not revisited.

• The release phase occurs at the end of each sprint, emphasizing that releases are continuous rather than one-time events; deliverables are handed over as they are completed.

Deployment and Learning from Challenges

• Deliverables undergo deployment at the customer site through a defined process. A final project retrospective meeting addresses challenges faced throughout the project lifecycle.

• Lessons learned from past projects are documented to benefit future projects, ensuring continuous improvement based on previous experiences.

Planning and Prioritization in Sprints

• During planning meetings, high-priority user stories are selected from the product backlog. This stage is crucial for determining what will be developed next.

• After development and testing phases, deployments occur followed by sprint retrospectives to assess progress before moving on to subsequent sprints.

User Story Management

• Stakeholder meetings focus on reviewing business cases and documentation necessary for creating a project vision statement.

• User stories must be prioritized based on their impact; higher-impact stories should be executed earlier while dependencies and risks dictate sequencing.

Release Planning Coordination

• The Product Owner collaborates closely with stakeholders to create a release schedule that outlines how many user stories will be delivered in each sprint.

• Upon completion of an initial sprint, reviews lead to adjustments in the product backlog based on feedback received during deployment.

Summary of Processes in Scrum

• The presentation illustrates that each sprint functions like its own mini-project within an overarching framework aimed at completing all user stories effectively.

• Various processes such as planning, implementation, review, and release highlight how Scrum integrates multiple stages into a cohesive workflow.

Comparison Between Scrum and Traditional Methods

• In contrast with traditional methods where comprehensive documentation is required upfront, Scrum emphasizes minimal essential documentation focused on immediate needs while allowing flexibility throughout development.

Quality Assurance and Project Management

Understanding Quality Assurance in Traditional Models

• The discussion begins with the concept of quality assurance, emphasizing its dependence on customer needs and processes within traditional project management frameworks.

• It highlights that quality organization is crucial when assessing projects, particularly in traditional settings where roles are clearly defined.

• The speaker contrasts decentralized management styles with centralized ones, noting that in a decentralized model, project managers have more autonomy over their tasks.

• Changes requested by customers can significantly impact project outcomes, necessitating updates to deliverables based on feedback.

Upcoming Assignments and Expectations

• The session concludes with an overview of upcoming assignments (Assignment 1 and Assignment 2), indicating that detailed discussions will occur in the following week.

• Students are reminded about submission deadlines for these assignments, reinforcing the importance of timely completion.