craigAgreen.com

I recently gave a high level presentation on Agile and Scrum. Below is a sanitized version for reuse. If you do resuse any of it all I ask is that you drop me a line to let me know that you found it useful.

What is your application's personality?

We are currently updating our error page ... this got me thinking about our what the error page says about our web application.  Is it serious, cool and business-like, does it "work hard, play harder", or is it light harted. Further more, is it consistent throughout the application or does it suffer from Multiple Personality Disorder?

As a user, how do you feel when a Windows error dialog comes up accompanied with the 'Critical Stop'  sound? Do you feel the same way when you see Twitter's Fail Whale? What about Google Chrome's "Aw, Snap" error?

Chances are you are more forgiving of the latter two than you are of Windows. Why? Same reason you are more likely to forgive people. You like them better, and that starts with personality.

In Marcus Buckingham and Curt Coffman's book, "First, Break All the Rules: What the World's Greatest Managers Do Differently", they explore what makes a great nurse. They found that it wasn't the technique used when giving an injection, it was what they said before the injection. It was their personality. Nurses that showed empathy and told their patients that the injection would hurt a little were see as superior nurses.

A software application should do the same. Even a line of business (LOB) application should say "I know you are forced to use me from 9 to 5 to do your job and you would much rather be on Facebook, but let me help to make your work a little less painful and maybe even enjoyable". For non-LOB applications a strong personality and sense of identity is a must.

The great thing about Scrum is that when you do it right it lets you know when you are doing it wrong. At ZTR we have been practising Scrum for a while now, but lately it hasn't felt right. Maybe it's because we've fallen back to the Waterfall mentality of "code now and let QA find the bug later" or perhaps it's becuase the team if feeling less empowered as some decision making is removed. Whatever the reason, something doesn't smell right, and as long as you are truthful with yourself, your team and your process Scrum has wonderful mechanisms to let you know when you've become a ScrumBut ("Oh yeah, we do Scrum, BUT... <insert shoot yourself in the foot shortcut here>).