Early voting in release Aug 05 2018

Introduction

The new release is now out and here are the outlines of what’s new in the latest release.

Bugs fixed

The following issues were resolved with the last release

Historical estimates do not always match what was chosen

When overriding the selected vote by Scrumpy, this vote was not properly displayed in the historical view (left pane). Now the correct vote is there

New features

The new features were carefully crafted according to the Feature Requests page and the received up-votes.

Auto-flip the cards once everyone has voted

Before, when all participants have voted, the timer was activated and the moderator had to press the forward button to complete the voting earlier. Now there is a new setting called Complete when everybody voted. When this option is enabled, the game ends immediately after all participants voted.

Early voting

Sometimes not all participants can be available for the planning/refinement session. In this case, it’s convenient to leave the vote in advance and let the team discuss it. Voting after is not possible since we believe that there must be always a discussion about the votes. In case early voting is not possible and being at the meeting is not an option, we think it is better to schedule another session.

The early voting can be enabled from the Settings page with the option Allow early voting as described below:

After the early voting is enabled, all the participants except the moderator can give their early vote at any time. This usually happens the same day or the day before the refinement session. The early vote is displayed on the right side of the ticket and is not visible to the other participants.

When the session starts, during the voting process the participants see the list of people who voted early:

Finally, when the cards are flipped and voting is complete, the result is shown in the summary page:

Happy voting!

All those nice features (and fixed bugs) have been completed thanks to our users – they have requested and we have implemented them. Please help Scrumpy Planning Poker become even more convenient for you by submitting a feature request/bug to our Feature Requests page or up-vote an existing feature that you find useful. Thank you!

July 28, 2018August 23, 2018

Fibonacci and T-Shirt in release Jul 28 2018

Introduction

The latest release of Scrumpy Planning Poker is focused on the different types of card types for estimation. With this release, the application now supports different type of cards and custom story points mapping that can fit every case like Fibonacci and T-Shirt story sizing.

New features

The new features were carefully crafted according to the Feature Requests page and the received up-votes.

Selecting cards sequences

Before, there was only one type of card sequence – 0,0.5,1,3,5,8,13,20,40,100. From the settings page, now you can select a few more sequences which have a different purpose. For example, the Fibonacci sequence is more accurate when estimating more complex tasks, while the T-Shirt estimate is not bound to points and can have a custom mapping from a T-shirt to story point.

The sequence can be chosen at any time from the Settings page. The Settings page can be open only when there is no current voting session.

Real Fibonacci sequence

Before, Scrumpy Planning Poker used only the most commonly used cards for estimation, which partly resembled a Fibonacci sequence, but was not exactly this. Now, the real Fibonacci sequence of 1,3,5,8,13,21,34,55,89,144 is available.

The Fibonacci sequence is more convenient when estimating more complex tasks which are above the regular 1-13 set of estimates.

T-shirt story sizing

The T-Shirt story sizing is convenient when stories are not visually bound to story points, but to T-shirt sizes. This way the voters evaluate tasks by small/big scale without thinking about the story points. This card sequence allows custom mapping to any type of ascending story points. The scale can be linear, progressive, exponential or anything that fits the project.

The adjusting of the mapping from a T-shirt to story points is available in the Settings page. Note that only ascending mappings is supported, e.g. the cards must be ordered from small to big.

Happy voting!

All those nice features have been implemented thanks to our users – they have requested and we have implemented them. Please help Scrumpy Planning Poker become even more convenient for you by submitting a feature request to our Feature Requests page or up-vote an existing feature that you find useful. Thank you!

July 21, 2018July 21, 2018

What’s new in release Jul 21 2018

Introduction

This release is the result of our new program to let our customers build Scrumpy Planning Poker the way it fits best their needs. We’ve opened a separate page for collecting ideas and allowing up-voting.

The ideas page

The page allows both us and our customers to freely submit ideas. Those ideas are edited and published in the ideas section of the page. Then anyone can vote up or down for a feature. We are implementing those feature requests according to the priority and include some of them in the next release. The new features are documented at the bottom of the same page.

Release Jul 21

The release includes the following features:

Exclude certain cards

Now cards can be excluded from the Cards tab in the settings page as follows:

Once the cards are excluded from the check mark in the Cards settings, they are marked as unavailable in the voting section to avoid disconcentrating the players.

Stop animated blue bar after voting

The annoying animated bar that distracts the voters attention when discussing the results is now gone. Now the box appears as follows:

Add support for JQL

Now you can enter regular JQL queries in the story search box. Additionally, there are other usability improvements like combining several JQL queries, adding individual tickets to the list and convenience buttons for adding and removing stories to the list for the refinement session:

Legend

JQL query in addition to individual Jira tickets
A clear button that also resets the drop down to the list of planned stories
A quick add/remove buttons to easily adjust the list of planned stories

Create poker room per team

Now inside the Jira plugin the currently selected board is used to map to a room, or the project itself when used in the root dashboard. The board is the closest match to ‘Team’ in standard Jira installations. In the future we might extend this to support Jira Portfolio teams.

legend

Mapping board per poker room. Each project can have more than one board. If no board is defined, the project is mapped to a room.
Planning poker shortcut in the project’s space

Shortcuts to project’s room in Jira

The project space now has a shortcut to the currently selected board’s poker room or the project itself if no board is defined. The Estimate button has been removed as it is much easier to use the new JQL query in the search box.

Support for IE11

Now IE11 is a supported browser. Before we didn’t consider this browser at all, but since it was submitted as a feature request and up-voted so it became a supported browser.

Your vote matters

Thank you all for submitting those nice and useful ideas! You can get back at any time to the feature requests page and tell us what you need or provide some instant feedback from inside the application.