-
Notifications
You must be signed in to change notification settings - Fork 0
/
Shape-Up-Shaping-vs-Building.html
1 lines (1 loc) · 8.62 KB
/
Shape-Up-Shaping-vs-Building.html
1
<!DOCTYPE html> <html lang="pl"> <head> <meta charset="utf-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <meta name="viewport" content="width=device-width, initial-scale=1" /> <title>Shape Up, Shaping vs Building · Rafal Makara</title> <meta property="og:title" content=" Shape Up, Shaping vs Building "> <meta property="twitter:title" content=" Shape Up, Shaping vs Building "> <meta property="og:description" content=" Shape Up is a product development methodology popularized thanks to Ryan Singer, a Head of Product Strategy at Basecamp. I cover the topics not entirely covered in the book to make your implementation of Shape Up much easier. "> <meta name="twitter:card" content="summary" /> <meta name="twitter:site" content="@rafalmakara" /> <meta property="og:image" content="https://rmakara.github.io/assets/20220328_header.jpg" /> <meta name="twitter:image" content="https://rmakara.github.io/assets/20220328_header.jpg" /> <meta name="description" content=" It is one of the articles in the Shape Up series. For Table of Contents go to: Shape Up, IntroductionSame shit, different namingThe whole process from idea..."> <link rel="icon" href="https://rmakara.github.io//assets/favicon.ico"> <link rel="apple-touch-icon" href="https://rmakara.github.io//assets/apple-touch-icon.png"> <link rel="stylesheet" href="https://rmakara.github.io//assets/core.css"> <link rel="canonical" href="https://rmakara.github.io//Shape-Up-Shaping-vs-Building"> <link rel="alternate" type="application/atom+xml" title="Rafal Makara" href="https://rmakara.github.io/feed.xml" /> </head> <body> <aside class="logo"> <a href="https://rmakara.github.io//"> <img src="https://avatars0.githubusercontent.com/u/1880231?v=4" class="logo-avatar"> </a> <span class="logo-prompt code">Back to Home</span> </aside> <aside> <p class="goodbye"> This blog is no longer maintained <br/><br/> Subscribe to new articles at <a href="https://www.sorryengineering.com/">https://www.sorryengineering.com/</a> </p> </aside> <p class="menu"> <br /><br /> <a href="/">EN Articles</a> | <a href="/pl">PL Articles</a> <br /> <a href="/about">About me</a> | <a href="/help">How can I help?</a> | <a href="https://www.linkedin.com/in/rafalmakara/">My LinkedIn Profile</a> </p> <div id="content"> <article> <div class="divider"></div> <div class="center"> <a class="prev" href="/Shape-Up-When-not-to-follow-the-book">Previous article - Shape Up, When not to follow the book</a> </div> <div class="divider"></div> <h1 class="title">Shape Up, Shaping vs Building</h1> <div class="center"> <time class="code">2022-04-14</time> </div> <div class="divider"></div> <blockquote> <p>It is one of the articles in the Shape Up series. For Table of Contents go to: <a href="https://rmakara.github.io/Shape-Up-Introduction">Shape Up, Introduction</a></p> </blockquote> <h2 id="same-shit-different-naming">Same shit, different naming</h2> <p>The whole process from idea to production might be called differently. Shape Up hasn’t invented the concept of separation, but it made it clear when the crossing line goes in this specific methodology.</p> <p>If we take a look at different ways of producing the software, we may realize such stages:</p> <table> <thead> <tr> <th>Earlier in the process</th> <th>Later in the process</th> </tr> </thead> <tbody> <tr> <td>Analyse & Specify</td> <td>Design & Develop & Test & Release</td> </tr> <tr> <td>Discovery</td> <td>Delivery</td> </tr> <tr> <td>Problem</td> <td>Solution</td> </tr> <tr> <td>Opportunity</td> <td>Solution</td> </tr> <tr> <td>Experiment</td> <td>Invest</td> </tr> <tr> <td>Shaping</td> <td>Building</td> </tr> <tr> <td>Refine</td> <td>Implement</td> </tr> <tr> <td>Discover & Explore & Define</td> <td>Design & Develop & Test & Deliver & Listen</td> </tr> </tbody> </table> <p>No matter the religion, phrases closer to the left-hand side are here to answer <strong>What we will build</strong>, while phrases on the right-hand side focus on <strong>Getting the solution done</strong>.</p> <p>The overlap of these two areas and the feedback frequency may differ depending on the methodology. <strong>The crossing line and its thickness are the main differences between the methodologies</strong>. Think where this line goes for your implementation of Shape Up.</p> <p>It is worth keeping the Shaping & Building naming convention for Shape Up. It will enable people to look for it in a book and give them a sense of working with a new fancy methodology.</p> <h2 id="explicit-separation-of-shaping-and-building">Explicit separation of Shaping and Building</h2> <p>When you start implementing the Shape Up, you need to understand the current state of Shaping and Building within’ your organization.</p> <p>In most companies, the whole Shaping process happens before something goes into Jira. Most engineers have no idea where the stories are coming from. If you want to learn how to visualize these stages, I encourage you to watch <a href="https://www.youtube.com/watch?v=wmaDppWNBJc">Upstream Kanban by Radoslaw Orszewski</a> or review a few images presenting the <a href="https://www.google.com/search?q=double+diamond">Double Diamong method</a>.</p> <p>In Shape Up, we want to raise awareness of the existence of the left-hand-side-phases. To do that, it is worth separating Shaping and Building explicitly. This is the moment to let everyone know what these phrases mean and what they will look like.</p> <p>Make it clear and explain <em>What Shaping means?</em> and <em>What Building means?</em>. Also, share your expectations on <em>Who should participate in which phase?</em>.</p> <h2 id="usage-of-non-shape-up-methods">Usage of non-Shape Up methods</h2> <p>As there are many similarities in Discovery/Shaping - Delivery/Building processes in various methodologies; this is wise to use techniques popularized elsewhere.</p> <p>For both stages, you may use such the methods or at least take some inspiration from:</p> <ul> <li>Personas</li> <li>Competitive Analysis</li> <li>Unfair Advantage</li> <li>Customer Interviews, Surveys, Visits</li> <li>User Journey Mapping</li> <li>User Story Mapping</li> <li>Impact Mapping</li> <li>Event Storming</li> <li>Jobs-to-be-done</li> <li>Opportunity Solution Tree</li> <li>Mind Mapping</li> <li>Prototyping</li> <li>A/B Testing</li> <li>Double Diamond</li> <li>Value Stream Mapping</li> <li>MoSCoW</li> <li>Vertical Slices</li> <li>Increments</li> <li>Kickoff</li> <li>Planning</li> <li>Health Checks</li> <li>RAG Light</li> <li>… and many more.</li> </ul> <p>Just think twice, do not over-complicate, and adjust it to your own needs within’ Shape Up.</p> <h2 id="each-framework-sets-up-the-mindset">Each framework sets up the mindset</h2> <p>And do not get me wrong - while the methodologies bring many similarities, and we may see the same big picture process everywhere - each methodology comes with a specific mindset. Techniques are easily transferable, but choosing a particular workflow framework will strongly influence the thinking around how your team wants to work.</p> <p>Shape Up seems to be the choice for high autonomy, understanding the users, giving trust from the leadership to the teams, and keeping developers creative and proactive. Shape Up may help you build very mature teams made of people willing to build high-quality, meaningful things. Many Mid-Level Developers grown within’ Shape Up will act like Lead Devs grown in Scrum environment.</p> <p>In the following article, we will answer the simple question <em><a href="https://rmakara.github.io/Shape-Up-Who-does-the-Shaping">Who does the Shaping?</a></em>.</p> </article> <div class="divider"></div> <div class="page-navigation code"> <a class="home" href="https://rmakara.github.io//" title="Back to Home">Back to Home</a> <br/><br/> <a class="next" href="/Shape-Up-Who-does-the-Shaping">Next article: Shape Up, Who does the Shaping?</a> </div> </div> <br/> <aside> <p class="goodbye"> This blog is no longer maintained <br/><br/> Subscribe to new articles at <a href="https://www.sorryengineering.com/">https://www.sorryengineering.com/</a> </p> </aside> <div class="footer"> <span class="block">© 2023 Rafal Makara</span> <span class="block"><small></> Powered by <a href="https://jekyllrb.com/">Jekyll</a> and <a href="https://github.com/heiswayi/the-plain">The Plain theme</a>.</small></span> </div> </body> <script> (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){ (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o), m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m) })(window,document,'script','//www.google-analytics.com/analytics.js','ga'); ga('create', 'UA-92815270-1', 'auto'); ga('send', 'pageview'); </script> </html>