To be most agile with your communication, understand several models of learning styles, where you fit into them, and where your team fits into them. By tweaking the ways you communicate to fit the information and the situation, you are helping your team remain agile by valuing people and interactions over processes.

There's a simple rule for the minimum values testers should explore: “none, one, some”—or, how the software behaves if you send it nothing, one thing, or some set greater than one. It's not comprehensive, but it gives a good feel for how the feature works at the moment. Developers can also use this in unit testing.

Sprint retrospectives are often skipped, compressed, or organized in a way that doesn't provide good feedback. This is unfortunate, as a well-planned retrospective is a great way to improve how you work. Good retrospectives enable engagement and safety, distill and prioritize ideas, and create concrete action items.