The myth surrounding Agile projects goes something like this: a small team of developers who can handle any coding task (database, business logic, user interface, middleware, etc.) works hand-in-hand with the end user who talks with the development team about the details of the work requirements. The small-team-filled-with-generalists model may work for some small projects, but it doesn’t scale. The problem has been with confusing two parts of the traditional development problem: collaboration and specialized skills.
Advisor
Agile in Balance: Collaboration and Specialization
Posted July 2, 2020 | Leadership |
![Agile in Balance](/sites/default/files/styles/square_thumbnail_180x180_/public/APM/Advisors/2020/bea200701.png?itok=jGdW_y53)
Don’t have a login?
Make one! It’s free and gives you access to all Cutter research.