Tag Archives: Best practice

Here at Kanban, we practice all software engineering best practices to the letter. Check out our content engineering blog to learn more!

Experience Optimization

Delivery Best Practice: The Value Of “Rambo” Testing

Content Engineer Karen PetersonThis is Part 2 in a series on Kanban’s delivery best practices.

At Kanban, we create test scripts that verify the proper display and behavior of every item that the client signed off on in our functional specification. When we plan our QA stage, we also take into account two other types of testing: regression tests of existing functionality, and Rambo testing.

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 →

The Marketing Technology Office

Delivery Best Practice: Single Comment Repository

This is Part 1 in a series on Kanban’s delivery best practices.

Content Engineer Karen PetersonMuch of a project manager’s job requires a wrangling of tiny details. The more complexity there is in the design, the more details will come out over the entire course of the project. Every touch point adds to our understanding of how the client expects their functionality to work.

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.

Continue reading →