Please enable JavaScript.

Coggle requires JavaScript to display documents.

AGILE (customer Satisfaction, Uncertainty Risk & Lifecycle Selection,…

- - - - D
    - - C
    - - C
  - - - C
    - - F
    - - R
    - - S
    - - TD
    - - M
    - - Dedicated
      - Cross-Functional
      - Co-located
      - T-shaped experts
      - Stable work environment - Caves & Common workspaces - Fishbowl Window - daylong live VC link; Remote pairing - VC tools to simulate Face to face pairing - Remove Silos
  - - - S
    - - W
    - - S
- - - - Map Value Stream
- - - - Scrum Team & stakeholders inspect the results and adjust for next Sprint
        
        Repeat
  - - - < 1 month; Fixed Goal; Backlog (groomed) refined as needed; Scope maybe clarify & renegotiated with PO;Can be cancelled only by PO
    - - Collaborative ; Plan made by team; PO ensures attendees discuss Prod Backlog
      - Why is Sprint Valuable? PO explains how Prod can increase its value & utility during the Sprint. Team collaborates to finalize Goal
      - What can be done ? **Collaboratively Developers select items from Prod Backlog to Sprint Backlog
      - How? Decompose Product Backlog items into smaller work items of one day or less. Sole discretion of the Developers.
    - - 15 min - Same place Same time - What yesterday? What today? Impediments? Not a status meeting
        
        Iteration based Agile - Time boxed round robin questions
        
        Flow based Agile - bottlenecks to flow; who is working on things not on the Board; Right to left on the Board
      - improves communication, decision making, produces actionable plan for the day
    - - Timeboxed to 4 hrs for 1 month sprint; ST & stakeholders Review backlog; inspect items, adjust future plans, review changes in environment
    - - Purpose is to plan ways to increase quality and effectiveness ; ST inspects **regards to individuals, interactions, processes,
        tools, and their Definition of Done**
    - - Demo of user stories given to PO,PO accepts or rejects output; If rejected shortcomings identified & story put back on Prod Backlog; Velocity (stories/SPRINT) recorded (2 weeks)
        
        Iteration based Agile - Demo of all items at end of interation
        
        Flow based Agile Demo when the product has enough features to make it coherent
    - - Story points are a unit of effort that uses relative sizing where stories are compared against previous, known, well-understood pieces of work.Relative sizing, Fibonacci/T-shirt/ fish sizes
    - - PO+SM+Team - 1 hr - Sprint Backlog
- - - - Discuss requirements
        
        Distill tests
        
        Develop code
        
        Demo software