Property:So
Jump to navigation
Jump to search
So Is a property of type String.
W
Control your response to a situation and contain your “hot buttons”. +
H
Create a habit of changing habits. +
P
Create a single ordered list of items to do, with crystal clear acceptance criteria. +
D
Create and evolve a clear list of criteria that demonstrate an item's readiness for the next step. +
R
Create and maintain a chart that tracks the burndown of story points of each sprint. +
U
Create, foster and communicate a single unity of purpose, a yearning for the sea. +
W
Q
Cultivate the art of asking good and effective questions. +
S
Describe and communicate a genuine, real and clear opportunity in ways that people can relate to and that draws on people’s feelings +
P
Do one or two rounds of planning poker. +
T
Document a membrane as a container for self-organization +
M
Establish a main effort, clear victory criteria, and have one unit lead its implementation. Subordinate all work to the main effort. +
K
Every day, focus on getting something ready to use for someone else. Set a work in progress limit to increase the number of daily ka-ching moments. +
S
Evolve stable, resilient, co-located, and multi-disciplinary development teams and let no one touch it. +
D
Express your disagreement while committing to support the implementation of the selected option. +
R
Facilitate a retrospective, opening with the prime directive that everyone did the best job they could. +
U
Find the sweet spot for best batch sizes by balancing the holding cost with the economy of scale. +
D
Fix all bugs in less than a day. Aim to have a completely clean base of code at the end of every day. +
F
Focus maximum effort to get the top priority ready to release and celebrate yet another ka-ching moment. +
T
Focus on three factors of disproportionate influence in motivating employees—kingpins, fishbowl management, and atomization. +
Form a triad of tribal leadership based on aligned values where each person is responsible for the quality of the relationship between the other two. +
S
Form subgroups that listen to each other’s conversations to discover differences that can be integrated. +
Foster teams of six plus or minus one so they excel in communication saturation and collective team knowledge. +
P
Generate a number of ideas and leave some white space in between for the others to embellish and augment. +
W
Get out all the issues, find out what matters most, and only then explore any solutions and directions to resolve one or more issues. +
T
Give people time to come to grips with their feelings before focusing on action. +
L
Hand-off the request to another party where it can later be retrieved and completed. +
D
Have a short inspect-adapt meeting, that lasts at most 15 minutes, every day. +
F
Have everyone compare words like inquiry/advocacy, dialogue/debate, conversation/argument, their meaning, and how they impact behavior. +
O
Have the product owner crew decide which build squad will pull this item into their sprint backlog. +
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. +