Agile development management
We recently started moving toward Agile software development at work, and I was feeling a bit uncertain. The core reason for this uncertainty was that Agile is a developer-centric methodology and I didn’t understand how I fitted in as a Business Analyst, Project Manager and/or Product Manager.
Now I am a big fan of constant change, I just felt that developers were being given tasks that (despite being scoped user stories) still contained a large number of unknowns. I didn’t know if I trusted them to call me in when they got stuck, rather than finding the quickest route themselves. Additionally the roles of Project Manager, Product Manager and Development Manager were stepping on each other’s toes. Normally I am happy to write the requirements up front and then manage the project. Now there were no complete signed off requirements documents, project management was on a wall and the development team was in control. What am I meant to be doing? I am not someone who likes to sit back and wait to be called upon! I eventually found the following presentation, which was literally one of the only sources I can find about how Agile development management is meant to work:
Even though I am only just beginning with Agile I felt the presentation gave me a good sense of where I fit. What are your experiences in Agile management outside the development team?