How to split user stories? Part 2: By Operations

User stories splitting, working with epic, epic splitting into user stories. One great art. In the first part, we have shown you examples for splitting requirements into smaller ones by the process. Although this is the last division step for many Product Owners, this is not enough for a reasoned app. In this part, [...]

August 30th, 2019|Categories: Agile Knowledge Hub, All|Tags: , , , |

How to split user stories? Part 1: By Workflow

The examples were created in the form of a user story map using the ScrumDesk app, where you can easily create a backlog from epics to embedded features to user stories. So far, in our consultation with the agile teams, we have always encountered unfamiliarity in each team about how to split the requirements [...]

August 30th, 2019|Categories: Agile Knowledge Hub, All|Tags: , , , |

Progress Measurement in Agile Product Management

Oh, that great idea once again. %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%. Apparently, the feature is 79% done. Round of applause, that’s a nice number. Nicer than 78%. Masturpercentobation. But what Jeff has to do with that, yes, that user Jeff. Team: ‘Ugh nothing we can do now, we have to wait 3 weeks for the next sprint release.’ Product [...]

Definition of Ready example from a real-life

The Definition of Ready helps save a lot of money on development for little effort. Or, why define requirements properly. The Punkers team The Punkers have been the worse team for a client and their management for several years now. Their requirements are constantly stretched, and even if they can be completed, the client [...]

ScrumDesk 4.16.3: User Story Readiness

Use what you need! Some of our clients are keen to use retrospectives, while they do not use Scrum because they prefer physical boards. Some other prefer simple backlog and not the story map. So now account administrator can activate selected modules which will make theirs functionality available to all organization team members. To activate, or [...]

ScrumDesk 3.14.1: User Stories Mapping Improvements

User Stories Mapping We are proud to say we finalized user story map, the new feature of ScrumDesk. At least up to the level, we think that usability and performance are perfect. But that doesn't mean we do not want to improve it. We have a couple of additional ideas as well, so be ready [...]

ScrumDesk 3.7: User Story Template

Performance improvements We continued with performance improvements targeting the second(s) goal instead of minutes for large backlogs. We are happy to share we were successful, but also that doesn't mean we have ended. As  Backlog and Work views are the most used parts of the application, we have chosen them for performance improvements of [...]

Free Scrum Guidelines

While being in agile transition, teams look for information on how to do agile correctly. Often the question sounds 'How to DO agile?' We prepared Scrum Guideline that we hope might be helpful to shorten your Agile transformation and stabilize the agile environment sooner. The paper describes all Scrum ceremonies with a focus on [...]

User Stories Relations and Dependencies

The customer asked us an interesting question regarding the relations of stories in ScrumDesk. What ScrumDesk supports now is simple relations tracking solution, the possibility to track, see and print out it in documents. For the first look, some basic functionality in ScrumDesk is missing. The functionality similar to Gantt chart way of relations [...]

ScrumDesk for Windows: User Story Card

Scrum as project management is using the concept of index cards introduced in Extreme Programming (XP). Cards are supposed to establish conversation and clarification of requirements.  The card in ScrumDesk displays more details than paper index card while still provides visibility. ScrumDesk index card's advantages compared to other project management tools: resizable many colors [...]

Kano Model helps Product Backlog Prioritization

Product management is about searching for the most important requirement that needs to be delivered as the next. There are different prioritization practices. One such dimension that product owner should be aware of is expected customer satisfaction. Satisfaction with developed feature or story. Mr. Noriaki Kano developed Kano model as valuable technique helping to recognize that. Applying this [...]

Agile prioritization. What to build the first?

Product owner  is often confronted with a large backlog. This post continues  to explain how to consider priority of stories. See principles in previous post. Measuring risk and positive value allows to calculate the order in which stories should be developed. Very nice and simple visualization can be Risk  vs. Value chart. Chart is split [...]

Business Value is not enough for Product Backlog Prioritization

Agile coaches teach teams to develop a  business value that is delivered at the end of the sprint. But should be a value an indicator of the priority? Yes, but not the only one. There are many other attributes we often forget to consider. We suggest applying a different approach. We would like to have [...]

Step 3: Define user story templates

In Step 3 we will define story templates according to company process requirements. If your process is not requiring precisely defined steps, go directly to Step 4. Who Scrum Master Story Templates Are story templates required? No. But they are great when you have defined the required development process steps. This is the typical [...]

Step 6: Backlog Stories

In this step product owner and development team are going to plan project sprints. Who Product Owner Creating stories The target for this step is to create backlog stories. Product Development Product Backlog Stories in scrum are mainly created by the product owners. As a first step let's log in as product owners. The product [...]

ScrumDesk for Windows (retired): Step 8 – Sprint planning meeting

In this step product, owner and development team will plan sprint. Who Product Owner Scrum Master Developers Visitors Sprint planning meeting Development team meats with the product owner on sprint planning meetings. The product owner shows the team his plan for the first sprint. Product owners chose stories by top importance (priority). Planning View [...]