"Agile Project Manager"? That's a no-op. A non sequitur. "Agile", in my opinion, is really about the following things (tactically, not philosophically, cuz we

"Agile Project Manager"? That's a no-op. A non sequitur. "Agile", in my opinion, is really about the following things (tactically, not philosophically, cuz we all know "people over processes" etc.): * Don't churn requirements * Ship quality software One could probably argue that the first probably is a necessity of the second (how can you ship anything of quality if the requirements are shifting under your feet?) but let's keep them separate. "Don't churn requirements" -> keep tasks small. don't change your mind 1000 times a week. keep tactical horizons short (e.g. don't estimate long-range). "Ship quality software" -> automated tests. code reviews/pair programming. just-in-time lightweight specs. integrated business users, design, ux, qa with development. retrospectives/kaizen.