The completion of the entire development lifecycle will often spawn into a new project. How do you deal with setting up a version 2.0 and what are some of the best practices for Team System? Here is a little bit of guidance:
The logical place to start is creating a new team project. This will allow you to designate new work items for your project (thus isolating them from the previous project). You can also assign new team members and a new workflow based on process improvement strategies outlined in this book.
There may be some circumstances where you will want to start development of your new version of an existing project within an existing team project. The main determination of whether a new team project is warranted should be based on factors such as the following:
Team members—If the personnel will remain relatively the same on both projects, then you can have the choice of either starting a new team project or sticking to the existing one. If you are starting with a considerably different team, then we would recommend starting a new team project.
Process—If your new project is substantially different from original one (for example, you are creating a Web-based version of a WinForms application), then creating a new team project makes sense. If you want to build the new application using a process that differs from the original project (for example, you used Extreme Programming on ...