Merge branch 'master' into gh-pages

CONTRIBUTORS.txt

@@ -9,4 +9,5 @@ By listing your name below, you indicate agreement to the following:
 * Matt Hornsby
 * Brightspace <brightspace.com>
 * Daniel Steinberg
+* Jay Bazuzi (@JayBazuzi)
 * Alex Kessinger (@voidfiles)

README.md

@@ -19,6 +19,6 @@ Contributing
 
 We love pull requests!
 
-Please make sure you can submit your work for publication under the above license. And add your name to the CONTRIBUTORS.txt as part of your pull request. That way we can thank you and also avoid (some) sticky legal situations.
+Please make sure you can submit your work for publication under the above license. And add your name to the [`CONTRIBUTORS.txt`](CONTRIBUTORS.txt) as part of your pull request. That way we can thank you and also avoid (some) sticky legal situations.
 
-To edit things, you can either edit stages_data.js directly or you can edit in the display. If you edit in the display, there is a little turned-up corner in the lower-left. Click that and you will see a text area. Copy the JS from that into stages_data.js.
+To edit things, you can either edit [`stages_data.js`](stages_data.js) directly or you can edit in the display. If you edit in the display, there is a little turned-up corner in the lower-left. Click that and you will see a text area. Copy the JS from that into [`stages_data.js`](stages_data.js).

stages_data.js

