Search by property

Jump to: navigation, search

This page provides a simple browsing interface for finding entities described by a property and a named value. Other available search interfaces include the page property search, and the ask query builder.

Search by property

A list of all pages that have property "So" with value "Document a membrane as a container for self-organization". Since there have been only a few results, also nearby values are displayed.

Showing below up to 26 results starting with #1.

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)


List of results

  • Ambiguity test  + (Count the number of words that are potentially ambiguous, and collect and compare interpretations.)
  • Habit of changing habits  + (Create a habit of changing habits.)
  • Product backlog  + (Create a single ordered list of items to do, with crystal clear acceptance criteria.)
  • Definition of done  + (Create and evolve a clear list of criteria that demonstrate an item's readiness for the next step.)
  • Babushka of value  + (Create and groom an ever evolving minimal set of quality filters in a value stream.)
  • Release burndown chart  + (Create and maintain a chart that tracks the burndown of story points of each sprint.)
  • Beauty of constraints  + (Create self-imposed constraints.)
  • Unity of purpose  + (Create, foster and communicate a single unity of purpose, a yearning for the sea.)
  • Wiki  + (Cultivate a open place where everyone can contribute and improve a shared document.)
  • Question carousel  + (Cultivate the art of asking good and effective questions.)
  • Sense of urgency  + (Describe and communicate a genuine, real and clear opportunity in ways that people can relate to and that draws on people’s feelings)
  • Aligning pivot plan  + (Design, evolve, and drill a number of tactical plans that kick in when needed.)
  • Belief statement  + (Distill and publish a believe statement and act accordingly.)
  • Planning poker  + (Do one or two rounds of planning poker.)
  • Team charter  + (Document a membrane as a container for self-organization)
  • Andon cord  + (Draw attention to human errors or malfunctioning equipment as they occur. Execute the emergency procedure, stop the line, swarm the problem.)
  • Main effort  + (Establish a main effort, clear victory criteria, and have one unit lead its implementation. Subordinate all work to the main effort.)
  • Ka-ching a day makes product owner hurray  + (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.)
  • Stable team  + (Evolve stable, resilient, co-located, and multi-disciplinary development teams and let no one touch it.)
  • Disagree and commit  + (Express your disagreement while committing to support the implementation of the selected option.)
  • Retrospective prime directive  + (Facilitate a retrospective, opening with the prime directive that everyone did the best job they could.)
  • U-curve  + (Find the sweet spot for best batch sizes by balancing the holding cost with the economy of scale.)
  • Daily clean code  + (Fix all bugs in less than a day. Aim to have a completely clean base of code at the end of every day.)
  • First things first  + (Focus maximum effort to get the top priority ready to release and celebrate yet another ka-ching moment.)
  • Tipping point leadership  + (Focus on three factors of disproportionate influence in motivating employees—kingpins, fishbowl management, and atomization.)
  • Tribal learning  + (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.)
  • Spectrum of views  + (Form subgroups that listen to each other’s conversations to discover differences that can be integrated.)
  • Six plus or minus one  + (Foster teams of six plus or minus one so they excel in communication saturation and collective team knowledge.)
  • Pen storm  + (Generate a number of ideas and leave some white space in between for the others to embellish and augment.)
  • 3 × 3 rule  + (Get any three levels and any three functions into the same conversation on any issue of mutual concern.)
  • Whole elephant  + (Get out all the issues, find out what matters most, and only then explore any solutions and directions to resolve one or more issues.)
  • Time to express yourself  + (Give people time to come to grips with their feelings before focusing on action.)
  • Agile architect  + (Grow a system, don't build it.)
  • Agile team dōjō  + (Guide and coach the team through an intense weekly training program.)
  • Lazy finish  + (Hand-off the request to another party where it can later be retrieved and completed.)
  • Daily standup  + (Have a short inspect-adapt meeting, that lasts at most 15 minutes, every day.)
  • Focus on focus off  + (Have everyone compare words like inquiry/advocacy, dialogue/debate, conversation/argument, their meaning, and how they impact behavior.)
  • Back brief  + (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.)
  • One service deserves another  + (Have the product owner crew decide which build squad will pull this item into their sprint backlog.)
  • Allies experience differences  + (Identify differences, make them heard, involve everyone, create subgroups exploring and integrating the differences.)