| Version 7 (modified by pavlina, 17 years ago) (diff) |
|---|
Analysis
Overview
To improve the quality of code, visible product, documentation and its regular reading we must have strictly defined rules to follow.
Task requirements
You have to:
- Define initial process(see http://10.10.117.10/mediawiki/index.php/Veda-Process-R2 for help)
- Keep track how the process works
- Tune it
Requirements to the task result
wiki page
Implementation idea
See http://10.10.117.10/mediawiki/index.php/Veda-Process-R2
How to demo
show the wiki page to the others, follow the instructions to the process and track the results
Design
- See what is useful from http://10.10.117.10/mediawiki/index.php/Veda-Process-R2 and write new document in important docs which define the process.
- In another document write down your observation and suggestions about the current process (see daily and global(if there is any) reports, iteration schedule, iteration logs and reviews)
- See what you can do to improve the process where it needs to be improved, gather opinions from others and redact the process document with the new ideas.
- there must be synchronization with the standards and the real analysis, design and implementation phases.
- there should be some rules and discipline added about the design phase, its review and implementation phase next to it.
- more discipline reading the available documentation and its changes during the iteration.(communication in the team with the new things for reading)
