Property:So
Jump to navigation
Jump to search
So Is a property of type String.
P
Capture your product vision in a concise and relevant template and use it consistently and repeatedly in all your communication. +
O
S
Collaboratively attack the topic in a logical sequence, using all six hats. +
H
Collect both strategic, tactical and operational information in a SMART way on a single A3. +
B
Collect everyone’s goals, desires, ideologies, soul profiles and forge a big, hairy, agressive goal. Pursue it. +
R
Collect the core interests of both parties and turn them into mutually agreed principles or ‘rights’. Ensure they resonate with each party's values. +
W
Conduct a small and focused workshop that brings out the best in all. +
Control your response to a situation and contain your “hot buttons”. +
A
Count the number of words that are potentially ambiguous, and collect and compare interpretations. +
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. +
B
Create and groom an ever evolving minimal set of quality filters in a value stream. +
R
Create and maintain a chart that tracks the burndown of story points of each sprint. +
B
Create self-imposed constraints. +
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 +
A
Design, evolve, and drill a number of tactical plans that kick in when needed. +
B
Distill and publish a believe statement and act accordingly. +
P
Do one or two rounds of planning poker. +
T
Document a membrane as a container for self-organization +
A
Draw attention to human errors or malfunctioning equipment as they occur. Execute the emergency procedure, stop the line, swarm the problem. +
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. +
3
Get any three levels and any three functions into the same conversation on any issue of mutual concern. +
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. +
A
Grow a system, don't build it. +
Guide and coach the team through an intense weekly training program. +
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. +
B
Have others brief what they think has just been said back to the sender so you can check if the intent is well understood; clarify when needed. +
O
Have the product owner crew decide which build squad will pull this item into their sprint backlog. +
A
Identify differences, make them heard, involve everyone, create subgroups exploring and integrating the differences. +
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. +