As an agile team we are terribly affectionate about lots of things and Standups is one amongst them. We do it everyday religiously and discuss our last day’s activity, plan for today and hurdles one needs to over come.
I feel like ritual when I attend the meeting every morning. I could feel very subtle differences between this type Standups and Status meeting. The bigger and better benefit of it is to have a shared commitment across the team and to get a positive feeling. If some pair is having a problem it becomes teams problem and the whole team should try to solve it.
Unfortunately umpteen times it remains as status meeting. I believe we should be proactive enough to say NO to such meetings because if it is just about status we have card wall.
I am working on how to make my team more insightful and proactive about standups rather than just one morning ritual.
Stuff about software development, agile and testing
Wednesday, June 27, 2007
Labels
- agile (4)
- agile testing (1)
- build tool (1)
- design (1)
- DSL (1)
- duck typing (1)
- eclipse (1)
- ejb3 (1)
- Fluent Interface (1)
- grails groovy (1)
- groovy (1)
- gwt (1)
- hacking (1)
- haskell (1)
- java (1)
- javascript (1)
- jvm (1)
- languages (1)
- mac (1)
- pipes (1)
- programming (1)
- qa (1)
- rant (2)
- ruby (6)
- sas (1)
- scala (3)
- scripting (2)
- software rewrite (1)
- statically typed (1)
- testing (4)
- two phase commit (1)