Comments on: Team Concert Beta 3 Out http://blog.martinig.ch/news/team-concert-beta-3-out/ Wed, 10 Mar 2010 07:07:29 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: Handly Cameron http://blog.martinig.ch/news/team-concert-beta-3-out/comment-page-1/#comment-2275 Handly Cameron Wed, 21 May 2008 10:25:26 +0000 http://blog.martinig.ch/?p=103#comment-2275 The daily meeting in Scrum is specifically not a status meeting. It is a way for the team members to coordinate their work and bring attention to any impediments to the progress of the current iteration. Problem solving and issue resolution is taken offline so this quick 'stand-up meeting' should take no more than 15 minutes. Here is a good reference: http://www.mountaingoatsoftware.com/daily_scrum The daily meeting in Scrum is specifically not a status meeting. It is a way for the team members to coordinate their work and bring attention to any impediments to the progress of the current iteration. Problem solving and issue resolution is taken offline so this quick ’stand-up meeting’ should take no more than 15 minutes.

Here is a good reference: http://www.mountaingoatsoftware.com/daily_scrum

]]> By: Bill Higgins http://blog.martinig.ch/news/team-concert-beta-3-out/comment-page-1/#comment-2186 Bill Higgins Tue, 13 May 2008 10:23:52 +0000 http://blog.martinig.ch/?p=103#comment-2186 Hi, thanks for the interesting write-up! With regards to: "we are agile" vs. reduce status meetings, I don't think these are in conflict. I think there are just different *types* of status meetings - the high-bandwidth sort that agile teams prefer and the low-bandwidth variety that suck time and energy. Jazz and Team Concert help eliminate the latter type. Some more detail... High-bandwidth status meetings are short and focused on clarifying priorities, communicating and reiterating important information, and reaching consensus on open issues. Low-bandwidth status meetings tend to be long, ponderous, and involve going around the room to find out "where is everyone at?" Developers take a guess at where they're at w/r/t their work (95% done!) but the guess is often based on a vague perception rather than empirical data. As a result, the quality of the information is very low, not to mention many people who might otherwise be coding or testing are simply sitting there waiting for "their turn". Jazz and Team Concert help eliminate the low-bandwidth status meetings by automatically collecting a lot of empirical data about the state of development as a side-effect of performing routine activities like delivering code and working with bug reports. Jazz does a lot of behind the scenes aggregation and analysis to distill many gigabytes of development data into meaningful reports that give you the high-level view of the state of development. Conversely, if you want more detail, you can drill-down from these high-level reports into the lower-level data (e.g. change-sets, bug reports) that are represented by the reports. But to be clear, we don't claim that Jazz and Team Concert make all status meeting unnecessary... just the ones that destroy our souls :-) Hope this was useful. If you'd like to see it in action, you can view our own self-hosting Jazz repository at Jazz.net: https://jazz.net/jazz/web/projects/Jazz%20Project (Jazz.net registration required). Bill Higgins Jazz.net and Jazz Platform teams Hi, thanks for the interesting write-up!

With regards to:
“we are agile” vs. reduce status meetings, I don’t think these are in conflict. I think there are just different *types* of status meetings – the high-bandwidth sort that agile teams prefer and the low-bandwidth variety that suck time and energy. Jazz and Team Concert help eliminate the latter type. Some more detail…

High-bandwidth status meetings are short and focused on clarifying priorities, communicating and reiterating important information, and reaching consensus on open issues.

Low-bandwidth status meetings tend to be long, ponderous, and involve going around the room to find out “where is everyone at?” Developers take a guess at where they’re at w/r/t their work (95% done!) but the guess is often based on a vague perception rather than empirical data. As a result, the quality of the information is very low, not to mention many people who might otherwise be coding or testing are simply sitting there waiting for “their turn”.

Jazz and Team Concert help eliminate the low-bandwidth status meetings by automatically collecting a lot of empirical data about the state of development as a side-effect of performing routine activities like delivering code and working with bug reports. Jazz does a lot of behind the scenes aggregation and analysis to distill many gigabytes of development data into meaningful reports that give you the high-level view of the state of development. Conversely, if you want more detail, you can drill-down from these high-level reports into the lower-level data (e.g. change-sets, bug reports) that are represented by the reports.

But to be clear, we don’t claim that Jazz and Team Concert make all status meeting unnecessary… just the ones that destroy our souls :-)

Hope this was useful. If you’d like to see it in action, you can view our own self-hosting Jazz repository at Jazz.net: https://jazz.net/jazz/web/projects/Jazz%20Project (Jazz.net registration required).

Bill Higgins
Jazz.net and Jazz Platform teams

]]>