ScrumDesk Roadmaps are here!

Do you take care of the complex agile project developed with one or more scrum teams?  Are your teams dislocated? Or do you manage product portfolio with the help of ScrumDesk? Now you can do scheduling of the project in ScrumDesk not just with releases or sprints. ScrumDesk Roadmaps are an easy way to plan and schedule [...]

Agile Estimation: Principles

An estimation has been questioned in software development for many years. How to estimate accurately & fast? And, is an estimation even necessary? Well, that is the question for thousands of bucks. Because estimation might be expensive. Especially in the age of changes. Time as an estimation unit is wrong! In our agile training, [...]

How to build product: Let’s start with the business

Agile development works very well in the product development area. But to build a successful product is much more work than just gather requirements and implement them.  One of the trickiest things in agile development is how to prepare requirements that are ready for incremental development while still delivering some value for the customers. [...]

Prioritization by Business value in Agile

The first blog post about prioritization was focused on MoSCoW - prioritization of the backlog from the perspective of customers. This is not enough for the products development of the commercial company. You need to survive, to pay bills, to pay the next sprints. You have to think about features from the perspective of the [...]

How to prioritize in Agile I.: Customer’s perspective with MoSCoW

Prioritization is probably the most discussed part of development processes. Product backlogs are often quite complex with hundreds of requirements. How to find user stories in your story map which you should start developing first? Traditional approach The approach of traditional processes is simple. You have high, medium, low priorities. Ok, for some organizations [...]

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.10: The Sprint Review Report. What has been finished?

Sprint review report Do you want to be prepared for a sprint review session with all information necessary to review your commitments and the status of the outcome? Sprint report is the document that summarizes: Sprint title and goals Sprint start and end dates Information about the team who worked on sprint items Information [...]

How To: Business Model and the Product Strategy

Agile works very well in a product-oriented environment. It’s understandable, as Agile Manifesto as a key document of whole Agile stresses the functional product as one of the most important values. When implementing agile practices, Product development is very often reduced to: Description of responsibilities for Product Owner role, Request recording, Maintenance of backlogs, [...]

ScrumDesk 3.8: Print the Product Backlog. Filters and Mentions.

Print the Product Backlog Printing has appeared in ScrumDesk. As we have great planning experience with physical cards, we decided on a card layout that we suggest to clients of our consultancy team. Printed card layout provides fundamental information necessary for proper release or sprint planning. Print is available in Backlog and Plan view. [...]

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

Agile Product Backlog Management with ScrumDesk

An index card for user story Fundamental XP practice is to keep requirements written on an index card. The index card should be: small, therefore requirement has to be written clearly, movable, so the product backlog is visually clean, resizable, so the size of cards can help to organize backlog, colored, so teams can categorize [...]

September 3rd, 2014|Categories: All, ScrumDesk Web Edition|Tags: , , , |

Organize the Product Backlog. The Tree of Requirements

You know that probably. Requirements are coming, coming and coming.  There is no time to stop and think about them. There is no time to organize them. There is no time to analyze your backlog so you know which requirements should be developed next. Even more, many customers ask you about new functionality or defect fixes. In our [...]

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

Scrum Glossary: Scrum Roles

Pig & chicken Metaphor that helps to distinguish people actively involved in development of the product and people who should not interrupt the team in an iteration. Product Owner Father of the product. Responsible for product success. Provides a vision to the team. Communication channel between the team, stakeholders and customers. Responsible for: product [...]

Product owner briefly

Product owner is a key role in Scrum framework. Companies used to start with intorudction of agile in development team, but the biggest mistake is missing preparation of Product owners before scrum/agile adaptation. Following slides pprovides fundamental information about Scrum and agile to Product owner role. Product Owner Briefly View more presentations from Dusan [...]

January 13th, 2011|Categories: Agile Knowledge Hub, All|Tags: , |

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

ScrumDesk for Windows (retired): Team Management

ScrumDesk for Windows (retired): Step 2 - Define a team Who Product Owner Work that needs to be done can be easily distributed in more development teams. ScrumDesk connects teams in one virtually connected social community. This community is notified by the ScrumDesk notification system about any change. Teams can be distributed over the [...]

ScrumDesk for Windows (retired): Step 4 – Planning Releases in Agile Project

In this step, the Product Owner and development team will try to plan project releases. Who Product Owner Scrum Master Planning in SCRUM SCRUM is based on development in timeboxes called Sprint. Sprint is the time needed to complete selected stories (features, bugs, requirements, tasks,...). The length of the sprint is typically 30 days, [...]

Step 5: Plan sprints

In this step product owner and development team will try to plan project sprints. Who Product Owner Scrum Master Planning in SCRUM In Step 4 Planning product releases we defined sprint as time box for developers to complete selected stories. Product Development Product Backlog Release A Release B Sprint 1 Sprint 2 Sprint 3 ScrumDesk: Planning [...]

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

Step 7: Planning Poker®

In this step development team is going to estimate stories. Who Scrum Master Developers Planning Poker® Our backlog contains all known stories which has to be developed for product. Team sits down together around the table and they starts to discuss size of each story. Product Development Product Backlog Every developer will get cards [...]

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