%% Last Updated: - [[2021-02-17]] - [[2020-09-06]] - [[2020-09-05]] Related: - [[Design]] [[Productivity]] [[Software Development]] %% A list of terminology specific to [[Shape Up]]. ### appetite - The amount of time that the team as a whole is willing to [[Shape Up Terminology#^b32489|bet]] on a piece of [[Shape Up Terminology#^6fec33|shaped work]] for. - "How much time do we want to spend on this?" instead of "How long will it take to finish this? - Appetite is the real constraint. ### bet ^b32489 - v. To commit to building a piece of [[Shape Up Terminology#^6fec33|shaped work]] that has been [[Shape Up Terminology#^c751d3|pitched]]. - n. An agreement to pursue a project for a limited time with the expectation of a payoff (a deliverable feature) but still with the risk of getting nothing in return (nondelivery). - Emphasizes the risk component of any commitment to work. - Why "betting"? - Bets have a payout, unlike planning. - Bets are commitments. - A smart bet has a cap on the downside. At worst, we stand to lose only 6 weeks. ### betting table ^40b3e5 - A meeting attended by management or senior staff to decide on which pitches to [[Shape Up Terminology#^b32489|bet]] on. The bets they place determine the [[Shape Up Terminology#^6fec33|shaped work]] that gets built in the next cycle. - Every pitch is a potential bet. It is held during a cool-down. ### circuit breaker - A metaphorical switch that turns off all power, signifying that work left unfinished after a cycle does not automatically get an extension by default. Instead, that work needs to be reshaped into a pitch and pitched as a new bet on the betting table. - The idea that if a six-week cycle ends and a team don't finish the work, they don't get an extension. Not having a finished product means something went wrong with the shaping, so the idea (if it's worthwhile) will need to get reshaped and be pitched again at a later time. ### cleanup mode ^850e87 - Useful right before releasing a product, and it's a free-for-all. It's closest to the bug smash idea. ### cool-down ^eaca83 - A cool-down is a two-week period after a cycle where the team have unstructured work, leaving them free to address bugs or other everyday activities. ### cycle ^d033e0 - A timeboxed [[Sprint]] of work on predetermined [[Shape Up Terminology#^b32489|bet]]. - In [[Shape Up Terminology#^6a4cda|production mode]]: - Big batch: 6 weeks - Small batch: 1-2 weeks - Teams assigned to small batches do several small-batch [[Shape Up Terminology#^b32489|bet]] at a time in remain in sync with the rest of the team ### [[Hill Charts|hill chart]] - Way to show project progress based on the amount of inherent unknowns left to chart for each [[Shape Up Terminology#^b8516a]]. ### pitch ^c751d3 A proposal to [[Shape Up Terminology#^b32489|bet] on previously [[Shape Up Terminology#^6fec33|shaped work]] for the next [[Shape Up Terminology#^d033e0|cycle]]. ### production mode ^6a4cda The normal state of building new features or addressing other issues as [[Shape Up Terminology#^6fec33|shaped work]]. ### R&D mode or spike ^fd5dce A type of cycle in which no payout is expected at the end; instead, the goal of this cycle is to explore and gather information about an idea that cannot yet be shaped to be built. ### scope ^b8516a A piece of demo-able work that might not have all the functionality, but does have both back-end and front-end elements integrated. ![[Shape Up: Stop Running in Circles and Ship Work that Matters#^918be5]] ![[Shape Up: Stop Running in Circles and Ship Work that Matters#^62782c]] ### scope hammering Being vigilant about not allowing [[scope creep]] and keeping the boundaries of [[Shape Up Terminology#^6fec33|shaped work]] narrow. ### scope map A scope map takes the boundaries set during [[Shaping work (Shape Up)|shaping]] and fills it in with the different [[Shape Up Terminology#^b8516a|scopes]] necessary to complete the cycle. The scope map is added to as more parts of the work become known. ![Drawing: the same outline now divided with boundary lines like states on a map. The regions are labeled: Field on Form, Preset Locations, Migrate Events, and Display on List.](https://basecamp.com/assets/books/shapeup/3.3/map_scopes-ef077052fd1354c32a3b98ca4374e5acdec4854dd25f2f9144681e931acb6ef4.png) ### shaped work ^6fec33 Work that has undergone the [[Shaping work (Shape Up)|shaping]] process and is sufficiently thought-through and narrow so as to be made into a [[Shape Up Terminology#^c751d3|pitch]] or be built. ### uphill/downhill ^d772a6 adj. Describes where a piece of work is on a [[Hill Charts|hill]]. _Uphill_ means that the unknowns inherent in the work have not yet been fully explored, and _downhill_ means that most of what the work entails has been identified and it's just a matter of building the pieces.