If you’ve ever wondered how much documentation is enough in an agile project, or you’ve heard you don’t even need documentation with agile, please check out my article on StickyMinds about how my teams have approached agile documentation.
I have enjoyed a lot of ensemble / mob programming, aka teaming, over the years. As a diverse group, including people with different deep skills,
Gitte Klitgaard reminded me recently that it’s been 10 years since we met at BoosterConf. It seems like yesterday, and it seems like a lifetime
Let’s take a look back at release engineering – my experiences with it, that is. I recently listened to an episode of the AB Testing
When I tell people what “DevOps culture” means to me, they want to know how they can help it grow in their organization. The term
More learnings from Agile Testing Days 2023! This is part 3, and I’ll need at least one more post! I still haven’t gotten to the
The Agile Testing Days program always includes a vast range of topics. Some are perennial favorites, some are totally original. This second post about stuff
3 comments on “Agile Documentation”
That was a really interesting article and on a topic I struggled with a lot when I first switched to Agile. And although my thoughts have evolved a lot since I started ( and wrote this piece on it: http://www.everydayqa.com/2010/agile-development/documentation-on-agile-developement-teams/ – I still feel like it is one of the biggest issues our team faces- the struggle to maintain the right amount of documentation with out getting bogged down by process.
As our automated regression suite has grown, it has been a great reference and in a way, has served that documentation role, as you mention. I am also hoping to get archived pivotal tracker stories to play a similar role in the future.
Great post!
Thanks, Devon! I’m going to read your post too.
[…] Agile Documentation […]