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 environment. 

  • Record who requested the changes, if applicable, in case they want to be notified.

    • NOTE: This could be multiple people.

  • Introduce and track new changes into the Customer Environment in Small Batches.

    • 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.

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

  • Record all activities involved in final delivery for faster resolution of problems.

Guidance

T5.3 Delivery Tracking

Remote Work Tools

  • Separate Physical Environments

  • Environment Cloning

  • Environment Containers

  • Environment Scripting

  • Cloud vs On-Premise Delivery

Techniques

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

  • It’s easy for non-tested code to be accidentally delivered to the customer when implementation or testing happen in the customer environment.

  • Customers are often blocked from doing their work by the introduction of new changes when implementation or testing happen in the customer environment.

  • Introduce new changes into the Customer Environment in Small Batches.

    • 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 advance notice to the customer.

Guidance

T5.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).

  • It’s easy for non-tested code to be accidentally delivered to the customer when implementation and testing happen in the same environment.

  • Testing is often prevented from doing their work by the introduction of new changes when implementation and testing happen in the same environment.

  • Introduce new changes into the Test Environment in Small Batches.

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

  • Always schedule the delivery of new changes with the testing team members upon their request.

Guidance

T5.1 Independent Test 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

T5.