• Organizational Resilience

    They develop empowered leaders who can confidently navigate their organizations through challenges.Our training courses on Scrum, Kanban, and SAFe teach techniques for efficient work management. They promote short decision-making paths, rapid adaptation and a high level of responsiveness – key building blocks for organizational resilience in dynamic markets.

  • High corporate responsiveness secures  business

    Iterative processes like Scrum or Kanban allow for testing new features in short cycles and quickly integrating customer feedback into further development. This approach ensures that products and services are continuously improved and can keep pace with changing market demands.

  • AI workshop for beginners

    The final module awaits you:Discussion about future developments in the field of AI and their impact on various industries: we develop forecasts for the development of AI in their specific areas of work and discuss how AI can influence future business and work processesPresentation of real use cases and interaction with an AI consultant: Introduction to the wibas AI Advisor based on the Ultimate Scrum

  • SAFe 6.0 DevOps Training (SDP)

    All members of Agile Release Trains Development and Engineering Manager Configuration and Release Manager Development Manager, Developer, UI/UX Developer System and infrastructure architects System Administrators, DBAs, InfoSec QA Manager and Tester Release Train Engineers, Scrum Master Varied mix of theory and practice Like all our agile trainings, this one is interactive.

  • Kanban System Design Training (KMP I)

    In addition to the Kanban content, we are therefore happy to share our experience with the combined use of Kanban and Scrum, for example, on request. InteractiveExperience-based, interactive training with simulations and flipcharts, no slides. AccreditedKanban University accredited trainers who explain applicable Kanban.

  • A tricky slide about Story Points and Capacity in SAFe® – and how to get it right.

    This is based on several assumptions: The length of an Iteration/Sprint is 2 weeks (which leaves us with 10 working days); 10% of our time is spent on Iteration/Sprint events (as suggested in the Scrum Guide); 10% of our time is spent on Product Backlog Refinement (as suggested in earlier versions of the Scrum Guide); Our reference Story, which represents “1” Story Point, takes about half a day to

  • Estimation with Normalized Story Points? Really?

    Another reason for not aligning may be that experienced Scrum teams come together that already have an existing Story Point scale. Read my other articles about SAFe estimation. Agile Estimation in SAFe: Debunking Myths and Clarifying Practices A tricky slide about Story Points and Capacity in SAFe® – and how to get it right. Thank you, reviewers. Estimation is a tough subject.

  • Change along the adoption curve: 5 groups for sustainable change

    During the event, the Scrum Team, which has already experimented a lot, will have the opportunity to share where the new way of working has helped them so far. Of course, questions may also be asked. It is important to Cedric that there is a chance for interested people to sign up. This opportunity is available directly and also afterwards with Malika and himself.

  • Chapter 2

    Particularly noteworthy are:Adaptability: The discussions about different methodological approaches, from Scrum to Kanban, show the need for a flexible approach to transformations. In a constantly changing environment, sticking to a single approach can be a hindrance.

  • Chapter 1

    I would therefore like you to accompany this change and coach the new Product Owner and also the Scrum Masters of the teams to achieve our goals." Katharina couldn't help but laugh for a moment. "You put that very nicely, Manfred. I'm looking forward to working with you. What have we experienced here? We witness a promising start.