Remove Proxies to People
In all cases, try and deal with the primary source of information, don’t rely exclusively on proxies to people: augment or replace proxies with direct involvement whenever possible to get better overall communication.
- Despite adding in multiple layers of system matter experts, teams still build the wrong things
- Requirements take months to generate
- Teams complain about the scarcity of information in the work they’re trying to complete
- Development and QA teams constantly feud over what a particular requirement means and how it should be implemented
- Direct access to information enables faster, and better, decisions
- Direct access to users enables teams to understand how the software works, and how it’s broken
- Fewer layers means faster access and less interpreted/misunderstood information
- Information power brokers are pushed aside and real work can progress
- Developers have full, unfettered access to product users (50pts)
- Team has full, unfettered access to managers and executives when needed (see MindTheGap) (20pts)
- Executives have full, unfettered access to team when needed (see TeamInterruptionProtocol) (20pts)
- Team has occasional access to managers and executives when needed (5pts)
- Developers have occasional access to product users (5pts)
- Use schedule or budget alone to rate product/project/organization quality (-20pts)
- Team has no access to managers or executives when needed (-20pts)
- Executives rely on managers instead of communicating with the team when needed (see TeamInterruptionProtocol) (-20pts)
- Developers have no access to product users (-50pts)
✓ Critical ❑ Helpful ❑ Experimental
Overview of steps to first adopt this practice. Please read detailed explanation below for important information.
- Take an inventory of all of your proxies
- Ask others for help finding proxies you may not have thought of
- Prioritize your identified proxies basd upon their impact or the importance you currently rely on the proxy for information
- Start going through your proxies one at a time, and find ways to eliminate the proxy in favor of a relationship with the person or people represented by the proxy
- How did you do? If you did this well, your information should be clearer and you should have a more accurate picture of where you are in relation to your goals
What Does it Look like?
First off, what is a proxy? In this context, we mean that an analyst is a proxy for a user; a manager is a proxy to an executive; a manager is a proxy to development team members. While these roles may be necessary and useful, don’t rely on the proxy exclusively.
In GROWS, development teams have direct access to users. Now, depending on your organization, you might still have product developers in place to collect and filter information, but that does not replace direct user involvement.
Team members can take turns going into the field and shadowing users as they perform actual work. Key users answer questions about workflows. When developers and QA disagree about something, both product developers and users provide the answer.
- No one on your teams has ever met a user
- No one on your team has talked to a user in the last month
- A user has never attended your team’s demos (even virtually)
- All user contact is forbidden and information is routed through a specific set of proxies
- Teams complain about not getting information when they need it
- Teams have no idea how users work with the product
How To Fail Spectacularly
- Relying on spreadsheets and reports instead of person-to-person communication
- Hiding developers from users, and vice-versa
- Setting up a customer feedback program, then hiding the results
- Polling users for feedback, then ignoring the results
←Prev (Three Track Attack)(Measure Actuals) Next→