Monitoring Team Process
Gu & Maher
[email protected]
University of Sydney, October 2004
DECO2005
Life-Cycle of Design Projects
•
Description of the events that occur between the
beginning and the end of a project inclusively.
Monitoring Team Process in Different Road Maps

Waterfall:





Classic life-cycle in
which each activity is
completed once for the
entire set of
requirements.
Top-down
development.
Independent phases
done sequentially.
An entry and exit point
of each phase.
Issues for monitoring:


Simple: top-down
monitoring.
Access outcomes with
the purpose of each
phrase.
Monitoring Team Process in Different Road Maps

Incremental



Waterfall in overlapping
sections.
An iterative life-cycle is based
on successive enlargement
and refinement of a project
through multiple sub-cycles.
Issues for monitoring:

Assess outcomes with the
purpose of each phrase in
each sub-cycles as well as
the flow in the main lifecycles.
Monitoring Team Process in Different Road Maps

Spiral
Identify sub-problems which
has the highest associated
risk.
Find a solution for that
problem.
No fixed phases.




Issues for monitoring:




Difficult to monitor: require
higher analysis skills.
First to asses the solutions: if
the solutions solve the subproblems.
Identify the phase that each
sub-problem belong to.
Evaluate the process: if the
team is working towards
solving the whole design
problems.
Monitoring Team Process in Different Road Maps

Prototyping




Building a replica of design.
Equivalent of a mock-up.
Start with informal
requirements, and use a
working model to transform
the requirements.
Issues for monitoring:


Similar to waterfall.
Access the development of
the prototype with the
purpose of each phrase.
Monitoring Team Process in Different Road Maps

Extreme






Listening, designing, coding, testing.
Lightweight, evolutionary development process.
Rapid feedback.
Incremental change.
Embrace change.
Issues for monitoring:

Dynamic monitoring as there is no map to follow.
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.
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.
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.
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.
Developing Your Own Project: General Issues
•
Review


Review whether the design meets the requirements.
Each group conduct a review session:
Each member is a reviewer.
Identifies potential problems and document them.
Address the problems.



Strategies towards a Smooth Team Process
•
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
•
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
•
About dividing workload:


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
•
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.
Strategies towards a Smooth Team Process
•
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
•
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.