Agile Testing with Lisa Crispin

My new article “Story Mapping the Wrong Way”, a tale of how I messed up our team’s first attempt at story mapping but we learned stuff anyway, is on Techwell and Stickyminds. How fascinating! :->

I just posted our team’s recent experience in taking a different approach when presented with an unusual problem: one theme that needs to get out the door, and another that will be hard to “hide” but will take multiple sprints. Please check it out on my Techwell/Stickyminds blog. How does your team handle unusual situations?

My teammate Nanda Lankalapalli and I have an article in StickyMinds on how we use technical debt sprints to keep our technical debt to a manageable level. There are lots of approaches to managing technical debt – what works for your team?

My first blog post on the new Techwell site (a site provided by the same people who bring you Stickyminds) tells the story of how my team recently tried an experiment to get the business and the Product Owner to give us requirements, mock-ups and other information about user stories before we do our sprint planning. Part of this experiment was inspired by our use of MercuryApp (itself another experiment, to improve our ability to learn from our retrospectives). Read more on my Techwell blog.

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.

Please see my StickyMinds Blog for a new post inspired by Jeff Patton’s recent presentation to our Agile Denver user group. The Whole Team Approach isn’t just for developing the software! We need to really think Whole Company. Comments welcome!