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 Methodologies and Frameworks

    Introduction to Kanban

    scheduling system / stock replenishment for lean manufacturing and just-in-time manufacturing (JIT)

    Scheduling system / stock replenishment for lean manufacturing and just-in-time manufacturing (JIT).

    Kanban is a popular Agile methodology that originated from the manufacturing industry in Japan. It is a visual system for managing work as it moves through a process. The goal of Kanban is to identify potential bottlenecks in your process and fix them so work can flow through it cost-effectively at an optimal speed or throughput.

    Definition and Overview of Kanban

    Kanban, which translates to "billboard" or "signboard" in Japanese, is a visual method for managing work. It emphasizes just-in-time delivery without overloading team members, by having work-in-progress (WIP) limits. The central aspect of Kanban is the Kanban board, a tool used to visualize work, workflow, and progress.

    The Kanban Method: Principles and Practices

    The Kanban method is based on four principles and six practices:

    Principles:

    1. Start with what you do now: Kanban doesn't require a specific setup, so you can overlay it on top of your existing workflow.
    2. Agree to pursue incremental, evolutionary change: Kanban encourages small, gradual changes to your current system.
    3. Respect the current process, roles, responsibilities, and titles: Kanban recognizes the value of existing roles and responsibilities, and suggests you make changes as you observe what is or isn't working.
    4. Encourage acts of leadership at all levels: Everyone is encouraged to contribute to the process improvements.

    Practices:

    1. Visualize the workflow: Seeing the work in a visual format allows team members to understand how work is flowing.
    2. Limit work in progress: This helps balance the flow-based approach so teams don't overcommit.
    3. Manage flow: The team should monitor and report on how work is flowing through the board.
    4. Make policies explicit: Any constraints or policies should be clearly displayed on the board.
    5. Implement feedback loops: Regular meetings, such as daily stand-ups, should be held to discuss issues and solutions.
    6. Improve collaboratively, evolve experimentally: Use a scientific approach to implement continuous, incremental and evolutionary changes.

    Visualizing Work with Kanban Boards

    A Kanban board is a physical or digital project management tool designed to help visualize work, limit work-in-progress, and maximize efficiency. The board is divided into different lanes, each representing a step in the workflow. Cards, which represent tasks, move from one lane to another as they progress through the workflow.

    Benefits and Challenges of Implementing Kanban

    Benefits:

    • Flexibility: Kanban is less prescriptive than other Agile methodologies, like Scrum, and can easily adapt to changes.
    • Efficiency: By limiting work-in-progress, teams can focus on completing tasks rather than starting new ones.
    • Transparency: The Kanban board provides a clear visual representation of the current state of the project.

    Challenges:

    • Over-simplification: While Kanban is simple to understand, it can be challenging to implement effectively.
    • Requires discipline: Teams need to respect WIP limits and not push too many items into the workflow at once.
    • Less structure: The lack of prescribed roles can lead to confusion or lack of accountability.

    In conclusion, Kanban is a powerful tool for managing work in a visual and efficient way. It's flexible and adaptable, making it a popular choice for many Agile teams. However, like any methodology, it requires understanding, discipline, and commitment to be effective.

    Test me
    Practical exercise
    Further reading

    Good morning my good sir, any questions for me?

    Sign in to chat
    Next up: Lean and XP Explained