Scrum Bubbles Recommendation of the Week

Have you checked out the Agile Uprising Coalition yet? If you haven’t, you should. According to their website, they are a “purpose-built network that focuses on the advancement of the agile mindset and global professional networking between and among practicing agilists.”

I check out Agile Uprising regularly to see what my fellow agilists say about things like Mike Cohn’s new Better User Stories course, to see how everyone is measuring flow efficiency in Kanban, or to listen to podcasts (They interview great minds in the industry).

There are plenty of other forums out there (I belong to several), but this one seems to be an open and effective way of sharing thoughts in the agile space.


“Size doesn’t matter…”

Anyone who tells you size doesn’t matter hasn’t tried to complete a huge mobile app with just two people… in two months. So yes. Size DOES matter.

But how big is too big? How small is too small? What is just right?

I set out to get some ideas not only from folks I work with, but from industry experts. First, let’s reacquaint ourselves with what a scrum team actually is, as stated in the 2017 Scrum Guide 

The Scrum Team consists of a Product Owner, the Development Team, and a Scrum Master. Scrum Teams are self-organizing and cross-functional. Self-organizing teams choose how best to accomplish their work, rather than being directed by others outside the team. Cross-functional teams have all competencies needed to accomplish the work without depending on others not part of the team. The team model in Scrum is designed to optimize flexibility, creativity, and productivity. The Scrum Team has proven itself to be increasingly effective for all the earlier stated uses, and any complex work.

Jeff Sutherland himself (co-author of the Scrum Guide) has been quoted as saying 7 teammates (+ or – 2) is the sweet spot. I did hear Mr. Sutherland say at the 2017 Global Scrum Gathering that he is rather fond of the number five; he admitted he loves fractals. Bob Galen, someone from whom I’ve taken some valuable guidance, wrote a quick blog post describing the “Goldilocks” team as being 6 or 7 people, excluding the Product Owner and Scrum master.

I tend to agree with Jeff and Bob. 5 to 7 people seems to be a manageable number. In my experience, anything larger could become unwieldy during scrum ceremonies such as daily stand-ups or the retrospectives.

What are your thoughts? Sound off in the comments.

Hackathon How-To

Recently, my company did its second-ever hackathon. It was somewhat thrown together, but I think the results were amazing. It provided all the scrum teams with a much-needed break from the everyday grind, but more importantly, it gave them the opportunity  to work on something they felt passionately about.

My company wants to give these teams more opportunities to innovate, so we’re doing two more this year; one is slated for August and the other for December.  As I reflect back on all the things that happened last week, I’ve realized we can do a lot better. So I wondered about what really makes up a good hackathon. Below are some ideas, but first what IS a hackathon, anyway? Continue reading


I’m back at it with a better blog here on WordPress. I also went out on a limb and purchased to make sure all this stuff belongs to me! Over the next few weeks, I’ll be transporting my old Blogger content here, but be on the lookout for new agile thought bubbles! They’re coming!