Please enable JavaScript.

Coggle requires JavaScript to display documents.

Agile frameworks (Agile manifesto (Individuals and interactions over…

- - - - Kanban cards, boards
    - - Stop starting and start finishing
    - - Value stream
    - - E.g. Defn of done
    - - Kaizen -- continuous improvement.
      - Theory of constraints
      - Lean Economic model
  - - - work / (wait+work) * 100
- - - - Portfolio
        
        Programme
        
        Agile Release Train -- multiple teams on a programme
        
        Programme iterations (5 iterations by default)
        
        5th iteration
        
        Innovation
        
        Planning next PI
        
        Retros
        
        Product manager defines features for the programme
        
        Release train engineer -- programme manager -- makes sure programme is on track
        
        PI starts with everyone meeting
        
        Review vision for PI
        
        Features to be included
        
        Teams commit to PI objectives, identify dependencies
        
        Bi-weekly Scrum of Scrums
        
        System demo at the end of each iteration
        
        Ensures integrated system
        
        Multiple Value Streams
        
        Based on themes from strategy
        
        Budgets allocated to value streams
        
        Cross-value stream initiatives
        
        Called Business epics
      - Value stream
        
        Multiple PI
      - Team
        
        Scrum or Kanban
        
        Cross-functional
        
        Regular releases
  - - - cross-team dependencies
      - integration issues
    - - responsible for ensuring that an Integrated Increment (the combined work completed by a Nexus) is produced at least every Sprint
    - - Identify integration between teams
    - - create plan for next sprint for all teams
      - Nexus Sprint Goal
        
        All teams work to achieve
        
        Nexus Sprint Backlog produced
    - - Reps from each team
      - Different to team daily Scrum
    - - replaces team sprint reviews
    - - Reps from each team identify shared challenges
      - Individual team retro
      - Reps from each team share actions
- - - - Problem when features have different work across components
- - - - Reduce context switching
      - Reduce WIP
      - Reduce manual tasks
      - Focus on value for customer
    - - Value stream
        
        Reduce hand off delays
        
        Reduce wait times
        
        Reduce re-work
    - - Analyse results of small changes
      - Share learning
      - Retain valuable learning
    - - Manage flow
      - Limit WIP
      - Focus on value delivery
      - Learn from customer quickly
    - - Automate standard/tedious/repeatable process
      - Reduce scope for human error
    - - Make decisions as the last responsible moment
      - . Most informed
    - - Customer value first
      - Employees