Version 6 (modified by todor, 16 years ago) (diff) |
---|
Analysis
Overview
Mail list eases communication between team members.
Task requirements
Send 2 e-mails
- Mail 1 should contain information from the sprint closing
- Mail 2 should contain sub-team information
- Collect information about sub-team mail lists
- Suggest creating sub-team mail lists where none (See implementation idea)
- Send an e-mail containing information on sub-team e-mails
Task result
e-mails sent to the developers mail lists. New mail lists if needed.
Implementation idea
Implement this tasks in parallel with SCS_PROJECT_BLOG_R2
For the sub-team mail list sophie2-devs-teamname@googlegroups.. format would be usable.
Related
SCS_PROJECT_BLOG_R2
SCS_MAIL_LIST_R2
How to demo
As the mails are sent and people have seen them, explain what is done in a sentence.
Design
- Used the 0m03-closing.txt to create a sample content of summary mail for the third iteration
With the end of ITERATION_03 comes our regular summary, about what has been done. At first look our results are not very impressive. We've managed to complete 40 out of 113 tasks which makes 34%. On the other hand the number of successful tasks is much higher than the previous sprints. The server team managed to finish all of their coding tasks and even one from the ITERATION_04. As a result we now have functional Hudson build server (www.sophie2.org:8080) and operational Sophie2 testing server (www.sophie2.org/s2s). Other teams also did a good job and now we have Sophie2 Author deployed via JWS. On 15 of December was launched our first release which is now available at http://sophie2.org/trac/wiki/Download , now we're looking forward to our second release which is planned for 13 of February. The conclusions of the ITERATION_03 closing are: What went well: * New PCs * Server team finished all their tasks * Team split * Progress checks are useful * Done more discussions * Utilize other rooms * New team members integrated * Some people with global vision What could be better: * Discipline and respecting the process * Availability of some remote team members * Need better organization * Small percentage of finished tasks * Better productivity needed After discussions in which participated all team members, we've decided that we need to work in several directions in order to improve our work: * Improve self discipline - we must respect the process and follow the established rules strictly (commit daily reports, use internal backlog, provide information about our availability in advance) * Better organization between teams - all team leaders need to improve their communication with their team members and other teams * Provide and discuss ideas about improvement - all team members are encouraged to propose different ways for improving our productivity (the proposals may concern all aspects of our work process) * Work towards the overall goal - we need to have better overall view of the project * Team leaders do daily reviews - this is one of the ways to improve the team communication and improve discipline Regards, Sophie team.
- Send a copy with the sample content to Ludmil and Nick for possible corrections.
Implementation
(Implementation results should be described and linked here (from the wiki or the repository))
Testing
Comments
(Write comments for this or later revisions here.)