Summary of my position is that public shaming sucks and I would not recommend using it. From my book draft: Don't Punish People for Breaking the Build (Safety)...
Thankyou all. You've helped me understand why I think the idea of "the duck" smells (to use a refactoring term) and have started me thinking about the ...
The duck *doesn't* work. It creates fear, and fear is the mind killer. It makes people conservative, when I want them to be aggressive. I have a funky...
I like that idea - that you're looking to support people as much as possible in order for them to reach further. Perhaps that's a secret behind good management...
We used to have a viking hat that people had to wear until the build was fixed. On 1 Nov 2005 07:32:02 -0000, melbourne_XP_enthusiasts@yahoogroups.com ... -- ...
Presumably the spirit was one of fun, and an indicator that someone was working on fixing it - yes? We do ask people to take responsibility for broken builds -...
The idea that concerns me is: mobbing - where the group chooses a single person the blame for the group's problems and starts attacking them. Usually, it tears...
Supporting people is a value. It is why the first value in the Agile manifesto is "Individuals and interactions over processes and tools", which generally...
... Heathen begone! No, I agree. If the build is never broken, then the "build box" doesn't really provide any value. A team could put a lot of effort into...
Roll Up! Roll Up! Come One, Come All! Welcome to the first inaugural MX-PEG Pair Programming Competition! On Tuesday November 8, from 6:30-8:30pm, MXPEG...
As steve pointed out, it was a sence of fun.. when emotions got a little raw we dropped the idea. The aim was to discourage broken builds.. My current project...
If you don't foster an environment where people are able to make mistakes, then people will not take risks and not learn. ... -- Nigel Thorne Extreme...
Please count me in. Cheers Dave ... From: melbourne_XP_enthusiasts@yahoogroups.com [mailto:melbourne_XP_enthusiasts@yahoogroups.com] On Behalf Of murray_bishop...
I found the presentations quite a good introduction to FDD, however I think more mention of how to incorporate formal testing teams into/around the process...
"Ask 'why' five times whenever you find a problem. By repeating why five times the nature of the problem as well as its solution becomes clear." Nope I haven't...
The five why process sounds interesting. I haven't heard of it before - but I'll take a stab at what it means. It seems to tap into the idea that examination...
It's not gimmicky, it's a well established process for root cause analysis used for a long time within major lean corporations like Toyota. It's a very simple...
I read the webpage. It seems you start of with the problem and a group. You put the problem to the group and use their responses to break down the problem into...
My interpretation of the five whys is to force you (the facilitator, investigator or whatever) to delve deeper than you might otherwise have done. In...
Hi All, Here's a quick unofficial statement of likely attendance numbers at the November MX-PEG, based on responses I've received in this forum and via email. ...
We would like to remind you of this upcoming event. Melbourne XP Enthusiasts Meeting Date: Tuesday, November 8, 2005 Time: 6:30PM - 8:30PM EST (GMT+11:00) ...
melbourne_XP_enthusia...
Nov 7, 2005 7:32 am
2334
Hi Andy, I will be interested to attend. I will take my laptop along. Java would be my preferred language :-) Another of my friend will be coming along too -...
Hi, At work I find some other teams are very strict and mechanically setting the next iteration target velocity to the last iterations obtained velocity, then...
Definatly take into account holidays and any known time you will loose. Also, take a rolling average of the last few iterations, so the velocity is smoother. ...
Speaking of estimation: Are there other tools, ideas, paradigms out there which people use to help them estimate. I see good estimation as critical in client...
I'd like to thank Andy Marks for putting together the workshop that we experienced tuesday night, Ben Johnston and whoever else helped put together the code ...
... * Estimate by comparison. "Story x is like story y, which took us 3 days". * Track reality. "We know story y took us 3 days cos it says it on the card" *...
... Of course it is. How silly of me (Year 11 was a long time ago for me). I wonder why the word velocity is used in XP development rather than speed......
