Rambo testing is somewhat of a misnomer: it’s not always about doing whatever it takes to break the new functionality. That would be too easy. It is about going off script in a thoughtful manner. The idea of Rambo testing at Kanban is to find legitimate ways that the customers or users might work with the system that are not explicitly documented in our functional spec, and thus wouldn’t be covered in our regular scripts. Continue reading
This is Part 1 in a series on Kanban’s delivery best practices.
Some project managers keep a record of everything that occurs in every meeting. This serves a CYA purpose, but it can create too much documentation to take action on. A comment repository only tracks decisions and remarks about the functionality of what is being built. We use it for creating and updating our functional specs and for refining our QA test scripts.