• Agile Myths: Agility equals Scrum?!?

    However, it has proven itself in practice, and so it was included in the Scrum Guide. Around the agile frameworks there is a – very broad – set of (agile) working techniques. Techniques can be used, exchanged or adapted more or less arbitrarily within agile frameworks.

  • Our agile coaches as supporters of your transformation

    As coaches and guides of an organizational transformation, we do everything we can to make this happen. Previous Next ★ ★ ★ ★ ★ Agile methods implemented expediently wibas supported our software development teams in introducing agile working methods - primarily Scrum. Our challenges were on the one hand the high workload of the teams and on the other hand the lack of prioritization of tasks.

  • About our trainings

    You can familiarize yourself with the tools before the training with the help of a guide so that you are optimally prepared. Our service team is also available to answer technical questions and provide assistance during the training. Q&A with wiba's trainer Sascha GeßlerThis is what remote training looks like in practice.

  • What is agile leadership?

    They need to be guided by guidelines and rewarded or sanctioned by appropriate measures. Many traditionally structured organizations have rules and instruments that are aligned to Theory X. Agile leadership and agile leadership means that I create a framework that pays into Theory Y ideas. Agility means designing an organization according to Y principles - and letting go of X techniques.

  • What is an agile mindset?

    Agile values as the foundation of the agile mindset.Frequently, agile values are mentioned as a description of the agile mindset - strictly speaking, these are the values that are defined in the official Scrum Guide are named as Scrum values: Focus, Courage, Respect, Commitment and Openness. These are the values that each individual should bring to the collaboration.

  • How to masterfully screw up your SAFe implementation

    How to safely fail your SAFe implementation The following non-recommendations are very much in the style of Watzlawick’s “Guide to Unhappiness”. What is failure and what is success is often subjective, as is this entire article. Rarely are there collectively objectified metrics that precisely define success or failure.

  • Lean-Agile Systems Engineering at Bosch Automotive Steering

    Their vision and commitment guided the launch of the PSYS ART and the broader adoption of lean-agile systems engineering practices.Tailoring is Key: Agile principles must be married with local practices.

  • Improving your Scrum with Kanban? You can do it.

    Often we then still find people with the titles “Scrum Master” and “Product Owner”, events are held more irregularly and less and less according to the idea of the Scrum Guide, sprints get out of sync more and more often because the customer, the market, the situation requires it.

  • 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

  • Agile Estimation in SAFe: Debunking Myths and Clarifying Practices

    Whether you’re new to SAFe or think you’ve heard it all, this article promises fresh insights, debunking myths and guiding you through the agile maze with clarity and precision. Read this article if you want to know how proper agile estimation works, since years, and still with SAFe. TLDR: When using SAFe®, we keep proven agile estimation practices. We do add another level of flow.