Matt Wynne taking it one tea at a time
Organised and facilitated by Elizabeth Hendrickson this was a great group of people to meet with. Elizabeth ran the day as an open-space, a format which I really enjoy, and which worked very well for such an interesting, intelligent and enthused bunch of people. I came away from the day having had the chance to …
Continue reading “The Agile Alliance Functional Testing Tools Workshop”
Did I mention that I like pair programming? Here are some reasons why it’s good for you and your boss. More Trucks The higher the truck number of your team, the more resilient it is to losing people. Pair programming spreads knowledge of the code around the whole team meaning each team member has a …
Continue reading “7 Reasons Why Pair Programming Makes Sense”
As I may have mentioned I’m running a session at Agile 2009 called ‘Debugging Pair Programming’. There’s a preview of the session tomorrow night at Skills Matter and I’ve just finished preparing for it. Mind if I run a couple of things past you?
I’ll be running a preview of my Agile 2009 workshop ‘Debugging Pair Programming’ at Skills Matter on Monday 10th August. If you’re on a team that’s using or trying to adopt pair programming, this is a great chance to explore and understand some of the complex reasons why this is such a difficult skill to …
This afternoon I paired up with a colleague to fix a bug that had been introduced some time ago but, because the effects weren’t very noticeable, had only just come to our attention. Fixing the defect itself was actually quite easy – the real pain was writing a script to clean up the bad data …
Talking on the internet is fine and everything, but there’s nothing like a face-to-face chinwag. This year I’ll be hanging around at a couple of conferences so maybe we can meet up? At Agile 2009, I’ll be running a workshop called ‘Debugging Pair Programming’. This is a spin-off from an impromptu open-space session I organised …
(1) Pick a new feature to add to the product you’re working on. (2) Sit down with the customer (or their representative on your team) and brainstorm all the scenarios that might happen when a user tries to use the new feature. Try to make the scenarios as small and granular as you can, so …
There are no iterations: only now. Work at a pace you can truly sustain. Done means it is in the user’s hands. Nothing less. Limit the Work in Progress. This forces you to get things done, or you’ll have nothing else to do. Get better all the time. Keep tuning your process and tools to …
My team has been working with a Kanban pull / flow system which means we have the luxury of being able to do just-in-time analysis of individual features, rather than trying to do them in a batch for an iteration. We’re getting better at this analysis, and I thought it was worth sharing what I …
Estimate: an approximate calculation of quantity or degree or worth Commitment: the act of binding yourself (intellectually or emotionally) to a course of action Estimates are not commitments. Plans based only on estimates are bad plans. Commitments based only on estimates are at best foolish, at worst dishonest. Estimates are certainly a useful tool for …