Please enable JavaScript.

Coggle requires JavaScript to display documents.

SAFEe Scrum Master - Coggle Diagram

- - - - Values
      - Principles
  - - - Waterfall
        
        Increased Overhead
        
        Too much WIP
        
        Context Switching
        
        Value delivered at the end
      - Agile
        
        Value Delivery
        
        Early
        
        continous
        
        Reduce WIP
        
        incremental
        
        development
  - - - Foundations
        
        Incremental Development
        
        Stories
        
        Allows refinement of understanding of functionality
        
        Vertical Slices
        
        Enable short feedback cycle
      - Iterations basics
        
        Definition
        
        Single Development Cycle
        
        Duration
        
        Same Duration
        
        Recomended 2 weeks
        
        Goal
        
        Working software/hardware at the end of interation
        
        Avoid
        
        Add scope
      - relations
        
        with
        
        PDCA
        
        Plan
        
        Iteration Planning
        
        Do
        
        Iteration Execution
        
        Check
        
        Iteration Review
        
        Adjust (Act)
        
        Iteration Retrospective
      - xSAFe Terminology
        
        The Scrum Team -> Agile Team
        
        Sprint -> Iteration
        
        Daily Scrum -> Daily Stand-up (DSU)
      - Values
        
        Openness
        
        Focus
        
        Courage
        
        Commitment
        
        Respect
      - roots
        
        The 'relay race' approach to product development ... may conflict with the goals of maximum speed and flexibility. Instead, a holistic or 'rugby' approach-where a team tries to go the distance as a unit, passing the ball back and forth-may better serve today's competitive
        requirements.-Hirotaka Takeuchi and lkujiro Nonaka, "The New New Product Development Game,"Harvard Business Review , January 1986
      - Artefatos
        
        Team Backlog
        
        has
        
        Stories
        
        User
        
        Enabler
        
        opportunities
        
        not
        
        commitents
        
        Created
        
        Team
        
        priorizaton
        
        PO
      - Pillars
        
        Transparency
        
        Inspection
        
        Adaptation
    - - Work
        
        in
        
        Progress
      - Need
        
        Limits
      - Avoid
        
        Waste
  - - - Customer colaboration
        
        over
        
        contract Negociation
      - Working software
        
        over
        
        comprehensive documentation
      - respondig to change
        
        over
        
        following a plan
      - individual and interactions
        
        over
        
        process and tools
    - - Deliver value early
      - Welcome changes
      - frequent delivery
      - Busness and developer sinergy
      - Motivated individuals
      - Face-to-Face conversation
      - Working software as measure of progress
      - Sustainable development
      - continuos attention do techinical excellence and good design enhances agility
      - Simplicity - Art of maximizing the amount of work not done - is essential
      - The best solutions arises from self-organizing teams
      - At regular intervals, te team reflects on how to become more effective, then tunes and adjust its behaviour accodingly.
- - - - #1 Take an economic view
      - #2 Apply systems thinking
      - #3 Assume variability: Preserve options
      - #4 Build inccrementally with fast, integrated learning cycles
      - #5 Base milestonnes on objective evvaluation of working systems
      - #6 Visualize and limmite WIP, reduce batch sizes, and manage queue lengths
      - #7 Appply cadence, syncrhonize with cross-domain planning
      - #8 Unlock the intrinsic motivvation of knowledge workres
      - #9 Descentralize descision-making
      - #10 Organize around value
    - - Roles & Responsability
        
        Agile Team
        
        Employ
        
        Built-in Quality Practices
        
        Design Patterns and practices
        
        eXtreme Programming (XP)
        
        Lean and Agile principles and pratices
        
        Behavior-drivven development (BDD)
        
        https://dannorth.net/introducing-bdd/
        
        https://www.agilealliance.org/glossary/bdd
        
        Code Quality
        
        Agile modeling
        
        https://www.umsl.edu/~sauterv/analysis/Fall2013Papers/Buric/agile-methodologies/agile-modeling.html
        
        Kanban
        
        Scrum
        
        Develop & Commit
        
        Iteration Plan
        
        Team PI Objectives
        
        Create & Refine
        
        Stories
        
        Test
        
        Define
        
        Build
        
        Deliver
        
        Acceptance Criteria
        
        5 to 11 members
        
        Scrum Master
        
        Coaches
        
        Team
        
        Facilitate
        
        Team
        
        Meetings
        
        Remove
        
        Ipediments
        
        Protect
        
        Team
        
        from
        
        1 more item...
        
        Attends
        
        Scrum of Scrum Meetings
        
        P.O. Project Owner
        
        Stories
        
        Accepts
        
        Create
        
        Priorizes
        
        Surrogate
        
        of
        
        Customer
        
        Works with Product Management to plan Program Increments
        
        Agile Release Train (ART)
        
        Team of Agile Teams
        
        5 to 12 teams
        
        50 to 125 people
        
        Events
        
        System Demo
        
        1 hour
        
        Deliverables are reviewed with stakeholdres
        
        PI Planning
        
        2 days
        
        Teams commit to the PI
        
        ART Sync
        
        1 hour
        
        Teams on the ART sync progress regarded with the PI
        
        Inspect and Adapt Event
        
        1/2 day
        
        The ART review and iproves its process bfore the next PI