Changes between Version 11 and Version 12 of PROCESS

Timestamp:

09/30/08 12:19:23 (17 years ago)

Author:

todor

Comment:

--

PROCESS

@@ -43 +43 @@
  * That is, seek a good solution. 
 7. Quality is not negotiable! - but scope and resources are
- * If something can not be done in acceptable quality, given the resources (time) and scope (functionality) it has, the we either reduce the scope, or increase the resources.
+ * If something can not be done in acceptable quality, given the resources (time) and scope (functionality) it has, then we either reduce the scope, or increase the resources.
  * We are not allowed to reduce the quality! 
 8. Accept the challenge!
@@ -70 +70 @@
  * For one month, we usually have 10 meetings, which means you may skip at most 3. 
 7. In case you can not be present in a meeting, you have to warn the leader before this, and have a representative (someone else in the team) who will represent you. [[BR]]
-8. You have to write in the end of every working day daily report about what have you done during the day. You have to write how much effort each activity takes. See report structure(TODO).
+8. You have to write in the end of every working day daily report about what have you done during the day. You have to write how much effort each activity takes. See report structure in the repository /manage/reports/0README.txt.
 
 == Other ==
@@ -95 +95 @@
  * Trying to have much higher quality.
  * Hoping that the lost of speed will be compensated by non lost of momentum (that we usually suffer from)
- * The sprint backlogs will be wiki page (TODO: link when ready).
+ * The sprint backlogs will be wiki page ([wiki:DevelopmentsHome]).
  * The four state of a story/task are:
   * to [analyzing, designing, implementing, done, testing]