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

Correctly displaying the votes
Correctly displaying the votes

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.

Enable auto-flip cards
Enable auto-flip cards

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:

Allow early voting (settings)
Allow early voting (settings)

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.

Early voting
Early voting

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

Seeing who voted early
Seeing who voted early

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

Complete voting
Complete voting

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!

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.

Custom card sequence
Custom card sequence

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.

Fibonacci sequence cards
Fibonacci sequence cards

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.

T-Shirt story sizing
T-Shirt story sizing

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.

Custom T-Shirt story sizes
Custom T-Shirt story sizes

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!

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:

Exclude cards
Exclude cards

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.

Excluded cards
Excluded cards

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:

Removed animated bar
Removed animated bar

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:

Quick add/remove JQL
Quick add/remove JQL
Legend
  1. JQL query in addition to individual Jira tickets
  2. A clear button that also resets the drop down to the list of planned stories
  3. 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.

New Jira shortcuts
New Jira shortcuts
legend
  1. 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.
  2. 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.

Scrumpy in IE11
Scrumpy in IE11

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.

Confluence, Jira, Stride and Slack integrations

Coffee Table atlassian products

Introduction

Scrumpy Planning Poker integrates with various external systems like Jira and Confluence to make the voting process as transparent and convenient as possible. In this post, we shall discuss, the most common integrations that are a must-have for every scrum team using story points for estimating tasks.

Setting up the integrations

When you sign in as a room moderator to the Scrumpy Planning Poker application, you can configure the integrations from the settings page:

Open the settings dialog box
Open the settings dialog box

Inside the settings, there are several integrations mainly done through user/API token combinations or web-hook URLs.

Jira integration

The Jira integration is described in detail in Jira integration for Scrumpy Planning Poker and consists of entering the details:

  • Jira root URL. This is the root domain which you open when navigating to the Jira ticketing system. For example, your-company.atlassian.net.
  • Jira user. This is the user on whose behalf Scrumpy Planning Poker will update story points, add comments with estimate summary or create Confluence summary pages for the refinement sessions. For example, [email protected]
  • Jira API token. This is the API token that can be obtained from the Atlassian Account Manager. The API token is used to authorize your Jira user to make comments, update story points or create Confluence pages.
Filling in Jira API token
Filling in Jira API token

After the Jira integration is set up, when a ticket is refined its story points are automatically updated and in addition to that, a comment is added when and how it was estimated.

Jira ticket integration
Jira ticket integration

Confluence integration

The integration with Confluence uses the same link and credentials as the Jira integration. You can specify which Confluence space will be used as a container for the summary pages created from the refinements.

When the last participant leaves a planning poker room, and this room is set up for summarizing in Confluence, a new Confluence page is created. The page is a summary of the voting session containing anonymous votes from the participants in the refinement session. The following screenshot shows an example:

Confluence summary page
Confluence summary page

Stride integration

The Stride application integration is used to publish messages in a chat room when a story is refined. A brief message similar to the one added as a comment in the refined Jira ticket is printed, for example:

Stride integration
Stride integration

The integration consists of entering the following details in the settings dialog box:

  • Stride room URL for posting messages. This is the link that can be copied from Stride when a bot needs to publish messages there. An example is https://api.atlassian.com/site/aedcbe61-1d38-4c3c-8781-aff9d49e7e12/conversation/5abe1d2c-d447-41ea-9cae-6ff44b1ecbf0/message”
  • Stride authorization token. This token can be obtained from the Stride application. For example: e6fK73KSUiRiKysQaQdb.

Slack integration

The Slack application integration is used to publish messages in a chat room when a story is refined. A brief message similar to the one added as a comment in the refined Jira ticket is printed, for example:

Slack integration
Slack integration

The integration consists of entering the following details in the settings dialog box:

  • Slack web-hook URL. This link can be taken from the Slack settings for the Incoming web-hook integration page. The appearance of the posting robot can be customized there also. The link can be entered in the settings dialog box of Scrumpy Planning Poker.

Integration demo

The following video shows how the Jira integration is used and the advantages when Scrumpy Planning Poker is directly integrated with Jira:

Jira integration for Scrumpy Planning Poker

Jira Integration

Introduction

Scrumpy Planning Poker provides an easy way to connect to Jira and Confluence. The integration includes automatically filling in story/bug/task details, placing story points on tickets when voting is complete and finally adding a comment in the story how it was estimated and what was the average estimate. Optionally, a Confluence summary page can be generated with anonymous voting information for each ticket refined during the session.

The Atlassian Plugin

The most straight-forward way to integrate with Jira and Confluence is to install the Atlassian plugin. From inside Jira using a simple shortcut, a planning poker room can be open and associated with the currently selected project board. The name of the room is the name of the Jira board. The Jira users will be mapped directly to participants and the estimating process can immediately start.

New Jira shortcuts
New Jira shortcuts

From inside the story search box in the planning poker room, the Jira tickets can be individually selected or in bulk using JQL.

Quick add/remove JQL
Quick add/remove JQL

Getting the Atlassian API token

In case installing the plugin to the Jira Cloud instance is not an option, an API token can be generated to let Scrumpy Planning Poker use Jira and Confluence on your behalf.

The information that Scrumpy Planning Poker needs

Using this API token, Scrumpy Planning Poker will be able to search tickets in Jira as you type them in the search box, automatically update the story points estimate, add comments in the ticket with a summary and finally generate a summary Confluence page.

Obtaining the API token

To get this token, navigate your browser to the Atlassian Account Management portal and log in if not yet signed in.

Atlassian Account Management
Atlassian Account Management

The next step is to select the API tokens menu on the left. This menu will take you to the next screen, where you can create a new API token. Those tokens can be revoked at any time and are not connected in any way with the master password of your account.

Atlassian API token
Atlassian API token

The final step is to press the Create API token which will generate a new API token. The token can be copied to the clipboard so that it can be easily pasted in the Scrumpy Planning Poker settings dialog box later.

Create new API token
Create new API token

After pressing the Create button, the token is ready to be entered in the Scrumpy Planning Poker settings and start using the Jira and Confluence integration.

Setting up Scrumpy Planning Poker

After the Jira site URL, the user on whose behalf the integration will happen and the API token are at hand, they can be entered in the settings page of Scrumpy Planning Poker.

Open the settings dialog box
Open the settings dialog box

When the Settings dialog box opens up, choose the Integrations tab to navigate to the settings that are specific to integrations with external applications.

Navigate to the Integrations tab
Navigate to the Integrations tab

The final step of the configuration is to fill in the Jira URL, the Username and the API token for Jira and Confluence integrations. The Jira URL is usually in the format <company>.atlassian.net or <company>.jira.com.

Filling in Jira API token
Filling in Jira API token

After the Atlassian credentials have been set up, a Confluence space can be selected to contain the summaries of the refinement sessions. For example, a brand new space called “Refinement Sessions” or “Refinement Sessions – Blockchain Team” can be created. If this is not needed, but previously set up, the X button can be used to remove the option to generate refinement session summaries.

Finally, the setup can be tested by trying to search for a Jira ticket in the search box of Scrumpy Planning Poker:

Searching for a Jira ticket
Searching for a Jira ticket

Congratulations! You can now set your Jira URL, user and API token in the Scrumpy Planning Poker’s room settings. This will allow you to search for Jira tickets, automatically fill in estimates in tickets and get a generated summary page at the end of the refinement session.

Please check this video tutorial on how you can setup Jira and Confluence integration and how you can prepare the tickets for the refinement sessions, estimate them and let Scrumpy Planning Poker automatically fill in the estimates and comments.