Skip to main content

About the Happiness App

The response to the HappinessApp has been really gratifying. Happiness in general seems to be an idea whose time has come.

This app came about as I participated in the Delight-the-Client exercise of Steve Denning's and my Radical Management workshop in May. Given my role as Scrum/RM Trainer & Coach, how could I delight my customer faster?

I thought: The earliest side effect of introducing Scrum is often significantly improved staff morale. How could I make this improvement visible quickly? Employee surveys are time consuming and expensive. The idea for an app was born. I came home totally enthusiastic ("jazzed" as they say in the US), wrote a vision and some user stories, asked some colleagues what they thought of the idea.

The initial user feedback was (mostly) really positive -- and gave me some really important changes in direction from my original idea! So off I went. A tweet to find a development team - I found someone who really understood what I was trying to accomplish - and 3 weeks after the initial idea, development started.

The development process is of course Scrum. We do TDD and continuous integration. And I think the definition of done will take on three or four new items in the next sprint. Improvement is a continuous process.

Today, we are about to finish Sprint 4, and you can record your happiness level, display the history graphically, and install the app on your iPhone. A web site is up and you can register for the beta program. Next week, we plan to start inviting the first beta testers to participate and we'll start integrated the Happiness App into social media.

Every week, more features become available. Every week we can adjust the plan to take advantage of what we did and what learned last week. This is the really cool part of doing Scrum - the visibility of progress is obvious so I can adjust the plan can to best pursue the vision.














Comments

Popular posts from this blog

Scaling Scrum: SAFe, DAD, or LeSS?

Participants in last week's Scrum MasterClass wanted to evaluate approaches to scaling Scrum and Agile for their large enterprise. So I set out to review the available frameworks. Which one is best for your situation?

Recently a number of approaches have started gaining attention, including the Scaled Agile Framework ("SAFe") by Dean Leffingwell, Disciplined Agile Development (DAD), by Scott Ambler, and Large Scale Scrum (LeSS), by Craig Larman and Bas Vodde. (Follow the links for white papers or overviews of each approach).

How to compare these approaches? My starting point is Scrum in the team. Scrum has proven very effective at helping teams perform, even though it does not directly address the issues surrounding larger organizations and teams. An approach to scaling Scrum should not be inconsistent with Scrum itself.

Scrum implements a small number of principles and constraints: Inspect and Adapt. An interdisciplinary Team solves the problem. Deliver something of va…

Sample Definition of Done

Why does Scrum have a Definition of Done? Simple, everyone involved in the project needs to know and understand what Done means. Furthermore, Done should be really done, as in, 'there is nothing stopping us from earning value with this function, except maybe the go-ahead from the Product Owner. Consider the alternative:
Project Manager: Is this function done?
Developer: Yes
Project Manager: So we can ship it?
Developer: Well, No. It needs to be tested, and I need to write some documentation, but the code works, really. I tested it... (pause) ...on my machine. What's wrong with this exchange? To the developer and to the project manager, "done" means something rather different. To the developer in this case, done means: "I don't have to work on this piece of code any more (unless the tester tells me something is wrong)." The project leader is looking for a statement that the code is ready to ship.

At its most basic level, a definition of Done creates a sh…

10 Warning Signs, that your team is not self-organizing

How do you know that self-organization is working? The Bern Chapter of Scrum Breakfast Club looked into this questions, and identified the following warning signs (which I have taken the liberty of translating).

The team reports to the Scrum Master at the Daily ScrumPeople wait for instructions from the Scrum MasterTeam members don't hold each other responsible [for their commitments]The same impediment comes up twice"That's the way it is" => resignation"I" instead of "We"Flip charts are lonelyCulture of conflict-avoidanceDecisions processes are unclear, nor are they discussedPersonal goals are more important than team goals
To this list I would add my a couple of my favorites:
you don't see a triangle on the task board (not working according prioritization of stories)after the daily Scrum, people return directly to their desks (no collaboration)there are a least as many stories in progress as team members (no pairing)
P.S. You can join the …