I have a confession to make: I was an agile developer.
I was one of this uncontrollable species who tells Project Managers that their plan isn’t working. We tore the BA’s specification apart and produced ominous user stories. We requested collaboration and wanted early end-user feedback on unfinished products. We had stand-ups, retrospectives and we always talked about time-boxes.
But it was us who made the magic happen. We delivered on time – probably not what was initially specified but what delivered most value to the customers. And they were pleased.
How did we achieve that? We followed agile principles using Scrum or Kanban. I’m now a Business Analyst/Requirements Engineer but I still believe in those principles. In this talk, I want to share 10 things you need to know, including:
•Why does the agile manifesto matter?
•How do Scrum & Kanban work?
•What is the BA’s role in an agile team?
Presentation held at Business Analysis Conference Europe 23-25 September 2013 in London (http://www.irmuk.co.uk/ba2013/)
Contact Christian via Twitter or LinkedIn.