They are asked to work together—producing “working code” in increments.
The team is self-directing; self-managing, and self-organizing. That implies that it’s pretty much up to the team to figure things out. Sure you can have managers hovering around the team and providing leadership, support and occasional guidance. But the best agile teams are pretty much left alone to deliver.
There is also the notion of generalization over specialization; in that you want the team to be as generalist as possible. For example, developers can design, write use cases or user stories, test, and deliver their functional contributions. So the broader each team member views their skill and responsibilities, the better. No hard silos allowed!
Call for Feedback
So, rather than my trying articulate whether they should or shouldn’t be in agile teams, I’m looking for reader feedback to generate discussion.
- Do Business Analysts and Project Manager(s) have a place within Agile teams?
- And if they do, what do they do? Seriously, what do they focus on?
- How do they collaborate as part of the team? What are their primary roles? And contributions?
- If they re-frame from “old role” to “new role”; what changes need to be made?
My personal sense in both cases is that, yes, there is a place for Business Analysts and Project Managers within agile teams. Not leveraging their skills as they traditionally have, but more so transforming themselves to contribute within the context of an agile team. I would also argue that there are wider opportunities within agile teams to contribute.
But that’s just my perspective. What’s yours?
Thanks for listening,
Don't forget to leave your comments below.