Currently we are developing the next major Sophie version - 2.1. The new version contains a lot of stability improvements as well as the HTML 5 export that was started this spring. This will allow Sophie users to create interactive books and put them on the Internet right away. Readers will no longer need to even have Sophie installed. Early pre-alpha is expected at the end of August this year.

For announcements about new Sophie releases, meetings and publications, sign up for the ​sophie2-announce mailing list. You can also follow us on Twitter: we're ​SophieSoftware.

• University of Illinois, Urbana-Champaign, University Libraries Scholarly Commons, Institute of Computing in the Humanities, Arts, Social Sciences, and Department of African American Studies. April 22, 2010.
• University of Illinois, Urbana-Champaign, English Department. April 23, 2010.
• Illinois State University, Normal, IL, English Dept, April 24, 2010.

• Occidental College faculty workshop led by Dave Lopez and Holly Willis. March 2, 2010.
• University of Southern California faculty and graduate student workshops led by Dan Visel, Virginia Kuhn, and Holly Willis. March 9, 10, 11, 2010.
• CalState Long Beach English Department, led by Dan Visel, Virginia Kuhn and Holly Willis. March 12, 2010.
• THATCamp: The Humanities and Technology Camp, Los Angeles. Hands-on workshop on Sophie authoring functionality, led by Dave Lopez and Holly Willis. March 13, 2010.
• Clemson University faculty and graduate student workshop. Hands-on workshop for 25 faculty members in the Art Department, Digital Production Department, and faculty in Rhetorics, Communication and Information Design. Mid-March, 2010.
• Society for Cinema and Media Studies, Media Literacy Panel. Sophie overview in the context of multimedia literacy, presented by Holly Willis. March 20, 2010.

Sophie 2.0 was recently featured as one of ten projects destined to impact next generation arts journalism by the National Summit on Arts Journalism, presented by the USC Annenberg School for Communication and the National Endowment for the Arts. Read more on the National Arts Journalism Program site. ​http://www.najp.org/summit

The Institute for Multimedia Literacy within the School of Cinematic Arts at the University of Southern California is seeking project proposals for exemplary Sophie 2.0 projects to be produced in collaborations between scholars and IML staff. If you have a project that would benefit from the unique compositional affordances of Sophie, and you wouldn't mind having these become showcase projects on the Sophie 2.0 Web site, please contact Holly Willis. Include a project description and explain why Sophie 2.0 would enhance the project.

If you are attending the 2010 EDUCAUSE Learning Initiative (ELI) Annual Meeting, January 19-21, in Austin, Texas, come find out more about Sophie 2.0 as Susan Metros and Holly Willis present a talk and demonstration titled "Reimagining the Book: A Multimedia Authoring Tool Named Sophie" on Wednesday, January 20, 2010 from 3:00 p.m. to 4:00 p.m.

The Institute for Multimedia Literacy within the School of Cinematic Arts at the University of Southern California is seeking project proposals for exemplary Sophie 2.0 projects to be produced in collaborations between scholars and IML staff. If you have a project that would benefit from the unique compositional affordances of Sophie, and you wouldn’t mind having these become showcase projects on the Sophie 2.0 Web site, please contact Holly Willis. Include a project description and explain why Sophie 2.0 would enhance the project. hwillis@…

During the last two iterations the team released two major versions of Sophie 2.0, Alpha 3 released on July 17 and Alpha 4 released on August 14.

We posted a release on September 15. This release marks the team's move to weekly releases as we approach October 15, when the full version of Sophie 2.0 will be released. This is being done to work more efficiently with the testing team organized at USC.

Here are the results of the retrospection for ITERATION_10.

What went well:

• Redesign
• New features
• Intrateam organization
• Look and feel

What could be better:

• Redesign speed
• End product focus
• Application startup speed
• Weekly timeboxing

How to improve:

• Focus on usability
• More testing
• More autotesting
• Concentrate on finalizing Sophie
• Concrete redesign goals

We bypassed the closing and retrospection for the eleventh iteration in order to reduce the process overhead and concentrate on the release of Alpha 4.

Best regards, the Sophie Team.

ITERATION_08 and ITERATION_09 Summaries

Today's report covers our last two Iterations. The team has been very busy and very productive. During these Iterations, the team achieved many of its goals and drastically advanced Sophie 2.0 capabilities. We released Alpha 3, available for download at ​http://www.sophie2.org/users/downloads.html, and we are now looking forward to our first beta version, scheduled for August 14. The new user interface will be included in this release.

We have posted two demo books, which can be found here and updated the user tutorials, available here.

During the eighth Iteration, the team held a very productive two day seminar at Panichishte, clarifying design ideas and planning integration. Several new developers joined the team during this period.

A significant event during the ninth Iteration was a demonstration of the Sophie 2.0 Alpha 2 release on July 2. Two videos of the demonstration are available at: ​VNC Demo and ​Demo.

Below are the results of our most recent retrospections.

ITERATION_08 retrospection:

What went well:

• More tasks finished
• Successful demo
• Process Improvements
• Release quality

What could be better:

• Weekly time boxing
• Defining scope
• Meeting weekly milestones

How to improve:

• Increase number of analysis discussions
• Work more carefully
• Stay on plan
• Intensify testing

ITERATION_09 retrospection:

What went well:

• Internal team communication
• Issuing bug tickets
• Working on the Sophie 2 Server
• New team members

What could be better:

