wiki:SCS_MAIL_LIST_R4

Version 9 (modified by todor, 16 years ago) (diff)

--

Error: Macro BackLinksMenu(None) failed
compressed data is corrupt

Error: Macro TicketQuery(summary=SCS_MAIL_LIST_R4, format=table, col=summary|owner|status|type|component|priority|effort|importance, rows=description|analysis_owners|analysis_reviewers|analysis_score|design_owners|design_reviewers|design_score|implementation_owners|implementation_reviewers|implementation_score|test_owners|test_reviewers|test_score|) failed
current transaction is aborted, commands ignored until end of transaction block

Analysis

Overview

SCS_MAIL_LIST keeps mailing lists healthy.

Task requirements

Send two e-mails:

  • Mail1 to the sophie2-devs list - contains last sprint summary (taken from SCS_PROJECT_BLOG_R4)
  • Mail2 to the sophie2-users list - contains information mentioned below
  • Define what will be sent to the sophie2-users mail list
    • Features
    • Latest release
    • Upcoming releases
    • Features expected in the next release
  • Collect this information about current iteration and send an e-mail containing it.

Task result

Two e-mails. One to the developer group and one to the user group.

Implementation idea

For the e-mail one, keep the structure of previous revisions of this task. Contact the release team to get the changelog. You may include feature from the feature schedule the release team is working on.

SCS_MAIL_LIST_R3
SCS_MAIL_LIST_R2
SCS_MAIL_LIST_R1
SCS_MAIL_LIST_R0

How to demo

Explain what is done.

Design

Implementation

  • After the feedback from Nick and Ludmil, the content of the mail for the mail list is the following:
    With the completion of our fourth iteration comes the summary of what we've accomplished. We launched our second release on schedule and with all of its planned functionalities. We also managed to catch up with our analyses from previous iterations, and have analyzed all tasks through iteration 04
    
    The new functionalities in the 13 February release are:
    
    
       * Selecting multiple page objects
       * Page object alignment
       * Frame bounding properties; for example margins
       * Basic audio and video support
       * Undo manager:
             * Undo/Redo of the insert frame action now works without exceptions
             * Undo/Redo of the move frame action now works
             * Create book action is now no longer un-doable
             * Undo/Redo of page re-size action now works
             * A book does not re-size with its title change action anymore
             * Selecting the current frame is no longer considered as change
    
             * Undo/Redo text editing in text frames now works
             * The "Redo" item in the edit menu has been fixed to show "Can't redo" when the user cannot redo an action
    
       * Improved Halos and HUDs
       * Initial plug in support
       * Build Server
    
    Additionally, many bugs were fixed. Other things worth mentioning are the branding discussions with Robert Abbot, leading to an upcoming update of the Website look.
    
    The results of our most recent "postmortem", are separated in the three usual categories (What went well; What could be better; and, How to improve):
    
    What went well:
       * Improved overall quality - for most of this iteration we focused on refactoring and improving the existing logic
       * Functionality - the release team managed to implement many new functionalities that covered all requirements for the current release
       * Analyses - we caught up on the analyses for the previous iterations as well as completing them for the next one
       * Discussions - we had many useful discussions concerning Sophie's design and overall ideas for the project, including marketing and Sophie adoption. Videos of these discussions are available here
       * HR and recruitment - we've refined the process for recruiting new team members
       * Improved Site - we refactored our old Website and we believe it is now more attractive and useful
    
    What could be better:
       * Not all tasks in the iteration were completed.
       * Discipline and process - it is improving, but we are striving for even higher standards
       * Better documented discussions - we need to improve the documenting of our discussions; this will help members of our staff who are working remotely people to be even more productive
    
       * More tested tasks - not enough tasks were tested during this iteration
    
    How to improve:
       * Spread global vision - our new team members need to better understand the fundamental concepts behind the project and to have an overall view of the global picture behind Sophie
       * Discuss - our staff members need to constantly ask themselves the questions: "Why?" and "How?"
       * Specification explanations – a more formal specification skeleton will improve consistency
       * Never accept code that is not 100% as it needs to be - we must fix less than perfect code, not to reproduce it
    
    
    Best regards from the Sophie team!
    

Testing

(Place the testing results here.) ITERATION_06 Summary

With little delay, we're sending you the regular summary of what's been done during our sixth iteration.

As we already decided on the ITERATION_05 closing, we were working towards imrpoving our self management, and optimizing the work process in order to increase our productivity. In the sixth iteration we've intorduced the "groups" tasks, which basically is way to work on several tickets using only one group ticket which includes them. After the fifth iteration now we're back again to the subteam structure. ITERATION_06 was split to two separate minisprints, this way we improved the timeboxing of the tasks.

On 17th of April we launched our fourth release which is available for download from here (http://www.sophie2.org/users/downloads.html). This release continues to improve existing features and brings additional features to prototype status, including:

  • Skinning
    • Default Skin
    • Alternative Skin
  • Application help
  • Resource list filters
  • Resource change list
  • Book templates base support
  • Page templates (as resource)
  • Internal definition of Sophie Book File Format
  • Page zooming
  • Page property editing
  • Frame rotation

Below you can read the results of the sprint retrospection. What went well: What could be better: How to improve:

Comments

(Write comments for this or later revisions here.)