Hits for your search: Service team

Example: moderation of Scrum events A team wants to gain more confidence in the Scrum events (review, retrospective and planning). Therefore, the team uses a facilitator from wibas, who designs and facilitates two working days together with the team. He contributes ideas on new techniques during the preparation, supports as a co-facilitator during the events and gives feedback afterwards.

You need a multidisciplinary team and a space where you can work together. Because it takes the right environment and the right teams for creativity to emerge. The most obvious benefit of design thinking is to create innovative solutions in short cycles. But as with all agile methods, it's not just about speed per se.

As a coach, trainer and consultant, I frequently come across teams that are having challenges getting their Kanban system up and running. However, it becomes especially tragic when teams expend a lot of energy to maintain something that has been ailing for a long time and only causes frustration.

This is a conference about agility in teams and companies. wibas is again part of it and moderates the track about Agile Leadership. What is the Tools4AgileTeams? The Tools4AgileTeams (T4AT), is a conference that focuses on the dialog about agility in teams and companies.

These teams are at the same time home base and thus also serve the personal exchange and teaming by e.g. cooking together or team days. We have fun ...working – and celebrating together.

Agile S/4HANA – that's more than Scrum Scrum is great at the team level: it helps teams with their focus and individual results. But if you want to leverage the benefits of agility for the program, for collaboration between teams and stakeholders, for joint planning for the overall system, it's worth thinking about agility at the program level with the help of the Scaled Agile Framework think.

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.

When it comes to more than one around one team, sooner or later you can't avoid frameworks like SAFe or LeSS, which provide patterns for agility across team levels. We're happy to look with you at which framework is right for your situation. And as pragmatic as we are, we take a LeSS configuration for an Agile release train without batting an eye.

Teaming with our customers The success of our customers is our top priority. Our commitment and loyalty distinguishes wibas to a special degree. We work with our customers in joint teams. We pass on our knowledge. We communicate at all levels and create an atmosphere of mutual trust and openness. Our consultants speak with one voice, work hand in hand and live an open-door culture. Sounds good?

Team days We not only work exclusively with and at the customer, but are members of self-organized teams with common interests and visions. This team structure enables us to work together on focused topics. At the same time, it serves as a harbor that people like to go to in order to exchange personal ideas, cook together and spend team evenings.