The Specialist Challenge on Agile Teams
When I first started managing projects it was normal that project managers would be responsible for multiple projects at the same time. Unless the project was especially large, it was expected that a project manager could simultaneously handle three or four separate initiatives at different stages of the project lifecycle. It was also common for team members on those projects to be assigned across multiple projects and to split their time between project and operational work.
That still happens to some extent, but fortunately organizations have recognized that having to continuously switch focus is an inefficient way of working, meaning it’s a much less common model today than it used to be. Agile goes one stage further, not only encouraging people to be assigned to one agile team 100% of their time, but also suggesting that those teams should be stable from one initiative to the next. There’s a lot to be said for this approach as it encourages heightened productivity with individuals becoming more comfortable working together. While there are limits to that, there’s no doubt that stable teams improve performance.
This stable team concept is made possible by another element of Agile—the idea that teams should be cross-functional. That is that multiple people on each team can do any given piece of work and that each person can perform multiple types
Please log in or sign up below to read the rest of the article.