{"id":91,"date":"2010-06-02T21:55:28","date_gmt":"2010-06-02T21:55:28","guid":{"rendered":"http:\/\/agilepartnership.com\/?p=91"},"modified":"2010-06-02T21:55:28","modified_gmt":"2010-06-02T21:55:28","slug":"are-we-only-having-fun","status":"publish","type":"post","link":"https:\/\/agilepartnership.com\/fr\/are-we-only-having-fun\/","title":{"rendered":"Are we only having fun?"},"content":{"rendered":"

\"\"<\/a>Like most of you, I\u2019ve had my fair (or unfair) share of meetings.\u00a0 Some were great and a lot of them were just ok. But a few weeks ago a <\/span>colleagueof mine said something during a ROTI<\/a> evaluation that forced me to look back at all those previous \u201cgreat\u201d meetings and re-evaluate their TRUE value.<\/span><\/p>\n

What he said was: \u201cAm I my really obtaining value from this activity or am I just having a good time?\u201d<\/span><\/p>\n

My jaw dropped!<\/span><\/p>\n

How can such a simple statement stir up so many issues in my mind? It not only forced me to re-evaluate the specific activity he was referring to, but everything else I\u2019d done and was about to do! <\/span><\/p>\n

Leaving aside the fact that fun has value in itself, why not challenge an initial assessment with a Fun vs. Value Evaluation?\u00a0 A meeting might have been fun, but did we reach our objectives?\u00a0 As an Agile coach (or ScrumMaster), if I suspect a misinterpretation of the true value of a meeting or an activity, I might try to validate it by whipping out a Fun\/Value graph<\/em>:<\/span><\/p>\n

\"\"<\/a><\/span><\/p>\n

No fun and No value<\/strong><\/span><\/h5>\n

If the meeting had low value, there\u2019s a good chance that fun is also on the low side.\u00a0 Those situations are usually easy to detect and numerous corrective actions can be put in place.<\/span><\/p>\n

No Fun and High Value <\/strong><\/span><\/h5>\n

Now here\u2019s an interesting situation! We managed to reach our objectives but getting there was about as much fun as a root canal.\u00a0 This situation might hurt in the long run as valuable contributors conveniently forget to attend.<\/span><\/p>\n

A Scrum example:<\/strong><\/span><\/em><\/p>\n

The recurrent Product Backlog estimation meeting (Backlog maintenance) is essential and the team is able to reach its goal with a two-hour meeting…but for most it feels like a five-hour meeting.\u00a0 The team sits in a large conference room, the projector is humming and item by item, one or two members shoot out some \u201cman days\u201d.<\/span><\/p>\n

Why not estimate using Poker or Wall planning? Maybe every two weeks, we hold this meeting in a local caf\u00e9 or bar. Everyone contributes, estimates increase in value and…IT\u2019LL BE FUN! We might even save time, making it still more fun!<\/span><\/p>\n

Lots of Fun and High Value<\/strong><\/span><\/h5>\n

This is good situation to be in!\u00a0 Some might say, if it ain\u2019t broke, don\u2019t fix it.\u00a0 I\u2019m more of a \u201cGood is the enemy of great<\/a>\u201d kind of guy.\u00a0 But trying to make it even better can be tricky.\u00a0 If such attempts are made, make sure the team buys in to it or better yet, get the team to come up with new and innovative ways to reach their objectives more efficiently.<\/span><\/p>\n

Lots of Fun but No Value<\/strong><\/span><\/h5>\n

Now here\u2019s the situation that motivated me to write this article.\u00a0 Is it possible to be blinded by fun?\u00a0 Of course! The meeting might have been called to shed some light on a problematic issue, but ended being little more than a laugh-fest. We walk out of there feeling pretty good but the real issue is nowhere near being resolved.<\/span><\/p>\n

Where I work<\/a>, we have bi-monthly meetings to explore various situations when coaching individuals.\u00a0 We do this through role playing; two individuals acting as coach and coached.\u00a0 As you can imagine, some scenarios are quite hilarious.\u00a0 Fun and laughter is guaranteed!\u00a0 It was so much fun that I had a (false) sense that we were accomplishing something of substance \u2013 that is, until my colleague casually questioned himself and stated, \u201cAm I my really obtaining value, or am I just having a good time?\u201d<\/span><\/p>\n

Once I filtered out the laughing and that great feeling associated with being with my colleagues, nothing much was left.\u00a0 There was some value but not nearly as much as I initially thought. It looked something like this:\"\"<\/a><\/span> With that new information in hand, we restructured the activity in order to increase its value, all while maintaining The \u201cFun\u201d.<\/span><\/p>\n

Value or Just Fun?<\/strong><\/span><\/h5>\n

It pays to be aware of what zone we are in, especially when in the \u201cMisinterpretation Zone\u201d.\u00a0 High levels of fun are beneficial to any activity, but reaching clear objectives remains the ultimate goal.<\/span><\/p>\n

I\u2019m looking forward to applying this in the real world and seeing what happens!\u00a0 I\u2019ll let you know how it goes. \ud83d\ude42
\n<\/span><\/p>\n

<a href=\u201d\u201d><\/span><\/div>\n","protected":false},"excerpt":{"rendered":"

Like most of you, I\u2019ve had my fair (or unfair) share of meetings.\u00a0 Some were great and a lot of them were just ok. But a few weeks ago a colleagueof mine said something during a ROTI evaluation that forced me to look back at all those previous \u201cgreat\u201d meetings and re-evaluate their TRUE value. […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[20,18],"tags":[],"class_list":["post-91","post","type-post","status-publish","format-standard","hentry","category-general","category-scrum"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/agilepartnership.com\/fr\/wp-json\/wp\/v2\/posts\/91","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/agilepartnership.com\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/agilepartnership.com\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/agilepartnership.com\/fr\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/agilepartnership.com\/fr\/wp-json\/wp\/v2\/comments?post=91"}],"version-history":[{"count":0,"href":"https:\/\/agilepartnership.com\/fr\/wp-json\/wp\/v2\/posts\/91\/revisions"}],"wp:attachment":[{"href":"https:\/\/agilepartnership.com\/fr\/wp-json\/wp\/v2\/media?parent=91"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/agilepartnership.com\/fr\/wp-json\/wp\/v2\/categories?post=91"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/agilepartnership.com\/fr\/wp-json\/wp\/v2\/tags?post=91"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}