Unstable Requirement vs. Unstable Team
As you would have noticed, the cyberspace is buzzing with discussions on Agile. It covers various aspects of theory and practice of agile methodologies, but I have seen very little discussion on what happens when the agile development team is not stable. What happens when number of the developers leave the team midway through the project and has to be replaced by developers who have not been a part of the project earlier?
Basic assumption in Agile is that both the requirement and the solutions crystallizes in the mind of the developers over multiple iterations. It is a shared knowledge among the member of the project team and can also be supplemented by documentation. The documentation is not expected to replace the understanding of the developers. In many cases the code is expected to be the documentation, but full understanding may not have been translated to code. There is built in redundancy to the developer knowledge as part of it is shared by the whole team. But it is obvious that 100% sharing is not possible. XP can help, but what happens if both developers leave?
So here is my conclusion!