🎯 Objective: Compare and contrast Scrum, Kanban, and Extreme Programming (XP) to determine the ideal approach for diverse project scenarios. 🧩 Scenario: Your team must select an Agile methodology for an upcoming project. Your challenge is to identify the most suitable framework. Form Teams Create small groups, each focusing on one Agile framework (Scrum, Kanban, or XP) Analyze Framework Document key characteristics, structure, planning approach, and core focus areas Present & Debate Share findings and engage in framework selection debates using real-world scenarios 🧠 Key Concepts: Scrum Time-boxed sprints, defined roles (PO, SM, Dev), structured ceremonies, prioritized backlog Kanban Workflow visualization, work-in-progress limits, continuous delivery model XP Technical excellence, pair programming, test-driven development, frequent releases

🎯 Objective: Develop and strategically prioritize a Product Backlog using proven industry techniques. 🧩 Scenario: You're stepping into the role of Product Owner for a new mobile application (such as a recipe sharing platform or local events discovery app). Phase 1: Feature Brainstorming (15 min) In teams of 3-4, generate a comprehensive list of potential features using sticky notes. Aim for at least 15 distinct features. Phase 2: User Story Creation (20 min) Craft compelling user stories for your top 10 features (e.g., "As a home cook, I want to filter recipes by available ingredients so that I can prepare meals without shopping"). Phase 3: Prioritization Exercise (25 min) Apply the MoSCoW methodology or RICE framework to establish clear priorities. Create a visual grid on your workspace and place each story in its appropriate category. 📝 Final Deliverables: A strategically prioritized product backlog with at least 10 well-crafted user stories Detailed acceptance criteria for your top 3 highest-priority items A concise 2-minute presentation justifying your prioritization decisions Completion of a "stakeholder negotiation" role-play with another team 🧠 Key Concepts: Compelling User Story Creation Strategic Backlog Refinement Prioritization Frameworks: MoSCoW / RICE / Value-Risk Analysis Testable Acceptance Criteria

🎯 Objective: Conduct a realistic Sprint Planning session by establishing compelling goals, selecting strategic backlog items, and accurately estimating work. 🧩 Scenario: Your team is preparing to launch a new sprint using the prioritized backlog you created in Exercise 2. Team Formation & Goal Setting Form groups of 4-5 people and craft a compelling Sprint Goal that directly aligns with your product objectives. Critical question: How will this goal deliver tangible value to your users? Backlog Selection & Estimation Strategically select items from your backlog considering: Your 2-week sprint timeframe Realistic team capacity Critical technical dependencies Use Planning Poker cards to estimate story points following the Fibonacci sequence. Task Breakdown & Commitment Decompose selected stories into specific, actionable implementation tasks. Create a clear physical/digital sprint board with your finalized sprint backlog. Make your team's sprint commitment and prepare a focused 2-minute presentation. ⏱️ Timeboxed Activities 10 minutes: Team formation & goal setting 15 minutes: Backlog selection & estimation 15 minutes: Task breakdown & commitment 10 minutes: Team presentations Materials Provided: Planning Poker card decks Sprint backlog templates Sample user stories Team capacity worksheet 🧠 Key Concepts: Strategic Sprint Planning Value-Driven Sprint Goals Accurate Relative Story Point Estimation Consensus-Driven Planning Poker Realistic Team Commitments

🎯 Objective: Perfect the art of running focused, time-boxed daily stand-ups that maximize team alignment and rapidly surface impediments. 🧩 Scenario: You're midway through the sprint planned in Exercise 3, and your team gathers for its essential daily synchronization. Preparation Phase 1. Assign key roles: Scrum Master, Developer A, Developer B, and Product Owner 2. Each participant receives a scenario card with specific updates and strategic blockers 3. Set up a prominent 15-minute timer for strict accountability Stand-Up Execution Each team member concisely addresses: ✅ What specific tasks did I complete yesterday that advanced our sprint goal? 🚀 What will I accomplish today to maintain our momentum? 🧱 What obstacles are currently blocking my progress? Evaluation & Reflection 1. Did the meeting conclude within the strict 15-minute timeframe? 2. Were all blockers properly identified but appropriately deferred for post-meeting resolution? 3. Did every participant maintain laser focus on the three critical questions? Second Round 1. Strategically swap roles and scenario cards 2. Execute another stand-up, implementing targeted improvements 3. Critically compare the effectiveness of both sessions 🔔 Critical reminder: Never resolve issues during the stand-up itself. Note blockers for immediate follow-up immediately after the meeting concludes. ⏳ Timebox: Strictly 15 minutes maximum (2 minutes per person in a team of 5) 📝 Common Pitfalls to Avoid: Slipping into problem-solving mode Providing excessive technical detail Reporting to the Scrum Master instead of the team Overlooking the critical "impediments" question 🧠 Key Concepts: The Three Essential Stand-Up Questions Core Scrum Ceremony Discipline Ruthless Focus and Time Management Effective Impediment Identification and Tracking

🎯 Objective: Foster a culture of relentless improvement through a thoughtful, structured retrospective process. 🧩 Scenario: Your sprint has concluded with mixed results—significant successes alongside several meaningful challenges. 🗣️ Team Reflection (15 min) Using color-coded sticky notes, have each team member thoughtfully answer: 🎉 What specific achievements deserve celebration? (Green notes) ⚠️ Where did we encounter significant difficulties? (Red notes) 🛠️ What targeted changes would make our next sprint more successful? (Blue notes) Post all notes on a shared visual board (physical or digital). 🔍 Group & Analyze (10 min) As a unified team, group related items and identify meaningful patterns. Utilize dot voting (3 votes per person) to democratically prioritize the most critical issues to address. Remember: Maintain a strictly blameless environment—emphasize systemic learning over individual criticism. 🚀 Action Planning (15 min) Collaboratively develop 1–2 concrete, actionable process improvements with: Specific, measurable success criteria for clear evaluation Designated ownership and firm deadlines Detailed implementation plans that can be tracked throughout the next sprint Document your action items on the provided "Sprint Improvement Tracker" sheet. ⏱️ Total Time: 40 minutes Materials Needed: Color-coded sticky notes (3 colors), markers, dot stickers, Sprint Improvement Tracker template, whiteboard/digital board 🧠 Key Concepts: Skilled Retrospective Facilitation Systems Thinking Over Individual Blame Kaizen: Unwavering Commitment to Incremental Improvement Collective Team Accountability