Roadmap for 2012
Thanks to support from our sponsor Kagilum, iceScrum development will continue in 2012 at a steady and regular pace. The team will continue to use Scrum (with iceScrum naturally) with the following agenda: two-week sprints and releases every two months. At the end of each release a major version will be published: R5 end of February, R6 end of April, R7 end of June…
Due to its stability and good ergonomics, new releases can be almost entirely devoted to adding new features. A lot of these are user requests that are incorporated if possible. Your suggestions are always welcome in the community sandbox.
Here are some of the features planned for the first half of 2012: storytests, team-member participation in a sprint, niko niko, kanban for stories, definition of ready, roadmap view with workflow for features, synchronised sprints for several teams (scrum of scrums), obstacles.
Some will take the form of associated applications, using the plugin mechanism. This mechanism was tested in 2010 on several prototypes now found in the catalog: integrated chat, Google Calendar and on-line planning poker.
It will become easier to integrate iceScrum into development environments. By using Web Services, IceScrum will be able to connect to directories (LDAP), source-code management (SVN, GIT), continuous integration (Jenkins), IDE (Eclipse), acceptance-testing tools (Cucumber). Integration possibilities as well as requirements are many and varied. Thus users with special integration needs can easily obtain a customised solution through specific developments (contact firstname.lastname@example.org).
As well as these features, some surprises may eventuate…
iceScrum R4 was published in November 2011. The release was delayed in order to incorporate a new event-pushing system based on atmosphere. It allows real-time updating for all project members and considerably improves performance; this is particularly noticeable in views where many tasks or stories are displayed, when many users are connected simultaneously.
Version R4 included a much-asked-for feature: improved and simplified team management.
In 2010 it was decided to use the new technology afforded by the Grails framework. The first Grails version appeared in October 2010.
iceScrum2 came out in 2008 as a J2EE application.
The first version of iceScrum, published in 2006, was a java application with a database.