Team Practices

Team working in an office

Remote Work Tools

  • Kanban Boards

Techniques

  • Keep track of whether and when all new changes are delivered to the customer (i.e. production environment). 

  • Record who requested delivery to the customer, if applicable, in case they want to be notified upon successful delivery.

    • NOTE: This could be multiple people.

  • Prioritize which changes require immediate delivery (e.g. defects) and which can be delivered in batches.

  • Record all activities executed for final delivery to enable faster resolution of problems.

Guidance

T6.3 Delivery Tracking

Remote Work Tools

  • Separate Physical Environments

  • Environment Cloning

  • Environment Containers

  • Environment Scripting

  • Cloud vs On-Premise Delivery

Techniques

  • Avoid accidentally-delivering non-tested code to the customer by keeping customer environments separate.

    • WARNING: Implementation and Testing should never happen in the same environment that your customers use.​

  • Introduce new changes into the customer environment in small batches to help customers with their Flow.

    • CAUTION: If new changes make the customer environment unusable, customers will be blocked from working until resolved.

    • CAUTION: Large batches of changes make identifying the source of the problem more difficult.

  • Schedule the delivery of new changes with plenty of advance notice to the customer.

Guidance

T6.2 Independent Customer Environment

Remote Work Tools

  • Separate Physical Environments

  • Environment Cloning

  • Environment Containers

  • Environment Scripting

Techniques

  • Every task and work product should be Verified Independently - by someone other than the person who completed it, and without their resources (e.g. not on their computer).

  • Avoid accidentally-delivering non-tested code to the customer by keeping implementation and verification environments separate.

    • CAUTION: Verification is often prevented or disrupted by the introduction of new changes when implementation and verification happen in the same environment.

  • Introduce new changes into the verification environment in small batches to encourage Flow.

    • CAUTION: If new changes make the verification environment unusable, team members will be blocked from working until resolved. 

  • All changes to the verification environment should be done at the request of those doing the testing.

    • WARNING: It is inappropriate for implementation teams to push changes to the verification environment upon completion of their work; the test environment belongs to the people doing the verification; changes should be requested and delivered at a time when those changes will not interrupt verification that is in-progress. ​

Guidance

T6.1 Independent Verification Environment

  • Confusion

  • Defects (Bugs)

  • Disgruntled Employees

  • Impediments & Delays

  • Lack of Communication

  • Late-breaking Requirements

  • Low Output

  • Rework

  • Unhappy Stakeholders

Problems Experienced Without These Practices

Operations

Team

T6.

© 2022 by The Library of Agile. Created on Editor X.

"Let's Make Life Workable and Work Loveable"