Yesterday I had the opportunity to participate in a one day Kanban workshop by AgileSparks. The workshop was intended for leaders and managers and so one morning I found myself sitting in a conference room with project managers, team leaders and one VP. Although it meant that not everything I learned was directly related to … Continue reading Kanban workshop for Leaders/Managers
In the last few weeks I’ve been presented with a new idea – a team that writes automated unit tests after the code has been fully implemented. Coming from a test first background the practice of writing unit tests seemed – just wrong. If writing unit tests for your code is a good practice – … Continue reading TDD is more than just writing unit tests
I have been practicing Agile and SCRUM for the better part of my career, I have seen it done in many ways as well as abused from time to time. Although there are clear guidelines on how SCRUM should be done, in each company it was done differently. Many SCRUM practitioners believe that “all team … Continue reading Code ownership in Agile teams
A while back during a presentation on unit tests a member of the audience asked me a question I hope never to answer ever again - “So these unit tests you’re talking about, are they written by developers?” The reason I don’t particularly care for that question is that developers think that unit tests (and … Continue reading Why TDD is good for testers
After we’ve covered the typed of developers I pair programmed with I want to explain how pair programming can be done – based only on my observations: Turn based The idea is very simple – you change places, after a predetermined interval. Whoever wrote code (driver) becomes the one who reviews the code (passenger) and … Continue reading Four ways to do pair programming
Pair programming is an agile practice – in a nutshell it means that two developers set together using the same computer to write code. If you look for pair programming definition in Wikipedia you’ll see a very concise and detailed definition of how pair programming should be done. in my experience there are several ways … Continue reading Four types of developers you might be doing pair programming with
It is always nice to hear when a fellow developer succeeds and what makes these posts even better is the fact that they also contain valuable tips as well. Lessons learned from an Agile project (David Tchepak): Dave^2 writes about an agile project he’s been part of for the last 18 months - and he … Continue reading Links: Being Successful with Agile and unit testing
If you’ve been reading my blog you may have noticed that I’m not above self advertisement and this post is no different. At Typemock we’ve started a series of webcasts called “this week in test”, as you might have guessed we post a new episode each week. This is the place where two guys talk … Continue reading This Week In Test Webcast
I just cam back from the ALT.NET meet-up (It was great!). I met with very interesting people and learned a few new things, right now I’m going over my notes from the session to try and sort the information in my head. One of the sessions I participated in was about how to convince a … Continue reading How to start SCRUM/Unit testing in your organization
IMistaken blog has a post about The Agile Bibliography Wiki - a great resource that anyone who uses Agile development methodologies should know. It has links to various studies and papers on all things Agile: How effective is TDD? How to apply Agile in difficult situation (ex. GUI testing). Success stories of large companies using … Continue reading Agile Bibliography Wiki
Helper Code 