Mind map

Quality in SCRUM

Alberto Apú SCRUM English

Map content

Quality in SCRUM

Definition
- Ability of DELIV to meet Acceptance Criteria => expected business value to customer
Continuous improvement
- Using
  - PPB
    - Never complete
    - Contains
      - US
        Three things about the requirement
        Who
        What
        Why
      - Estimates for US
        SPRINT B: subset of approved and estimated US that can be completed in, well, one SPRINT
        Final decision about SPRINT is in ST
        PO also influences the LIST
      - Epics
        Too complex to be finished in one SPRINT
        Decomposed in smaller US
      - US ACC Criteria
        DEV by PO
        Used at the end of sprint to verify the completed DELIV
        Done: All ACC Criteria OK
        Blank and White
        Set of rules FOR all US in one SPRINT
        Remove ambiguity about quality level/norms
        Done definition typically determined by SGB
        SM assures ACC Criteria for a US are not changed by PO in the middle of the SPRINT
        Reject: Back to PPB for future SPRINT
        UNIQUE to each US
        Minimum ACC Criteria
        affects all ACC criteria of any US in the SPRINT/PROJECT
        Become part of EVERY US for BUSS unit
        May have a cascade effect
        also affects
        PROJ
        Set by PROJ PO
        PORT
        Set by PORT PO
        Could Include
        Completed US reviewed by pair
        Unit testing
        QA test
        Documentation
        All isues are fixed
        Demonstration to STKHLD
  - SPRINT
    - Repetitive QA testing
      - Errors/defects identified early
      - Increase P(Achieve expected Q Level)
    - After user's needs assesment
      - ST+PO+STKHL Can
        Stop current
        Agree for future
        Fuck it
- Stop doing what is not needed
- Q Mngmt
  - Any problem is known early
  - Recognize if PROJ will enable to achieve the expeced outcomes
  - Facilitated by
    - Q Planning
      - Advantages
        Reduce
        Technical DEBT
        Work with low priority
        Accrueds over the duration of the PROJ and MUST be paid in the future
        Can be caused by
        Quick fixes
        DELIV not complying with Q standards
        Inadequate or incomplete testing
        Incomplete documentation
        Lack of coordination
        Poor BUSS KNOW from STKHLD
        Focus on short tem
        Any SPRINT tech debt should be paid in the same SPRINT
        Decrease it providing appropiate documentation/def of PROC
        SGB
        Define Quality PROC and DOCUMENTS
        Can be minimized by
        Clear definition of development methods
        Key responsibilities of ST in regards to Q
        Good and clear ACC Criteria
      - Define ACC Criteria
    - Q Control
      - Execution of planned Q activities by ST in the fabrication of DELIV
      - Focus ON
        DELIV'S Q
        PROCESSES to plan, develop and verify DELIV
      - Lessons Learn
        Discussed in
        SPRINT Retrospect Meeting
        Input of
    - Q assurance
      - Asses PROCESSES and STANDARDS that gobern Q Mngmt to assure they are still appropiate and relevant
      - Carried out as part of DEV WORK
      - INTEGRAL part of DoD
      - DELIV not complete until QA Check
      - Is demostrated during
        SPRING Review Meeting
      - Plan - Do - Study - Check ACT (PDCA) Cycle
        Based on
        Deming's Theory of Profound Knowledger
        What MNGMNT should do to
        Create WORK ENVIRONMENT
        Where
        Each employee can make significant contribution to quality improvement
      - Responsibilities
        SGB
        Defines
        Tools to DEV and TEST
        Provides
        DoD
        Framework and guidance
        PORT PO
        Sets
        Min PORT ACC Criteria
        Reviews
        PORT DELIV
        PROG PO
        Sets
        Min PROG ACC Criteria
        Reviews
        PROG DELIV
        PORT SM
        Ensures
        Sustainable pace
        PROG SM
        Ensures
        Sustainable pace
        STKHLD
        Review and accept
        DELIV
        PO
        States
        Business Requirements
        PPB
        Assess
        Viability
        Ensures
        DELIV meet Q
        Sets
        Min PROJ ACC Criteria
        Facilitates
        ACC Criteria for US creation
        Review and validate
        DELIV
        SM
        Facilitates
        "Team first" mentality
        Eliminates
        Obstructions
        Ensures
        Sustainable pace
        SCRUM Process
        ST
        Develops & maintain
        DELIV in SPRIN
        Practices
        Good COMM
        Shares
        Knowledge
        Makes
        Appropiate change to DELIV, swiftly
- Customer Satisfaction
Scope
- =
  - Sum(PROD increments) + Sum(DEV Work)
- Determined by
  - BUSS need
  - ORG's capability/ willingness
  - TARGET audience's current/future needs
Business VALUE
- High priority to US that meet CUST need
Improved over time by
- Sustainable pace, ooommmm
  - Ideal velocity
    - not compromising
      - Q of life
      - Q of DELIV
  - Translates to increased
    - satisfaction
    - stability
    - estimation accuracy
- Continuous integration
  - PM adaptive mechanism
    - Accomodate change without significant impact
  - Provide value at frequent intervals
Advantages over PM
- Emphasis in
  - Potentially shippable DELIV per SPRINT
- PO and CUST constantly inspect, approve and accept DELIV
- VALUE prior to termination

Images and files in the map

Information

Description: Quality aspect in SCRUM
Created by: Alberto Apú
Views: 1
Tags: quality scrum
Rating

Quality in SCRUM

Map content

Images and files in the map

Information

Feedback

What do you think of the new look?