Changes between Version 17 and Version 18 of SCS_PROJECT_BLOG_R1

Timestamp:

10/21/08 15:45:43 (16 years ago)

Author:

pavlina

Comment:

--

SCS_PROJECT_BLOG_R1

@@ -26 +26 @@
 As a whole during this iteration we've established some fundamental standard about the work processes and created templates for task completion howtos. Most of our work was concentrated on writing documents and templates that will ease our work in the future. Although we've made a lot of changes on them and that cost us a lot of time in refactoring already finished tasks according to the new templates. Now we have a firm base that we'll use in the future.
 
-Our goal for the next sprint is to increase productivity, so that we can do everything on time. For the second iteration we have 61 planned tasks + 3 unplanned tasks (left from the previous sprint). These should be done until 2008-10-31.
+Our goal for the next sprint is to increase productivity, so that we can do everything on time. For the second iteration we have 61 planned tasks + 3 unplanned tasks (left from the previous sprint).
 We've also took some decisions on how to improve:
  * Focus time - from :15 to :00 of each hour is time to focus. No distractions are allowed during focus-time. If it is really important to communicate with someone, the communication should be done in a way that does not affect the others.
- * Task ordering - as part of SCHEDULE_MAINTAINANCE task, the tasks should be ordered in appropriate way.
- * Maintainance tasks should be done first (and not last).
- * As part of WIKI_SETUP someone should ensure that everything is up after a power failure.
- * In order for people to have better idea what each task is about, we should describe each planned task briefly in the beginning of the sprint. The results of these are in m02-descriptions-bg.txt and m02-descriptions-en.txt
+ * Task ordering - as part of [wiki:SCHEDULE_MAINTENANCE_R1] task, the tasks should be ordered in appropriate way.
+ * Maintenance tasks should be done first (and not last).
+ * As part of [wiki:SCS_WIKI_SETUP_R1] someone should ensure that everything is up after a power failure.
+ * In order for people to have better idea what each task is about, we should describe each planned task briefly in the beginning of the sprint. The results of these are in [source:manage/reports/m02/0m02-descriptions-bg.txt] and [source:manage/reports/m02/0m02-descriptions-bg.txt]
  * We decided to have a weekly meetings, every monday at 10:00(EEST). They should not be long, so everyone has to be on time. The weeklies consists of a short report of everyone, on "What were you doing the last week", "What will you do the next week", "Impediments", followed by a tech presentation (of a library, technology, tool, etc.) or a design discussions. Everything should be no longer than 1 hour.
 
@@ -39 +39 @@
 The following post will be the second for this revision of the task:
 
-At the moment we're in the middle of our second iteration. And we decided that it is about time to give you some more information about our progress. We've managed to integrate Maven and Ant so far, and we're adopting new workflow which aims to ease us in distinguishing the different phases of each task. It also will give us the opportunity to leave comments which is very useful option. After the first iteration being more "documents/standards oriented", we're now beginning to focus more and more on coding tasks related to Sophie basic functionalities. We're also working on the three unfinished tasks from the first iteration.
+At the moment we're in the middle of our second iteration. And we decided that it is about time to give you some more information about our progress. We've managed to integrate Maven and Ant so far, and we have Sophie 2.0 builds using these technologies. We're adopting new workflow which aims to ease us in distinguishing the different phases of each task. It also will give us the opportunity to leave comments which is very useful option. After the first iteration being more "documents/standards oriented", we're now beginning to focus on coding tasks related to Sophie basic functionalities. We're also working on the three unfinished tasks from the first iteration.
 
 As we're moving forward we expect our team to grow, this way we will sustain our work pace. This way it will be easier to achieve higher quality at the expected milestones.