Skip navigation

Tag Archives: agile

I spend a ton of time in DHTML land these days. Most of that development takes the form of a hybrid XP/Scrum Agile methodology. That said, I’m dealing with story cards. While the system works well, there’s nothing I dislike more than a story with endless acceptance criteria. I’m sure you’ve experienced one of these. There has to be a better way, right?

Let’s try screenshots, pictures, storyboards — call ’em what you want. I’d prefer a business analyst scribbling on a blank canvas much more than line items. Especially (ESPECIALLY) when we’re talking DHTML. Find a whiteboard, grab a marker, and bring the digital camera.

=)

I’m making an attempt to introduce Selenium into the development cycle. With that said, a fellow programmer mentioned that he’s been “thinking more and more like a QA tester”. I believe his comment is spot on in terms of how testing toolkits change the development thought process. No more are we simply “fixing the bug”, but we’re now spending more thought cycles making an attempt to keep the story from coming BACK from QA. This is clutch. Recognizing that time is wasted moving story cards back and forth from stages in the agile development cycle. Eric Gamma mentions “Test Infected” programmers as those who cannot begin coding without a test in place. I’ll admit, we’re using Selenium AFTER writing code, but I’m hopeful we’re not far from becoming, well – infected.

My point is that velocity isn’t necessarily about coding quickly, but is more about minimizing defects and keeping closed story cards — closed. Again, tighten the feedback loop.