In my technology career, the movement from Waterfall (which should never have been adopted and is in the original paper as not being suitable for most software development) to Agile development of either Kanban or Scrum are the main processes adopted.
Bags of time and effort has been spent on which method is better.
It generally comes down to the capability of the team, with the self-managing better suited for Kanban and the less experienced, for Scrum. 90% of my teams have run a Kanban process.
I could easily disparage one, big up the other and reopen that old debates about which is best. But for a CTO, it doesn’t really not matter.
From the development teams, the CTO is only concerned about delivery. Making sure that new features are released and any bugs (never in my systems) are fixed. Whether you have a continuous delivery or fixed at specific times, other teams in your business need to be aware of what has been delivered and what is not in the release, along with what is coming up.
It is the “what is coming up” and the bigger picture that a CTO needs to communicate, but can be very difficult with many of the Agile systems and processes. For example, Jira is great at the micro ticket level, but very bad at trying to communicate the roadmap and strategy for a product, both to the team(s) and to the company. (There have been some improvements recently but it is still disjointed).
The purpose of a roadmap is to allow the rest of the business to prepare for new functionality that is arriving, whether that is for marketing to prepare campaigns or sales to use it to close deals. It’s clearly important and the CTO needs to know from scrum masters the status of the work and if there are any blocks or issues coming up that might cause problems. Hiding problems and expected delays, which is particularly common in the public sector, can cause a project to be delayed at the last minute, creating embarrassment and distrust at all levels of a development team and with the rest of the company.
The best working relationships are those with radical transparency, particularly when working in a high performing tech team.
If the scrum masters are honest (and if the CTO has built a team that is not reliant on superstars, it will help!) then the CTO needs to reciprocate by giving them clear direction about the wider business strategy and how the roadmap fits into it. That CTO will then need to give the scrum masters required time and resources to deliver their part of the roadmap.
Take a software company selling SaaS on a monthly subscription. There is concern about customer churn.. Assume the software is nice to have but not essential. This could be addressed several ways
Superb customer service by identifying customers that could leave
Some of these solutions can be addressed by development but let’s concentrate on the third and how to convert that in practice.
Making it sticky means integrating with other systems and becoming part of a process providing significant value to a customer. Thus if a customer wants to leave they will have to change their whole process. Back to the roadmap – “integrate with X system”. To an uneducated scrum master and team, this could be just another piece of functionality, potentially perceived as pointless? But if a CTO explains the thinking behind the functionality then teams are able to make intelligent decisions. In this case, they may decide to build a framework for the functionality today, so that integration with other systems can occur more easily in the future.
The CTO needs to explain strategy and roadmap, in a way that scrum masters and team feel engaged, energised and more than just implementation robots.
The CTO has to communicate to the rest of the business on behalf of the tech team, and will need openness and honesty from the scrum masters to ensure this is done most effectively.
For the scrum master to maximise the potential of their technology career and move from scrum master to CTO, they need to understand in reverse, what the CTO needs.
CTO Academy has been Ranked #2 Best CTO Course in the World. We provide online management skills training, mentoring and career development advice for tech leaders and managers around the world. Membership starts from just $49 per month, more details available here.
“The skill set CTOs and IT Managers now require are a world away from what was needed in the past. I find the CTO Academy training modules to be highly valuable resources, providing broad-based business skills and awareness essential for success in the modern workplace.” – Eli Oshorov, Sydney
90 Things You Need To Know To Become an Effective CTO
An IT Manager (a.k.a Information Technology Manager) oversees and manages IT operations, systems and infrastructure. Additionally, they serve as a connection between technology strategies and the broader goals of the organisation. As such, they a) ensure the efficient, secure operation of IT resources and b) nurture the overarching objectives of the business. Common types of […]
As many of you will be aware, one of our key missions at CTO Academy is to see a CTO on every board. A part of that mission is to research the real value of a CTO. Now, we can all agree that it is nonsensical not to have deep technical knowledge at the board […]
In this post, we explain the relatively new Field CTO role and how it differs from a more traditional Chief Technology Officer role. We will see how a Field CTO job description determines the type of person suitable for the job. We will take a look at the job prospects and, of course, the average […]