1. Your dress code prohibits hoodies – a key requirement of Agile.
2. You consider yourself an Agile centrist – that Manifesto sounds kinda socialist.
3. You keep a copy of the project requirements in your trunk for traction.
4. You hold a scrum every third Wednesday, whether you need it or not.
5. You favor Agile process – as soon as requirements, design, implementation, verification and maintenance are done.
6. The cafeteria vending machines don’t carry Red Bull.
7. You practice occasional iteration. Continuous iteration sounds so exhausting.
8. Your project manager is well-rested, takes long lunches, and golfs twice a week.
9. Your meeting minutes binder weighs the same as a small pony.
10. Stakeholders don’t want to know about coding progress – it would ruin the surprise.
One thing I also do as a tester is to help the team coonrtl scope. Most newbie agile teams over-commit, and they work on stories that are too big. Find ways to divide the work into small chunks or threads. Make sure testing estimates are included in story estimates. Sometimes features take longer to test than to code! When you see a story that looks too big, ask if it can be divided up. Sometimes the smaller piece may not deliver much business value, but the team needs to focus on getting one small story done at a time, including all the testing activities.