Hits for your search: Change management

You can also take a look at our website, for example on the topics of leadership development, corporate strategy and portfolio management or our training courses, for example our certified Kanban training courses.If you have any questions or suggestions… Feel free to contact us.

In a world that is constantly changing and increasingly characterized by agility, a new kind of leadership is needed. Instructions and reporting lines are no longer enough. Instead, the agile organization requires managers to shift towards coaching, mentoring and support.This training is designed for all those who are ready to make the paradigm shift towards more self-organization in teams.

Examples of this: Agile collaboration of multiple teams and/or Agile portfolio management. The goal of scaling agile is for the entire organization to become more responsive. Scaled Agile implements Agile for more than one team. Agile & Lean techniques have found their way into many companies and help them to be more responsive and to successfully deal with complex challenges.

Product Backlog Items The Scrum Guide describes product backlog items as follows: “The product backlog lists all features, functionalities, improvements and bug fixes that will make changes to the product in future releases. A product backlog item contains a description, order, estimate and value as attributes.”

Get daily reports from your team members on every change and movement. Document twice rather than not at all and discuss with your team the perfect wording for each work package. Don’t have a conversation without first creating a Kanban card in the system.

Structure larger product backlogs (story maps) Experience a sprint - develop products evolutionarily Estimate and track delivery dates and scopes (e.g., velocity, release burndown) Product owner from hell and heaven Communication with stakeholders (customers, department, line management) Cut Product Backlog entries small Product owner with multiple teams Release planning As a participant, you will

What often happens is that boards are implemented as they are recommended in some management magazine or are already used in other teams in the Orga. Behind this is typically the hope to achieve an ideal state by forcing oneself into a corset of “good practices” of others. This is not how Kanban was intended. However, what is good for others at the time may have a very different effect on you.