dodoskido powered by

The Hanso Foundation :: home :: Mascara Reviews


* Scrum *
comments

Moving to a new project isn't enough. Let's mix things up a little. We'll introduce a whole new set of tools for test modeling, coding, and automation (mostly internal Microsoft tools) and let's change the entire process! They call it scrum, so far it's ho-hum.

I mean, I'm all for scrum and what it entails, but so many folks in our team has been doing waterfall for so long that things are just difficult for them now. While I understand their predicament, it has been rough on me and the likes of others who are gung ho on the whole scrum thing.

Scrum seems to be especially rough on QA since we're used to (or supposed to be used to) getting full documentation of things before we begin testing. The QA team I'm on is definitely a document heavy group. The problem is that we've always written a lot of documents in the past but rarely have they been used. We'll use them ourselves for writing test cases, but bevelopers and PMs just sign off on them and hide them under their pile of documents.

The idea of scrum and agile development is to document things just in time and to have the entire team work in sync rather than throwing documents over the wall at each other. Not to sound "zen" or anything, but the whole point is to just start writing good code that will document itself.

Anyway, we're just beginning our second sprint and things have been slow going. The morning scrum has been dragging on quite long. We're supposed to be speaking for 60 seconds each, but invariably the team gets rat-holed or we spend lots of minutes saying


"let's take this offline"
"ok, I'll schedule a meeting"
"ok"
"today at 2pm good for you"
"sure..oh wait, let's do three"
"ok, I'm looking for a room now"
"ok, I think conf room b is available at that time"
"yeah, you're right"
yada yada

You get the point...I hope it isn't always like this, but I kinda think it's going to take a lot longer to adapt to the new system than we thought. It'd be nice to have a scrum master lead us through the conversations in the morning until we get the idea (so far QA has been doing well in this regard...we just say what we did, what we're doing today, and how we're blocked and that's it).

Anyway from all of this, I've been looking at unit testing frameworks and so far I think the team has settled on nUnit, but I think this is in flux now that Visual Studio Team System 2005 has some nice testing tools built in.

My research has lead me to a mega blog post that lists a LOT of resources for learning about this stuff: Darrell Norton's Blog [MVP] : .NET Test Driven Development. Now I just need to sift through it all and come up with a sample application to play.












Post Your Comments (scroll down). Jump back to archived comments or the top.




Drink Guinness?
Tags