Scrum Meeting – Punishment by collecting $ is it the right way ?

One of the first rules of Scrum Meeting is to ensure that it is conducted at the same time every day at the same place. It also expects that the team members should come on time to the Scrum Meeting.

Typical practice is that, late comers to the Scrum Meetings should either wear a joker cap or pay a $ as punishment for arriving late. However many thought leaders share that these practices of punishment is bad and it is not going to improve the situation or change the behavior of the late comers. Worse, Thought Leaders proficient in Intrinsic and Extrinsic Motivation, believe that, over a period of time the extrinsic motivators(reward or punishment) actually reduces the intrinsic motivation.

* So, what should we do in this situation ?
* How do we handle the late comers ?
* Should we ignore them ?
* How do we make the late comers for the Scrum meeting to come on time ?

The answer seems to be not easy. Researchers believe that there is no one formula that could be used to motivate every one. If some one is not coming on time to the Scrum meeting means either he/she is not interested or does not believe in these meetings and could be something else. One needs to identify the root cause of lack of intrinsic motivation and work on an individual basis rather than applying the same reward/punishment formula.

Cognitive Evaluation Theory and FLOW seem to provide some insights to improve the Intrinsic motivation.

Retrospectives in Agile Multi Site Development

Unlike other Agile practices, Retrospective sessions involves a lot of
emotions. Emotions could be easily understood(also handled) by looking at the body language of the people around us. However, in a distributed development projects, teams are scattered across various locations and this in turn makes it hard to understand the body language. This is one of the reasons why it takes more time for the scattered teams to bond with each other and thus reducing the efficacy.

Even though no tool or technique can replace the experience
emanating in a collocated team, there are a few that could

be practiced to improve the effectiveness of distributed retrospectives.

From the logistics perspective, one or more of following tools
could be used

Tool Name	Effectiveness
Voice chat through Wired phones, typically what is termed landlines or using popular tools like Skype, Yahoo Messengers, etc   without  Web cams	Low
GoogleDocs, Wikis in addition to voice chat and no web cams. Download the GoogleDocs Retrospective template from here	Low
Web cameras connected to tools like Skype or Office Communicators in addition to use of Google docs, Wikis,etc	Medium
http://www.CardMeeting.com Using this in addition to voice/video tools increases effectiveness	Medium
http://www.Dabbleboards.com Using this in addition to voice/video tools increases effectiveness	Medium
http://www.IdeaBoardz.com Using this in addition to voice/video tools increases effectiveness	Medium
http://www.IdeaScale.com Using this in addition to voice/video tools increases effectiveness	Medium
http://www.mindmeister.com Using this in addition to voice/video tools increases effectiveness	Medium
http://www.etherpad.com Using this in addition to voice/video tools increases effectiveness	Medium
http://en.linoit.com Using this in addition to voice/video tools increases effectiveness	Medium
Telepresence and Video Conferencing kind of tools  in addition to one or more of above mentioned tools	High

 

Note: Some of the above mentioned online tools could also be used for other Agile practices like Requirement gathering, brain storming, design discussions in distributed mode.

 

Patterns

Two popular patterns of distributed retrospectives include
1. All hands Retrospective
2. Location Specific Retrospective

In case of All hands Retrospective, all teams participate together
using one or more of above logistics. This pattern works well if teams
are located in same or closer time zones. May not be a good idea to apply this for larger teams . 

Location Specific Retrospective, In this pattern, location specific
teams conduct retrospectives and then the leads from each of these
location conduct “Retrospective of retrospectives” synching
Sad/Mad/Glad data. Larger teams (>15) can apply this pattern.