Raba - Defend your code RSS 2.0
# Saturday, March 10, 2007

At my team we start using the scrum methodology, we are now learning this stuff on the fly, for further understanding I recommend reading Avi Wortzel blog. Avi is the other team leader and a good friend and I admire his way of thinking, pay attention to him.
As Avi said, on daily meeting post, we are two team leaders and we make together the daily meetings (6 people), we both scrum masters each one gets his turn.

I would like to share my thoughts with you:

  1. Fix the "daily meeting" method (or, one more question to the casual three questions)
    • The problem
      I have a problem with the way people are letting you know what they are going to do today, for example: I am working on this module or I am doing that aspx page. The real problem is that the day after it will probably be the same task.
    • Resolving the problem
      • my first rule: talk about the things you really do, the problems you are trying to solve today.
      • I also added one more question, "what did you had to do yesterday and didn't make it".
        This question is the connection between the first and the second. so a co-worker should say: "Yesterday I did this and that, and didn't make this," and then continue with: "today I would continue in that and this"  or maybe: "I won't make it today also it will be postponed to the next week".
      • Don't ask: "why didn't you do this!", you are a scrum master, not a mother, this will annoy your programmers! (read the "Talk to your co-workers not to me: " section for better understanding) .
  2. Keep the order for better understanding.
    • The problem
      • programmers told me that they are confused and do not understand a word from the other programmers, there are many way to solve this issue.
    • Resolving the problem
      • try to keep the order of the sentences, about yesterday, today and impediments while the fourth question is like a hidden question between the yesterday and today.  the fourth is a connective question, you should still distinct between the three parts.
      • don't mess the sentences order, it will cause a confusion in some of your co-workers.
      • there are people who like to talk, that is not a problem, but do it in your turn, and in the right order.
  3. Talk to your co-workers not to me:
    • The problem
      • I always feel that people are talking to me and not to the other co-workers at the room, I don't have a good solution for this issue, but as far as I know it will take them time to understand it.
        You are probably asking time? so when? I think that on the day that they will really feel that the last meeting was helpful to you he or she will do it right.
    • Resolving the problem
      • I don't have a good solution for this issue, but as far as I know it will take them time to understand it.
        You are probably asking time? so when? I think that on the day that they will really feel that the last meeting was helpful to you he or she will do it right.
      • Scrum master questions: don't!, if you are the team leader & also the scrum muster, you should try to be less dominant, your workers\programmers always feel that you are testing them, yes this is true the team leader is always watching you, but try to do this without irritate them, let them feel you trust them, let them make their mistakes, this will also help them feel that they are talking to their friends not to you. (it sounds stupid, but there is a lot of ego in the room after all, and some one should give up).
  4. Implement the whole class do not left stubs out there. (or, daily meeting as a part of the whole scrum methodology)
    • The problem
      • People are implementing only part of the system.
    • Resolving the problem
      • I don't think that this is a real big problem, but you must understand the strengths and weaknesses of each feature in the methodology so you could choose whether to implement or not.
      • I think you can't do daily meetings without the scrum review.
      • I do think that you need to implement the whole methodology together, but if you need to start, it is better to start with
           part of the methods and learn the other on the fly.

What do you think?

Saturday, March 10, 2007 11:01:03 AM (GMT Standard Time, UTC+00:00)  #    Comments [2] - Trackback
Software Development | Agile | Scrum

Monday, March 12, 2007 12:42:11 AM (GMT Standard Time, UTC+00:00)
Hi all,

This is a great posting and good luck with your starting of Scrum!

If you'd like to learn more about Scrum, please visit www.implementingscrum.com -- a blog that I update at least on a weekly basis and covers a lot of ground about what Scrum is like in the real world.

Enjoy!

- mike vizdos
www.michaelvizdos.com
www.implementingscrum.com
Wednesday, March 14, 2007 8:49:06 PM (GMT Standard Time, UTC+00:00)
Hi Mike,
Thanks for your feedback.
Comments are closed.
Archive
<February 2012>
SunMonTueWedThuFriSat
2930311234
567891011
12131415161718
19202122232425
26272829123
45678910
Disclaimer

Disclaimer
The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.

© Copyright 2012
Shani Raba
Sign In
Statistics
Total Posts: 145
This Year: 0
This Month: 0
This Week: 0
Comments: 97
Cool Stuff
Add to Technorati Favorites
Themes
Pick a theme:
All Content © 2012, Shani Raba
DasBlog theme 'Business' created by Christoph De Baene (delarou)