Agile Sprint Activities and Planning Overview
Explore the Agile sprint activities and planning process including current, previous, and next sprint activities. Learn about the specific tasks and roles involved in a ten-day Agile sprint cycle. Dive into week one and week two activities to understand the detailed schedule and tasks for each day of the sprint.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
LiquidHub consulting | solutions | outsourcing AN AGILE DEVELOPMENT METHODOLOGY THE SPRINT ACTIVITIES SCHEDULE THE SPRINT ACTIVITIES SCHEDULE The Agile Process Team Brad Huett Megan Schmid Erich Villasis Siva Natarajan Don Kasner Dave Latham Steven Hill Bryce Budd Thursday, April 3, 2025 fueling business transformation fueling business transformation
What are Sprint Activities? The Iteration Cycle: A Ten Business Day Activities Plan The Agile Sprint has three types of activities that are performed within the ten day period: 1. Current Sprint Activities 2. Previous Sprint Activities 3. Next Sprint Activities The activities are labeled as Day 1 through Day 10. Most days have activities that span two types. The Sprint Activities Schedule helps define and clarify the activities that a given Agile Role has on any given day of the iteration. 2 fueling business transformation
What are Week One Activities? Week 1 of the Agile Sprint Sprint Mon-Day 1 Tue-Day 2 Wed-Day 3 Thu-Day 4 Fri-Day 5 Previous Sprint PO & BA: Demo Certification and Dress Rehearsal QA & Architect: Demo Validation Support Developers: Code Migration, Demo Validation, and troubleshoot Execution Issues Team: Sprint Demo Product Demonstration Team: Sprint Retrospective Meeting Next Sprint Planning PO, BA & QA: Select and Prioritize next sprint candidate stories. Initial creation of test data and test cases. Current Sprint New Sprint Kickoff Team: Stand Ups QA: Smoke Test QA environment, Validate Daily Builds Architect: Dev Support Developers: Coding, Daily Builds & Push to QA, Code Review, Enter Time in JIRA Team: Stand Ups QA: Testing, Validate Daily Builds Architect: Dev Support Developers: Coding, Daily Builds & Push to QA, Enter Time in JIRA Team: Stand Ups QA: Testing, Validate Daily Builds Architect: Dev Support Developers: Coding, Daily Builds & Push to QA, Code Review, Enter Time in JIRA Team: Stand Ups QA: Testing, Validate Daily Builds Architect: Dev Support Developers: Coding, Daily Builds & Push to QA, Code Review, Enter Time in JIRA Team: Stand Ups QA: Testing, Validate Daily Builds Architect: Dev Support Developers: Coding, Daily Builds & Push to QA, Code Review, Enter Time in JIRA 3 fueling business transformation
What are Week TwoActivities? Week 2 of the Agile Sprint Sprint Mon-Day 6 Tue-Day 7 Wed-Day 8 Thu-Day 9 Fri-Day 10 Previous Sprint Next Sprint Planning PO & BA: Groom next sprint candidate stories. QA: Create use cases, test data, test suite for selected sprint candidate stories. Architect & Lead Developers: Analysis of selected next candidate stories. Architect: Review & Certify Initial Design for next Sprint candidate stories. Lead Developers: SpecFlow Feature Stories for next Sprint candidates & create Initial Design Document for next Sprint candidate stories. QA: Validate, Create Test Cases and Data for next Sprint Candidate stories as the initial Developer s QA Objective. Team: Begin Next Sprint Planning Sessions: - Poker Planning, - Acceptance Criteria, - Team Capacity, - Task Acceptance Team: Continue Next Sprint Planning Sessions: - Poker Planning, - Acceptance Criteria, - Team Capacity, - Task Acceptance If Required Team: Continue Next Sprint Planning Sessions (Validation, Poker Planning, Acceptance Criteria, Team Capacity, Task Acceptance) If Required Validate the QA Objective as defined by the initial QA Test Suites Current Sprint Team: Stand Ups QA: Testing, Validate Daily Builds Architect: Dev Support Developers: Coding, Daily Builds & Push to QA, Code Review, Enter Time in JIRA Team: Stand Ups QA: Testing, Validate Daily Builds Architect: Dev Support Developers: Coding, Daily Builds & Push to QA, Code Review, Enter Time in JIRA Team: Stand Ups QA: Testing, Validate Daily Builds Architect: Dev Support Developers: Coding, Daily Builds & Push to QA, Code Review, Enter Time in JIRA Team: Stand Ups QA: Testing, Validate Daily Builds Architect: Dev Support Developers: Coding, Technical Debt & Bug fixes, Daily Builds & Push to QA, Code Review, Enter Time in JIRA Team: Stand Ups PO & BA: Demo Planning QA: Testing, Validate Daily Builds, Final Demo Testing, Integration Support Architect: Demo and Integration Support Developers: Coding, Daily Builds & Push to QA before 12:00 Code Freeze, Code Review, Code Freeze at 12:00PM, Push to Demo Environment, Enter Time in JIRA 4 fueling business transformation
In Conclusion: Sprint Activities Schedule Understanding the Sprint Process Change is hard for most people. Our comfort zones protect us from harm in our minds. This is a false sense of protection. As a working team we need clarity and comfort in our roles and responsibilities In the transition stages of change we need a Security Blanket . The Sprint Activities Schedule is the blanket. It life span is generally very short as the Sprint daily activities become second nature very quickly The Sprint Activities Schedule is a Short-term Cheat Sheet that adds Process Clarity to the Changing Environment 5 fueling business transformation
