| Version 11 (modified by todor, 16 years ago) (diff) |
|---|
Analysis
Overview
The mail list must provide to the registered users information about the current state of Sophie 2.0, and give them opportunity to participate in the product's development, and learn about product functionalities and the status of the project.
Task requirements
During this revision of the task you must:
- make sure that everyone is subscribed (Nick, Steve,...)
- send at least one mail with the progress of the last iteration
During the task you may (suggestion):
- send 2 more e-mails with current status notifications - when all of the analyses are completed and when all designs are completed.
Task result
The result of this task must be at least one mail that everyone of the mail list has received.
Implementation idea
The mail about the status of the project might be similar to the post in the blog about our progress for the last iteration.
Related
How to demo
Show the mail(s) that were sent to the mailgroups.
Design
The design of this task will include the mail that will be sent during the implementation phase:
- mail to sophie2-devs maillist:
Hello to all who are interested in the Sophie 2.0 development process, with the end of our first iteration comes our first mail about the current status of the project.
Like some of you may know we've managed to complete almost all tasks of ITERATION_01, and now we're looking forward our next iteration. As a fully open project like Sophie 2.0 is the information about our progress is publicly available at http://asteasolutions.net:7080/sophie2/wiki/SCS_SITE_DESIGN/DevelopmentHome where you can find more detailed information about the tasks we're working on and their condition.
Overall during this iteration we've established some fundamental standard about the work processes and created templates for how tasks must be executed. 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 and that cost us a lot of time in refactoring already finished tasks according to the new templates, now we've 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 in 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. We've also took some decisions on how to improve:
- Focus time - from :15 to :00 of each hour is time to focus. During it no distractions are allowed. 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 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
- 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.
I hope this mail will satisfy your interest in the project and its current status, now it is time to work so you can read such mail for the second iteration as soon as possible.
Implementation
Testing
Comments
Log
