What makes Scrum teams different?

I was in a daily standup last week watching a team that is reasonably new to Scrum, and witnessed a team start the path towards self-organization and collective ownership.  The conversation went something like this:

Bob the Developer: I’m finishing up coding that feature, handing it over to Joe to test this afternoon, and then I think I’m done with all coding work for this sprint.

Sally the Scrum Master: What will you work on after you give that feature to Joe?

Bob: Hmmm…well, I think I’ll swarm with Joe on testing that feature, and work with him immediately on any issues.  We will make sure it’s wrapped up and the product owner sees it too to get their feedback.

This response from Bob was very different than what he would have said 3 months prior.  3 months prior, his response would have been something like “I’m going to go look at the next feature” or “I’m not sure, I guess I’ll wait for a bug to show up”.   Bob had radically transformed his view on his role on the team, and was understanding that he was part of a collaborative group whose collective responsibility was to deliver to his customers.  He wasn’t there just to write code.  His role was now bigger than that. 

It’s this type of maturity that makes Scrum (and more generally, any flavor of agile) teams special and different from traditional waterfall “teams”, which are usually a collection of people with different goals, responsibilities, and probably work in different departments.  They aren’t populated with people who only want to live in their world.  They are cross-functional teams, with a broad range of skills and capabilities – but these people understand the goal of a Scrum team.  The team works together to achieve, even if that means doing something outside their core skills.     

The Scrum Guide states this very clearly:

Individual Development Team members may have specialized skills and areas of focus, but accountability belongs to the Development Team as a whole.

I’ll repeat that: Accountability belongs to the team as a whole.

This simple, but immensely powerful, concept is one of the core tenets of Scrum, and what makes Scrum teams special.

Advertisements

My ideal wearable

There is a lot of noise lately about wearables, from Google Glass to the Samsung Gear watches to the upcoming Apple Watch.  So far though, nothing is what I would consider worth me plunking down hundreds of dollars.  With CES 2015 going on right now, wearables, and especially watch-form factors, are looking to be a large part of the new gadgets that are making their way into the market this year.  

The show isn’t over yet, but here’s what I’m personally looking for in a smart watch wearable:

  • Built-in GPS with Garmin-like functions, so I can use it as a running watch.  I have a Garmin 620 now, and love it.  A smartwatch that could fill this role would be great.  Integration with a heart rate monitor too.
  • Stylish but rugged – if it’s going to be something I wear all the time and for running, it needs to be able to take a bit of beating and be…
  • Waterproof, and most certainly sweat-proof.  I should be able to run in the rain or swim with it also.
  • Phone capability – without an accompanying smartphone!  Paired with a very small Bluetooth ear bud for communication so I don’t have to look like Dick Tracy talking into my wrist.
  • SMS/MMS capabilities – receive/send texts and picture texts.
  • Application store/platform – for 3rd parties to integrate with.
  • Payment feature – support for paying for things.  (Apple Watch will have Apple Pay, so something like this)
  • Lightweight – shouldn’t be big or clunky, and weigh no more than your average watch.
  • Touchscreen – obviously.

And oh – battery life of at least a day.  I don’t mind recharging once a day – I take my watch off at night anyway – but even 8 hour battery life is too short. 

That’s all obviously a pretty tall order, and we are headed in that direction I believe, but we do have a ways to go before smart watch wearables are truly and incredibly useful.  Until then…we’ll be using multiple devices.     

Update: the Garmin Fenix 3 is getting close.