101.school
CoursesAbout
Search...⌘K
Generate a course with AI...

    Agile project management

    Receive aemail containing the next unit.
    • Introduction to Agile Project Management
      • 1.1History and Evolution of Agile Methodologies
      • 1.2Key Concepts and Principles of Agile
      • 1.3Introduction to Agile Project Management
      • 1.4Roles and Responsibilities in Agile
    • Agile Mindset and Agile Manifesto
      • 2.1Understanding Agile Mindset
      • 2.2Agile Manifesto and its Principles
      • 2.3Building an Agile Culture
      • 2.4Agilism and the Role of a Leader
    • Agile Leadership
      • 3.1Agile Leadership Styles
      • 3.2Role and Responsibilities of Agile Leaders
      • 3.3Facilitating Team Performance
      • 3.4Managing Conflicts and Backlogs
    • Agile Methodologies and Frameworks
      • 4.1Introduction to Scrum
      • 4.2Introduction to Kanban
      • 4.3Lean and XP Explained
      • 4.4Choosing the Right Agile Framework or Methodology
    • Building an Agile Team
      • 5.1Organizing Agile Teams
      • 5.2Building Psychological Safety Within Teams
      • 5.3Distributed Agile Teams
      • 5.4Team Performance Metrics in Agile
    • Agile Planning and Estimation
      • 6.1Introduction to Agile Planning
      • 6.2Story Points and Velocity
      • 6.3Agile Estimation Techniques
      • 6.4Capacity Planning in Agile
    • Executing Agile Projects
      • 7.1Running Agile Meetings and Setting Sprint Goals
      • 7.2Managing and Prioritizing Backlogs
      • 7.3Tracking Project Progress: Burn-Down and Burn-Up Charts
      • 7.4Handling Blockers and Impediments
    • Agile Quality Assurance
      • 8.1Quality Metrics in Agile
      • 8.2Agile Testing Strategies
      • 8.3Test-Driven Development
      • 8.4Continuous Integration and Continuous Deployment
    • Value-Driven Development
      • 9.1Principles of Value Driven Development
      • 9.2Prioritizing Value in the Backlog
      • 9.3Minimum Viable Product and Incremental Delivery
      • 9.4Value Stream Mapping
    • Agile Contracting and Governance
      • 10.1Agile Contract Models
      • 10.2Vendor Management in Agile
      • 10.3Governance in Agile
      • 10.4Compliance and Documentation in Agile
    • Agile Transformation and Scaling
      • 11.1Agile Transformation Pathways
      • 11.2Implementing Agile at Scale
      • 11.3Challenges in Agile Scaling
      • 11.4Tools for Managing Agile at Scale
    • Case Studies and Best Practices
      • 12.1Agile in IT and Software Development
      • 12.2Agile in Non-IT Industries
      • 12.3Agile Project Pitfalls and Mitigation
      • 12.4Sharing Best Practices
    • Reflection and Synthesis
      • 13.1Agile Leadership Reflections
      • 13.2Applying Agile Methodologies in Real-life Scenarios
      • 13.3Adapting Agile Frameworks to Unique Situations
      • 13.4Continuing Education and Certification in Agile

    Executing Agile Projects

    Running Agile Meetings and Setting Sprint Goals

    Agile software development framework

    Agile software development framework.

    In Agile project management, meetings play a crucial role in ensuring effective communication, collaboration, and decision-making. These meetings, often referred to as ceremonies or events, provide a structured platform for the team to plan, synchronize, review, and improve their work. This article will delve into the purpose and structure of key Agile meetings and how to set clear and achievable Sprint Goals.

    Agile Meetings

    Sprint Planning

    Sprint Planning is a meeting that marks the beginning of a new sprint. The Product Owner, Scrum Master, and the Development Team come together to plan the work to be done in the upcoming sprint. The Product Owner presents the highest priority items from the Product Backlog, and the team collaboratively decides what they can commit to completing. The outcome of this meeting is the Sprint Backlog and a clear Sprint Goal.

    Daily Stand-up

    The Daily Stand-up, also known as the Daily Scrum, is a short meeting (usually 15 minutes) held every day at the same time and place. The Development Team uses this meeting to synchronize their work and plan for the next 24 hours. Each team member answers three questions: What did I do yesterday? What will I do today? Are there any impediments in my way?

    Sprint Review

    At the end of the sprint, the team holds a Sprint Review to inspect the increment of work completed and adapt the Product Backlog if needed. The Product Owner explains what backlog items have been "Done" and what has not. The Development Team discusses what went well during the sprint, what problems it ran into, and how those problems were solved.

    Sprint Retrospective

    The Sprint Retrospective is a meeting held after the Sprint Review and before the next Sprint Planning. The team reflects on the past sprint with regards to people, relationships, process, and tools. They identify and order the major items that went well and potential improvements, and create a plan for implementing improvements to the way the Scrum Team does its work.

    Setting Sprint Goals

    A Sprint Goal is an objective set for the sprint that can be met through the implementation of a set of Product Backlog items. It provides guidance to the Development Team on why it is building the increment. The Sprint Goal is a commitment by the Scrum Team and provides flexibility in terms of the functionality implemented within the Sprint.

    Setting clear and achievable Sprint Goals is crucial as it guides the team's work, helps maintain focus, and provides a measure of success. The Sprint Goal should be determined during the Sprint Planning meeting and communicated clearly to all team members.

    In conclusion, running effective Agile meetings and setting clear Sprint Goals are fundamental to the success of Agile projects. They foster collaboration, enhance communication, and ensure that the team is always focused on delivering value.

    Test me
    Practical exercise
    Further reading

    Hey there, any questions I can help with?

    Sign in to chat
    Next up: Managing and Prioritizing Backlogs