• Value stream mapping in practice

    Step by step, we apply value stream mapping methods, identify bottlenecks and potential for improvement and discuss concrete solutions.The workshop is limited to 6 participants; Caroline Haußmann and Frank Eberhard - our&nbspexperienced coaches Caroline has been guiding companies and managers through complex change processes for over 20 years.

  • When working harder is not the solution …

    In the modern business world, where speed and efficiency are key, managers are often looking for ways to ‘push’ their teams to perform better. But what if working harder is not the solution? What if the key to higher productivity lies in optimising the flow of work? This is where Kanban comes into play.

  • E-T-A and wibas design a participative and agile strategy process

    Managers began to model agile and a distributed digital work practice was introduced that encouraged self-organization and self-management.

  • Agile Usergroup Rhein Main on 07.03.24: Agile Transformation

    We will also use the Agile Coaching Growth Wheel - a tool for coaches, scrum masters and managers. Speaker: Caroline Haußmann Caroline Haußmann is a Senior Agile Coach at wibas and has been supporting clients in agile transformations for many years. She is an expert in Scrum, agile organizational design and change management.

  • Agile Myths: User Stories – a mandatory format for Scrum Teams?!?

    And product backlog entries can be written by anyone and brought to the product owner.

  • Agile Requirements Management Workshop

    InteractiveExperience-based, interactive training with simulations and flipcharts, no slides AccreditedAccredited trainers who explain real applicable agile methods and principles, not an interpretation InnovativeDedicated training rooms in the wibas training center with innovative equipment, no hotels Agile product vision Creating a product vision Visualization of the product vision with the product

  • SMART Goals in Scrum

    Firstly, the Product Backlog is created jointly by the Product Owner and the team – in order to achieve a common acceptance of the entries. Secondly, the team is responsible for pulling the Product Backlog entries into the Sprint. So: “Accepted” is addressed by a joint Product Backlog Refinement and by the team pulling Product Backlog entries into the Sprint.

  • Kanban Compact

    In Kanban, work does not need to be planned or controlled by a manager. Through visualization and the pull principle, in the self-regulating system, the team can organize the work independently and optimize its processes. Kanban is used in many teams to perform tasks together effectively and efficiently. Kanban Compact provides you with the most important contents in a condensed form.

  • What is Scrum?

    The goal is to make the product better. In the Sprint Retrospective, the Scrum Team plans ways to increase quality and effectiveness. The Product Backlog Refinement is more than an event The Product Backlog Refinement is listed again and again as a Scrum event, but in fact the Product Owner works on the refinement of the Product Backlog during the entire Sprint.

  • What is Scaled Agile?

    Scrum is primarily about one team and one product. We talk about scaling Scrum in the case of multiple teams and/or multiple products. The graphic shows four typical cases of one or more products, and of one or more teams. Bottom left: The typical Scrum team works on a product and has a product backlog. Bottom right: A Scrum team works on multiple products.