Thanks to the Boston IIBA for an excellent presentation & discussion last night about collaboration, requirements and how the role of the analyst fits into an Agile project. For me, the discussion was quite interesting and I came out with a couple key points that are worth reiterating. I find myself being confronted with the question, “so what does an analyst do in an Agile project?”. There are a number of derivations on this query, but the thinking seems to go something like this: the job of the analyst is to write the requirements, if we’re now putting the customer in direct contact with the development team, what’s the point of an analyst? One participant even mentioned that taking a complex document away and simply helping people write user stories sounded like “a glorified secretary”.


Techniques for Agile Project Managers -