Last modified 16 years ago
Last modified on 03/06/09 13:06:08
Analysis
Overview
The project blog shows the world what happens into Sophie 2 and how
Task requirements
Write two blog posts for this iteration
Post 1: (at the iteration start)
- Last sprint overview (added features and functionality)
- Explain interesting technologies introduced in this sprint
- What went well
- What could be better
- Decided improvements that will be applied
Post 2: (at the middle of the iteration)
- Progress overview
- Interesting technologies used
- Challanging tasks
- Applied improvements (from the sprint closing)
Task result
Two blog posts.
Implementation idea
Use the 0m04-closing.txt in the manage folder in the repository - there are collected the "What went well, what could be better and how to improve.
Related
SCS_PROJECT_BLOG_R0
SCS_PROJECT_BLOG_R1
SCS_PROJECT_BLOG_R2
How to demo
Show the blog posts.
Design
- Content of the Summary post:
With the conclusion of our fourth iteration comes the summary of what have been done. As scheduled we've launched our second release which covers all functionalities that we've promised. We manged to catch up with the analyses from previous iterations and the next one. The new funtionalities included in the release from 13th February 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 exeptions. * Undo/Redo of the move frame action works. * Create book action now is not undoable. * Undo/Redo of page resize action now works. * The book does not resize with it's title change action anymore. * There is now change when selecting the current frame anymore. * Undo/Redo text editing in text frames now works. * Fixed the "Redo" item in the edit menu to show "Can't redo" when the user can not redo an action.) * Improved Halos and HUDs * Initial plugin support * Build Server Also numerous bugfixes were done. Other things that worth mentioning are the branding discussions with Robert Abbot from ''Shift Global'' which are available [http://sophie2.org/trac/wiki/Videos here] and the fact that we analized all tasks till iteration 04. The results of the retrospection, as usual are separated in the following three categories: What went well: * Improved overall quality - most of this iteration we were working on refactoring and improving the existing logic * Functionality - the release team managed to implement many new funtionalities that cover all requirements for the current release * Analyses - we managed to catch up with the analyses for the previous and next iterations. * Discussions - we've done a lot of useful discussions concerning the design and the overall ideas of the project. Videos of these discussions are available [http://sophie2.org/trac/wiki/Videos here]. * HR and recruitment - we've improved the procedure for recruiting new team members * Improved Site - we refactored our old website and now it is more attractive and useful What could be better: * Some team members weren't available - this was due to the exams at the university * Few tasks of this iteration were done - we worked on few tasks from fourth iteration * Discipline and process - it is improving, but it still could be better * Better documented discussions - we need to document better our discussions, this way it's going to be easier for the remote people to be productive * More tested tasks - not enough tasks were tested during this iteration. How to improve: * Spread global vision - more people need to understand the fundamental ideas behind the project, and have overall view of the entire picture * Discuss - the people need to ask themselves the questions "Why?" and "How?" that's why we need to discuss even more * Specifications explanations - something like a specification skeleton needs to be created * Don't accept - we must fix the bad code, not to reproduce it Best regards from the Sophie team!
- Send the sample content to Ludmil and Nick for approval
- After discussion with milo we've decided that the second post is obsolete because of the changed process and the fact that we needed to catch up, and most of the information in it will be presented in the summary for the fifth iteration.
Implementation
- After the feedback from Nick and Ludmil, the content of the post for the blog 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.)
Comments
Declare this task implemented when both posts are done.
