As you can see from the WebLog title I am a bit sarcastic and cynical about this thing we call Software Testing. Over my years of experience in Software Development and Testing I have seen some very very Dilbert things happen.
Hopefully this Blog will be a good place for you to learn from some of the things I have experienced and allow you to be more effective in your efforts in Software Testing.
• January 29, 2010 - Traditional vs. Agile methods
Because I am a smartaleck... In tribute to George Carlin (think Football vs. Baseball)
Traditional vs. Agile
----------------------------
Stern Manly voice: In Traditional methods we drive to production.
Not so manly voice: In Agile methods we iterate until it's good enough.
Stern Manly voice: In Traditional methods we push a system out the door.
Not so manly voice: In Agile methods we deliver a demonstrable piece.
Stern Manly voice: In traditional we have firm and well defined requirements in documents in a repository.
Not so manly voice: In Agile we have loosely written user stories on post cards on a wall.
Stern Manly voice: In traditional the Project Manager is the quaterback of the group and guides the team to the release date.
Not so manly voice: In Agile we are all equal on the team and run together through the sprint.
Stern Manly voice: In traditional we have specifically trained people who wear a specific hat.
Not so manly voice: In Agile we have cross-trained people who can wear multiple different colored hats.
Stern Manly voice: In traditional we meet on a predifined weekly schedule to discuss the progress of the work.
Not so manly voice: In Agile we meet every day for 15 minutes to talk about what's blocking us.
Stern Manly voice: In traditional the product is the most important deliverable in the project regardless of individual contribution.
Not so manly voice: In Agile the people are the most important thing because we want them to feel good about their product.