• If you understand Kanban, your SAFe will be better.

    The innovations in the SAFe 6.0 framework aim to streamline the delivery process so that the right value is delivered to the customer in the shortest possible time. So they aim to deliver the right thing at the right time (you remember? 😉). This applies to all levels of SAFe: Team, Agile Release Train (ART), Solution Train and Portfolio.

  • Chapter 2

    He remembered a statement from Katharina: "For that to work, we first need to better understand the product and the value stream." He paused for a moment, then continued: "Maybe we really need to think about the whole logistics value stream and how leadership and structure can work in such an extended environment."

  • Scrum: Framework for development with agile teams

    Your expert for Scrum: Sascha Geßler 64293 Darmstadt sascha.gessler@wibas.com E-mail Call Business card

  • Kanban Service Team - a development journey

    Your contact person: 64293 Darmstadt julia.stiegelmayer@wibas.com E-mail Call Business card

  • Certified Agile Leader (CAL 1)

    Your contact person:: 64293 Darmstadt training-order@wibas.com E-mail Call Business card

  • Certified Scrum Professional Scrum Master (CSP-SM)

    Request support now Your expert for wibas trainings: Jana David wibas GmbH 64293 Darmstadt training-order@wibas.com E-mail Call Business card

  • SAFe 6.0 for Teams Training (SP)

    Your expert for wibas trainings: Otto Hesse St. 19B 64293 Darmstadt training-order@wibas.com E-mail Call Business card undefined

  • Implementing SAFe 6.0 Training (SPC)

    Configure SAFe® for your individual business context.

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

    Cedric has already heard all the mutterings and knows that even though the group is often difficult, the Late Majority is of great value to the organization. It provides stability in all the changes and wants to make sure that what’s new really works for everyone.

  • Agile myth: Writing user stories is Product Owner work

    The Scrum Guide records the following tasks for the Product Owner: Clearly formulate product backlog entries; Sort the entries in the product backlog in such a way that goals and missions can be optimally achieved; Optimize the value of the work done by the development team; Ensuring that the product backlog is visible, transparent and clear to everyone and shows what the Scrum team will be working