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

    Value-Driven Development

    Understanding and Applying Value Stream Mapping in Agile

    Value Stream Mapping (VSM) is a lean-management method used for analyzing the current state and designing a future state for the series of events that take a product or service from its beginning through to the customer. In the context of Agile, VSM is a powerful tool that helps teams visualize work processes and understand the flow of value in the system.

    Components of a Value Stream Map

    A value stream map typically includes the following components:

    1. Customer: The customer is the end recipient of the product or service. In VSM, the customer defines value.

    2. Value Stream: This is the sequence of all actions, both value-adding and non-value-adding, required to bring a product or service from request to delivery.

    3. Flow: This represents the movement of information and materials along the value stream.

    4. Pull: This is the principle that nothing is produced by the upstream process until it is required by the downstream process.

    5. Perfection: This is the aim of eliminating waste so all steps add value to the product or service.

    Creating a Value Stream Map

    Creating a value stream map involves the following steps:

    1. Identify the product or service: Choose a product, service, or product family to map.

    2. Identify the customer: Determine who receives the output of the value stream.

    3. Map the value stream: Document all the steps and processes involved in taking the product or service from request to delivery. This includes both value-adding and non-value-adding activities.

    4. Analyze the map: Look for waste and areas of improvement in the value stream. This could be in the form of delays, rework, unnecessary movement, overproduction, etc.

    5. Design a future state: Based on the analysis, design a future state map that eliminates or reduces the waste and improves the flow of value.

    6. Implement changes: Develop a plan to move from the current state to the future state. Implement the changes and monitor progress.

    Using VSM to Identify Waste and Improve Processes

    Value stream mapping is a powerful tool for identifying waste in a process. By visualizing the flow of work, teams can easily spot bottlenecks, delays, and areas of inefficiency. Once these areas are identified, teams can work on eliminating or reducing these wastes to improve the overall flow of value.

    In addition, VSM can also help improve processes by:

    • Increasing visibility: VSM provides a clear visual representation of the process, making it easier for everyone to understand the flow of work.

    • Promoting collaboration: Since VSM involves multiple stakeholders, it encourages collaboration and communication among team members.

    • Driving continuous improvement: VSM is not a one-time activity. It's a continuous process of mapping, analyzing, improving, and re-mapping.

    In conclusion, Value Stream Mapping is a valuable tool in Agile environments. It helps teams visualize their work processes, identify waste, and continuously improve their value delivery.

    Test me
    Practical exercise
    Further reading

    My dude, any questions for me?

    Sign in to chat
    Next up: Agile Contract Models