Remote Work Tools

Techniques

  • When designing the architecture of a system, identify the feedback loops and other affected systems, and outline contingency plans should the new system introduce new behaviors in those connected systems.

  • Contingency plans do not have to all be implemented at the time of creation, but they should be identified and easily accessible for future implementation when needed.

  • When possible, design systems that are decoupled, that can operate independently without knowledge of any other systems.

  • Strive to make unexpected conditions irrelevant by designing systems using “white list” modeling, identifying expected conditions for all inputs along with systems that address, ignore, or can automatically recover from anything outside expected parameters.

Guidance

O4.2 Technical Health

Remote Work Tools

  • Thinking Fast and Slow” by Daniel Kahneman

  • Lean Startup Solution Interviews

  • Concierge MVPs (Minimum Viable Products)

  • Wizard of Oz MVPs (Minimum Viable Products)

  • Frankenstein MVPs (Minimum Viable Products)

  • Human-Centered Design

  • Lund’s Usability Maxims

Techniques

  • Since humans make decisions based on emotions, not logic, implementation details will often not match designs or expectations.

  • Customers, when observed, tend to not use products as intended, so user experience (UX) must be based on the observed behavior patterns of your actual customers.

  • Full understanding of the motivations and actions of users requires the collection and processing of both quantitative data collection to catalog their actual behavior patterns and representative qualitative research to understand why.

  • Those building the product need to either have regular access to recordings of customers interacting with the product or direct access to customers to truly understand their target audience.

Guidance

O4.1 Customer-Centered Implementation

  • Confusion

  • Defects (Bugs)

  • Disgruntled Employees

  • Impediments & Delays

  • Lack of Communication

  • Late-breaking Requirements

  • Low Output

  • Rework

  • Siloed “Not My Job” Thinking

  • Unhappy Stakeholders

Problems Experienced Without These Practices

ation

Organization

O4.

Implement

Remote Work Tools

  • REST APIs

  • Property Invocation Programming

Techniques

  • When possible, design systems that are decoupled, that can operate independently without knowledge of any other systems.

  • Any time you discover a vulnerability to your system, build the solution to that vulnerability into reusable components so that security and reliability are not dependent upon team members remembering to address that vulnerability every time they encounter it.

  • The addition of any reusable component adds a maintenance cost every time that it is used. The cost and time spent creating reusable components should be less than the extra time spent maintaining the reusable components.

Guidance

O4.3 Decoupled Reusable Components

Org Practices

Organization Practices

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

"Let's Make Life Workable and Work Loveable"