You recently completed the first phase of a software-intensive mission-critical system. Your clients and stakeholders are all pleased, and you move on to the next stage of growth. This phase will...

You recently completed the first phase of a software-intensive mission-critical system. Your clients and stakeholders are all pleased, and you move on to the next stage of growth. This phase will bring a new set of highly wanted features and is expected to take roughly a year to develop and deploy. Because you're working in stages, many internal versions will be produced and evaluated before the final product is delivered. You're currently using a configuration management system, with all development in a trunk. You have a release plan that outlines the iteration in which the second phase features will be implemented. Everything is going as planned. You get a call from your user point of contact around two months into the second phase. They have an urgent system problem that they need you to fix. You have more resources (developers, testers, equipment, etc.) to deal with the issue. It will, however, necessitate concurrent development on the same system, with one team focusing on the fix and the other on the second phase.

Part 1)Explain how you'd modify the development process to solve the issue while continuing to work on the second phase features.

Part 2) Would you alter your configuration management strategy in order to incorporate the fix? Why do you think that is?

Part 3)How would you organise the fix's pre-delivery testing?

Part 4) Would you consider including any of Phase 2's features into the "fix" delivery? What variables might influence your choice?