As Esther says in her fine comment,
There are lots of ways to do all these things — and sometimes teams do all the “practices” but still don't meet the principles.
Exactly. And it's very hard to see the principles under the project when you're reviewing a resume.Here's a statement I've seen on lots of resumes: “Led the development of some-feature-or-system.” Does that mean the candidate architected the whole thing and handed it off to coders? Does it mean that the person used some set of collaborative techniques, but did all the architecture at the beginning of the project? Does it mean that the person was a technical lead who collaborated on several prototypes with other developers? Maybe the candidate helped the product owner decide which features were architecturally risky, and suggested the team implement those features first, to see how to evolve the architecture. And if you're seeing a person who's collaborative, is that enough for your project?I don't know how to see the underlying principles on a resume in keywords. I do know how to look for principles as I read the whole resume. And if you see enough principles, then it's worth a phone screen for the candidate.