Ryan Singer - Applying Shape Up in the Real World - Rails World 2023

Teams everywhere are tired of scrum and curious about Shape Up. But very few of them are able to apply it by-the-book, because their companies are structured differently than 37signals, where Shape Up was created.
That hasn’t reduced the demand, however. People understand that estimating story points and writing better tickets isn’t going to solve their problems. There are disconnects between the vision of what to do and what actually gets built. Building takes longer than expected and scope gets out of control. Programmers are treated like ticket-takers when what they really want is to see the whole problem and creatively solve it.
Over the last couple years, Ryan Singer, author of ‘Shape Up’, has worked with a wider variety of companies with very different structures - teams with big gaps between junior and senior, where programmers far out-number designers, and where external pressures make six-week cycles out of the question. The result is new language, new techniques, and some broken rules, that will help you apply Shape Up in a way that’s custom-fit to your team.
Links:
rubyonrails.org/
basecamp.com/shapeup
#RailsWorld #RubyonRails #rails #shapeup #scrum
Thank you Dell APEX for sponsoring the editing and post-production of these videos.Visit them at: dell.com/APEX

[@hugobarauna]

Amazing talk! 🎉👏

[@alabhyajindal]

Wow great talk. Thanks!!

[@ricardo.fontanelli]

08:18 to 09:38 there's so much value here

[@andrefgallo]

Great talk

[@SteveHazel]

it's nice to give these crazy things that shouuuld happen when ya build an app nicely coined terms.

[@tmnsun]

Great talk! Think i need to read the book.

[@Sammi84]

Changing the naming of Pitch to Package is such a small thing, but it's such a great improvement. Pitch was misunderstood before. Package is much more direct.

[@iamfrankstallone]

24:17 - Brilliant - Agreed! Adding the term Framing and slightly modifying Shaping to creating a Package is subtle but a useful distinction.

[@kieranklaassen]

great reminder of why ShapeUp is so good! thanks Ryan!

[@svalasek]

Amazing speech and explanation. Thank you! I have started to read the book but did not finish. Now I want :-) I am so excited again, that I want to work for a company which will give me a room to use ShapeUp to deliver business value delivery to the customers. I have a lot of experience with scrum but ShapeUp just resonates more with me. And I also realise how full-stack developers and small teams (can do it all) makes this delivery method way more efficient.

[@sculderoy]

It's funny to watch someone talk about Scrum when they never really experienced it the way it was designed :) Your understanding/experience of Scrum is wrong at so many level 😅. And I can tell you, I am "using Shape Up" in my company, in a different way that you are describing, and this is bad. Because it's not used as it was designed. I am using agile frameworks since 2011, my first professional year, and everything that you describe as i can understand as "good solutions" I knew and did before discovering Shape Up. My point is that it's pointless to say that something is bad, just for the buzz. Simply offer an alternative, and don't use the competition as an argument. Mostly when the only new feature that Shape Up brings is the Appetite. And that is a great one ! The rest is already existing, just rebranded. 1. Shaping is called Product Backlog refinement. 2. Appetite, or "How much time I want to spend on this" is called Sprint. 3. Shapes and Scopes are called Product Backlog items (that the Scrum Guide explain that it is the accountability of the PO, but that they can delegate this - ie : within the team). 4. Cool-down is, in my opinion and experience, just a way to finish what was late. Which, I think, is not your intention. But if it is, I think it's a non-sense. PS : Writing is bad for detecting tone, so I want to insist in the fact that I'm saying this with the most friendly tone possible 🫶