The development team decides how many sprints will be required for a release and how many user stories they can commit to in each sprint. Product managers collaborate with the engineering team to set the scope of a release based on the capacity of the team. Product managers decide which work items go into the product backlog, ensuring each item delivers the highest value. Familiarize yourself with the key elements of each backlog so you can confidently decide when to use each type:ĭefine and prioritize which features should be worked on in upcoming releases.ĭefine which features need to be completed within a release.ĭefine which user stories need to be completed within a sprint. Using product, release, and sprint backlogs helps streamline your product planning process. The graphic below illustrates how creating product, release, and sprint backlogs can help you define the most important work items to be completed at different stages in your planning process: Understanding which type of backlog to use and when helps you deliver against your product roadmap in an incremental and iterative way. Sprint backlog: User stories that need to be completed during a specific period of time Release backlog: Features that need to be implemented for a particular release Product backlog: Features you want to implement but have not yet prioritized for release There are three main types of backlogs used for prioritizing and implementing features: What tools can you use to manage your backlog?

What is the difference between each type of backlog? Do your release planning in Aha! Roadmaps. This helps you narrow the list of what you want to implement - so you can focus on prioritizing and wait to build out requirements as you get closer to when you plan to ship. It can also be useful to create backlogs for additional planning stages after feature requests are captured. This approach makes it easy for product managers to quickly prioritize the most important work. Requests for new features and enhancements to existing functionality can be added to a backlog and ranked based on business value, for example. However, it is now common even for teams that do not follow a strict agile approach to use backlogs for organizing and prioritizing work items. Many teams use adaptive planning techniques to continuously prioritize what to build and when. The concept of a backlog is rooted in agile methodologies. In order to manage ideas and active work, most product teams use some sort of backlog. You need a way to gather and evaluate requests for your current roadmap. But you need to do more than just be a sounding board for a lot of ideas. These inputs are what drive business innovation and a collaborative team environment. sprint backlogĮvery product team is responsible for capturing new ideas and requests for enhancements. Broken Ranks is a cross-platform title with client for both desktop and mobile.Product backlog vs. The new version features improved graphics, state-of-the-art technology and a lot of new content. We are currently focused on Broken Ranks, a full remake of Taern. Global, including USA, UK, Russia, France, Bulgaria and Germany. Most popular Polish browser mmorpg with over 1 mln registered players.

Our title The Pride of Taern (launched in Poland in December 2010) quickly became the Initially, our activities were pushed towards browser mmorpg on Polish market. On our goal to deliver attractive electronic entertainment to the players. Our team consists of experienced industry specialists along with young talented individuals. We are driven team of 20 people with creative passion for games. We are an independent studio established in 2008 based in Wroclaw, Poland. WHITEMOON System Krzysztof Danilewicz specializes in development, publishing and distribution of mmorpg games.

Broken ranks release date