1. Gu & Maher ning@design-ning.net University of Sydney, October 2004 DECO2005 Monitoring Team Process

2. Life-Cycle of Design Projects Description of the events that occur between the beginning and the end of a project inclusively.

3. Monitoring Team Process in Different Road Maps  Waterfall: l Classic life-cycle in which each activity is completed once for the entire set of requirements. l Top-down development. l Independent phases done sequentially. l An entry and exit point of each phase.  Issues for monitoring: l Simple: top-down monitoring. l Access outcomes with the purpose of each phrase.

4. Monitoring Team Process in Different Road Maps  Incremental l Waterfall in overlapping sections. l An iterative life-cycle is based on successive enlargement and refinement of a project through multiple sub-cycles.  Issues for monitoring: l Assess outcomes with the purpose of each phrase in each sub-cycles as well as the flow in the main life- cycles.

5. Monitoring Team Process in Different Road Maps  Spiral l Identify sub-problems which has the highest associated risk. l Find a solution for that problem. l No fixed phases.  Issues for monitoring: l Difficult to monitor: require higher analysis skills. l First to asses the solutions: if the solutions solve the sub- problems. l Identify the phase that each sub-problem belong to. l Evaluate the process: if the team is working towards solving the whole design problems.

6. Monitoring Team Process in Different Road Maps  Prototyping l Building a replica of design. l Equivalent of a mock-up. l Start with informal requirements, and use a working model to transform the requirements.  Issues for monitoring: l Similar to waterfall. l Access the development of the prototype with the purpose of each phrase.

7. Monitoring Team Process in Different Road Maps  Extreme l Listening, designing, coding, testing. l Lightweight, evolutionary development process. l Rapid feedback. l Incremental change. l Embrace change.  Issues for monitoring: l Dynamic monitoring as there is no map to follow.

8. Developing Your Own Project: General Issues Important issues:  A self-directed work team.  Follow the waterfall development model.  Always document your progress.  Design brief reflects the clients’ requirements  Each student in class is a supplier.  Define tasks required for completing the project and divide the workload equally.  Estimate time and resource required for each task.  Reserve time for review and design documentation.

9. Developing Your Own Project: General Issues Initial  First establish group dynamics.  Meetings, venues, modes of communication among the group members.  Strengths and experiences of each group member and other relevant information.

10. Developing Your Own Project: General Issues Requirements analysis  Design brief.  Collect the functionalities of the project from the customer (design brief) and provide an outline of what is expected from the project.  Documents the requirements and functionalities as the team perceive them.  Plan the processes and define roles.

11. Developing Your Own Project: General Issues Design  Conceptual design: big ideas.  Detailed design: decompose the project into smaller components and further decompose until they become well understood and manageable problems.  Define the internal structure of each component, and interface for each component.  Document the design for presentation.

12. Developing Your Own Project: General Issues Review  Review whether the design meets the requirements.  Each group conduct a review session: l Each member is a reviewer. l Identifies potential problems and document them. l Address the problems.

13. About communication:  Define roles of different members as early as possible.  Define relationships of different tasks as early as possible.  Choose effective communication tools that suit the team is a key factor to achieve success.  Develop an agenda for every meeting.  Learning to accept different viewpoints and being more willing to compromise are essential in all collaborative projects.  Keep other team members informed of your progress. Strategies towards a Smooth Team Process

14. About schedule:  Each member should take responsibility to complete his/her parts on time.  Have more than one person working on all parts of the project just in case one falls ill and so on.  Plan the due date of your project at least 1 week’s earlier than the actual due date. Strategies towards a Smooth Team Process

15. About dividing work load:  Divide the workload equally among the team members and make sure all conflicts are settled before the detailed development of design.  Keep track of the progress of members through group meetings. Strategies towards a Smooth Team Process

16. About design:  Plan adequate time on each phase, especially requirements analysis and design.  Make sure the design solution is agreed and understood by all team members.  Continually documenting the progress and reviewing the documentation is essential to the quality and completeness of the product.  Try to stay focus during the detailed development of design, and only modify the design as needed, but never change the whole design at this stage.  Reserve time for design integration if member are working on different parts of the design.

17. About review:  Constantly question on each design solution.  Conduct at least one review session among all team members.  Make use of the group presentation and address the feedbacks your receive. Strategies towards a Smooth Team Process

18. About documentation:  Document individual and team progress during the whole project.  Use the documentation from each stage for review.  Refine these data as resources for completing final submission and presentation. Strategies towards a Smooth Team Process