Search by property

Jump to navigation Jump to 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 "Publish and pin “even over” statements all over the place.". 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

  • Knowledge injection  + (Inject the required knowledge by hiring an external expert or coach that teaches the team to fish (rather than feeding it a fish).)
  • We don’t make mistakes, we learn  + (Insititutionalize failures.)
  • Kanban  + (Institutionalize reflection and retrospection at all levels and across all disciplines.)
  • Interview & draw  + (Interview the other for five muntes while sketching what you hear, using little or no words.)
  • Cumulative flow diagram  + (Know how to collect and interpret good data from your ‘operating system’.)
  • Intent at least two levels up  + (Know the intent at least two levels up and decide in favor of that general direction. Subordinate everything else.)
  • Liberating constraints  + (Less is more. TImebox the unknown. One guiding goal at a time.)
  • Daily scrum of scrums  + (Let one or more team members from each team have a short, daily meeting.)
  • Just say no  + (Listen to the other's request and provide an understanding “No”, along with its motivation. Find a solution and track progress.)
  • Product portfolio  + (Maintain a product portfolio.)
  • Set of reference stories  + (Maintain a set of baselined reference stories used by all squads as a benchmark for estimation.)
  • Blocker waiting room  + (Make blocked items stand out and move them to a special subcell in the current column, release them as soon as possible and continue working on them before pulling in new work into this column.)
  • Ready to build  + (Make sure any item is fully ready to implement before you start working on it.)
  • Ruthlessly lovingly  + (Make sure concrete and co-evolve clear values, principles and fair conventions and guidelines and uphold them ruthlessly.)
  • Snapshot delivery  + (Make sure that everything that comes out of the build cycle is ready to release so that you effortlessly can deploy it.)
  • Meeting length proportional to agenda  + (Match the gathering’s length to its agenda and goal.)
  • Clarifying go-around  + (Nearly always start with a go-around, giving everyone a chance to suggest a next step.)
  • Story telling  + (Obey the 10 commandments of story telling.)
  • Only move forward  + (Only promote items—never back them up to a previous state—and mark the item blocked until all earlier work completes.)
  • Weighted shortest job first  + (Order the items based on weighted shortest job first.)
  • Foreign glimpses  + (Organize a few short and effective visits to other scrum teams, preferably outside your own company.)
  • Pair working  + (Pair up in a master apprentice way. Or just pair.)
  • Decision spectrum  + (Pick the fastest decision process on the on the scale from “fast” to “well-anchored”.)
  • Speed and adaptability  + (Practice speedy decision-making, agility, and flexibility. Outmaneuver uncertainty.)
  • Don’t just do something, stand there!  + (Prepare and structure gatherings thoroughly and carefully. Invite the right people. Manage yourself.)
  • Even over  + (Publish and pin “even over” statements all over the place.)
  • Yesterday’s weather  + (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.)
  • Decentral control  + (Put decision-makers close to the action and facilitate decentral control so decisions can be made quick and nimble.)
  • Mirror, mirror on the wall  + (Read out loud the three qualities of someone you find totally attractive and someone you find totally irritating.)
  • Product review meeting  + (Reserve time in the agenda to collect some basic feedback about the results of the last sprint.)
  • Ritual dissent and assent  + (Ritualize dissent and assent and consent to harden ideas and proposals and their decisions.)
  • Open space  + (Ritualize regular open space gatherings.)
  • Bun owner  + (Secure an owner of the request at all times. Allow others to pull the request with the owners consent. Follow-up within two days.)
  • Ask for the moon  + (Secure the essential ingredients for a successful agile adoption are in place, like executive support. assessment, cross-functional community, an awesome workplace, training & coaching, chartering, retroprostpectives, and coach-the-coaches.)
  • Sprint goal  + (Set a clear goal for every sprint and only pull in work that helps reach that goal.)
  • Scrum  + (Set up and uphold a small set of roles, rituals, and social objects.)
  • Small group self-management roles  + (Show the self-managing roles—leader, timer, decoder, and reporter—and invite everyone to take the responsibility for themselves.)
  • Teams that finish early accelerate faster  + (Slow down to speed up—create some slack time for process improvement by pulling in just a bit less than yesterday's weather.)
  • Nemawashi  + (Slowly and thouroughly consider and consent all real options, and implement decisions rapidly.)
  • Unique specific tasks  + (Split a work item into unique tasks specific to this work item.)
  • Story splitter  + (Split it into bite-sized chunks that each deliver value.)
  • Strategic product owner  + (Split the single product owner into a strategic product owner and tactical product owner.)
  • Tactical product owner  + (Split the single product owner into a strategic product owner and tactical product owner.)
  • Goldilocks sizer  + (Split too big and join too small items into just the right size to enable flow.)
  • Cruise missile  + (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.)
  • A3 solver  + (Take a single A3 and describe the background, current situation and desired goals, as well as a number of experiments and ways to verify their outcomes.)
  • Refactor code  + (Take every opportunity to eliminate redundant code and rewrite code, making it more elegant.)
  • Mission order  + (Train lateral communication by building teams in which members only need half a word for proper action.)
  • Talking stick  + (Use a token as talking stick. Only the one holding the talking stick can speak.)
  • Improvement board  + (Use an information radiator to list and execute improvement kata towards the definition of awesome.)
  • Elegant checklist  + (Use and evolve a concise and complete checklist detailing what must be done before advancing.)