What kind of setup do teams really need to perform at their best? Agile or conventional? Guided by principles or governed by rules? Should hierarchy be based on seniority or competence? A fixed structure built on deep mutual trust—or a flexible collective that reinvents itself regularly in response to market changes?

At BRANDAD, we're proud of our standing teams: well-coordinated, finely tuned, and ready for action. Stefan Roock from it-agile, on the other hand, advocates for fluid teams—more adaptable, less static, and focused squarely on value creation. In large companies, staffing is often handled pragmatically and on demand, depending on the project. Experienced organizational and team developers are well aware of the pros and cons of assembling new teams with roles tailored specifically to the next project’s needs.

In our panel discussion, we’ll bring these (and other!) perspectives together—including at least:

Together, we’ll explore lessons learned, friction points, and real-world challenges—and work toward identifying what it actually takes for teams to not just sound agile, but truly be agile.

New to terms like “standing team,” “mission team,” or “floating team”? No worries! Before the panel, we’ll run a quick, practical mini-bootcamp to get everyone up to speed—buzzword-light, impact-heavy.