What are you trying to say in this article? That the resume writer doesn't have IT experience or that that he doesn't know how to express it? This is a typical user-response to an IT catch-22:
No matter how the author (resume writer) tries to address the problem, the variety of the audience, from non-technically-interested mangement to non-educated employees, nitpick the words. If we use technical words and ideas to automate and streamline, the response is: it's "too simplistic" (because they don't understand the context). If we try to describe the detail, our design "is too complex". If we try to implement user simplicity, 'it's too expensive'.
Perhaps SCRUM was a fresh approach to *his* former company. Or perhaps you are exactly correct in this example and didn't adequately communicate that.
Who will be *filtering* his resume, by the way? An IT expert who is hiring another IT expert, or an HR person with minimal IT experience and simplistic hiring directives (from the non-technical CEO)?
Keep Up with TechRepublic