Summary


On this project, our team understood what we needed to build and we were eager to get started. But it took much longer than we'd predicted before we were a productive team. If we had the project to do over again, we'd spend more time in the beginning focused on the people issues. We'd make it easier for the team to coalesce by launching the project in a more formal way ”by holding meetings ”instead of expecting things to just "work out." Our experience indicates that spending time in the beginning of the project to create the team will save you time later.

In parallel with attending to the team issues, you need to prepare for the work ahead. Create simple plans that communicate your intentions. Remember: At this stage of the project all plans you produce are best guesses rather than accurate statements. Don't spend a lot of time on details; most details will probably change later.

Finally, select your initial process. As with your other plans, this is a best-guess process. It too will change. Most project teams put too much effort into their initial plans; remember that your initial attempt does not have to convey all the details. However, when you've assembled your plans, make sure you communicate them to the whole team and that the team members agree to work with the plans and process you devise .



Software Development for Small Teams. A RUP-Centric Approach
Software Development for Small Teams: A RUP-Centric Approach (The Addison-Wesley Object Technology Series)
ISBN: 0321199502
EAN: 2147483647
Year: 2003
Pages: 112

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net