fberriman.com

Fruit salad: a scrum estimation scale

When I first joined Netlify over 2 years ago, I took over sprint planning for a while.

As many teams do, they were doing a sort of scrum-lite. They didn’t have an estimation scale and we all agreed at various times that the traditional scrum scales of t-shirt sizes or fun bucks didn’t really capture the concept of scoring complexity.

So, I came up with a scale I thought captured complexity better and used emoji. Fruit! The idea is that as the score increases, the complexity one might expect about how to prepare and eat the item of fruit increases. So, you declare a fruit for a task, and build up a fruit salad of a size the team can handle (eat!) for a sprint.

1 🍇 A grape. Trivial, very quick, no brainer.

2 🍏 An apple (green, specifically, so it stands apart from the tomato emoji). Most people know how to cut up or bite into an apple and eat it. You know generally what needs to happen for the task, but it might take a little bit of time.

3 🍒 A cherry. Pretty easy to eat, but sometimes has that troublesome pit in the middle you either need to extract or spit, and certainly try not to bite or swallow. So, you know most of what needs to happen, quite straight-forward, but there’s some unknowns.

5 🍍A pineapple. Does anyone really know how to cut up a pineapple? Cutting pineapples isn’t something I do often, so I’m a bit unsure about where I’ll start. There’s some parts of the task still to work out, no major unknowns, but it’s still meaty work.

8 🍉 A watermelon. OK, now this is a real wild card. Do I have to have a machete to cut one open? What about the seeds? Do they just get left in? There’s lots to work out, some unknowns, and it might get messy.

?? 🍅 A Tomato. Apparently you’re a fruit, but you certainly don’t belong in a fruit salad. Declare tomato when you really have no idea about the task and it needs more info/breaking down before it can be estimated.

🥑 An avocado. Also a fruit, but it goes bad really quickly. Work that’s not scope-able because it’s a chore or something that just takes a fixed amount of time.

The term "Responsive Web Design" has failed

Desperate times call for desperate measures, and although Alex’s recent slide is a bit full on, it’s not entirely wrong.

I think what he should have said was that Responsive Web Design alone has failed so far in keeping the web at the forefront of users experiences where most users are most of the time -- on mobile. Of course, that’s much more nuanced than he had time for in his talk, but if that is a goal of RWD then it has failed. If the goal of RWD is just to be a practice to making things visually work on different screen sizes, then gold stars all around.

Responsive web design in and of itself is a really smart way to think about developing sites, assuming that you’re taking it from the mobile-first strategy. It’s been a while since I’ve come across a major digital service that hasn’t had a mobile-optimised layout of some nature, so I think on the whole that’s worked. Although, I have to ask where the "so focused on mobile they didn’t bother with a desktop optimisation" crew are - I sort of expected that to happen, but I’ve not yet hit a serious site that has a mobile-only view and presents that to it’s end users on desktop as a fallback. I have, however, seen buckets of splash screens that block me entirely and point me at the native app as the exclusive and only way to access their content and services. That’s scary.

What’s lacking about the responsive web design story is it has always focussed so heavily on the visual, dimensional, aspects of digital design. What are the snap points? How do we scale the images, the text? Can we trim content for some or enhance for others?

As a movement, it’s failed to capture the true otherness of being on a small screen. The fact that CPU, memory, network speed, storage and so many other aspects need to be first-level concerns. I’d argue that for most sites, the compromise for small screen devices has gone about as far as the ever-maligned hamburger menu and largely stopped there.

What I think I, and folks like Alex and Jeremy, who are fearful of the future of the Open Web really want to see is the sort of design work that Jad spoke about at Fronteers. That deep, close, observation of what our users _really_ expect on their devices - given that a majority of their experiences are with native apps and we’re trying very much to slip in our non-native experiences and pass them off as as reliable, integrated and valuable as those. RWD also isn’t taking us into where people find their online experiences (app stores). It could, but it needs to be tightly coupled with a strong PWA game with Trusted Web Activities, for example.

So, in short, RWD didn’t fail so much as it stopped short. Let’s not bicker about the specifics and just focus on getting out of our doom loop, eh?

Trash and plastic replacements

I've become one of those people who gets angry about plastic straws and I know that it's not going to save the planet and governments have to set policies that stop companies using so much trash, yadda yadda, but it at least gives one a new high-horse on which to ride since I already don't eat animals and I have a reusable mug.

Monica suggested I start a blog, but that sounds like work so here's a bunch of plastic/trash reducing replacements I have tried.

Good

Meh

Bad

A Book Apart: Progressive Web Apps

This time last year, I was at Chrome Dev Summit. I ran into Jason Grigsby, who I am always glad to chat with. He mentioned, slightly off-hand, that he was writing a new book about Progressive Web Apps and jokingly suggested that I would be a good person to contribute to a foreword.

Well. He wasn't joking.

His wonderful new book is out now, published by A Book Apart.

A real book made of trees!
A real book made of trees!

The foreword is written by myself and Alex, and we mean every word we say in it. We couldn't be happier with how Jason's book turned out and it's really the only book you need if you want to understand why, and how, you should be building PWAs.

I'm very thankful for his kindness and the opportunity to contribute in a tiny way to his amazing work.

Birds

A couple of months ago I read Jenny Odell's transcript of a keynote she gave at a conference. It's a good talk and well worth a read/watch, but the part about her bird encounters caught my attention the most.

I ended up reading "The Genius of Birds", which she mentions and that book referenced some sections of "Gifts of the Crow" which I read immediately after. The latter covers a lot of the same topics as the first, but focuses on Corvid research. Since reading them, I'd say I've become mildly obsessed with crows and their kin - I generally have nuts in my bag now just in case I meet a friendly one.

I highly recommend at least reading The Genius of Birds - it's an easy-going read in a light-hearted tone and just generally full of fascinating little stories about bird research and their obvious intelligence and charm.

I just moved house, and it turns out that a member of the corvid family already frequents my yard - a pair of bright blue Scrub Jays. On just the first day of my hanging out with them, they already know what the deal is. So happy about my new neighbours!

Older Posts