Hits for your search: Ulassa Planning Poker

„Sure, it’ll be your board, not the team’s.“ Here are the steps of our moderation plan: We ask the workshop participants about their experience with Kanban. The query helps us as moderators to understand how many explanations we have to include on the way. Our motto is: we explain stuff when it is needed. This saves us a big Kanban explanation at the beginning.

We like plans - precisely to be able to accommodate change. We like shared direction - because purpose and vision give people freedom to act. And we believe that interdisciplinary teams rather than homogeneous departments support joint working and bring work into flow. For us, these are all essential components of New Work.

Scene 1: Thoughts and plans Manfred stood at the window of his office and looked out at the open-plan office opposite. He could hear the quiet hum of the air conditioning and the clicking of keyboards. He noticed the subtle signs of unease among the team members. Some seemed anxious, others appeared to be engrossed in intense conversations.

You will learn how long-term planning works - even in an agile environment. Agile leadership should know different agile models and methods. You should know the different scaling models in your organization and understand which operating principles come into play there.

Kanban in portfolio management At the portfolio level, Kanban helps to create a clear overview of all current and planned projects. This enables management to make informed decisions about priorities and resource allocations. Important aspects here are Creating transparency: A Kanban board at portfolio level visualises the status of all projects and makes bottlenecks visible.

Change in the chemical industry Establishment of an agile way of working as well as stage planning and introduction of a portfolio level to avoid continuous overload. Upcoming events 06.-08.05.25 wibas at the MedConf 2025 Medconf is the technology hub and networking platform for medical technology. We are now participating for the 2nd time in Munich.

Your path to a profitable sustainability report according to CSRD could look like this: The principles of our work in sustainability reporting We plan and design an individual sustainability reporting process for and with you in accordance with CSRD. With our partner we offer nunc sustainability a unique mix of technical expertise in report preparation and experience in process design.

For example, SAFe offers as one pattern the "Planning Interval" which holds a cadence superior to the Sprint. LeSS offers as a pattern a Product Owner for several teams, which the team members then support in their requirements management. Both are good ideas - it depends on what fits the specific situation and what fits the company.

An example of this article format can be found in the PI Planning article The Importance of Distinguishing Between the Framework and Implementation Guidance Our experience shows that it is crucial to differentiate between the core framework and its implementation guidance. This distinction is essential for: Consistently applying the core framework.

Build high-performing teams and drive consistent improvements at scale Address Agile and Scrum Anti-Patterns Support the application of engineering practices, DevOps and agile architecture Apply Kanban and eXtreme Programming (XP) frameworks to optimize the value stream and improve the work of the team Support PI planning and the generation and delivery of value streams in end-to-end systems Support