[L17][09/12/2025][S1 2025-26] SE440 Software Project Management

Understanding the Scrum Team Dynamics

Overview of Scrum Team Responsibilities

• The Scrum team is responsible for executing actual work, starting from the selection of user stories from the product backlog for each sprint. They plan the sprint and create deliverables to implement it.

• After completing a sprint, they conduct a review with the Product Owner before deployment to customers, followed by a retrospective meeting to discuss lessons learned.

Key Roles in Scrum

• The Product Owner defines project priorities and context, while the Scrum Master plays a crucial role in facilitating processes within the team. This includes assisting in writing user stories and conducting release planning sessions.

• Team members contribute significantly by helping refine user stories and providing estimations that are ultimately approved by the Product Owner. They also create tasks based on these stories.

Prioritization Challenges

• Customer feedback may necessitate re-prioritizing items in the product backlog, especially when customers believe certain features are more critical than others listed lower down. This requires careful management of priorities within the backlog.

• In larger projects where multiple teams are involved (more than nine), coordination becomes essential as dependencies between user stories can lead to delays if not managed properly. Each team must be aware of how their work impacts others.

Managing Multiple Scrum Teams

Structuring Large Projects

• When dealing with large projects requiring many team members (e.g., 30), it's necessary to divide them into smaller groups or "Scrums" for effective management, ensuring no single Scrum exceeds nine members per team for optimal performance.

• Each subgroup operates independently but feeds into a central product backlog that remains unchanged across all teams, allowing parallel sprints without confusion over dependencies among user stories from different teams.

Planning Complexity

• Effective planning becomes increasingly complex with multiple Scrums; thus, professionals need to be meticulous about managing dependencies and ensuring smooth collaboration across teams during project execution phases.

• The speaker emphasizes that transitioning from single-Scrum models to multi-Scrum frameworks requires significant effort due to increased complexity in modeling processes and inter-team communication challenges.

Organizational Hierarchy in Large Scale Scrum

Coordination Among Teams

• In large-scale projects involving numerous teams (up to nine), each having its own Product Owner and Scrum Master, coordination is vital for maintaining workflow efficiency across all levels of operation within an organization’s structure.

• A hierarchical model is proposed where Chief Product Owners oversee clusters of three teams each, preventing any one individual from being overwhelmed by too many direct reports while enhancing organizational clarity and focus on objectives at various levels of management.( t = 612 s )

Flexibility in Structure

• The hierarchy allows flexibility; organizations can adapt their structures based on project size and complexity while distributing workload effectively among leaders rather than concentrating authority excessively at higher levels.( t = 699 s )

Scrum Team Dynamics and Roles

Overview of Scrum Team Structure

• The final level in the Scrum hierarchy is referred to as "Chief of Chiefs" for product owners, while maintaining the same team size.

• A shared product backlog approach can simplify project management by allowing teams to pull user stories independently from a common backlog.

Team Collaboration and Responsibilities

• During Scrum meetings, each team member discusses their work progress since the last meeting and outlines tasks for the upcoming week.

• Teams are encouraged to identify obstacles they face, enabling other teams to provide assistance when necessary.

Portfolio Management in Scrum

• The concept of a portfolio in Scrum includes various roles such as Portfolio Product Owner and Program Scrum Master, emphasizing structured layers within projects.

• Different roles at the project level include Chief Product Owner, Scrum Masters, and stakeholders who contribute to overall project success.

Team Formation Techniques

Methods for Building Effective Teams

• Various methods exist for forming teams; one approach involves categorizing potential members into circles based on familiarity or recommendations.

• The "forming-storming-norming-performing" model describes stages of team development where initial brainstorming leads to selecting suitable members.

Adjusting Team Composition

• If issues arise during execution due to poor member selection, revisiting earlier stages (storming/norming) may help find replacements from previously identified candidates.

Conflict Management Strategies

Addressing Conflicts Within Teams

• Conflict management is crucial in Agile environments; it’s important to resolve disagreements without escalating tensions among team members.

• Employing a win-win conflict resolution strategy ensures that both parties feel satisfied with outcomes rather than feeling like they lost something.

Conflict Resolution and Leadership Styles

Understanding Conflict Scenarios

• The speaker discusses situations where one party feels defeated, suggesting a willingness to concede for the sake of progress. This reflects a common dynamic in conflict resolution.

• Emphasizes the importance of convincing the opposing party of their mistakes, highlighting four methods to address conflicts effectively.

Leadership Styles Overview

• Recaps various leadership styles previously discussed: autocratic, bureaucratic, democratic, and charismatic.

• Introduces "servant leadership" as a key concept in Scrum methodology, emphasizing the leader's role in serving and supporting their team.

Delegation and Team Empowerment

• Discusses delegation within leadership roles; leaders should empower team members to take responsibility while maintaining oversight.

• Highlights the significance of coaching in sports management as a parallel to effective leadership practices.

Business Justification in Scrum

• Stresses that every action must be justified within business contexts, indicating that justification is crucial for decision-making processes.

• Mentions quality requirements (functional vs. non-functional), underscoring their importance in project management discussions.

Change Management Essentials

• Addresses change management as an essential aspect of Scrum, noting that teams must adapt while considering impacts on finance and deliverables.

• Explains how change requests can affect timelines and specifications, necessitating careful evaluation before approval.

User Story Impact Assessment

• Provides an example involving multiple change requests affecting user stories; highlights the need for thorough analysis when assessing impacts on projects.

• Discusses how changes can influence various user stories differently, stressing the importance of tracking these relationships accurately.

Risk Management Framework

• Introduces risk identification and assessment within Scrum methodologies; emphasizes communication about risks among stakeholders.

• Concludes with insights into managing risks at different levels (portfolio vs. program), reinforcing the necessity for structured approaches to risk management.