Please enable JavaScript.

Coggle requires JavaScript to display documents.

SCRUM MASTER (Practitioner -Change Agent (Anitpatterns (Ersatz PM: The…

- - - - WFH Coffee catchup
  - - - Spike
      - New Story in middle of the sprint
      - Someone "Leads" a standup and makes it a status meeting
      - Dev thinks standup is a waste of time
      - Sprint hardening - is a specialized sprint dedicated to stabilizing the code base so that it is robust enough for release; it is often necessary because the Team failed to use an appropriate Standard of Care when it did its work.
  - - - Adapt
        
        Get commitments or next actions clarity from Individuals
  - - - Refer Agile Metrics in SM Toolbox
- - - - Use toolxyz
- - - - Transparency
      - Inspection
      - Adaption
    - - Prod.Backlog
        
        In case of multiple teams 1 PB grouped by feature set, Architecture, technology etc
      - Sprint Blg
      - Sprint Burndown
      - Sprint Goal
      - Product Vision
      - Increment
    - - Framework for complex products
      - emperical
      - Incremental
      - to optimize predictability and risk control
      - Just in Time planning
        
        Like Daily scrum,Planning,Review
    - - Scrum Teams
        
        3 Roles
        
        Dev Team
        
        Self-organizing
        
        Cross Functional
        
        3 to 9 members
        
        Own SprintBlg
        
        Does estimations solely
        
        Does work and has all necessary skills
        
        Members can change at end of sprint
        
        Committed to sprint goal
        
        SM-
        
        Refer to Practictioner Branch
        
        PO
        
        Sets Vision, priorities
        
        can cancel sprint
        
        responsible for ROI , Owns PB and only PO can add / prioritise PB
        
        cant be SM,DevTeam member,not a commitee, 1 person
      - Time Boxes
        
        Sprint- Length1month, or less, consistent delivery potentially shippable product, at beginning 2 weeks less uncertainty, constant - sprint goal, team composition, can be cancelled when goal is obsolete or it no longer makes sense given circumstances -Input -sprint backlog . Output - increment
        
        Sprint Planning
        
        8h for 1month sprint , first day of sprint, attendees - PO,DevTeam, other experts for advice
        
        input -PB, latest increment, capacity, past performance Output- sprint goal,sprint Blg, Team commitment
        
        Retro
        
        3h for 1 month sprint , after sprint review, agenda - continue,stop,do better
        
        Team to revise - people, relationships, process, tools
        
        Types of retro-refer to SM toolbox
        
        Output:actionable improvement measures for next sprint
        
        Review
        
        collaborate on whats done and what could be done
        
        Attenedes: Scrum Team, Stakeholders
        
        4h for 1mo sprint, at end of sprint,, Product demo
        output - input to subsequent sprint planning meeting
        
        Backlog Refinement
        
        DOD,DOR
        
        Daily Scrum
        
        not a status meeting, everyday, sample & time , standing,
        
        Inspection - process toward sprint goal
        
        3 Qs
        
        Purpose
        
        Improve comm
        
        eliminate other meeting s
        
        identify & remove impediments
        
        highlight & promote quick decision makin
  - - - Based on Maturity
    - - Pair Programming.
      - Test Driven Development/Unit Testing.
      - Continuous Integration.
      - Refactoring.
      - Acceptance Testing.
      - Small Releases.