Summary

In this chapter, we revisited the mapplet design for release 1 and kicked it into shape, in preparation for release 2. There is often a bit of a lull between releases while the requirements are being sorted out for the next release. By keeping the releases short (no more than a month or two each), this lull is minimized—but it’s often still there. Your development team members may spend this time fixing bugs, playing Unreal Tournament, or sharpening up their resumes. But this could instead be an ideal time for them to revisit the design and bring it and the code back in sync. This prepares them nicely for building upon the product in the next release. This is also an Agile ICONIX safety net: a chance to regroup and put all your ducks back in a row if they have started to wander off their line.

The mapplet release 1 was an early alpha release of the mapplet. It immediately generated some interesting feedback from the customer, which helped the team to formulate and prioritize the second release. But that’s another story (…but luckily, it’s in the next chapter).

The next chapter also introduces an interaction design technique that can be used in conjunction with ICONIX Process.