ScrumDesk v6.29.1: improved Root Cause Analysis editor, KANBAN style + more!

Root Cause Analysis Editor We are glad to see more and more (and especially experienced) agile teams to use Root Cause Analysis editor to build a shared understanding of reasons for their impediments. This way agile teams can focus on the true cause of the problem instead of solving some indicators. In this version [...]

By |February 9th, 2018|Categories: Blog, Latest news, Releases, ScrumDesk|Tags: , , , , |Comments Off on ScrumDesk v6.29.1: improved Root Cause Analysis editor, KANBAN style + more!

Epical epic. How to write epics in Agile.

What is an epic, what to use it for and foremost how? Requirements. Small, large, technical, business, operational, researchable. And above all, plenty of them. During four years of ScrumDesk development, we have more than 800 requirements in our backlog. And these are only requirements that we have decided to implement without any further [...]

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

Version 5.27.2 – Archive epic, bring transparency into the backlog

Archive epic From this version, you can archive not just release, but epics as well. ScrumDesk is used by customers in multiple ways. Some customers prefer epics as long-term containers of user stories. This is especially useful for product development where epics represent bigger functionality. Some other customers prefer however epics as project phases [...]

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

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 v3.9 – retrospective done well

Retrospective techniques Do you need to energize your retrospectives? There is one very easy receipt to try. Just changing retrospective format or technique helps a lot. ScrumDesk enables now to apply following retrospective techniques: classic Good vs. Better, Star Fish, Mad Sad Glad, 4L, Star Stop Continue, 6 Thinking Hats, and even possibility to place [...]

ScrumDesk v3.8 – print backlog, filters and mentions

Print backlog Finally! Printing has appeared in ScrumDesk. As we have great planning experience with physical cards, we decided for 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. Printed are just visible cards so filter [...]

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

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

Grow your 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 as next. Even more, many customers ask you of new functionality or defect fixes. In [...]

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

By |September 28th, 2010|Categories: Blog, ScrumDesk for Windows (retired)|Tags: , , , , , |Comments Off on Step 5: Plan sprints

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