@@ -1,6 +1,6 @@
 function load_data() {
 	return {
-		version: "0.11.3",
+		version: "1.0.0",
 		file_format_version: "2.0.0",
 		levels: {
 			L_TRADITIONAL: {
@@ -2610,15 +2610,23 @@ function load_data() {
 				],
 				obsoletes: [],
 				description: [
-					"bq>. 1-sentence mindset quote goes here",
+					"bq>. If it is not on the one true board, it doesn't exist.",
 					"",
 					"h1. What this is",
 					"",
-					"###. TBD",
+					"There must be no hidden work, i.e. there must be no tasks or activities that team members do without others being aware of it. Additionally, there must be one single place to go that shows all the team's work.",
+					"",
+					"The simplest way to make the work in progress transparent is to have a board, physical or virtual, which represents the workflow that the team follows, reporting all the tasks in progress on the board itself.",
+					"",
+					"Preparing a kanban board is certainly a good starting point.",
 					"",
 					"###. h2. How it helps",
 					"",
-					"###. TBD",
+					"At any time, the team can quickly (visually) have an idea of the status of the activities. By viewing the work in progress, control mechanisms can be enabled on the amount of work in progress, highlighting any bottlenecks.",
+					"",
+					"By making the board visible even outside the team, a real information radiator is created which will allow the team to display the situation of the activities in real time to the outside: those who are interested in the team's activities will be able to consult the board before possibly interrupt the team to ask for information or to take charge of new activities.",
+					"",
+					"Having a board that represents your workflow, updated in real time as much as possible, helps communication within the team. A typical example is that of a team that meets daily to organize the day and does so, physically or virtually, having the board in front of it and moving the tasks contained therein in correspondence with the evolution of the activities.",
 					"",
 					"###. h2. Mindshifts",
 					"",
@@ -2672,7 +2680,7 @@ function load_data() {
 					"",
 					"",
 				],
-				help_needed: ["H_KEY", "H_CORE", "H_REQS", "H_ADV", "H_REVIEW"],
+				help_needed: ["H_CORE", "H_REQS", "H_ADV", "H_REVIEW"],
 				slug: "visible_work",
 				is_key: false,
 			},
@@ -3399,7 +3407,7 @@ function load_data() {
 					"",
 					"No code is considered done until it has been proven. We are starting to apply this thinking to our other work as well, especially habit changes from retros. The call *Prove it!* starts to ring around the halls.",
 					"",
-					"When we way Prove it, however, we currently mean just to prove that you are done and didn't break anything. We don't yet have the maturity to prove whether what we did matters.",
+					"When we say 'Prove it', however, we currently mean just to prove that you are done and didn't break anything. We don't yet have the maturity to prove whether what we did matters.",
 					"",
 					"h2. What it is not",
 					"",
@@ -7863,6 +7871,86 @@ function load_data() {
 				slug: "auto_rollback",
 				is_key: true,
 			},
+			SK_INTENTIONAL_TECHNICAL_DEBT: {
+				name: "Intentional Technical Debt",
+				x: 20,
+				y: 9,
+				level: "L_NO_DEBT",
+				component: "V_REQUIREMENTS",
+				requires: [
+					{
+						skill: "SK_FIX_LEGACY",
+						kind: "IS_REQUIRED",
+					},
+				],
+				obsoletes: [],
+				description: [
+					"bq>. We can occasionally defer refactoring and will come back to it before long.",
+					"",
+					"h1. What this is",
+					"",
+					"###. TBD",
+					"",
+					"###. h2. How it helps",
+					"",
+					"###. TBD",
+					"",
+					"###. h2. Mindshifts",
+					"",
+					"###. TBD",
+					"",
+					"###. h2. Measuring impact",
+					"",
+					"###. If you are doing this well, you should see improvements in:",
+					"",
+					"###. * TBD",
+					"",
+					"###. You may also see:",
+					"",
+					"###. * TBD",
+					"",
+					"###. h2. Side effects",
+					"",
+					"###. TBD (list side effects and practices / stages that can be used to counter them).",
+					"",
+					"###. h1. Acquiring the skill",
+					"",
+					"###. TBD",
+					"",
+					"###. h2. Role during transition",
+					"",
+					"###. TBD",
+					"",
+					"###. h2. Why these prereqs help",
+					"",
+					"###. TBD",
+					"",
+					"###. h2. Recipes to follow",
+					"",
+					"###. TBD",
+					"",
+					"###. h1. Attaining fluency",
+					"",
+					"###. TBD",
+					"",
+					"###. h2. Measuring proficiency",
+					"",
+					"###. TBD",
+					"",
+					"###. h2. Recipes to follow",
+					"",
+					"###. TBD",
+					"",
+					"h2. Further resources",
+					"",
+					"TBD",
+					"",
+					"",
+				],
+				help_needed: ["H_KEY", "H_CORE", "H_REQS", "H_ADV", "H_REVIEW"],
+				slug: "intentional_technical_debt",
+				is_key: false,
+			},
 			SK_HYPOTHESIS_STORIES: {
 				name: "Hypothesis stories",
 				x: 21,
@@ -7874,6 +7962,10 @@ function load_data() {
 						skill: "SK_STORY_CLUSTERING",
 						kind: "IS_REQUIRED",
 					},
+					{
+						skill: "SK_INTENTIONAL_TECHNICAL_DEBT",
+						kind: "IS_HELPFUL",
+					},
 				],
 				obsoletes: [],
 				description: [
@@ -9322,11 +9414,11 @@ function load_data() {
 				],
 				obsoletes: [],
 				description: [
-					"bq>. 1-sentence mindset quote goes here",
+					"bq>. Your code can tell you things that are hard to learn anywhere else.",
 					"",
 					"h1. What this is",
 					"",
-					"###. TBD",
+					"As programmers we develop the ability to detect complexity in software systems. At first we use that to identify and eliminate accidental complexity, but when the code eventually becomes an excellent model of the problem domain, our sensitivity complexity helps us detect and resolve complexity in the problem domain.",
 					"",
 					"###. h2. How it helps",
 					"",

static/css/layout.css

@@ -154,8 +154,8 @@ html, body {
 		.focus_dialog .description_block .edit_button {
 			position: absolute;
 			display: block;
-			right: 0.4em;
-			top: 0.4em;
+			right: 20px;
+			top: -15px;
 			height: 25px;
 			width: 25px;
 			z-index: 1;