> The coding part might or might not be pair-programming
If more than one developer is working on a task and they aren't pair-programming doesn't that suggest that they have looked at the task and how to implement it and split the task into independent sub tasks that they are each working on. But isn't that the approach to just about any modern development process?
In just about any team I've been in we've all had a good understanding of the architecture and issues/approaches that other developers are working on both formally and informally.
If more than one developer is working on a task and they aren't pair-programming doesn't that suggest that they have looked at the task and how to implement it and split the task into independent sub tasks that they are each working on. But isn't that the approach to just about any modern development process?
In just about any team I've been in we've all had a good understanding of the architecture and issues/approaches that other developers are working on both formally and informally.