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

    Agile Planning and Estimation

    Capacity Planning in Agile

    Agile software development framework

    Agile software development framework.

    Capacity planning is a critical aspect of Agile project management. It involves determining the team's ability to complete work in a given time frame, typically a sprint or iteration. This process helps Agile teams to manage their workload effectively and avoid overcommitting.

    Understanding Capacity Planning

    In Agile, capacity is the total amount of work that a team can handle during a sprint. It is usually measured in hours or story points. Capacity planning is the process of determining this capacity before the start of each sprint during the sprint planning meeting.

    The goal of capacity planning is to ensure that the team does not commit to more work than it can realistically complete. This helps to maintain a sustainable pace of work, reduce stress, and improve the quality of the deliverables.

    Calculating Team Capacity

    The first step in capacity planning is to calculate the team's capacity. This involves several factors:

    1. Team size: The number of team members available to work on the project.
    2. Individual capacity: The amount of productive work each team member can do in a day. This is usually less than the total working hours due to meetings, breaks, and other non-project activities.
    3. Sprint length: The duration of the sprint, typically in weeks.
    4. Availability: The number of days each team member is available during the sprint. This should account for holidays, vacations, and other absences.

    The team's capacity is calculated by multiplying these factors together. For example, if a team of five members each has an individual capacity of six hours per day, and the sprint length is two weeks (10 working days), the total capacity for the sprint is 5 members * 6 hours/day * 10 days = 300 hours.

    Factors Affecting Team Capacity

    Several factors can affect a team's capacity:

    • Team member skills and experience: More experienced team members may be able to complete work faster than less experienced ones.
    • Complexity of the work: More complex tasks may take longer to complete.
    • External dependencies: If the team is dependent on external resources or teams, this can affect their capacity.
    • Unplanned work or interruptions: These can reduce the team's capacity.

    Using Capacity Planning for Sprint Planning

    Once the team's capacity is known, it can be used during the sprint planning meeting to select the right amount of work for the sprint. The team should aim to fill their capacity with user stories from the product backlog, starting with the highest priority ones.

    However, it's important not to overfill the sprint. It's better to undercommit and overdeliver than to overcommit and underdeliver. A good rule of thumb is to plan for about 80% of the team's capacity, leaving some buffer for unexpected issues.

    In conclusion, capacity planning is a vital tool for Agile teams. It helps to ensure a sustainable pace of work, improve predictability, and increase customer satisfaction by delivering high-quality work on time.

    Test me
    Practical exercise
    Further reading

    My dude, any questions for me?

    Sign in to chat
    Next up: Running Agile Meetings and Setting Sprint Goals