Analysis
(The purpose of the analysis is to give as much as possible of the needed information for designing and implementing the task.)
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 the new team members are subscribed
- send at least one mail with the progress of the last iteration
- create manage/reports/m02b/0m02b-closing.txt in the design part and use it when writing the mail
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 results of this task must be mails that all subscribers of the sophie2-dev mailgroup will recieve.
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.
- You may use the manage/reports/m02b/0m02b-closing.txt
Related
SCS_MAIL_LIST_R0
SCS_MAIL_LIST_R1
SCS_PROJECT_BLOG_R2
How to demo
Show the mail(s) that were sent to the mailgroups.
Design
- Created manage/reports/m02b/0m02b-closing.txt containing information about the last sprint
- Open sophie2-dev mailgroup and check whether all team members are subscribed
- Send mail about our progress since the last mail report
- Sample content of the mail:
It's been a while since we've last reported our progress. Now it's time to catch up and inform you about Sophie2 status.
Because we didn't manage to finish ITERATION_02 in time and with desired result, we were compelled to schedule additional ITERATION_02b in order to finish all the tasks left from previous iterations and raise even more the quality of the product. Because the lack of resources during ITERATION_02, we started and designed most of the task but few tasks were completely finished. On the other hand a lot of new people joined our team for ITERATION_02b and with collective effort we've finished it successfully. Most of the tasks were completely finished and the rest we intend to finish as soon as possible. Some of the things that need to be mentioned are the created overviews (project and development) and our progress in server related tasks (some demo pages are already created).
Results from the retrospection of ITERATION_02b: What went well:
- There are more people integrated now
- Useful discussions were done
- Most tasks were finished
- Very good productivity at the end of the sprint
- Useful presentations in Sheraton Hotel
What could be better:
- We didn't finish all tasks
- Lack of machines
- The oragnization should be better (too much noise)
- There was no clear description to some tasks
How to improve summary:
- Make more design discussions
- Start hard tasks early
- Focus on PLATFORM_STANDARDS
- No new code last day
- Weekly task boxing
- More information about development tools in the wiki
Another thing worth mentioning is the new team infrasrtucture. Because now we're more people working on more tasks, we decided to make team split in order to achieve better productivity and quality. Now all team members are divided into a different teams (Main, Base, Extra, Server, Analysis, Release). Maybe later more detailed information will be included in the process page. Now we're looking forward to our first release scheduled for 15th of December.
Best regards, Astea Team.
Implementation
The mail has been sent with some little corrections the result of this task must be in your mail's inbox.
Testing
Comments
Since there are no releases yet, the "users" mail group is missed. The next revision of this task will have a sophie2 release behind, so we must not forget to address them next time. -kyli
