How many developers do you have working simultaneously on 1 Appian development i

On our current project, we've had up to ten working simultaneously, but I'm sure there are other project that have had more.

Were they working on completely seperate applications? How do you prevent them from stepping on each other's toes?

We had 5 or 6 working on one application and the rest on another.

The applications were large enough that developers didn't need to work on a single item at the same time so managing that wasn't too hard, though we did need to coordinate things like changes to core CDT items as such a change would update many peripheral items that might be locked by other developers. We did this using a combination of email and IM as we have a distributed team, and any changes such as the one above were done outside of normal development hours.

Obviously there's a point at which developers start to get in each other's way as you can't have two or more developers working on a single process - though I would imagine if you reach the point where timelines are so constricted that you're having to get two users to work on the same thing, then the project has wider issues...!

Was your distributed team in the same timezone?

No - some in IST and the rest GMT.

What was the highest number of developers that you had working in the same timezone?

The timezones overlap so ten would work at once, but we'd have had about six at once in GMT.

Thanks Phil! Anyone else interested in sharing some stats?

I've worked in an environment with 6 simultaneous developers working on the same code base. However unlike Philb we were all in the same building so proper coordination between the developers was far easier to achieve.
Ultimately we ended up assigning two developers to every large piece of functionality (for redundancy) and segmented the code base as much as possible to partition each person's reach.
Shared code was inevitable and we actually implemented a 'soft locking' style of development on them - any shared/global object that had to be modified, regardless of the scope of change, had to be clearly communicated to the group.