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.
Not a member? Gain Access to the Cutter Experts today — register now to read select open-access articles.
Member/Guest loginForgot your password?