{"id":25932,"date":"2021-04-14T10:42:27","date_gmt":"2021-04-14T10:42:27","guid":{"rendered":"https:\/\/www.process.st\/templates\/shape-up-process-building\/"},"modified":"2024-02-29T03:48:43","modified_gmt":"2024-02-29T03:48:43","slug":"shape-up-process-building","status":"publish","type":"post","link":"https:\/\/www.process.st\/templates\/shape-up-process-building\/","title":{"rendered":"Shape Up Process: Building"},"content":{"rendered":"<section id=\"introduction-to-building\">\n<h2>Introduction to building:<\/h2>\n<div class=\"image-content\">\n<figure> <a href=\"https:\/\/www.process.st\/templates\/wp-content\/uploads\/2024\/02\/ipOxDTYd3HYuCkjEVHFLzg.png\" alt=\"Shape Up Process: Building\" target=\"_blank\" rel=\"noopener\"> <img decoding=\"async\" loading=\"lazy\" src=\"https:\/\/www.process.st\/templates\/wp-content\/uploads\/2024\/02\/ipOxDTYd3HYuCkjEVHFLzg.png\"> <\/a><figcaption>\n     Shape Up Process: Building<br \/>\n<\/figcaption><\/figure>\n<\/div>\n<div class=\"text-content\">\n<p><span style=\"text-decoration: underline;\">Welcome to Process Street's Shape Up Processes template pack. <\/span><\/p>\n<p>This pack will take you through the three key phases of Shape Up's development methodology:&nbsp;<\/p>\n<ol>\n<li><strong>Shaping<\/strong><\/li>\n<li><strong>Betting<\/strong><\/li>\n<li><strong>Building<\/strong><\/li>\n<\/ol>\n<p class=\"style-success\"><strong>This template focuses on the last phase, building. The key concepts for this process include:&nbsp;<\/strong><\/p>\n<ul>\n<li>Breaking projects apart into scopes<\/li>\n<li>Downhill versus uphill work and communicating about unknowns<\/li>\n<li>Scope hammering to separate must-haves from nice-to-haves<\/li>\n<\/ul>\n<p class=\"style-info\"><strong>The building phase is where you turn the shaped pitch into something shipable.<\/strong> Start this <em>Shape Up Process: Building<\/em> checklist by creating a new project and adding the team to it. Be sure to make sure each team member has access to the shaped pitch.<\/p>\n<\/div>\n<\/section>\n<section id=\"enter-basic-information\">\n<h2>Enter basic information<\/h2>\n<div class=\"text-content\">\n<p class=\"style-success\">Use the form fields below to <strong>record basic information about yourself<\/strong> and <strong>the project<\/strong>.<\/p>\n<\/div>\n<div class=\"text-field-content form-field-content\">\n<div class=\"form-group\"> <label> Your full name <\/label><br \/>\n<input type=\"text\" placeholder=\"Something will be typed here...\" disabled=\"\" class=\"form-control\"><\/div>\n<\/div>\n<div class=\"text-field-content form-field-content\">\n<div class=\"form-group\"> <label> Project name <\/label><br \/>\n<input type=\"text\" placeholder=\"Something will be typed here...\" disabled=\"\" class=\"form-control\"><\/div>\n<\/div>\n<div class=\"date-field-content form-field-content\">\n<div class=\"form-group\"> <label> Today's date <\/label><\/p>\n<div class=\"date-container\"> <button type=\"button\" disabled=\"\" class=\"btn btn-default\"> <i class=\"fa fa-calendar btn-icon\"><\/i> Date will be set here <\/button><\/div>\n<\/div>\n<\/div>\n<\/section>\n<section id=\"add-team-members\">\n<h2>Add team members<\/h2>\n<div class=\"text-content\">\n<p class=\"style-success\"><strong>Add the team members who will be working on the building of this project.&nbsp;<\/strong><\/p>\n<\/div>\n<\/section>\n<section id=\"get-one-piece-done\">\n<h2>Get one piece done:<\/h2>\n<div class=\"text-content\">\n<p class=\"style-info\"><strong>The way to figure out what needs to be done is to start doing real work.<\/strong> Start by building something that is central to the project while still small enough to be done end-to-end\u2014with working UI and working code\u2014in a few days.<\/p>\n<p class=\"style-danger\"><strong>There are three criteria to think about when choosing what to build first:<\/strong><\/p>\n<p><strong>It should be the&nbsp;core<\/strong>. Without it, the other work wouldn\u2019t mean anything.&nbsp;<\/p>\n<p><strong>It should be<\/strong>&nbsp;<strong>small<\/strong>. If the first piece of work isn\u2019t small enough, there isn\u2019t much benefit to carving it off from the rest. The point is to finish something meaningful in a few days and build momentum\u2014to have something real to click on that shows the team is on the right track.<\/p>\n<p><strong>It should be<\/strong>&nbsp;<strong>novel<\/strong>. If two parts of the project are both core and small, prefer the thing that you\u2019ve never done before.<\/p>\n<\/div>\n<\/section>\n<section id=\"pick-off-a-slice-of-the-project\">\n<h2>Pick off a slice of the project<\/h2>\n<div class=\"text-content\">\n<p><strong>Choose the piece to work on.&nbsp;<\/strong><\/p>\n<p class=\"style-info\">Think of projects in two layers: front-end and back-end, design and code. Technically speaking there are more layers than this, these two are the primary integration challenge in most projects.<\/p>\n<p>The point is to create a back-and-forth between design and programming on the same piece of the product. Instead of one big hand-off, take turns layering in affordances, code, and visual styling. Step by step, click through the real working feature-in-progress to judge how it\u2019s coming and what to do next.<\/p>\n<p class=\"style-danger\">Each slice or piece of work integrates front-end and back-end tasks. This allows you to finish one slice of the actual project and definitively move on. That\u2019s better than having lots of pieces that\u2014fingers crossed\u2014are supposed to come together by the end of the cycle.<\/p>\n<p><span style=\"background-color: #fce8a7;\"><strong>Use the form fields below to summarize what you've chosen to work on and why.<\/strong><\/span><\/p>\n<\/div>\n<div class=\"textarea-field-content form-field-content\">\n<div class=\"form-group\"> <label> Summarize the chosen slice <\/label> <textarea placeholder=\"Something will be typed here...\" rows=\"3\" disabled=\"\" class=\"form-control\"><\/textarea><\/div>\n<\/div>\n<div class=\"textarea-field-content form-field-content\">\n<div class=\"form-group\"> <label> Reason for choosing the slice <\/label> <textarea placeholder=\"Something will be typed here...\" rows=\"3\" disabled=\"\" class=\"form-control\"><\/textarea><\/div>\n<\/div>\n<\/section>\n<section id=\"map-the-scopes\">\n<h2>Map the scopes:<\/h2>\n<div class=\"image-content\">\n<figure> <a href=\"https:\/\/www.process.st\/templates\/wp-content\/uploads\/2024\/02\/jq9czk0v3bKTscYasgVH6w.png\" alt=\"Shape Up: Example of a scope map\" target=\"_blank\" rel=\"noopener\"> <img decoding=\"async\" loading=\"lazy\" src=\"https:\/\/www.process.st\/templates\/wp-content\/uploads\/2024\/02\/jq9czk0v3bKTscYasgVH6w.png\"> <\/a><figcaption>\n     Shape Up: Example of a scope map<br \/>\n<\/figcaption><\/figure>\n<\/div>\n<div class=\"text-content\">\n<p>The integrated pieces or slices of the project are called scopes.&nbsp;<\/p>\n<p><code>What is a scope?<\/code><\/p>\n<p class=\"style-info\"><strong>Scopes:<\/strong> Parts of the project that can be built, integrated, and finished independently of the rest of the project. You <strong>break the overall scope (singular) of the project into separate scopes (plural)<\/strong> that can be finished independently of each other.&nbsp;<\/p>\n<p>The scopes reflect the meaningful parts of the problem that can be completed independently and in a short period of time\u2014a few days or less. They are bigger than tasks but much smaller than the overall project. The header image provides an example of a completed scope map.&nbsp;<\/p>\n<\/div>\n<\/section>\n<section id=\"upload-scope-map\">\n<h2>Upload scope map<\/h2>\n<div class=\"text-content\">\n<p><strong>Define and track the scopes as to-do lists.<\/strong> Each scope corresponds to a list name. Then any tasks for that scope go in that list.<\/p>\n<p class=\"style-success\">To deal with different kinds of tasks and scopes that will come up Shape Up suggests using the following techniques.&nbsp;<\/p>\n<p><strong>Layer cakes:<\/strong> Most software projects require some UI design and a thin layer of code below. Think of a database app where all you need to do is enter information, save it, and display it back. You can judge the work by UI surface area because the back-end work is thin and evenly distributed.&nbsp;<a href=\"https:\/\/basecamp.com\/shapeup\/3.3-chapter-12#layer-cakes\" rel=\"nofollow noopener\" target=\"_blank\"><\/a><\/p>\n<p><strong>Icebergs:<\/strong> If there&nbsp;is significantly more back-end work than UI work or vice versa. For example, a new feature that only requires submitting a form could require very complex business logic to return the right answer. This kind of work is like an iceberg.<\/p>\n<p><strong>Chowder<\/strong>: <a href=\"https:\/\/basecamp.com\/shapeup\/3.3-chapter-12#chowder\" rel=\"nofollow noopener\" target=\"_blank\"><\/a>There are almost always a couple of things that don\u2019t fit into a scope. In this case, allow yourself a \u201cChowder\u201d list for loose tasks that don\u2019t fit anywhere. But always keep a skeptical eye on it. If it gets longer than three to five items, something is fishy and there\u2019s probably a scope to be drawn somewhere.<\/p>\n<p><strong>Upload\/link the scope map in the form fields below.<\/strong><\/p>\n<\/div>\n<div class=\"file-field-content form-field-content\">\n<div class=\"form-group\"> <label> Upload scope map <\/label><\/p>\n<div class=\"file-container\"> <button type=\"button\" disabled=\"\" class=\"btn btn-default\"> <i class=\"fa fa-upload btn-icon\"><\/i> File will be uploaded here <\/button><\/div>\n<\/div>\n<\/div>\n<\/section>\n<section id=\"show-progress\">\n<h2>Show progress:<\/h2>\n<div class=\"image-content\">\n<figure> <a href=\"https:\/\/www.process.st\/templates\/wp-content\/uploads\/2024\/02\/o2BxdTIXy84ajgKWg85KCw.png\" alt=\"Shape Up: Hill diagram\" target=\"_blank\" rel=\"noopener\"> <img decoding=\"async\" loading=\"lazy\" src=\"https:\/\/www.process.st\/templates\/wp-content\/uploads\/2024\/02\/o2BxdTIXy84ajgKWg85KCw.png\"> <\/a><figcaption>\n     Shape Up: Hill diagram<br \/>\n<\/figcaption><\/figure>\n<\/div>\n<div class=\"text-content\">\n<p>To show the progress of a project without getting bogged down counting tasks and making numerical estimates Shape Up relies on the hill diagram.&nbsp;<\/p>\n<p><code>What is a hill diagram?&nbsp;<\/code><\/p>\n<p class=\"style-info\"><strong>Hill diagram: <\/strong>A diagram, shaped like a hill, used to show the progress of projects. Every piece of work has two phases. First, there\u2019s the uphill phase where the individual is figuring out what approach to take\/what they\u2019re going to do. Then, once you can see all the work involved, there\u2019s the downhill phase of execution.<\/p>\n<p>The following task asks you to create a hill diagram to show the progress of the project and the scope's status.&nbsp;<\/p>\n<\/div>\n<\/section>\n<section id=\"create-hill-diagram\">\n<h2>Create hill diagram<\/h2>\n<div class=\"image-content\">\n<figure> <a href=\"https:\/\/www.process.st\/templates\/wp-content\/uploads\/2024\/02\/pOgZbcAXo51r1rOPlHxInQ.png\" alt=\"Shape Up: Scopes on the hill\" target=\"_blank\" rel=\"noopener\"> <img decoding=\"async\" loading=\"lazy\" src=\"https:\/\/www.process.st\/templates\/wp-content\/uploads\/2024\/02\/pOgZbcAXo51r1rOPlHxInQ.png\"> <\/a><figcaption>\n     Shape Up: Scopes on the hill<br \/>\n<\/figcaption><\/figure>\n<\/div>\n<div class=\"text-content\">\n<p><strong>Combine the hill with the concept of scopes to create a hill diagram.&nbsp;<\/strong><\/p>\n<p class=\"style-info\">The scopes give you the language for the project (\u201cLocate,\u201d \u201cReply\u201d) and the hill describes the status of each scope (\u201cuphill,\u201d \u201cdownhill\u201d). To see the status of the scopes,&nbsp; plot each one as a different color on the hill.&nbsp;<\/p>\n<p><span style=\"background-color: #fce8a7;\">Use the form fields below to <strong>upload\/link your hill diagram to show progress.<\/strong><\/span><\/p>\n<\/div>\n<div class=\"file-field-content form-field-content\">\n<div class=\"form-group\"> <label> Upload hill diagram <\/label><\/p>\n<div class=\"file-container\"> <button type=\"button\" disabled=\"\" class=\"btn btn-default\"> <i class=\"fa fa-upload btn-icon\"><\/i> File will be uploaded here <\/button><\/div>\n<\/div>\n<\/div>\n<\/section>\n<section id=\"share-progress\">\n<h2>Share progress<\/h2>\n<div class=\"text-content\">\n<p><strong>Share the hill diagram and show progress of the project.&nbsp;<\/strong><\/p>\n<p class=\"style-success\">Use the \"Members\" field below to <strong>assign the next task to the Manager(s)<\/strong>. This will let them know they can <strong>view, and approve the hill diagram<\/strong> in the following task.&nbsp;<\/p>\n<\/div>\n<\/section>\n<section id=\"approval\">\n<h2>Approval:<\/h2>\n<div class=\"approval-content\">\n<div class=\"header\">\n<div class=\"list-title\">\n    Will be submitted for approval:<\/div>\n<\/div>\n<div class=\"approval-rule-subject-tasks-list\">\n<ul class=\"list\">\n<li>\n<div class=\"approval-rule-subject-tasks-list-item\">\n<div class=\"item\">\n<div class=\"container\"> <span class=\"title\">Create hill diagram<\/span><\/p>\n<div class=\"body\">\n         Will be submitted<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/li>\n<\/ul>\n<\/div>\n<\/div>\n<\/section>\n<section id=\"decide-when-to-stop\">\n<h2>Decide when to stop:<\/h2>\n<div class=\"text-content\">\n<p class=\"style-warning\">Recall that the six-week bet has a&nbsp;<code>circuit breaker<\/code>\u2014if the work doesn\u2019t get done, the project doesn\u2019t happen. Having <strong>a fixed deadline motivates you to ask questions about what you're willing to trade-off and to limit motivations.<\/strong>&nbsp;<\/p>\n<p>Having a variable scope enables you to act on these questions. By chiseling and hammering the scope down, you can stay focused on the things you need to do to ship something effective that you can be proud of.<\/p>\n<p class=\"style-danger\">The aim is to actively make trade-offs and question the scope instead of cramming and pushing to finish tasks.<\/p>\n<p>The following tasks will <strong>help you decide when to stop<\/strong> and will <strong>help you hammer the scope of your project<\/strong>.&nbsp;<\/p>\n<\/div>\n<\/section>\n<section id=\"hammer-the-scope\">\n<h2>Hammer the scope<\/h2>\n<div class=\"text-content\">\n<p><strong>Hammer the scope.<\/strong><\/p>\n<p class=\"style-info\">People often talk about \u201ccutting\u201d scope. Shape Up use an even stronger word\u2014<code>hammering<\/code>\u2014to reflect the power and force it takes to repeatedly bang the scope so it fits in the time box.<\/p>\n<p><span style=\"background-color: #fce8a7;\">As you come up with <strong>things to fix, add, improve, or redesign<\/strong> during a project, <strong>ask<\/strong> yourselves <strong>the following questions<\/strong>. Tick off the list as you go.<\/span><\/p>\n<\/div>\n<div class=\"multi-select-content form-field-content\">\n<ul class=\"items\">\n<li class=\"item\">\n<div class=\"step-number-container\">\n<div class=\"step-number\">\n       1<\/div>\n<\/div>\n<div class=\"step-checkbox-container\">\n<div class=\"step-checkbox\"><\/div>\n<\/div>\n<div class=\"item-name-static\">\n      Is this a \u201cmust-have\u201d for the new feature?<\/div>\n<\/li>\n<li class=\"item\">\n<div class=\"step-number-container\">\n<div class=\"step-number\">\n       2<\/div>\n<\/div>\n<div class=\"step-checkbox-container\">\n<div class=\"step-checkbox\"><\/div>\n<\/div>\n<div class=\"item-name-static\">\n      Could we ship without this?<\/div>\n<\/li>\n<li class=\"item\">\n<div class=\"step-number-container\">\n<div class=\"step-number\">\n       3<\/div>\n<\/div>\n<div class=\"step-checkbox-container\">\n<div class=\"step-checkbox\"><\/div>\n<\/div>\n<div class=\"item-name-static\">\n      What happens if we don\u2019t do this?<\/div>\n<\/li>\n<li class=\"item\">\n<div class=\"step-number-container\">\n<div class=\"step-number\">\n       4<\/div>\n<\/div>\n<div class=\"step-checkbox-container\">\n<div class=\"step-checkbox\"><\/div>\n<\/div>\n<div class=\"item-name-static\">\n      Is this a new problem or a pre-existing one that customers already live with?<\/div>\n<\/li>\n<li class=\"item\">\n<div class=\"step-number-container\">\n<div class=\"step-number\">\n       5<\/div>\n<\/div>\n<div class=\"step-checkbox-container\">\n<div class=\"step-checkbox\"><\/div>\n<\/div>\n<div class=\"item-name-static\">\n      How likely is this case or condition to occur?<\/div>\n<\/li>\n<li class=\"item\">\n<div class=\"step-number-container\">\n<div class=\"step-number\">\n       6<\/div>\n<\/div>\n<div class=\"step-checkbox-container\">\n<div class=\"step-checkbox\"><\/div>\n<\/div>\n<div class=\"item-name-static\">\n      When this case occurs, which customers see it? Is it core\u2014used by everyone\u2014or more of an edge case?<\/div>\n<\/li>\n<li class=\"item\">\n<div class=\"step-number-container\">\n<div class=\"step-number\">\n       7<\/div>\n<\/div>\n<div class=\"step-checkbox-container\">\n<div class=\"step-checkbox\"><\/div>\n<\/div>\n<div class=\"item-name-static\">\n      What\u2019s the actual impact of this case or condition in the event it does happen?<\/div>\n<\/li>\n<li class=\"item\">\n<div class=\"step-number-container\">\n<div class=\"step-number\">\n       8<\/div>\n<\/div>\n<div class=\"step-checkbox-container\">\n<div class=\"step-checkbox\"><\/div>\n<\/div>\n<div class=\"item-name-static\">\n      When something doesn\u2019t work well for a particular use case, how aligned is that use case with our intended audience?<\/div>\n<\/li>\n<\/ul>\n<\/div>\n<\/section>\n<section id=\"decide-whether-to-extend-or-ship\">\n<h2>Decide whether to extend or ship<\/h2>\n<div class=\"text-content\">\n<p><strong>Decide if you will extend the project.&nbsp;&nbsp;<\/strong><\/p>\n<p class=\"style-success\">In very rare cases, you'll need to extend a project. How do you decide when to extend a project and when to let the <strong>circuit-breaker <\/strong>do its thing?<\/p>\n<p>First, the outstanding tasks must be true<strong> must-haves<\/strong> <em>(tasks that must be completed for a scope to be considered done)<\/em> that withstood every attempt to<strong> scope-hammer<\/strong>&nbsp;them.<\/p>\n<p>Second, the outstanding work must be all<strong> downhill <\/strong>(think: hill-diagrams). No unsolved problems; no open questions. Any uphill work at the end of the cycle points to an oversight in the shaping or a hole in the concept.&nbsp;<\/p>\n<p>Even if the conditions are met to consider extending the project, it is still preferred to be disciplined and enforce the<strong> appetite<\/strong>&nbsp;for most projects.<\/p>\n<p><span style=\"background-color: #fce8a7;\">Use the drop-down below to <strong>select<\/strong> whether you <strong>wish to ship or extend the<\/strong> <strong>project<\/strong>.<\/span><\/p>\n<\/div>\n<div class=\"select-field-content form-field-content\">\n<div class=\"form-group\"> <label> Ship or extend project? <\/label> <select disabled=\"\" class=\"form-control\"><option value=\"An option will be selected here\">An option will be selected here<\/option><\/select><\/div>\n<\/div>\n<\/section>\n<section id=\"sources\">\n<h2>Sources:<\/h2>\n<div class=\"text-content\">\n<h4 style=\"text-align: center;\">Sources<\/h4>\n<hr>\n<ul>\n<li><a href=\"https:\/\/basecamp.com\/shapeup\" rel=\"nofollow noopener\" target=\"_blank\">Shape Up: Stop Running in Circles<\/a><br \/>\n<a href=\"https:\/\/basecamp.com\/shapeup\" rel=\"nofollow noopener\" target=\"_blank\">and Ship Work that Matters<\/a><\/li>\n<li><a href=\"https:\/\/www.process.st\/shape-up\/\" rel=\"nofollow noopener\" target=\"_blank\">Process Street: Shape Up vs Scrum: 6 Months to 6 Weeks \u2013 How We Cut Our Dev Cycle 75%<\/a><\/li>\n<li><a href=\"https:\/\/www.process.st\/help\/docs\/getting-started\/\" rel=\"nofollow noopener\" target=\"_blank\">Process Street: Getting Started with Process Street<\/a><\/li>\n<li><a href=\"https:\/\/basecamp.com\/shapeup\/3.1-chapter-10\/\" rel=\"nofollow noopener\" target=\"_blank\">Shape Up: Hand Over Responsibility<\/a><\/li>\n<li><a href=\"https:\/\/basecamp.com\/shapeup\/3.2-chapter-11\/\" rel=\"nofollow noopener\" target=\"_blank\">Shape Up: Get One Piece Done<\/a><\/li>\n<li><a href=\"https:\/\/basecamp.com\/shapeup\/3.3-chapter-12\/\" rel=\"nofollow noopener\" target=\"_blank\">Shape Up: Map the Scopes<\/a><\/li>\n<li><a href=\"https:\/\/basecamp.com\/shapeup\/3.4-chapter-13\/\" rel=\"nofollow noopener\" target=\"_blank\">Shape Up: Show Progress<\/a><\/li>\n<li><a href=\"https:\/\/basecamp.com\/shapeup\/3.5-chapter-14\/\" rel=\"nofollow noopener\" target=\"_blank\">Shape Up: Decide When to Stop<\/a><\/li>\n<li><a href=\"https:\/\/basecamp.com\/shapeup\/3.4-chapter-13\/\" rel=\"nofollow noopener\" target=\"_blank\"><\/a><a href=\"https:\/\/basecamp.com\/shapeup\/3.6-chapter-15\/\" rel=\"nofollow noopener\" target=\"_blank\">Shape up: Move On<\/a>\n<p><a href=\"https:\/\/basecamp.com\/shapeup\/3.4-chapter-13\/\" rel=\"nofollow noopener\" target=\"_blank\"><\/a><\/li>\n<\/ul>\n<\/div>\n<\/section>\n<section id=\"related-checklists\">\n<h2>Related checklists:<\/h2>\n<div class=\"text-content\">\n<h4 style=\"text-align: center;\">Related checklists<\/h4>\n<hr>\n<p><a href=\"https:\/\/www.process.st\/templates\/shape-up-process-shaping\/\" rel=\"nofollow noopener\" target=\"_blank\">Shape Up Process: Shaping<\/a><\/p>\n<p><a href=\"https:\/\/www.process.st\/templates\/shape-up-process-betting\/\" rel=\"nofollow noopener\" target=\"_blank\">Shape Up Process: Betting<\/a><\/p>\n<\/div>\n<\/section>\n","protected":false},"excerpt":{"rendered":"<p>Introduction to building: Shape Up Process: Building Welcome to Process Street's Shape Up Processes template pack. This pack will take you through the three key phases of Shape Up's development methodology:&nbsp; Shaping Betting Building This template focuses on the last phase, building. The key concepts for this process include:&nbsp; Breaking projects apart into scopes Downhill [&hellip;]<\/p>\n","protected":false},"author":3,"featured_media":25933,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"ep_exclude_from_search":false,"cover_icon_emoji":"","cover_icon_url":"","tasks_count":"16","template_description":"Building is the third and final phase of Shape Up's development method, follow this checklist to start building.","template_id":"leHTJ4zxiNffYSJErXZI5Q","task_0":"Introduction to building:","task_slug_0":"introduction-to-building","task_1":"Enter basic information","task_slug_1":"enter-basic-information","task_2":"Add team members","task_slug_2":"add-team-members","task_3":"Get one piece done:","task_slug_3":"get-one-piece-done","task_4":"Pick off a slice of the project","task_slug_4":"pick-off-a-slice-of-the-project","task_5":"Map the scopes:","task_slug_5":"map-the-scopes","task_6":"Upload scope map","task_slug_6":"upload-scope-map","task_7":"Show progress:","task_slug_7":"show-progress","task_8":"Create hill diagram","task_slug_8":"create-hill-diagram","task_9":"Share progress","task_slug_9":"share-progress","task_10":"Approval:","task_slug_10":"approval","task_11":"Decide when to stop:","task_slug_11":"decide-when-to-stop","task_12":"Hammer the scope","task_slug_12":"hammer-the-scope","task_13":"Decide whether to extend or ship","task_slug_13":"decide-whether-to-extend-or-ship","task_14":"Sources:","task_slug_14":"sources","task_15":"Related checklists:","task_slug_15":"related-checklists","task_16":"","task_slug_16":"","task_17":"","task_slug_17":"","task_18":"","task_slug_18":"","task_19":"","task_slug_19":"","task_20":"","task_slug_20":"","task_21":"","task_slug_21":"","task_22":"","task_slug_22":"","task_23":"","task_slug_23":"","task_24":"","task_slug_24":"","task_25":"","task_slug_25":"","task_26":"","task_slug_26":"","task_27":"","task_slug_27":"","task_28":"","task_slug_28":"","task_29":"","task_slug_29":"","task_30":"","task_slug_30":"","task_31":"","task_slug_31":"","task_32":"","task_slug_32":"","task_33":"","task_slug_33":"","task_34":"","task_slug_34":"","task_35":"","task_slug_35":"","task_36":"","task_slug_36":"","task_37":"","task_slug_37":"","task_38":"","task_slug_38":"","task_39":"","task_slug_39":"","task_40":"","task_slug_40":"","task_41":"","task_slug_41":"","task_42":"","task_slug_42":"","task_43":"","task_slug_43":"","task_44":"","task_slug_44":"","task_45":"","task_slug_45":"","task_46":"","task_slug_46":"","task_47":"","task_slug_47":"","task_48":"","task_slug_48":"","task_49":"","task_slug_49":"","task_50":"","task_slug_50":"","task_51":"","task_slug_51":"","task_52":"","task_slug_52":"","task_53":"","task_slug_53":"","task_54":"","task_slug_54":"","task_55":"","task_slug_55":"","task_56":"","task_slug_56":"","task_57":"","task_slug_57":"","task_58":"","task_slug_58":"","task_59":"","task_slug_59":"","task_60":"","task_slug_60":"","task_61":"","task_slug_61":"","task_62":"","task_slug_62":"","task_63":"","task_slug_63":"","task_64":"","task_slug_64":"","task_65":"","task_slug_65":"","task_66":"","task_slug_66":"","task_67":"","task_slug_67":"","task_68":"","task_slug_68":"","task_69":"","task_slug_69":"","task_70":"","task_slug_70":"","task_71":"","task_slug_71":"","task_72":"","task_slug_72":"","task_73":"","task_slug_73":"","task_74":"","task_slug_74":"","task_75":"","task_slug_75":"","task_76":"","task_slug_76":"","task_77":"","task_slug_77":"","task_78":"","task_slug_78":"","task_79":"","task_slug_79":"","task_80":"","task_slug_80":"","task_81":"","task_slug_81":"","task_82":"","task_slug_82":"","task_83":"","task_slug_83":"","task_84":"","task_slug_84":"","task_85":"","task_slug_85":"","task_86":"","task_slug_86":"","task_87":"","task_slug_87":"","task_88":"","task_slug_88":"","task_89":"","task_slug_89":"","task_90":"","task_slug_90":"","task_91":"","task_slug_91":"","task_92":"","task_slug_92":"","task_93":"","task_slug_93":"","task_94":"","task_slug_94":"","task_95":"","task_slug_95":"","task_96":"","task_slug_96":"","task_97":"","task_slug_97":"","task_98":"","task_slug_98":"","task_99":"","task_slug_99":"","footnotes":""},"categories":[40,5,52,58],"tags":[],"class_list":["post-25932","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-design","category-featured","category-management-system","category-product"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/posts\/25932","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/comments?post=25932"}],"version-history":[{"count":0,"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/posts\/25932\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/media\/25933"}],"wp:attachment":[{"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/media?parent=25932"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/categories?post=25932"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/tags?post=25932"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}