Advices of the Support Tools
From Ameise-en
The following list includes various advices for the relevant OS-Model which are associated to the support tools. Trainees get these advices directly from the advisor or the friendly-peer, to indicate and avoid difficult situations.
Allocation of the identifying advices on the support tools
| Advice | Tool(s) | |
| Friendly-Peer | Advisor | |
| The author should not be used as a consultant. | 
|
|
| The author itself should perform the correction of documents. |
|
|
| Previous phases should not be forgotten. |
|
|
| The previous phase should be finished, before starting the next phase. |
|
|
| The previous phase should be checked, before starting the next phase. |
|
|
| The previous phase should be corrected in reference to the review, before starting the next phase. |
|
|
| Only after a successful correction of a proceeded review, a new review can be proceeded |
|
|
| A correction should be made after performing a test. |
|
|
| The customer should participate in specification- and manual reviews. |
|
|
| The manual should be written in an early phase of the project. |
|
|
| Do not execute personal changes all the time. |
|
|
| The activity and utilization of your developers should be observed. |
|
|
| The employment of staff should be observed in each single phase. |
|
|
| Employees should not be removed prematurely from a phase. |
|
|
| Removing employees should be considered accurate. |
|
|
| Employees should get activities which they are qualified for. |
|
|
| Incomplete documents should be subjected to a further review. |
| |
