Confirmed users
717
edits
Security/Driving: Difference between revisions
m
→Characteristics of a good solution
(Created page with "==How do we effectively prioritize and drive non-feature work?== ===Problem=== While feature work gets a lot of natural attention both internally and externally, an equally impo...") |
|||
| Line 13: | Line 13: | ||
===Characteristics of a good solution=== | ===Characteristics of a good solution=== | ||
Reliable - It results in the outcome (i.e. priorities) we expect | *Reliable - It results in the outcome (i.e. priorities) we expect | ||
Predictive - We can use this mechanism to plan our work | *Predictive - We can use this mechanism to plan our work | ||
Bidirectional - Priorities can't be set in a vacuum or simply driven top-down, but are really a negotiation between the various stakeholders and the developers who will actually do the work | *Bidirectional - Priorities can't be set in a vacuum or simply driven top-down, but are really a negotiation between the various stakeholders and the developers who will actually do the work | ||
Accountable - For a solution to be reliable, predictive and bidirectional people must feel accountable to each other to follow through on requests in a timely manner | *Accountable - For a solution to be reliable, predictive and bidirectional people must feel accountable to each other to follow through on requests in a timely manner | ||
Flexible - Priorities and resources are always in a state of flux, so any solution needs to be predicated on that | *Flexible - Priorities and resources are always in a state of flux, so any solution needs to be predicated on that | ||
===Potential tools/approaches=== | ===Potential tools/approaches=== | ||