Training

If you’re a senior leader or business partner, how should you engage with Agile teams? What should you change in terms of management systems and human systems for real Agility? How can you get your objectives met, especially if the Agile transformation has resulted in a wide spectrum of understanding, buy-in, and implementation?

Most senior leaders struggle with these questions, often due to assumptions they make. Mistakenly, they think Agile is “better, cheaper, faster”, a process with a set of best practices, or a framework they can “install” for managing technical work. With little change in the organization’s middle (or higher), little agility is gained.

It gets worse. Even when technology managers learn the answers, their business counterparts are usually left guessing.

This one-day experiential training, “The Leader’s Guide to the Agile Mind-Set”, will give you everything you need to know for healthy engagement with Agile teams that deliver reliably. It is a scalable solution for large organizations due to its brevity (only one day). And it builds partnership and mutual understanding due to its design, which is neither process-heavy nor technology-focused.

This training is a game changer for large corporations undergoing massive Agile transformations. Ask us privately for references.

If your team has been doing Agile for a few months, are they also being Agile? That is, do they truly put people before process, deliver value frequently, respond to change economically and without drama, and collaborate with their customer?

Many teams start their Agile journey doing Agile: going through Scrum/SAFe/Kanban motions and trying “best practices.” But without a solid grasp of the Agile mindset — values, beliefs, and principles — those motions will not make them agile. People cannot get great at Agile by following recipes and imitating moves, as if they’re learning to drive; the concepts that make Agility work must permeate their work.

This workshop is perfect both for teams that need to level up with Agile and for teams that are struggling to get Agile (and perhaps take a dim view of it, for the wrong reasons).

Class size: 12-20 participants.

In a healthy Agile environment, people communicate, collaborate, and decide together all the time. The big idea is that the group can be smarter than the individuals, which means it will do better work and produce better results.

However, too many teams do not experience this synergy:

• Rather than have valuable interactions, they complain, “Agile has too many meetings!”
• Instead of determining work together, they wait for someone to assign them tasks.
• They default to working on tasks individually “because that would be faster”.

These patterns rule out group wisdom, but that’s not the only problem. When the team doesn’t act as a team, the non-collaborative power structure (“command & control”) fills the vacuum. This is especially evident in team events (“ceremonies”), which are frequent in Agile. Soon enough, team members get disillusioned about empowerment and disenchanted toward Agile.

It’s actually quite easy to turn this situation around. In this one-day training with Gil Broza, you will:

• Identify the elements of your Agile setup that discourage collaboration.
• Practice powerful, simple techniques to make every meeting collaborative, worth having, and a welcome experience for its participants.
• Discover what it takes to move from a group of busy individuals to a healthy, thriving team.

Class size: 8-20 participants.

Almost every month, we receive an inquiry from an organizational department that wants Agile, but they don’t do software. Recent examples include medical research, HR, corporate real estate, marketing and branding, media digitization, and TV show development. They don’t quite know how to start, and correctly sense that Scrum training isn’t quite what they need.

All of these clients required custom implementations of the Agile mind-set; some were charting new territory, as their work context was too far removed from what the popular methods have been designed for. Their teams and managers all took our “Agile for Non-Software Work” course to learn the ins and outs of the Agile way of working without being attached to any particular practice or process framework. What they learned enabled them to start on the right foot. Interested? Talk to Gil.

Class size: 10-20 participants.

This course is designed for teams that realize that simplistic Scrum mechanics, roles, and artifacts won’t make them Agile.

With this course, teams learn the Agile values, beliefs, and principles (= the mindset), what Agile is and isn’t, how to perform good practices correctly and usefully, and what Agile behaviours look like. It also includes critical components that are missing from certified Scrum.

This experiential training makes use of powerful simulations, activities, and interactions not found in the hundreds of publicly available Scrum courses. We evolve the material continuously based on the best knowledge the Agile community has to offer. The instructor, Gil Broza, has been coaching organizations since before Agile had its name, and has authored books on the most commonly neglected aspects of Agile — the mindset and the human side.

Class Size: Up to 20 participants

You’re using Agile ways of working for certain benefits: adaptation, better customer-product fit, and frequent value delivery. Do your software developers exhibit the necessary Technical Agility to support all that, both short term and long term?

It might feel that way if you have developers talking with POs a lot, backlogs full of detailed stories with acceptance criteria, a CI environment, some unit- and end-to-end automated tests, and lots of DevOps. But if you look closely, you might discover — this is painfully common — that developers overbuild, write ineffectual tests, wade in messy code, or create designs that will make later changes very costly. They don’t have sufficient Technical Agility to support the desired Business Agility. What’s worse, some of those teams also do continuous delivery (CD), and their behaviours are really too unsafe for CD!

In this Agile Engineering course, programmers learn reliable, sustainable, and enjoyable software development attitudes and practices. They’ll be poised to become true Agile developers, collaborators that POs may rely on to consistently produce easily changeable code. They can immediately put to use everything they learn in this course to reduce time to market, increase quality, and contain technical debt.

Participants’ learning objectives:

• evolve well-designed software with minimal cost of change
• develop simple, clear, and proven code faster than ever
• keep their code shippable at all times
• take on legacy code confidently
• make continuous delivery possible and safe

Note: Delivered in Java and with exercises in both Java and JavaScript, this course is also suitable for mobile, C#, and PHP developers. It is carefully designed to impart principles and techniques independently of the programming language, therefore the exercises use only basic language constructs.

Class Size: Up to 20 participants

Product managers, UX/UI designers, business analysts, and domain architects are all Agile Customers. (One of these roles is typically designated as the lead, or Product Owner.) This role comes with great responsibility, far beyond merely writing user stories and prioritizing a backlog.

To be successful their role, the Agile mindset must permeate everything Agile customers do: choosing the work, engaging with delivery teams, working better. They need to know how to make commitments while eschewing predictions, how to thin-slice work items, and how to chart meaningful evolutionary paths. The tools and techniques are secondary, yet somehow they are the focus of most PO courses out there.

Participants’ learning objectives:

• Decide (easily) what to work on… and what not to work on
• Perform useful customer practices
• Structure your daily activities well (and stay sane)
• Feel confident about carrying out your role effectively
• Work collaboratively and effectively with delivery teams

Class Size: Up to 20 participants

If you’re a tester, your Agile team invites you to be an equal, contributing member from the very first day. What are you supposed to do? How can you contribute? What are effective, desirable behaviours and attitudes? And what would you need to do to adopt them easily and confidently?

The course is designed to turn testers from people who “happen to be in a Scrum team” to bona fide Agile testers. Participants will see exactly where they fit in an Agile team throughout the work’s life-cycle. They’ll understand how Agile teams can deliver working software on time without squeezing the testers (or testing in the next iteration). Throughout the course, they will examine their beliefs and assumptions about software testing and adjust them easily to an Agile environment.

Participants’ learning objectives:

• Test more effectively and pragmatically than ever before
• Engage productively with developers, product owners, and managers
• Add value to your team and organization every day (not just at the end of the project)
• Understand what’s changed and what’s remained in the move from traditional testing (e.g. ISTQB) to Agile testing
• Cover all of your team’s testing needs

Class Size: Up to 18 participants