CodeBetter.Com
CodeBetter.Com
RSS 2.0 via Feedburner
           Do you Twitter? Follow us @CodeBetter

Raymond Lewallen

Framework Design, Agile Coach, President Oklahoma City Developers Group, Microsoft MVP C#, TDD, Continuous Integration, Patterns and Practices, Domain Driven Design, Speaker, VB.Net, C# and Sql Server

June 2007 - Posts

  • Calling Bologna!

    The title may sound obscure, but its actually something our scrum team recently implemented.  Using a keyword to designate that the scrum was turning towards status-meeting or small meetings are taking place.  This team is new and has limited or no experience working together, and most of them have not worked under Scrum process management, so there is an overal team learning curve that is ongoing.

    Daily stand-up meetings are designed to answer 3 questions: what did you do yesterday, what are you going to do today, and do you have any obstacles in your way?  A good indicator that your daily meeting is not following the quick path to conclusion is when somebody actually asks a question.  Usually, this shouldn’t happen, although is permissible depending on the context.

    We were having issues with daily stand-ups getting way out of hand and conversations between 2 or 3 people (of a 10 person team) taking up 10–15 minutes of time, while the rest of us just sat around waiting for them to finish.  After several comments by multiple team members, we have now decided that we would implement a keyword that anyone can shout out at any time they think the daily stand-up is getting off course.

    Bologna!  I wanted to go with bullshit, but bologna was the 2nd thing that came to my mind and the rest of the team seemed to be ok with that word.  What’s great about the new warning signal, is that when somebody gets off track and doesn’t notice, somebody cries Bologna! and they instantly realize “Yeah, I was getting away from the purpose.”  Its a great tactic and is serving us well in the first week of implementation.  Its still being said every day, but I think we’ll move to point where it may come up once or twice a week at most.

    Also, after spending a day with Pete Behrens and another day with David Hussman, I took Pete’s advice and went ahead and went to Mike Cohn, an awesome teacher, and did my scrum master certification.  3rd time in 5 years I’ve been through a scrum course and I just keep learning every time.  If you are looking into it, I’d definately recommend Pete or Mike either one.  David isn’t a CST that I am aware of, but awesome, awesome agile trainer.

  • Welcome new CodeBetter member, Patrick Smacchia, the man behind NDepend!

    In case you didn’t notice, CodeBetter has added none other than your favorite static code analysis tool author, Patrick Smacchia!  Patrick Smacchia is the author of NDepend.

    Patrick brings to the table a wealth of information and experience, and we certainly look forward to reading what he has to say about the trials and tribulations of developing a tool like NDepend, and where its headed in the future.  I personally have had the privilidge of knowing Patrick for awhile now and have had many conversations with him about NDepend and the future and features of the tool.  Patrick never ceases to amaze me with his visions.  He is an exciting person to be around and is very passionate about great software and code metrics.

    I could write 2 pages on why I am a big fan of Patricks and we are all thrilled to have him aboard.  We certainly needed someone to take up the slack that I’ve left behind, having not blogged in over a month (summertime, kids, work, running user groups, directing code camps and helping with conferences, training, the list goes on and on and on).

More Posts

Our Sponsors

Free Tech Publications