##Some quick thoughts on tracking happiness I've done this with a couple of teams. I've used Mercury App and Google Forms.
Some things I've learned from this:
- Setting expectations is important - we're going to have good and bad days - that's okay. That's human.
- It's important to PAY ATTENTION and HONESTLY AND OPENLY discuss the reasons we're happy / unhappy. (make sure there's room for notes)
- It's important to remember balance - making one group happy can easily make another one unhappy. Be mindful of the impact of our actions in a larger context!
- IMO, as with all metrics, this is one the team should own.
- This definitely takes discipline. It's easy to forget to track things. Try and set a calendar reminder (or similiar) to take 5 minutes or so and keep this habit.
Sounds good. I personally like "how happy were you in THIS iteration" more than the relative question - I feel like the relative question might be a bit problematic as you'd mentioned.
Also - I feel like it may be hard to gauge how happy someone was over a 2 week period. It's easy to get caught up in an iteration and, without taking some serious time to reflect (and maybe having some data to reflect on), things might get skewed. It might be helpful to have folks try and just jot down a note on a post-it daily just to help with accuracy to give them something physical to help drive out a more accurate answer for that time frame.
Just my thoughts though - as with all things (A|a)gile - experimentation is key so I'm curious what you do and how it works out!