ScrumDesk v4.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 [...]

Version 3.7 – story template + performance

Performance improvements We continued with performance improvements targeting the second(s) goal to 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 back-end service calls and [...]

Free Scrum Guidelines

While being in agile transition, teams look for information 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 agile environment sooner. The paper describes all Scrum ceremonies with a focus on Why, What, Who, Where and [...]

Are user stories relations necessary?

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

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 [...]

ScrumDesk for Windows – User Story Template

Reaching wider community is for us absolutely welcome not just because of numbers (either count or price). For us, the value is a knowledge how scrum adaptation is done. It is very interesting to see how such simple project management framework is adapted in so many ways. ScrumDesk development begun as materialized idea based on Scrum [...]

How Kano model helps to agile 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 do as 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 [...]

Is business value enough for product backlog agile 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 company process requirements. If your process is not requiring precisely defined steps, go directly to Step 4. Who Scrum Master Story Templates Is story templates required? No. But they are great when you have defined required development process steps. This is typically case for enterprise [...]

By |September 28th, 2010|Categories: Blog, ScrumDesk for Windows (retired)|Tags: , |Comments Off on Step 3: Define user story templates

Step 6: Backlog Stories

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

By |September 28th, 2010|Categories: Blog, ScrumDesk for Windows (retired)|Tags: , , , , |Comments Off on Step 6: Backlog Stories

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 product owner on sprint planning meeting. Product owner shows the team his plan for first sprint. Product owner chose stories by top importance (priority). Product Development Product Backlog Release A [...]

By |September 28th, 2010|Categories: ScrumDesk for Windows (retired)|Tags: , , , , , , |Comments Off on Step 8: Sprint planning meeting