Notice: add_custom_background is deprecated since version 3.4! Use add_theme_support( 'custom-background', $args ) instead. in /home/abe/domains/ on line 3573

Notice: add_custom_image_header is deprecated since version 3.4! Use add_theme_support( 'custom-header', $args ) instead. in /home/abe/domains/ on line 3573

Warning: Cannot modify header information - headers already sent by (output started at /home/abe/domains/ in /home/abe/domains/ on line 446
Mateusz Srebrny – AgileByExample 2012
October 4-5 2012
in Warsaw Spread the word!

Mateusz Srebrny

Mateusz is a Scrum Master and Agile Coach who helps teams and companies improve as an independent consultant.
He is one of the founders and animators of AgileWarsaw - a group of Warsaw-based Agile and Lean enthusiasts.
Mateusz has 5 years' experience of using scrum both with a team, and - on a larger scale - in the company.
He was in charge of redesigning and scaling out the server-side software infrastructure for the biggest Polish instant messenger.
At the moment he takes care of a team of 40+ developers working in a multinational environment building an advanced backup system.

Session: Backlog 3D

Keeping track of backlog of a single-team project tends to be pretty much straightforward. You break down the product into small bits of functionality, order them by the importance and put into a spreadsheet or even a wiki page.

The whole thing gets much less obvious when your project team gets bigger and the product more complex. Suddenly the flat list of user stories stops giving you enough insight into what is going on in the project. Even worse - you’re not able to build a flat list of anything out of a bunch of separate backlogs of your sub teams.

This is the situation I am currently dealing with. I am coaching a team of 40 developers and we need to plan and track half a year of product increment. I will share the approaches we took and the reasons why we are still looking for a better way :)

back to Speakers