|
Collaboration and reuse lie at the heart of every Agile project. To deliver quality software, teams must rely on each others' knowledge and feedback. Of course, there's never time to start from scratch - refactoring and leveraging existing assets are mandatory parts of an effective process. It's also great to see reuse truly be a means to an end, rather than seeing companies just promote a "reuse initiative" as a general goal. What's most interesting to me, however, is how distributed Agile projects implement collaboration and reuse. In this issue, we'll hear some experiences from highly distributed onshore and offshore Agile projects and how they've succeeded.
To start, Kirk Knoernschild presents an "Agile Matrix" for cross-pollinating teams with process and technology expertise. Kevin Parker describes how the next generation of application lifecycle management tools must support micro- and macro-level development processes. And John Cunningham shares his company's best practices in delivering complex distributed Agile projects.
Set as favorite
Bookmark
Email this
Hits: 4030 Comments (0)
|
| < Prev | Next > |
|---|


Collaboration and reuse lie at the heart of every Agile project. To deliver quality software, teams must rely on each others' knowledge and feedback. Of course, there's never time to start from scratch - refactoring and leveraging existing assets are mandatory parts of an effective process. It's also great to see reuse truly be a means to an end, rather than seeing companies just promote a "reuse initiative" as a general goal. What's most interesting to me, however, is how distributed Agile projects implement collaboration and reuse. In this issue, we'll hear some experiences from highly distributed onshore and offshore Agile projects and how they've succeeded.
