Agile Technical Coaching is about helping teams to solve (mostly non-technical) business problems efficiently with available technologies and tools.

It's about finding ways to make things that should be simple and easy, in fact simple and easy.

Here you have a short checklist. Consider which of these are true in your organization:

If you checked none of the items above, you probably don't need Agile Technical Coaching. Your technical capabilities are in good shape. Great!

If you checked only one or two, agile technical coaching might help. If you checked more than three, we most likely can help you a lot. Let's talk!

There is not a silver bullet that solves every problem, but a great number of small things. We need to understand a bit more what kind of problems you are struggling with.

This is how to get started:

Our proposal is most likely a mixture of hands-on consultation as a part of your team, workshops, training, mentoring and coaching.

We will agree together on an initial plan, set priorities for improvements, and specify what kind of outcomes we expect to see.

Here are some themes we might propose as a solution:

Improve DevOps practices
Maximize value adding work by minimizing time wasted with necessary routines

  • Continuous integration (CI) and continuous delivery (CD)
  • Test automation
  • Infrastructure as Code (IaC)

Improve knowledge sharing and performance
From individual heroes to robust and resilient teamwork

  • Pair and mob programming
  • Efficient use of version control and fruitful code reviews
  • Agile retrospectives

Improve technical competencies
Skilled teams deliver orders of magnitude faster with higher quality

  • Technical, one-to-one mentoring
  • Modern programming practices (e.g. test driven development (TDD), functional programming, SOLID architecture)
  • Learn new technologies and tools

Improve problems solving practices
Complex solutions are a lot easier to invent than simple ones

  • Hands-on problems solving as pair or mob programming
  • Systematic problems solving methods (e.g. TRIZ)
  • Problems solving and innovation workshops

Build shared vision and understanding
Insane amounts of time and money is wasted by building wrong things and for wrong reasons

  • Workshop facilitation (e.g. User Story Mapping, Event Storming)
  • Agile risk management with systematic experimentation
  • Make vision, progress and work visible (Kanban, public demos, feedback cycles)

Each of Flowa’s technical coaches have over 15 years of experience of hands-on experience as developers, coding architects, change agents and agile coaches.


Juha is a holistic software developer. He understands the problems people face while working inside complex systems and helps to solve those through empathy and kindness. He strives to make software development graceful and wants to see happy people create beautiful software that meets the needs.

His specialties are DevOps, functional programming, test automation and the stuff that you probably call agile.

Contact Juha:


Tero is a human and product developer. His sweet spot is in the intersection of people, technology and business. The software that has real impact is created with teams with clear vision, tools and skills to get there and the ones that are having fun in the process. On the technical side he really enjoys functional programming and especially Clojure.

Contact Tero:


Ari-Pekka is a hybrid of engineer and philosopher with endless curiosity to learn more. He has succeeded as an agile coach and scrum master, a coding architect and tech mentor, and a UX specialist and product visionary, and his eager to work in all these areas - and especially in between them. Ari-Pekka is a programmin language nerd, who likes especially functional-first programming languages such as Clojure, F# and Rust.

Contact Ari-Pekka: