Scrum Master Toolbox Podcast: Agile Storytelling from the Trenches Episode Summary: CTO Series – "The Anti-Scaling Paradox: Why and When a CTO Should Refuse to Grow His Team" with Markus Kjort

Host: Vasco Duarte
Guest: Markus Kjort, Co-founder and CTO of Bitmagic
Release Date: April 7, 2025

Introduction

In this insightful episode of the Scrum Master Toolbox Podcast, host Vasco Duarte engages in a compelling conversation with Markus Kjort, the visionary CTO of Bitmagic, an AI-aided game development company. Drawing from over two decades of diverse experience in software development, gaming, fintech, and leadership, Markus delves into the nuanced challenges and strategies surrounding team scaling within tech startups. This episode, titled "The Anti-Scaling Paradox: Why and When a CTO Should Refuse to Grow His Team," offers invaluable perspectives for CTOs, Agile Coaches, and Scrum Masters navigating the complexities of team dynamics and organizational growth.

Pivotal Moments in Leadership and Technology

Leading by Example and Positive Attitude

Markus begins by reflecting on formative experiences that shaped his leadership style. He recounts an early career moment where his project manager praised his unwavering positive attitude during a farewell party (01:58). Initially questioning whether he should express concerns more openly, Markus eventually realized the profound impact of maintaining optimism as a leader. He emphasizes the importance of fostering a resilient team mindset, especially during challenging phases:

"Even in very hard situations, when I as a leader say that, okay, now this is a very bad situation, but we can handle this, let's just start doing one task at a time... that helps the team a lot." (07:00)

The Reality of Estimates

Markus also highlights the critical skill of making accurate estimates, referencing Steve McConnell's "Programming Pearls" (06:00). He shares a candid story about underestimating a project's timeline, which ultimately led to a more sustainable and realistic development pace:

"If I would have implemented in a way that we have only months, it would have been a nightmare. That helped us create a different kind of setup and a mood to the project." (07:14)

Aligning Tech Strategy with Business Goals

Continuous Stakeholder Engagement

A significant portion of the discussion focuses on the alignment between technology strategy and business objectives. Markus underscores the necessity of maintaining ongoing dialogues with key stakeholders, including CEOs and leadership teams, to ensure that tech initiatives are in sync with broader business aims (11:20). This proactive communication fosters trust and transparency, enabling informed decision-making that aligns development efforts with strategic goals.

"This gives me a picture of what kind of features we might end up doing, and then it helps with the technology strategy." (09:41)

Transparent Communication Across the Organization

Markus advocates for open communication of the tech strategy beyond the leadership level. By articulating the rationale behind technical decisions in non-technical terms, he ensures that the entire organization understands and supports the technology direction:

"We are using these cloud services because we want to go fast... or later shift to focus on reliability and security." (14:17)

Fostering Tech and Business Collaboration

Collaborative Team Structures

To bridge the gap between tech and business teams, Markus emphasizes the creation of collaborative environments where developers and business representatives work closely on features. This approach not only enhances alignment but also builds mutual trust and understanding:

"There should be these kinds of situations where they work together in some cases... that helps them trust each other and align better." (19:02)

Playtest Sessions as a Bridge

In his current role at Bitmagic, Markus introduces innovative practices like daily playtest sessions. These sessions serve as informal yet structured opportunities for team members to engage directly with the product, fostering spontaneous and meaningful interactions between business and development personnel:

"We have daily playtest sessions where everyone can join, play, and provide feedback, leading to informal discussions and continuous improvement." (20:47)

The Anti-Scaling Paradox

Strategic Team Scaling

Addressing the core theme of the episode, Markus discusses his philosophy on team scaling within startups. He advocates for deliberate and strategic growth, emphasizing the importance of maintaining small, highly skilled teams over rapid expansion. Markus highlights the balance between permanent hires and contractors, suggesting that while contractors can offer immediate expertise, permanent team members provide long-term stability and cohesion:

"It's very important to pick that it's okay to spend time on recruiting the right people... sometimes deciding not to scale immediately and instead finding ways to hit milestones without new developers." (22:25)

Balancing Growth with Team Cohesion

Markus shares his experiences of managing team splits during critical projects, illustrating the tough decisions involved in balancing financial necessities with project demands. He describes a pivotal moment where he had to divide his team to undertake a profitable side project without derailing the main product development:

"Splitting the team was one of the hardest decisions because, from a technical point of view, half the team leaving for side projects was detrimental, but it was necessary to secure funding." (30:24)

Navigating AI's Impact on Development

