Online meetings are the new reality of our everyday lives. Most of us have already been to an online meeting with a difficult agenda or maybe you’re just planning one. But achieving demanding goals in the online world is not easy. Working from home means more distractions when you’re already trying to concentrate on [...]
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, [...]
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 [...]
Lots of requirements. Lots and lots and lots A story about what will your ‘Yes’ answer cause in the long run. Lots of work. If it was about fire being once here and once there. But the fire burns always, everywhere and every single day. We develop a number of system customizations and our app [...]
New features in ScrumDesk v. 6.32 Objectives and Key Results Dependencies tracking Faster time tracking Filter improvements Billable work Change hierarchy in the STORY MAP Measure spent time vs. capacity planned Recurring payments Objectives and Key Results (OKR) — track goals with ScrumDesk Agile is a great tool for the company to execute its [...]
Root Cause Analysis Editor We are glad to see more and more (and especially experienced) agile teams use the Root Cause Analysis editor to build a shared understanding of the reasons for their impediments. This way agile teams can focus on the true cause of the problem instead of solving some indicators. In this [...]
What is an agile epic, what to use it for, and foremost how? Requirements. Small, large, technical, business, operational, and 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 the only requirements that we have decided to implement [...]
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: [...]
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 [...]
How to balance business and technology requirements in a product backlog to build a successful product in long term. Product ownership is hard stuff. Very often you feel 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 architects [...]
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 [...]
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 [...]
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. [...]
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 [...]
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 [...]
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 [...]
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 [...]
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 [...]
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 [...]
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 [...]
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 [...]
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 [...]
