Property:So
Jump to navigation
Jump to search
So Is a property of type String.
S
Identify the single most important accelerator at the Sprint Retrospective and remove it before the end of the next sprint. +
W
Improve your situational awareness and take big action when weak signals elude danger. +
In each meeting, include all the relevant people who “ARE IN” . +
M
Include all key actors in the dialogue. +
K
Inject the required knowledge by hiring an external expert or coach that teaches the team to fish (rather than feeding it a fish). +
W
Insititutionalize failures. +
K
I
Interview the other for five muntes while sketching what you hear, using little or no words. +
C
Know how to collect and interpret good data from your ‘operating system’. +
I
Know the intent at least two levels up and decide in favor of that general direction. Subordinate everything else. +
L
Less is more. TImebox the unknown. One guiding goal at a time. +
D
Let one or more team members from each team have a short, daily meeting. +
J
Listen to the other's request and provide an understanding “No”, along with its motivation. Find a solution and track progress. +
P
Maintain a product portfolio. +
S
Maintain a set of baselined reference stories used by all squads as a benchmark for estimation. +
R
Make sure any item is fully ready to implement before you start working on it. +
Make sure concrete and co-evolve clear values, principles and fair conventions and guidelines and uphold them ruthlessly. +
S
Make sure that everything that comes out of the build cycle is ready to release so that you effortlessly can deploy it. +
M
Match the gathering’s length to its agenda and goal. +
S
Obey the 10 commandments of story telling. +
O
Only promote items—never back them up to a previous state—and mark the item blocked until all earlier work completes. +
W
Order the items based on weighted shortest job first. +
F
Organize a few short and effective visits to other scrum teams, preferably outside your own company. +
P
Pair up in a master apprentice way. Or just pair. +
D
Pick the fastest decision process on the on the scale from “fast” to “well-anchored”. +
S
Practice speedy decision-making, agility, and flexibility. Outmaneuver uncertainty. +
D
Prepare and structure gatherings thoroughly and carefully. Invite the right people. Manage yourself. +
E
Y
Pull a little bit less, and certainly no more than the running average of the velocities of the last three sprints into the new sprint. +
D
Put decision-makers close to the action and facilitate decentral control so decisions can be made quick and nimble. +
M
Read out loud the three qualities of someone you find totally attractive and someone you find totally irritating. +
P
Reserve time in the agenda to collect some basic feedback about the results of the last sprint. +
R
Ritualize dissent and assent and consent to harden ideas and proposals and their decisions. +
O
Ritualize regular open space gatherings. +
S
Set a clear goal for every sprint and only pull in work that helps reach that goal. +
Show the self-managing roles—leader, timer, decoder, and reporter—and invite everyone to take the responsibility for themselves. +
T
Slow down to speed up—create some slack time for process improvement by pulling in just a bit less than yesterday's weather. +
N
Slowly and thouroughly consider and consent all real options, and implement decisions rapidly. +
U
Split a work item into unique tasks specific to this work item. +
S
Split it into bite-sized chunks that each deliver value. +
Split the single product owner into a strategic product owner and tactical product owner. +
T
Split the single product owner into a strategic product owner and tactical product owner. +
G
Split too big and join too small items into just the right size to enable flow. +
C
Stabilize the specification above a certain threshold, minimize the items lead time, and follow any and all changes in the spec while the item is in progress. +
R
Take every opportunity to eliminate redundant code and rewrite code, making it more elegant. +
M
Train lateral communication by building teams in which members only need half a word for proper action. +
T
Use a token as talking stick. Only the one holding the talking stick can speak. +
I
Use an information radiator to list and execute improvement kata towards the definition of awesome. +
E
Use and evolve a concise and complete checklist detailing what must be done before advancing. +