[L16][07/12/2025][S1 2025-26] SE440 Software Project Management

Agile Overview and Methodologies

Introduction to Agile Principles

• The discussion begins with an overview of Agile methodologies, emphasizing the Agile Manifesto and its main principles.

• Scrum is highlighted as a prominent Agile methodology, alongside others like Kanban, Lean, Crystal Method, and Extreme Programming.

Project Management Constraints

• The speaker discusses project management constraints such as time limitations set by customers, which can lead to conflicts between estimated timelines and customer expectations.

• Emphasizes the need for flexibility in Agile to accommodate rapid changes and prioritize tasks effectively.

Cost Considerations

• Customers often have high expectations regarding system performance while being constrained by budget limits; this creates challenges in meeting requirements within financial boundaries.

• Scope definition is crucial; it drives requirements gathering and helps manage customer expectations regarding deliverables.

Resource Requirements

• Discusses the importance of having experienced team members (minimum 10 years of experience recommended), particularly for Scrum projects.

• Highlights potential resource shortages that may necessitate hiring external talent at higher costs due to additional logistical considerations.

System Development Challenges

Institutional Constraints

• When developing systems for institutions (e.g., universities), adherence to existing regulations is critical; any new system must align with institutional policies.

Integration Needs

• Stresses the necessity for coherence between new systems and existing platforms (e.g., student services), ensuring seamless integration across various functionalities.

Scrum Project Initiation

Role of Product Owner

• Introduces the role of the Product Owner in Scrum projects, who gathers requirements from stakeholders including customers and investors.

Requirement Gathering Process

• The process involves collecting user stories from stakeholders to understand their needs better. This leads to creating a vision statement based on gathered insights.

Prioritization Techniques

• After stakeholder meetings, the Product Owner organizes user stories into a prioritized product backlog, determining release sequences based on estimated completion times for each story.

This structured approach ensures clarity in project goals while allowing flexibility in execution.

User Story and Sprint Planning in Scrum

Understanding User Stories

• The concept of large user stories is introduced, emphasizing the need to break them down into smaller, manageable tasks to reduce execution time.

• The role of the Product Owner is highlighted as crucial for preparing the stage for Scrum teams, ensuring clarity in requirements and user stories.

Sprint Structure and Duration

• Sprints are defined within a timeframe of one to six weeks, with four weeks being the typical recommendation based on experience.

• Each sprint should have a fixed duration agreed upon at the project's start; flexibility in sprint length can lead to inconsistencies.

Prioritization and Backlog Management

• User stories are prioritized based on various factors such as impact, associated risks, and dependencies. This prioritization influences which stories are tackled first.

• The Sprint Backlog is created from prioritized user stories; only those with the highest priority are selected for implementation during a sprint.

Implementation Process

• Development begins with delivering outputs from each user story sequentially. Internal deliverables may not be customer-facing initially but must be completed before moving forward.

• Daily stand-up meetings (15 minutes long) facilitate team communication about progress and obstacles encountered during development.

Review and Retrospective Phases

• After completing a sprint, a Sprint Review Meeting occurs where deliverables are assessed by the Scrum Team alongside stakeholders to ensure acceptance criteria are met.

• Following delivery, a Retrospective Meeting allows teams to reflect on lessons learned from customer feedback and adjust priorities for future sprints accordingly.

Continuous Improvement Cycle

• Adjustments in prioritization may occur based on retrospective insights; this iterative process ensures that subsequent sprints align better with stakeholder expectations.

• Each completed sprint contributes incrementally towards project goals while maintaining an ongoing delivery model that adapts based on feedback received throughout development cycles.

Final Project Reflection

• A final Project Retrospective Meeting assesses overall project learnings aimed at benefiting future projects by documenting experiences gained during execution.

Project Management Insights

Project Initiation and Planning

• The speaker discusses the unique nature of project phases, emphasizing that they are interwoven rather than sequential as in traditional project management. Initial steps include gathering business cases and writing a project vision statement.

• User stories were documented based on stakeholder discussions, marking the first phase of initiation. This phase is crucial for establishing a clear understanding of project requirements.

• Planning occurs once at the beginning, focusing on creating product backlogs and release schedules, which can be adjusted later but are foundational to the project's structure.

Execution and Review Processes