• Availability of the team members
• Time management
• Submitted quality
• Integration speed

How to improve:

• Move declaration of tasks to Monday
• Additional integrators
• Pick smaller tasks
• Increase effort on bug fixes

Best regards, The Sophie Team.

We have concluded and released our seventh iteration.

New people were hired and our team expanded, so we've divided into additional, smaller subteams. A team of integrators is now responsible for reviewing tasks and committing in the trunc. Each developer has an individual branch. Splitting into smaller teams improved both our process and our internal communications because there is a now person in each subteam responsible for the managing the process, including duties such as following the backlog and daily reporting.

The team has had numerous discussions in order to improve the global understanding of several fundamental issues. Many of these discussions are available as English videos.

Results of the ITERATION_07 retrospection are listed below.

What went well:

• New people to the team
• Integrator team helps raise the quality of the product
• Release demo

What could be better:

• Some fundamentals starting late
• Late submits for integrators
• Application performance

How to improve:

• Concentrate on application performance
• Discussions and improved communications
• Better scheduling and weekly timeboxing
• Improve professionalism

Best regards, The Sophie Team.

In order to ease wiki usage, we installed following plugins:

• Wikify - creates a link to wiki page without using [wiki:...]. For example

  ITERATION_06
  

  is enough to link this page
• Ticketbox - using queries displays tickets # and summary: Reminders (yellow), Failed Reviews (red), In Progress (green) and Design OK (blue) depending on username of the logged user at the top of the current iteration page.

Here is our regular summary of what's been done during the sixth iteration.

As decided at the ITERATION_05 closing, we are introducing organizational and operational improvements aimed at self management and optimizing the work process in order to increase our productivity. In the sixth iteration we've introduced "groups" tasks, a way to work on several tickets using only one group ticket which includes them. After the fifth iteration we are using again a subteam structure. ITERATION_06 was split into two separate mini-sprints, improving the time boxing of tasks.

On April 17 we launched our fourth release which is available for download from ​here. 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
• Bugfixes

Below you can read the results of the sprint retrospection. What went well:

• Release was on schedule
• A lot of the fundamental designs were finished
• Done a lot of discussions

What could be better:

• Sometimes the process is slowing us down
• The communication between team members coudl be better
• Some fundamentals weren't finished

How to improve:

• Better understanding of the ideas
• More pair programing
• Simpler process
• Improve the inteam communication

Best regards, Sophie Team.

ITERATION_05 is now complete and the information below summarizes what has been achieved with this iteration.

On March 13, as scheduled, we delivered the pre-Alpha 4 version of Sophie 2.0, which is available for download ​here. We are also pleased to present the new ​Sophie 2 community site, which we will continue to enhance in the upcoming week. Please note that ​the new primary domain for the Sophie project is available.

In addition to holding numerous design meetings involving the entire team, we also created stable wireframes for the project's specification and continued to make improvements to the overall quality of the code.

Sophie 2.0 pre-Alpha 4 can run on Windows, Linux and MacOS, and includes many of the functionalities (some in prototype form) to be included in the final product. They include the insertion of different types of resources such as PDF files, images, audio and video files; the creation of annotations; basic frame manipulation; and many others that you can try for yourself. There are still, however, some known issues to be resolved, all of which are listed in ​the product’s download page in the section “Known Problems”.

Results of the closing:

What went well:

• release was on time
• new functionalities were added to the product
• additional design discussions helped to spread our global vision for the product to new team members
• lots of blockers were fixed

What could be better:

• the process must be followed closely even under time pressure
• we need to continue to improve and simplify the process

How to improve:

• better self management
• continue to optimize the process
• better prioritization of tasks
• do more pair programming

Best regards from the Sophie team!

A required line for each Sophie file is introduced here: PROCESS

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 February 13 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 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 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 exam and dissertation commitments 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!

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.

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. However, the number of successfully completed tasks is much higher than in previous sprints.

The server team finished all of their coding tasks including one from 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 Sophie 2.0 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 February 13.

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!

20.01.2009

start: 14:50

pro_lib = - designed to help people! If they are not helping, either something should be fixed or people do not understand how to use it.

• attibute - self responsible.
• do not care about initializing order.
• good practices:
  • defaulty constructors.
  • avoid final properties.
  • push updates - instead of updating things manually, provide these things the ability to auto-update.
  • avoid trying to use unconventionally the pro_lib since this is error prone.
• Property improper use cases:
  • accessing an AutoProperty WILL NOT invoke its compute() method!
  • resource properties:
    • create method should depend on NOTHING => it is invoked once and will not update things.
    • setup methods are designed to keep things synchronized for people. @Setup may be put to split setup things in different methods, so that they are updated in groups.
    • destroy methods are not working.
• List properties.

core_modularity

• extensions are now sortable by comparator.

base_visual

layout

menus

• this is a new module to split the layout and menus from the main.view things.

base_skins

• provides things to simplify things that are registered for a single skin => currently a map with (id, value) entries.

global things

• few people have a global vision about things.
  • people should get a better overall idea.
• supercool model.
  • not only implement a great library but find a task to actually use it and also do that task.
    • this will improve the library.
    • things that are error prone will appear.
• the "not my task/class" problem (people tend to do only things that are tracked and planned):
  • the code is owned by everyone!
  • fix things that need to fixed in order to implement you things, otherwise the next revision of the task will fail.
  • if the things are complicated to be fixed, ask the others, make discussions about it.

end: 16:05