Can you build and deploy to test with one step? I bet you can build in one step. Can you get your software somewhere it can be tested just as easily, reducing your cycle time.
Can you go from commit to production deploy in less than 30 minutes, including running your tests?
Do you do an automatic build after each commit and keep historical metrics on your builds? Doing a build on every commit means that you may be able to track the origin of a failing test to a single culprit. Keeping metrics means you'll be able to spot when a build starts to take longer, or help identify twitchy tests.
Do you have a bug database? Does someone own the triaging of bugs? Does the person who wrote it, fix it?
Do you have daily stand-ups where the whole team attends, and an active product owner?
Do you have quiet working conditions? Are they relaxed and flexible? Does the team look forward to coming to work?
Do you have access to the tools you want? Do you have to beg for a virtual machine to run tools on? Do you have the flexibility to choose your desktop system?
Do you ever have to hot desk?
Do you use TDD and/or BDD? Do you have team members who focus on automated quality assurance?
Do you have testers with a good understanding of the problems you're trying to solve.
Are you encouraged to innovate? Do you have some latitude in the technical solutions? Can you embrace new methodologies, and happily discard those found wanting?
Java technical lead and solutions architect in London for the e-gaming industry for ten years. more...