Daily Scrum Rules

Today, while reading about the patches for Teamsystem, came across of Rules to follow while conducting Scrum. This data found from Scrumforteamsuit product website. As the website says, this product is developed by Conchango in collaboration with Ken Schwaber and Microsoft. At this point of time, I need to mention about Ken Schwaber, Ken Schwaber co-developed the Scrum Process with Jeff Sutherland in the early 1990s. Visit Ken’s website to learn more on Scrum.

Here are the guidelines or thumb rules during the scrum participation. Let me see, how this will work out for me.

  • Hold the Daily Scrum in the same place at the same time every work day. The best time for the meeting is first thing in the day so that Team members think about what they did the day before and what they plan to do today.
  • All Team members are required to attend. If for some reason a Team member can't attend in person, the absent member must either attend by telephone or by having another Team member report on their status.
  • Team members must be prompt. The Scrum Master starts the meeting at the appointed time, regardless of who is present. Any members who are late pay a fine that is donated to a worthy charity!
  • The Scrum Master begins the meeting by starting with the person immediately to his or her left and proceeding counter clockwise around the room until everyone has spoken.
  • Each Team member should respond to the following questions:
    • What have you done since the last Daily Scrum regarding this project?
    • What will you do between now and the next Daily Scrum meeting regarding this project?
    • What impedes you from performing your work as effectively as possible?
  • Team members should not digress beyond answering these three questions into issues, designs, discussions of problems, or gossip. The Scrum Master is responsible for moving the meeting along briskly from person to person.
  • Team members should address the Team. This is not a "Reporting to the Scrum Master" meeting.
  • During the meeting only one person talks at a time. Everyone else listens without any side conversations.
  • When a Team member reports something that is of interest to other Team members or needs assistance from other Team members, any Team member can immediately arrange for all interested parties to get together after the Daily Scrum Meeting.
  • Chickens (non Team members) are welcome to attend the Daily Scrum Meetings but they are not allowed to talk, make observations, make faces or otherwise make their presence in the meeting obtrusive.
  • Chickens stand on the periphery of the Team so as not to interfere with the meeting.
  • If too many chickens attend the meeting, the Scrum Master can limit attendance so that the meeting can remain orderly and focused.
  • Pigs or chickens who cannot or will not conform to the above rules can be excluded from the meeting (chickens) or removed from the Team (pigs).

Source: http://www.scrumforteamsystem.com/ProcessGuidance/Process/DailyScrumMeeting/DailyScrumMeetingRules.htm

Did you try out this?

Comments

Rajiv Gowda said…
Nice srum rules involving Chickens, Pigs and Team Members :)
May 28, 2007 3:31 PM
Post a Comment

Popular posts from this blog

Network Intrusion Detection using Supervised ML technique

Declaimer This is my initial version of the synopsis for PhD studies. There are plenty of things that i have to complete before i prepare the final version. Thus, this would be the alpha version. Due to the length of the blog post, will not be posting the entire draft. 1.Title of the thesis Network Intrusion Detection using Supervised Machine Learning Technique with Feature Selection 2.Introduction Intrusion Detection System, IDS, is a development which improve the network security and defending the information of the association. The IDS encourage the network chairman to recognize any malicious action on the network and alarms the executive to get the information made sure about by taking the appropriate activities against those attacks. An intrusion alludes to any unauthorized access or malicious usage of data assets. An intruder or an attacker is a true element that attempts to discover a way to increase unauthorized access to data, causes hurt or take part in different
Read more

Common mistakes by Interviewer

Now-a-days am conducting few interviews for our organization. While sitting in the other side of the table, I've visualized why most of the interviews fail with me. But when conducting these interviews, most of the candidates are attending with self confidence that they are suitable for the mentioned role and attend without preparation. When people do some real preparation, they tend to fail due to lack of awareness at the interviewer towards interviewing techniques. Having failed in many interviews, I've learned that the interviews fail because of the following... Reflection (or) Mirroring: The interviewer tends to see self within the candidate. The interviewer starts to compare self with the candidate and evaluate. This evaluation is totally personal. The yard stick for measuring the candidature is not generalized, but influenced.   Template (or) Checklist: The interviewer has a template of a questionnaire. The interviewer measures the candidate with respect to the list of st
Read more

Keep the system active, to avoid the auto lock

Most of the corporate offices will have a policy for screen locking. While working with a long running applications at background, like the automation scripts for testing the applications, it would be difficult to maintain the unlock state of the screen. Thus, we found a technique to keep the system active with a cheating technique. Below is the powershall scripts that keeps the system active ' I am clicking on NUMLOCK for every 5 seconds to keep the system awake Set objNetwork = CreateObject("Wscript.Network")'to get user name numOfHours=inputbox("Hi " & objNetwork.UserName & ", How many hours you want me to be awake? :->") 'time variable conatins the time in hours Set WshShell = WScript.CreateObject("WScript.Shell") 'Creating an object for clicking keys from keyboard numOfMilliSecs=numOfHours*3600*1000 'converting hours to milli seconds While numOfMilliSecs>0 'runs until tym becomes zero WshShell.Send
Read more