Difference between revisions of "Schedule"
(→By Friday, May 6th) |
|||
| Line 1: | Line 1: | ||
| − | + | ===Team Management Overview=== | |
| + | <br /> | ||
| + | The team will be exercising an agile development plan. The team will meet up for 15 minutes at least every two days and tell the team what they have done since the last meeting, what they will do before the next meeting | ||
| − | |||
| + | In the standard of the agile development process we will value: | ||
| − | |||
| − | + | ''' Individuals and interactions''' over processes and tools | |
| + | ''' Working software''' over comprehensive documentation | ||
| + | ''' Customer collaboration''' over contract negotiation | ||
| + | ''' Responding to change''' over following a plan | ||
| − | |||
| + | Individuals and Interactions – in agile development, self-organization and motivation are important, as are interactions like co-location and pair programming. | ||
| + | Working software – working software will be more useful and welcome than just presenting documents to clients in meetings. (Getting the game working is more important than documents) | ||
| + | Customer collaboration – the requirements for the game can not entirely be collected at the start of the project, we must collaborate with customers (audience) to find flaw and redesign the game. | ||
| + | Responding to change – agile development is focused on quick responses to change and continuous development. | ||
| − | |||
| − | + | The principles are: | |
| − | + | * Working software is the principle measure of progress. | |
| + | * Sustainable development, able to maintain a constant pace. | ||
| − | + | * Close co-operation with lecturers, critics and audience. | |
| − | |||
| − | + | * Face-to-face conversation is the best form of communication. | |
| + | * Projects are built around motivated individuals, who should be trusted. | ||
| − | |||
| − | + | * Continuous attention to technical excellence and good design | |
| − | + | * Simplicity | |
| + | * Self-organizing teams | ||
| − | + | * Regular adaptation to changing circumstances | |
| + | <br /> | ||
| + | <br /> | ||
| − | + | ===Team Member Check-in=== | |
| − | + | Each team member must provide their check-in here every day before they go to bed. They must write what they have done, what they will do, and what problems they have encountered. Team members should keep abreast of their fellow member's check-ins. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 02:34, 19 June 2011
Team Management Overview
The team will be exercising an agile development plan. The team will meet up for 15 minutes at least every two days and tell the team what they have done since the last meeting, what they will do before the next meeting
In the standard of the agile development process we will value:
Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan
Individuals and Interactions – in agile development, self-organization and motivation are important, as are interactions like co-location and pair programming.
Working software – working software will be more useful and welcome than just presenting documents to clients in meetings. (Getting the game working is more important than documents)
Customer collaboration – the requirements for the game can not entirely be collected at the start of the project, we must collaborate with customers (audience) to find flaw and redesign the game.
Responding to change – agile development is focused on quick responses to change and continuous development.
The principles are:
- Working software is the principle measure of progress.
- Sustainable development, able to maintain a constant pace.
- Close co-operation with lecturers, critics and audience.
- Face-to-face conversation is the best form of communication.
- Projects are built around motivated individuals, who should be trusted.
- Continuous attention to technical excellence and good design
- Simplicity
- Self-organizing teams
- Regular adaptation to changing circumstances
Team Member Check-in
Each team member must provide their check-in here every day before they go to bed. They must write what they have done, what they will do, and what problems they have encountered. Team members should keep abreast of their fellow member's check-ins.