Adapting to Rapid Technological Changes

Although the conversation briefly touches on AI's influence, Markus underscores the transformative effect of AI on both product development and team operations. He notes how AI tools have augmented his coding capabilities, enabling him to handle more complex tasks and stay abreast of evolving technologies:

"AI assists me tremendously, allowing me to implement features I previously didn't know how to create." (31:01)

Future-Proofing Development Practices

Markus anticipates that AI will continue to reshape development workflows, urging teams to remain adaptable and continuously assess how emerging technologies can enhance their processes and products.

Key Performance Indicators for CTOs

Prioritizing Working Software and Team Well-being

In reflecting on organizational performance, Markus emphasizes the paramount importance of delivering working software frequently as a measure of success, aligning with Agile principles:

"How often we can release working software to end users is the most critical factor." (34:05)

Beyond technical output, he highlights the significance of monitoring the team's energy and morale, recognizing that a motivated and happy team is essential for sustained performance:

"It's very hard to quantify, but the team's energy and mood level are crucial for performance in a small startup environment." (35:27)

Implementing Feedback Mechanisms

Markus discusses practical methods for gauging team sentiment, such as one-on-one meetings, attention to informal signals during playtest sessions, and even leveraging AI for sentiment analysis in commit messages:

"Using an AI agent to perform sentiment analysis on commit messages could provide early warning signals for potential issues." (37:10)

Lessons Learned and Influential Reads

Embracing Deliberate Decision-Making in Crisis

One of the standout lessons Markus shares is the importance of deliberate decision-making during crisis situations. Drawing from "Rapid Development" by Steve McConnell, he advises against reacting impulsively under pressure, advocating instead for structured problem-solving:

"In crisis situations, instead of immediate action, it's better to pause, assess, and decide who does what effectively." (40:46)

Influential Literature

Markus credits "Rapid Development" by Steve McConnell as a pivotal book that influenced his approach to reliable and fast software development, particularly noting its insights on avoiding planning under pressure.

Conclusion and Resources

As the episode wraps up, Markus provides listeners with avenues to connect and learn more about his work:

• LinkedIn: For professional networking and updates.
• Bitmagic AI: Visit Bitmagic AI to explore their projects and join playtest sessions.
• Kodia Pinala Podcast: A Finnish technology podcast co-hosted by Markus.

Global Agile Summit Promotion

The episode concludes with a promotion for the Global Agile Summit in Tallinn, Estonia, highlighting an array of speakers and tracks focused on Agile Business, Agile Product, and Agile Developer practices. Markus encourages listeners to attend and engage with over 200 Agile professionals worldwide.

Notable Quotes

• Markus Kjort on Leadership:
  "Even in very hard situations, when I as a leader say that, okay, now this is a very bad situation, but we can handle this, let's just start doing one task at a time... that helps the team a lot."
  (07:00)

• On Estimates and Reality:
  "If I would have implemented in a way that we have only months, it would have been a nightmare. That helped us create a different kind of setup and a mood to the project."
  (07:14)

• On Tech and Business Alignment:
  "We are using these cloud services because we want to go fast... or later shift to focus on reliability and security."
  (14:17)

• On Team Scaling:
  "It's very important to pick that it's okay to spend time on recruiting the right people... sometimes deciding not to scale immediately and instead finding ways to hit milestones without new developers."
  (22:25)

• On Crisis Management:
  "In crisis situations, instead of immediate action, it's better to pause, assess, and decide who does what effectively."
  (40:46)

Key Takeaways

• Positive Leadership: Maintaining a positive attitude as a tech leader can significantly influence team morale and resilience.

• Realistic Estimations: Providing ballpark estimates helps set realistic expectations and fosters honest communication with stakeholders.

• Strategic Scaling: Deliberate and measured team growth, balancing permanent hires with contractors, ensures sustainable development and team cohesion.

• Collaboration and Trust: Facilitating close collaboration between business and tech teams builds trust and enhances alignment with organizational goals.

• AI Integration: Leveraging AI tools can augment development capabilities and streamline complex tasks, but requires continuous adaptation.

• Performance Metrics: Focusing on frequent delivery of working software and monitoring team well-being are crucial for sustaining performance in startups.

• Crisis Management: Adopting structured decision-making processes during crises can prevent panic-driven mistakes and ensure effective problem resolution.

This episode offers a rich blend of practical insights and strategic perspectives, making it an essential listen for Agile practitioners and technology leaders aiming to navigate the delicate balance between team growth and maintaining a cohesive, high-performing development environment.