{"id":6128,"date":"2022-01-24T21:36:52","date_gmt":"2022-01-24T21:36:52","guid":{"rendered":"https:\/\/mailinvest.blog\/index.php\/2022\/01\/24\/delivering-features-modernizing-our-tech-stack-via-shape-up-process-street\/"},"modified":"2022-01-24T21:36:52","modified_gmt":"2022-01-24T21:36:52","slug":"delivering-features-modernizing-our-tech-stack-via-shape-up-process-street","status":"publish","type":"post","link":"https:\/\/mailinvest.blog\/index.php\/2022\/01\/24\/delivering-features-modernizing-our-tech-stack-via-shape-up-process-street\/","title":{"rendered":"Delivering Features & Modernizing Our Tech Stack via Shape Up | Process Street"},"content":{"rendered":"

<\/a>\n<\/p>\n

\n

\"deliver<\/p>\n

A while back, we wrote about how Shape Up* helped our EPD team 5x their dev cycle<\/a>. We also talked about how it\u2019s different from Scrum<\/a>, and even did a piece exploring the dangers of fake agile<\/a>.<\/p>\n

So how are things looking, a little further down the line? Mike Schutte, a Senior Front-end Engineer at Process Street<\/a>, gave us his thoughts on how Shape Up has impacted our EPD team.<\/p>\n

How Shape Up helped us 5x our dev cycle<\/h2>\n

\"mike<\/p>\n

Time is perhaps the most precious resource when building a product. And yet, it\u2019s often spent lavishly as if it\u2019s in infinite supply. Teams often adapt timelines to fit features and requirements instead of the other way around. <\/p>\n

The essence of the Shape Up<\/a> methodology of product development is exactly that: adapt requirements to fit timelines<\/strong>.<\/p>\n

We\u2019ve been using Shape Up at Process Street for a little over a year now and our EPD team (engineering, product, and design) has more momentum than ever.<\/p>\n

Here\u2019s the thing: we never ship the \u201cidealized\u201d version of what we originally envisioned for the product. We don\u2019t talk about things being \u201cfeature complete.\u201d We build, communicate, revise, and repeat on a daily basis. The key is to identify the biggest levers at our disposal to add as much value as we can within the six-week cycle without compromising on quality. <\/p>\n

The shapers identify a valuable area to invest effort in, the builders get to work, then we test the bet based on real users\u2019 feedback. We get a lot good-enough things shipped at a predictable cadence instead of one perfect thing with an amorphous timeline.<\/p>\n

We\u2019re following Shape Up pretty much by the book, so there isn\u2019t much to elaborate that can\u2019t be found in the book or from other teams that have written about it. The key is to stay committed to the mindset of adapting requirements to fit timelines. This influences everything from how you approach meetings to whether or not to use a preexisting library to jump-start a particular feature.\"shape<\/p>\n