Thursday, 29 May 2014

Ssshhhhhhh... What did he say?

Listening is an art and meeting room is the Gridiron where you can actually see the masters of this art. Any and every meeting has always got me new learning. As an active or passive participant a meeting can teach you a lot and not all of it would be from the content of the meetings. People, Environment, Attitudes and flow contribute a big chunk. While in the last few months we religiously started pulling scrums, requirement meetings, technical calls and other project discussions and each of them called for a a few meetings. For few of these meetings I just attended as passive participant and took time to observe and notice a few things. I tried but could not resist myself from putting this over....

How do you identify who is not listening or been attentive in the meeting?

I noticed a pattern, a pattern that speaks when people are not listening, understanding or don't care. Here are a few of them...

1. Eye Contact
Participants that are not making eye contact are most times not listening. Although this is not a hard and fast rule, I have noticed that non listeners are usually found looking in Zero or most times at objects. 

2. Reaction
If they don't react to situations they are not listening. The funniest thing I observed was when a spontaneous joke is cracked you would notice the non listeners to burst into laughter or smile when everyone is done or midway. An absurd thing said in the meeting would also go unnoticed by the non listeners.

3. Body Language
Folded Hands, raised eyebrows, blank face and consistently moving / shaking legs also display that the focus is not meeting. People who are attentive or listening can be found either leaning forward to speak or listen.

4. Questions, Replies and endorsements
You would always notice non listeners raising or asking questions that are already answered. Easiest way to track them. If a person endorses everything it "can" mean he/she was not listening.

5. The Zero Effect
Participants that are standing with absolutely no emotions, words and actions are probably thinking of what they are wearing for their date in the evening. I have also noticed some of the non listeners to be drawing things.

6. Interjections
If they consistently use interjections like "Yeah" "Yes" "hmm" without any changing patterns.. they are probably not listening.

7. All the Gadgetry Goofs
Fiddling phones, Nails, keys are signs of no interest in discussions.

Do you see any disconnected meeting participants? What do you think they do?

Tuesday, 27 May 2014

Things I miss.....

Things I miss....

1. A display of committed vs achieved.
2. A view to what is blocking.
3. An integration that happens on every logical point as opposed to complete story point.
4. An ambiguous requirement that you encountered mid way.
5. A design that evolves with audit.
6. A user story that is sliced enough to know what is achievable and when.
7. A glimpse to non-availability that is blocking.
8. A list of leftovers every 2 weeks
9. A list of leftover gulped every 2 weeks.
10. An impediment found early
11. A build that says all is right and ready to go.
12. Board that truly reveals the work in progress.
13. A retrospective that truly reveals the good, the bad and the ugly
14. A loud shout of "Yes I have done it"
15. A call to review small things that build up large blocks
16. A scrum where huddling is allowed
17. A demonstration that comes with high value feedback
18. A contribution of how best it can be done.
19. A list we call "Technical Debt"
20. A process that is looked to be improved and evolved.
21. An estimate that cuddles the requirement
22. A practice that cares for User experience more than technology
23. An attitude that says "Customers are not Gods"
24. A High Five
25. A WOW
26. A Great Idea
27. A "That's Kewl"
28. A "Why not?"
29. Clarity of what is to be achieved and why
30. A Goal, that's just not completing a story point
31. A pat for an orthodox approach
32. A non traditional success pattern

I miss "Agile...." I really do.....

From the old books... Curated a list of things that a agile developer would always miss. My part is here.. what is yours?