• The execution process involves continuous planning with each sprint, including development execution and delivery reviews. After all sprints conclude, a closure review is conducted to assess overall performance.

• The speaker highlights the importance of certified Scrum managers in clarifying processes that may seem ambiguous due to their interconnected nature across multiple phases.

Transparency in Agile Processes

• Empirical process control relies on three key elements: transparency, inspection, and adaptation. These principles guide how teams manage new code integration within existing systems.

• Transparency is vital during daily stand-ups and review meetings; it ensures that all team members have access to relevant information displayed on boards like Scrum boards.

Process Association and Feedback Loops

• The discussion transitions into associated processes that impact transparency. Frequent feedback loops are essential for maintaining clarity throughout inspections and adaptations within projects.

• Inspections must be transparent so everyone understands details; this includes displaying results clearly through tools like Scrum boards to facilitate effective communication among team members.

Risk Management Strategies

• Risk identification is critical; teams need strategies for managing risks effectively throughout the project lifecycle while ensuring proactive responses are planned ahead of time.

• Self-organizing teams should not rely solely on others for task completion; individuals must take initiative in their responsibilities without waiting for direction from others.

Collaboration and Knowledge Sharing

• Cross-functional collaboration among team members enhances understanding of project vision statements. Continuous knowledge upgrades are necessary for personal growth within agile frameworks.

• Awareness among team members about contract details fosters better collaboration; everyone should understand their roles concerning project objectives to ensure alignment with goals.

Prioritization Techniques in Agile Framework

• Prioritization involves assessing dependencies between user stories; those dependent on others must be sequenced accordingly to avoid bottlenecks during development cycles.

• Risks associated with user stories influence prioritization decisions—stories with lower risk should be prioritized higher to maintain momentum without encountering significant obstacles during implementation.

Overview of Scrum Roles and Processes

Introduction to Stakeholder Engagement

• The initial phase involves engaging with stakeholders without a strict time box, allowing flexibility in discussions that can range from an hour to a month. This is crucial for developing a vision statement and understanding user stories before prioritization.

Understanding Scrum Team Structure

• In Scrum, traditional roles like Project Manager or Developer are replaced by Product Owner and Scrum Master. The team members are expected to be versatile, capable of handling development, planning, testing, and quality assurance tasks.

• Team members are referred to as "Scrum Team Members" rather than developers or QA specialists, emphasizing their multifaceted roles within the project.

Key Roles in Scrum Projects

• The project includes various roles such as customers (project owners), sponsors (funding the project), and advisors/consultants (SGP). These roles contribute significantly to the project's success.

• In larger projects requiring multiple teams, each Scrum team should not exceed nine members. If more members are needed, additional teams must be formed while maintaining this limit.

Managing Multiple Teams

• For example, if a project has 30 members needing division into smaller teams, it could result in four separate Scrum teams. Each team would have its own Product Owner and Scrum Master.

• When managing multiple Scrums within one project, each Sprint is treated as an individual project. Coordination becomes essential among different Product Owners and Scrum Masters across these teams.

Chief Roles in Large Projects

• In scenarios where there are multiple teams (e.g., four), a Chief Product Owner coordinates between them while ensuring alignment on goals and processes.

• Chief roles become optional when team sizes remain below nine; however, they become necessary for larger groups to maintain effective communication and coordination.

Roles of Product Owner

Responsibilities of the Product Owner

• The primary role of the Product Owner includes creating the project vision and identifying key stakeholders involved in the process.

• They also oversee user story creation which serves as foundational narratives for what needs to be accomplished within the project scope.

User Stories Development Process

• User stories help articulate customer expectations regarding features that will ultimately define success for the product being developed.

• Additionally, they play a dual role by serving both as promotional material for stakeholders and as assessment criteria during evaluations of progress or outcomes.

Role of Scrum Master

Functionality of the Scrum Master Role

• The Scrum Master acts similarly to a Project Manager but focuses on facilitating communication between the Product Owner and the development team.

• Their responsibility includes resolving issues faced by team members—whether technical challenges or resource access—ensuring smooth workflow throughout sprints.

This structured approach highlights key concepts related to stakeholder engagement, team dynamics within scrum frameworks, responsibilities associated with product ownership, and facilitation provided by scrum masters—all critical components for successful agile project management.