3 ms·
I personally would look for specific practices and specific results. For example, I think a focus on quality is necessary to enable real agility, so I'd look f
by wpietri 10y ago
I personally would look for specific practices and specific results.
For example, I think a focus on quality is necessary to enable real agility, so I'd look for unit tests, acceptance tests, continuous integration, continuous deployment, pair programming (or fast-cycle code reviews).
And for looking at results, I look for things that are hard to fake, like release cadence, amount of work in process, and unit of work size. So I'll ask, "When was your last release? And how about the release before that?" And I'll want the difference to be small. (My favorite place to work released multiple times a day.) I'll ask other questions like, "What are you working on? Who's working on that? When did that start?"
Another thing I'll measure teams by is the extent to which they're focused on problems vs features. Good teams ship things that solve problems (and make sure that they actually do). Bad teams ship features because that's what the spec says or what the boss wants.
- BurningFrog 10y agoThose are good ideas. Better than asking "So how agile are you?". I was hoping for a way to look at a job posting without going in and ask people, but I guess that's not really that feasible. Maybe I just need to devote a few weeks to chat with a lot of companies when I'm ready to go back to work.
- wpietri 10y agoYeah, I think most job postings are so poorly written that there are too many false positives and negatives to use them for much filtering. The main thing I'd eliminate first off is anybody requiring Agile certifications; organizations that lean on that have basically given up on thoughtful hiring. Good luck with your search! If you're in the Bay Area, feel free to drop me a line when you go back and I can recommend some places.