Sep 172011
It's the software, silly

Earlier this week, Renee Troughton wrote about the confusion that sets in with the various definitions used to describe requirements in agile development: Epics, Themes, Stories, Features, MMFs, MVPs, MVFs, MMRs, Goals, Objectives, Tasks, etc. As I read her post, I caught myself thinking about whether the different distinctions really help me write better software. Meanwhile, Renee points out that people don’t always agree on the distinctions. Go figure, with so many ways to describe them. If producing software is our main objective, then we come up with distinctions to [read more…]

Sep 122011
Getting started with a new agile team

Starting an agile project with a new team provides a great time to reflect on what we take for granted. It offers an opportunity to refocus on what we think is ultimately most important. We anticipate the questions new team members have. We see reservation as they engage teammates who have more experience. We’re ready for the moments they sometimes shut down or defer to others’ “leadership”, even as I hear them making sound observations and assertions, and leading the team in their own way. We watch their pensive expressions [read more…]

Aug 132011
Running the QA guantlet?

To borrow from another phrase, “defects happen.” Even six sigma processes are not without defects. By definition, a six sigma [manufacturing] process is one in which 99.99966% of the products manufactured are statistically expected to be free of defects. That amounts to an average of 3.4 defects per million opportunities. We are left to ask how much is reasonable to invest in those last 3.4 defects… It is not the role of QA to prevent defects Over the last couple weeks there has been a great conversation on LinkedIn about [read more…]