One of my goals is to have the teams leave their projects in a state that will make it possible - even easy - for other developers to resume wherever they leave off.

In order for that to happen it has to happen soon - not at the last minute. To that end, the second sprint will include a deliverable to test that.

For each team, some one person from each of the other two teams will build/deploy/install a version of the product. That means each team needs to specify the process carefully - the "one step build". In particular, the preconditions must be spelled out - what languages and environments are required on the development and production machines.

Each team will choose which two people get to work on building the other two projects. Of course their schedules will allot time for this.

The guest builder is the tester for the build instructions, so will provide feedback to improve them.

In principle, the guest builder has access only to the wiki, not to conversation with the team. In practice that might not be possible. But if it's not it should lead to an improvement in the handoff instructions.

We rejected my first idea, which asked each team to specify some particular (possibly small) piece of functionality that another team must code, test and deliver. That might asked too much of both teams. In particular, it might be too time consuming to specify the new feature clearly in advance, rather than in the relatively informal (read agile) incremental way we're used to in these projects. But if it's appropriate in any particular case this can happen.

The documentation required by the guest builder should be ready by Tuesday, March 23. You should schedule the two guest builds (by your team for the other two teams) after that - soon enough so that a there's time for a second iteration if that turns out to be needed. Back to the CS682 home page.