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

    Introduction to Agile Planning

    Agile software development framework

    Agile software development framework.

    Agile planning is a critical component of project management, particularly in Agile methodologies where change is not only expected but embraced. Unlike traditional project management, where a detailed plan is created at the beginning of the project, Agile planning is iterative and flexible. It allows for adjustments as the project progresses and new information becomes available. This approach is often referred to as progressive elaboration.

    The Importance of Planning in Agile

    While Agile methodologies value responding to change over following a plan, this does not mean that planning is unnecessary. On the contrary, planning in Agile is continuous and provides a roadmap for the team. It helps to set expectations, align the team towards common goals, and provides a basis for measuring progress.

    Traditional Planning vs Agile Planning

    Traditional project planning is often detailed and fixed, with changes being seen as a sign of problems. It typically involves creating a comprehensive plan at the beginning of the project, with detailed schedules, budgets, and resource allocations.

    On the other hand, Agile planning is iterative, flexible, and embraces change. It recognizes that it is impossible to anticipate all details and changes at the beginning of a project. Therefore, instead of a detailed upfront plan, Agile planning involves creating a high-level plan with the understanding that the plan will be refined and elaborated as the project progresses and more information becomes available.

    Progressive Elaboration

    Progressive elaboration is a project management technique where planning and documentation are continually refined and expanded throughout the project lifecycle. This approach acknowledges that it is not possible to know all the details of a project at its start. As the project progresses, more information becomes available, allowing for more accurate and detailed planning.

    Levels of Agile Planning

    Agile planning occurs at multiple levels, each with a different planning horizon and level of detail:

    1. Strategic Planning: This is the highest level of planning, where the vision, strategic themes, and portfolio backlog are defined. It provides a long-term view and is typically done by top management and product owners.

    2. Release Planning: This level of planning involves deciding which features or user stories will be delivered in each release. It provides a mid-term view and is typically done by the product owner and the team.

    3. Iteration Planning: This is a short-term plan that details what the team will deliver in each iteration or sprint. It is typically done by the team.

    4. Daily Planning: This is done during the daily stand-up meetings where the team plans work for the next 24 hours.

    In conclusion, Agile planning is a vital aspect of Agile project management. It provides direction, aligns the team, and allows for measuring progress. However, it is flexible and iterative, allowing for adjustments as the project evolves and more information becomes available.

    Test me
    Practical exercise
    Further reading

    My dude, any questions for me?

    Sign in to chat
    Next up: Story Points and Velocity