[L15][02/12/2025][S1 2025-26] SE440 Software Project Management

Introduction to Chapter 5

Overview of Agile and Scrum

• The session begins with an introduction to Chapter 5, the final chapter in the course, which will cover Agile methodologies, specifically focusing on Scrum project management.

• The speaker mentions that slides for this chapter will be uploaded soon, as they are currently undergoing minor adjustments.

Understanding Agile Methodology

• Agile is described as a flexible approach that emphasizes planning and defining requirements before execution. This flexibility allows teams to adapt to changes efficiently.

• The process involves breaking down work into smaller components or user stories, prioritizing them based on importance, and managing them through sprints.

Sprint Management

Components of Sprint Execution

• Each sprint is treated as an independent project with specific outputs contributing to the overall product or software system being developed.

• Decomposition of problems into smaller issues allows for better management and response strategies at various levels of complexity.

Importance of Iteration

• Emphasizes iterative work processes where each component is linked together progressively. This method enhances adaptability but may lead to non-standardized architecture or design outcomes.

Agile Principles and Manifesto

Historical Context

• The speaker discusses the emergence of Agile methodologies around 2001 with the introduction of the Agile Manifesto, which outlines core principles distinguishing it from traditional methods.

Key Principles

• Collaboration between team members and customers is crucial; customer involvement should start early in projects rather than waiting until completion.

• Incremental delivery is highlighted as a significant aspect where components are delivered upon completion rather than waiting for full project completion.

Collaboration and Communication

Customer Interaction

• Continuous collaboration with customers ensures their needs are met throughout development. Feedback loops help address issues promptly during the process.

Team Dynamics

• Effective communication within teams is essential; face-to-face interactions are preferred for discussions to enhance understanding and collaboration among team members.

Tools and Techniques in Agile

Focus on Individuals Over Tools

• Emphasizes that successful planning relies more on individuals' collaboration than merely on tools or processes used in project management.

Visual Management Tools

• Various tools like Kanban boards facilitate tracking progress visually. These tools help manage tasks effectively by providing clear visibility into project status.

Conclusion: Measuring Success in Projects

Project Evaluation Metrics

• Success can be measured by how many deliverables are completed successfully over time. Regular updates keep stakeholders informed about progress.

This structured overview captures key insights from the transcript while maintaining clarity and organization for effective study purposes.

Lean Project Management and Methodologies

Introduction to Lean Campan

• The concept of Lean Campan is introduced, emphasizing its similarity to traditional campan methods but with a focus on waste reduction and resource recycling in project planning.

Crystal Methods Overview

• Crystal methods have been utilized since the late 1990s, particularly for analysis in projects. The speaker recalls supervising a PhD student who employed these methods.

Importance of DSDM (Dynamic Systems Development Method)

• The speaker stresses that no project can succeed without adhering to certain methodologies, indicating that failure is inevitable without them.

Customer Expectations and Deliverables

• Discusses the importance of managing customer expectations regarding deliverables, including what must be provided versus optional features.

Traditional Methodologies and Project Phases

• Traditional methodologies consist of phases such as initiation, planning, execution, control, and closure. Each phase is crucial for project success.

Pre-project Phase Insights

• Emphasizes the significance of pre-project phases which include requirement gathering and foundational work necessary before contract signing.

Deployment and Benefits Assessment

• After system development comes deployment followed by benefits assessment to evaluate the advantages gained from the project.

Agile Methodologies: Extreme Programming

Feature Driven Development

• Introduces Feature Driven Development where services are outlined first; each feature is developed individually before integration into a complete system.

Test Driven Development Approach

• In Test Driven Development (TDD), testing occurs at every stage; if tests fail, developers return to previous stages until issues are resolved.

Adaptive Software Development Models

Unified Process Model

• Discusses the Unified Process model (UP), which adapts based on circumstances faced during software development projects.

Domain Driven Design Considerations

Business Domain Impact on Design Decisions

• Highlights how design decisions should align with business domain requirements; examples include choosing between cloud-based or in-house hosting based on data sensitivity.

Scrum Implementation Scenario

Stakeholder Engagement in Scrum Projects

• Describes an example scenario where stakeholders provide input for developing a hospital management software system using Scrum methodology. Engaging stakeholders ensures their needs are documented effectively.

User Story and Stakeholder Engagement

Understanding User Stories

• The concept of user stories is introduced, emphasizing that stakeholders may provide multiple stories, each recorded as a separate user story.

• A project business case document is created by the customer, outlining the system's general requirements. This document is crucial for understanding stakeholder needs.

Roles in Scrum

• Key roles in Scrum are identified: Product Owner (responsible for documenting requirements), Scrum Master (facilitates the process), and Scrum Team members.

• The Product Owner creates a vision statement and documents user stories, which are prioritized in a product backlog.

