Last modified 16 years ago
Last modified on 02/07/09 14:42:01
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 0m03-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
- File 0m03-closing.txt was created and stored in the reports directory of iteration 03:
Closing of Sprint 3 tasks complete/planned: 40/113 19 tasks were left as new: PRO_LIB_MODEL_COMMONS_R0 PRO_LIB_MODEL_PRO_OBJECTS_R0 PRO_LIB_MODEL_PRO_LISTS_R0 PRO_REGISTRY_PROP_VALUES_R0 PRO_REGISTRY_DEPENDENCY_TRACKING_R0 PRO_LIB_REMOTE_OBJECTS_R0 PRO_LIB_CONNECTION_INTERFACES_R0 PRO_LIB_LOCAL_CHANGE_SERVER_R0 CORE_LOCAL_STORAGE_R0 CORE_TEST_HELPERS_R0 CORE_ADDITIONS_R1 SCENE_COMMONS_R1 BASE_RESOURCE_LOCATOR_R0 BASE_SECURITY_MODEL_COMMONS_R0 PAGE_SCENE_IMPL_ALTERNATIVE_R0 TEXT_FRAME_NON_FLOW_R0 SEARCH_COMMONS_R0 MEDIA_ENGINE_IMPL_COMMON_R0 MEDIA_ENGINE_IMPL_ALTERNATIVE_R0 3 tasks were left in analysis started state: PRO_CHANGE_UNDO_MANAGER_R0 APP_PLUGIN_MANAGER_ABOUT_R0 MEDIA_ENGINE_IMPL_MAIN_R0 14 tasks were left in analysis finished state: UNPLANNED_DEVELOPMENT_OVERVIEW_R1 UNPLANNED_PLATFORM_STANDARDS_GENERAL_R0 PLATFORM_STANDARDS_CODE_R1 PLUGIN_SUPPORT_LIB_BASE_R1 PRO_LIB_CORE_PERFORMANCE_R0 PRO_CHANGE_INFOS_R0 PRO_CHANGE_MANAGER_R0 PRO_REGISTRY_PARENT_CHILD_R0 BASE_RESOURCE_POINTS_R0 DOCUMENT_FILE_MANAGEMENT_R0 BOOK_FILE_OPERATIONS_R0 EMBEDDED_BOOKS_RESOURCE_SUPPORT_R0 EMBEDDED_BOOKS_MANAGING_R0 GLOBAL_SPEC_MANAGING_R2 21 tasks were left in analysis ok state: PLATFORM_STRUCTURE_R2 PLATFORM_STANDARDS_DESIGN_R1 PLATFORM_STANDARDS_AUTO_TESTS_R1 PLATFORM_STANDARDS_MANUAL_TESTS_R1 PLATFORM_NFR_EXTENSIBILITY_R1 PLATFORM_DEPLOYMENT_BUILD_MAVEN_R1 PLATFORM_DEPLOYMENT_TARGET_APPLET_R0 PRO_LIB_CORE_THREAD_SAFETY_R0 PRO_CHANGE_COMMONS_R0 PRO_CHANGE_PRIMITIVES_R0 PRO_CHANGE_TRANSACTION_SAFETY_R0 PRO_CHANGE_COMPOSING_R0 BASE_MODEL_PAGE_ELEMENTS_R0 APP_BASIC_MENUS_R0 PAGE_TEMPLATE_BEHAVIOUR_R0 PAGE_TEMPLATES_LISTING_R0 PAGE_ELEMENT_ALIGNING_R0 PAGE_ELEMENT_MULTI_SELECT_R0 FRAME_HUD_R0 FRAME_Z_ORDER_R0 EMBEDDED_BOOKS_CONTENT_R0 7 tasks were left in design started state: PRO_LIB_CORE_MEMORY_MANAGEMENT_R0 BASE_MENUS_R0 APP_PLUGIN_STARTUP_R1 FRAME_TEMPLATES_R0 FRAME_PROPERTY_LOCKING_R0 SCS_ISSUE_TRACKER_MAINTENANCE_R2 SCS_TEST_TRACKING_MAINTENANCE_R2 2 tasks were left in design ok state: BASE_PERSISTENCE_INTERMEDIATE_STORAGE_R0 VIDEO_CONTENT_R0 2 tasks were left in implementation started state: PLUGIN_MODULE_STRUCTURE_R1 BASE_PERSISTENCE_COMMONS_R0 5 tasks were left in implementation finished state: PRO_LIB_CORE_MISUSE_DETECTION_R0 FRAME_MARGINS_R0 FRAME_PADDING_R0 AUDIO_CONTENT_R0 SCS_TEST_TRACKING_SETUP_R2 40 tasks were completed: PLATFORM_STANDARDS_REPOSITORY_R1 PLATFORM_DEPLOYMENT_BUILD_ECLIPSE_R1 PLATFORM_DEPLOYMENT_TARGET_JWS_R0 PLUGIN_DECOMPOSITION_R2 BASE_HALOS_R0 BASE_BOOK_COMMONS_R0 FRAME_INSETS_R0 FRAME_BOUNDS_R0 FRAME_BORDERS_R0 FRAME_POSITION_R0 FRAME_SIZE_R0 FRAME_CONTENT_R0 IMAGE_CONTENT_R0 S2S_WEB_COMMONS_R1 S2S_WEB_USER_RELATED_R0 S2S_WEB_BOOK_MANIPULATION_R0 S2S_WEB_BOOK_MANAGEMENT_R0 S2S_CORE_MOCK_SERVER_R0 S2S_WEB_SERVICES_R0 S2S_CORE_MODEL_R0 S2S_PERSIST_MODEL_R0 S2S_TESTING_SERVER_R0 SCS_SITE_DESIGN_R1 SCS_MACHINE_SETUP_R1 SCS_BACKUP_R2 SCS_INFORMATION_R1 SCS_REPO_MAINTENANCE_R2 SCS_WIKI_MAINTENANCE_R2 SCS_PROJECT_BLOG_R2 SCS_FORUM_R2 SCS_MAIL_LIST_R2 BUILD_SERVER_INSTANCE_R0 BUILD_SERVER_INTEGRATION_R0 BUILD_SERVER_REPORTS_R0 BUILD_SERVER_DEPLOYMENTS_R0 SCHEDULE_MAINTENANCE_R2 GLOBAL_SPEC_STRUCTURE_R1 INTERNAL_BACKLOG_STRUCTURE_R1 INTERNAL_BACKLOG_MAINTENANCE_R2 PROCESS_R2 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 How to improve summary: * Improve self discipline * Better organization between teams * Provide and discuss ideas about improval * Work towards the overall goal * Leads do daily reviews Total time spent for review and retrospection - 4 hours.
- Used the contents of the 0m03-closing.txt to create summary post for the last 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.
- Second post sample content:
As announced earlier a wiki page with links to useful videos is now available at http://sophie2.org/trac/wiki/Videos . We hope that you will find answers to most of your questions about the project there.
- Send copy to Ludmil and Nick to review it before posting.
- Use their recommendations to correct the post if needed
- The second post will be done later in this iteration.
Implementation
- After review and some minor corrections made by Ludmil the following post was created in the blog:
With the conclusion of ITERATION_03 comes our usual summary as to what has been done. At a first glance, the results of our work might not appear as especially impressive. We managed to complete 40 out of 113 tasks, which means 34%. However, the number of successfully completed tasks is much higher than in the previous sprints. The server team managed to finish all of their coding tasks including one from the ITERATION_04. As a result we now have a functional Hudson build server (www.sophie2.org:8080) and operational Sophie2 testing server (www.sophie2.org/s2s). Our other Sophie project teams have also done a good job and we now have Sophie2 Author deployed via JWS. On 15 December we launched our first release, which is now available at http://sophie2.org/trac/wiki/Download. We are now looking forward to our second release, which is planned for 13 February. The list below summarizes ITERATION_03: What went well: * The arrival of additional hardware and software for the expanded team * The Server team completed all of its tasks * The overall team was successfully organized into separate groups with specific tasks * Progress checks proved useful * More discussions took place * The utilization of additional facilities for the team * The successful integration of new team members * The addition of some outstanding new members with a "global" vision of the product What could be better: * Discipline and respecting the process * Even better organization * A higher percentage of completed tasks * Even higher productivity After discussions in which all team members participated, we decided that we need to work in several directions in order to implement improvements: * Improve self discipline - we must respect the process and follow the established rules strictly (commit daily reports, use internal backlogs, etc.) * Better coordination between the teams - all team leaders need to improve their communication with their team members and other teams * Circulation of ideas concerning improvement - all team members have been encouraged to propose different ways for improving productivity (the proposals may concern all aspects of our work process) * Work towards the overall goal - we need to have an even better overall view of the project and its future * Team leaders to do daily reviews - this is one of the ways to improve the team communication and improve discipline Best regards from the Sophie team! - Second post content:
As announced earlier a wiki page with links to useful videos is now available at http://sophie2.org/trac/wiki/Videos . We hope that you will find answers to most of your questions about the project there.
Testing
Comments
(Write comments for this or later revisions here.)
