As a developer/tester I want to understand the user story So I can build/test it correctly. Mind you, this is a terrible user story. What does “understand” mean? And what is the acceptance criteria for “build it correctly”? Life is messy, and the “As a…” template doesn’t always help. You can over-cram it to make
Every now and then, I need to remind people what is the point of this agile thing. I know, I know, still they forget. Agility is the ability of the organization to react effectively to changes in a volatile environment. The “more” agile the organization, it can cope better, faster to things thrown at it.
Scene 1: Tragedy We’re in a retrospective. This was after a major event, so we discussed a few of the things that have gone awry, like delayed integration with other teams, unfinished stories, and then how we’re going to fix them. All in all, a good open discussion. And then, as we’re getting ready to close
WHAT A RUSH! Still thinking about the awesome conference. But that’s for a separate post. For now, here are the slides for my BDD/TDD Star Wars talk.
That’s it boys and girls, we’re coming to the finish line! We’ve got Melissa Perri and Olaf Lewitz as keynotes, got workshops for everyone and I’ll be giving my Star Wars BDD session. I have friends I can’t wait to see again, and new people to meet. There’s probably going to be some booze involved
My interview on InfoQ about “Test-first approaches with TDD and BDD” is live. Go check it out. And come to the Agile Practitioners conference to experience these things yourselves!
New post in the Everyday Unit Testing series, dealing with instance constructors. Check it out!
When people first try scrum, or TDD (or any new process), they feel uncomfortable. We “know how to do” stuff, but then we’re asked to try on something new. Then our comfort zone alarm goes off. We feel constrained. Scrum puts limit on sprints, so we’ll need to actually help the testers finish testing our story.
Or is it MOAR? Check out the new post (and example) on Everyday Unit Testing. It’s fresh!
This is the final part of the Rebooting ALM series. You should also read: Part I: Evolution Part II: Power Part III: Weakness We’ve covered where ALM tools excel, and where they falter. Now, allow me to fantasize about how we can take a leap forward and start solving actual problems for real ALM users (that’s