A Product Owner and a Scrum Master can ajust a few settings on the projects they are working on. This article will explain what is possible and how to change the default configuration on a project.

Let’s consider the project myProject. To change the project settings, locate the link called « Project : myProject » on the top of the page, next to the illustration of your role :

Opening the project panel (click to enlarge)

Clicking on this link will open the project panel. Here you have a recap of the project characteristics, you can also get the list of the members and access all the global charts.

Then, on the right part of the main window, you can find a few expandable panels, click on their header to see their contents. While the « Project Information » panel will only display a short text, the options available in the next panels depends on your role, which is detailled below.

As a Scrum Master I can …

The Scrum Master is the only one who can change the Members management settings. Note that all these options are cumulative. An indicator is display next to your role label when one of these options is enabled (see illustration).

A project with the « Disable role changes » and « Mask project » options enabled

Refuse new members

If the Scrum Master enables this option, then a new user won’t be able to join your project as an active member. New users can still join as Stakeholders – and Stakeholders only – and won’t be able to change their role even if the « Disable role changes » option is not enabled. While a Stakeholder field of actions is very restricted (see the article on the users rights), you may want to completely forbid anyone to join your project, in this case consider the « Mask project » option.

Note that any active members of the project (Member, Scrum Master, Product Owner) can still change their role at any time.

Disable role changes

Since the R2#15 version, this option has merely the same effect as the « Refuse new members » option, meaning that new users will be restricted in the role choice (they can choose Stakeholder or Member), but in addition, all roles are blocked, may it be an active Member, the Product Owner or even the Scrum Master, no one will be able to change its own role.

Mask project

When this option is enabled, the project will only be listed in the projects list (in the main menu) to the members of the project. Any new user will not see the project, so you can use this option to make a private-only project and prevent anyone to join.

As a Product Owner I can…

The Product Owner is the only one who can change the project characteristics or even decide to delete the entire project. Note that the « Activate End of Sprint Mail notification » action is currently not fully functionnal, so I won’t talk about it for now.

Auto-Reset Tests state each sprint

With this option enabled, when you start a new sprint, all the tests are reset to their initial state (Waiting). So you have to revalidate them in the following sprint.

Autochange story state to « Done » when all its tasks are done

When this option is enabled, a story will automatically be declared as « Done » when every tasks associated to it are done (in the Sprint Backlog). The Product Owner then won’t have to validate the story by himself, but use this option carefully, since a « Done » story cannot be « undone » !

Update project characteristics

This action allows the Product Owner to changes the project characteristics : name, description, starting date, and the planning poker numeric suite (Fibonacci or Naturals).

Delete project

Well, the title is explicit enough, it will delete the entire project. Don’t play with this action, you may regret it later

As a Member or a Stakeholder, I can…

Members and Stakeholders cannot change any project-level settings.

Leave project

The user can decide to leave the project, he will be removed from the project’s members list. If the Scrum Master had enabled the « Mask project » option, he will no longer be able to see the project the next time he logs on the server !

Hi everybody,

We have made a short recap of the user rights in IceScrum² for each roles (Product Owner, Scrum Master, …).
The document is immediately available for download in PDF in english or in french.

Best Regards,

The IceScrum² Development Team

Hi everybody,

Because IceScrum has more and more users, we thought we should give you some tips about IceScrum² usage. We realized that some features aren’t well known.

So, today we’ll give you a few tips about the Sprint Backlog in IceScrum² R2#14.2.

(Click on a screenshot to enlarge)

1. Direct Input for the Remaining Time in the table view

A feature, which is not very intuitive, I’ll admit that fact, can be very useful for those who commonly use the Table View: the direct input on the Remaining Time column.

If you have already defined an initial value for the remaining time of one task, you can just click on that cell to modify the value. An input field will appear, and you will be able to set a new value. Then, just validate with the « Enter » key.

Well, it won’t work if you haven’t already specified a value in the Remaining Time before, so it will only be useful after you have estimated every tasks.

2. Sort tasks in the table view and ajust column’s width

In the table view again, you can sort the tasks list by clicking on the column’s name in the header of the table. The first click will apply an ascending sort, then click again to switch between ascending and descending sort.

Note : Until the R2#14.2, the column « Responsible » is sorted on the user’s last name (but the information is formated as « First name – Last name »), so it can be a little tricky.

Moreover, you can manually ajust the column’s width by dragging the column’s borders in the header of the table.

3. The Sprint Backlog window in full-screen

This is not a feature exclusive to the Sprint Backlog, but this is probably where it is the most useful. You can make the sprint backlog view full-screen by double-clicking on the window’s header.

Double-clicking again will reduce the Sprint backlog view to its original size. Alternatively, you can click on the classic « maximize » action on the right-hand corner of the window.

The sprint backlog view will take all the available width of your web browser’s window. In this mode, a column can display more than one task on the same row (more or less, depending of your screen resolution), which is more convenient when you need a global visualisation of every tasks.

Don’t forget that you can also ajust one column’s width manually by dragging the horizontal blue bars in the header of the table (see the following illustration).

That’s all for now, we hope you have learnt something new that you’ll find useful !

In IceScrum², as a user, there are some actions that you can do on the different items of the applications :

• Right-clicking:

On every post-it, right-clicking is available. Some actions might not be allowed to you if you are not Product Owner or Scrum Master, but there is always a right-click pop-up menu associated to post-it of the application.

In the roadmap view, there is a right-click pop-up menu on the releases.

In the Release Plan, there is a right-click pop-up menu on sprints.

• Left-clicking:

On every post-it, left-clicking is available to enlarge them and display all the information. You have to click on the top right of the post-it to do it.

In the roadmap view, you can left-click on a sprint to display it in the sprint backlog view, or on a release to display it in the release plan. The color of the sprint changes to show that.

In the release plan, you can left-click on a sprint to display it in the sprint backlog view.

• Drag & drop:

If you are Product Owner, you can drag & drop postits in the product backlog in the « To prioritize » filter. The aim is to set an higher, or a lower priority to a story. You can also drag and drop a feature from the feature minimized view to a story to associate it to the feature.

In the release plan view, if you are Product Owner, you can drag and drop a story from a sprint to another one. You can also drag and drop a story from the product backlog minimized view to a sprint to associate it to the choosen sprint.

In the sprint backlog view, you can drag and drop tasks to change their state, you can also drag and drop a story from the product backlog minimized view to the current view to associate a story to this sprint.

To allow multiple instances running, another level of subdirectory is allocated for databases/configurations based on the context root name.

e.g.:

_ your icescrum url -> http://localhost:8080/iceScrum2
_ settings path -> [user.home]/.icescrum/iceScrum2