Prioritization of User Stories

• Prioritization factors include impact on the system, associated risks, and dependencies between user stories. Higher impact increases priority.

• Risks associated with user stories affect their prioritization; lower risk leads to higher priority placement.

Creating a Release Plan

• After preparing the product backlog, the Product Owner schedules releases based on estimated completion times for each user story.

• An initial schedule is established to determine which user stories will be addressed first during sprints.

Sprint Planning and Execution

Sprint Planning Process

• The team prepares for execution by estimating time required for each user story. Each story's complexity can vary significantly.

• The sprint planning meeting involves collaboration among team members to review prioritized backlogs and select appropriate user stories for implementation.

Timeboxing Sprints

• Sprints are typically timeboxed from one to six weeks; four weeks is common in practice. This structure helps manage workload effectively.

• During sprint planning, teams assess how many user stories can fit within the designated sprint timeframe based on their estimates.

Daily Stand-Up Meetings

• Daily stand-up meetings facilitate communication among team members about progress, challenges faced, and assistance needed. These meetings last approximately 15 minutes.

Sprint Review Meeting Objectives

Purpose of Sprint Review

• The Sprint Review meeting aims for the team to discuss with the Product Owner whether they have completed the required tasks. The Product Owner is responsible for confirming if deliverables are ready for acceptance.

• Stakeholders may also review deliverables, allowing them to accept some while rejecting others based on readiness.

Acceptance of Deliverables

• It is not mandatory for all deliverables to be accepted; stakeholders can approve three out of four, indicating flexibility in the acceptance process.

• Accepted deliverables may require further work, leading the team to engage with customers for additional development.

Feedback and Retrospective Process

Gathering Feedback

• After customer engagement, a Sprint Retrospective meeting occurs where feedback is collected from the team regarding each deliverable's performance.

• This feedback helps identify areas needing improvement or adjustments based on customer satisfaction.

Prioritizing Product Backlog

• Following feedback, there’s a grooming process where product backlog items are prioritized based on customer needs and urgency.

• Adjustments made during this phase ensure that high-impact items receive attention first.

Iterative Development Cycle

Moving to Next Sprints

• Once a sprint concludes, teams prepare for subsequent sprints by selecting new user stories to work on in an iterative manner.

• Each sprint involves developing new features while integrating previous work and conducting reviews and retrospectives regularly.

Completion of Project Lifecycle

• Upon project completion, a final retrospective assesses lessons learned to inform future projects. Documentation of these insights is crucial for ongoing improvement.

Project Management Insights

Questions and Clarifications

• The speaker invites questions about project management processes before transitioning into more detailed discussions about methodologies used in Scrum.

Iterative Nature of Scrum

• Emphasizes that Scrum operates through iterations at both sprint levels and daily meetings aimed at continuous improvement and adaptation.

Challenges in Current Methodologies

Identifying Weaknesses

• Discusses two main weaknesses within current methodologies: handling requirements effectively and having weak processes that require experienced personnel to succeed.

Proposed Methodology Improvements

• Suggesting enhancements by injecting software requirement classifications into Scrum practices while restructuring processes for better agility.

Final Thoughts on Agile Practices

Benefits of New Methodology

• Highlights how new methodologies support junior members by providing structured processes that facilitate success compared to traditional frameworks lacking such guidance.

Addressing Requirements Effectively

• Stresses the importance of treating software projects according to established classifications which enhance overall project management effectiveness.

Conclusion: Lessons Learned from Projects

Acknowledging Framework Limitations

• Recognizes limitations within existing frameworks while advocating for improvements rather than outright criticism.

Importance of Continuous Learning

• Concludes with an emphasis on learning from past experiences as essential for refining future project management strategies.

Sprint Retrospective Meetings and Project Management

Overview of Sprint Retrospectives

• The speaker discusses the importance of sprint retrospective meetings, noting that they occur at the end of each sprint. They mention having conducted 10 retrospectives to date.

• Emphasizes that a project retrospective meeting is held only after completing the entire project, highlighting its significance in evaluating overall performance.

Calculation of Project Duration

• The speaker outlines a calculation for project duration based on sprints, stating that with 10 sprints lasting four weeks each, the total project time would be 40 weeks.

• Breaks down workdays: if there are five working days per week over 40 weeks, this results in a total of 200 working days required for the project.

Daily Stand-Up Meetings

• Discusses the necessity of daily stand-up meetings during each workday, indicating these meetings last approximately 15 minutes.

• Concludes that with 200 working days and two stand-up meetings per day, careful calculations are essential for effective project management.

Roles in Project Management

• Clarifies roles within the team structure; specifically mentions not having a title such as "Project Manager" but rather referring to a "Project Owner."

• Suggests that understanding roles is crucial for maintaining structured communication and accountability throughout the project's lifecycle.