Workshops & team sessions
Agile without the hype
A framework alone will not make a team effective. We choose what fits your work, establish a clear way of collaborating, and support the team until the new practices hold up in real delivery.
A new team needs shared direction and a way of working that fits its challenges. Scrum, Kanban, and other agile approaches can help—but choosing a framework is only the beginning.
Together, we take a critical look at your work and decide which practices make sense. In workshops, we clarify goals, responsibilities, and collaboration. In team sessions, we put those decisions into practice with your own product and backlog. If Scrum is the right fit, I support you through the setup and your first sprints.
The goal
Determine whether Scrum, Kanban, or selected agile practices fit the nature of your work, then turn that decision into a usable team setup. When Scrum is the right choice, we establish the product goal, accountabilities, initial backlog, working agreements, and a practical rhythm for the first sprints.
How you benefit
You avoid adopting a framework on assumptions or copying practices that do not solve your problem. The team develops a shared language, a clear operating model, and concrete experiments for learning what works. Teams introducing Scrum can start delivering while continuing to improve the system themselves.
Who is it for?
For newly formed teams, teams redesigning how they work, and organisations considering Scrum or another agile approach. Product Owners, prospective Scrum Masters, developers, team leads, and the people responsible for the team’s mandate and priorities should shape the setup together.
What to bring
No previous Scrum knowledge or specific agile maturity is required. You do need a defined product or challenge, a reasonably stable group of people, and a sponsor who can clarify priorities and working conditions. Openness to questioning familiar processes is more valuable than framework experience.
Preparation
Bring a shared challenge or product, examples of your work, and a willingness to try new practices. Initial product ideas or an existing backlog are useful inputs. For implementation sessions, involve the people who will work together and those who can support the necessary changes.
What we work on together
- Distinguish predictable tasks from complex challenges and understand where agile approaches help.
- Compare Scrum, Kanban, and individual practices against your work.
- Clarify shared goals, roles, responsibilities, and working agreements.
- Build and order an initial backlog around your product.
- When introducing Scrum, establish Sprint Goals, Scrum events, and a Definition of Done.
- Put the approach into practice, support your first sprints or workflow experiments, and learn from feedback.
What you take away
A reasoned choice of approach, clear team agreements, and practical experience with your own work. Teams introducing Scrum also leave with an initial backlog and a foundation for continuing independently.
What’s challenging your team?
Let’s discuss where you are today and what support would help. Together, we’ll agree on the right scope and format.
Book an introductory call