The conference has been opened by Krisztina Fogl from Stamford Global and I would like to thank her for organizing this event and inviting me as a speaker. And now Beth Ouellette and Greg Balestrero are doing a competition in collecting the most business cards within 45 seconds, so people are starting to wake up ,-)
Opening of the Nordic Project Zone
14.11.2011Scrum Pattern: ScrumBan
13.11.2011
| Context | A Scrum Team is working on many tasks at the same time and productivity is low. |
| Problem | Multitasking drastically reduces productivity. Multitasking requires many context switches, so productivity gets reduced by bringing one task to a state where it can be put away for some time and (re)starting the next task requires some ramp up effort. Furthermore having a head full of many tasks which need to be done does not free the mind to focus on a few tasks to be done right. |
| Forces | too little/too much multitasking too little/too much flexibility |
| Solution | Spice up Scrum with Kanban Kanban brings two important aspects to Scrum. Transparency is increased with a Kanban board which shows tasks in a column view, representing a value chain. E.g. put Product Backlog Items in the leftmost column, Technical Tasks in the next one, followed by an “in progress” and a “done” column. By moving the cards through the columns, the teams always knows where it stands. The second aspect is the work-in-progress limit (WIP). It limits the number of cards per column. The limit can either be imposed per team member or for whole team per column. Thus multitasking is limited and productivity is increased. If the process gets stuck, the team members blocked by the WIP limit(s) switch over to supporting those members which are working on stuck tasks in order to remove road blocks. Note: The “pull pattern” from Kanban is already part of Scrum. |
| Resulting Context | The throughput of the Scrum Team increases and the Kanban board provides a higher level of transparency. |
Before the Nordic Project Zone 2011 @ Stockholm (Photos)
13.11.2011On Friday, I arrived at the conference hotel with quite a nice view on the city of Stockholm. And I even more enjoyed the concert of the Stockholm Swing All-Stars yesterday. They are superb musicians and I recommend visiting one of their concerts, especially in such a nice location as the Konserthuset:
Greg Balestrero, former CEO of the Project Management Institute is already here and I will have a look into the conference rooms later today.
I hope the weather will improve and tomorrow you can join my presentation on Advanced Enterprise Scrum Patterns.
Scrum Pattern: Company Backlog
11.11.2011
| Context | An organization has many Scrum Teams working on different Product Backlogs. |
| Problem | No top-level-priorization of Product Backlog Items. The investment into an important project is limited by the number of Scrum Teams working on their respective Product Backlog. For individual Product Backlog Items, priorization only works within projects and important Product Backlog Items might be delayed. |
| Forces | too little/too much centralization |
| Solution | Create a Company Backlog Integrate all Product Backlogs into a global Company Backlog and assign a single person to be the Product Owner of that backlog (e.g. a Chief Product Owner). When using epics and themes, the Company Backlog becomes clearer and supports regular priorization reviews by senior management. |
| Resulting Context | ROI for the organization is increased as the most important requirements are implemented first. |
Posted by Andreas Heilwagen







