De-bugize! How to plan fixing of bugs in Scrum.

Are you distressed by the huge amount of defects in the product? In this article, you will learn about what practical possibilities you have in agile teams and managing error correction. One of the first questions that pop up whilst introducing agile is how to deal with errors. Too often I hear an immediate answer: [...]

Business and technology requirements leveled

How to balance business and technology requirements in a product backlog to build a successful product in long-term. A product ownership is hard stuff. Very often you feel a schizophrenia. Often you play for a customer, but later, suddenly, you have to protect your team. Sometimes you are pushed by the business, later by [...]

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

How to prioritize in Agile II.: Business value prioritization

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 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 company as well. Business perspective This [...]

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

How To: Business Model and the Product Strategy

Agile works very well in the 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, 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 [...]

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