Crash-course: Chief Technology Officer 2.0
Description
Crash Course: Chief Technology Officer is a training course where you will be able to go through the main stages of a technical specialist in the position of STO in the realities of Ukrainian outsourcing.
The knowledge gained will be useful to those lucky people who already hold the position of CTO in outsourcing, and to those who are just planning to develop their career. Based on practical experience, real cases and analysis of the speaker's facaps (which, of course, were) you will significantly save your time and resources for more effective performance of your duties. And you will be able to become an indispensable technical visionary and enabler in your own company.
Expert - Serhii Herasymov, CTO at OTP bank Ukraine, 15+ years of experience in software development
Audience
- CTO in IT outsourcing and product companies
- Technical specialists who are interested becoming technical managers
- Operational managers of Ukrainian outsourcing companies
Format:
Date and time: January 13&20, 10:00 - 16:00, (Kyiv time, GMT+3).
Duration: 2 days of ~6-7 hours (depends on practical tasks)
Platform: Zoom
Language of the event and presentation: Ukrainian
Maximum number of participants: 40 people
Program
January 13:
-
Basics
- CTO role in outsourcing and product
- Responsibilities of the CTO
- Structures and commands
- Interaction with C-level and subordinates
- Management styles (Command and control vs everything else)
- Financial management
- KPI, OKR
-
The first hundred days
- Technical analysis of the company
- Easy wins / significant wins
- Planning your time
- Tasks:
- Find gaps in current technical excellence state
- Create helicopter-view strategy for company growth
- Detect and eliminate potential risks
- Tools: Miro board
-
Tasks:
- Design and validate potential structure of technological department for such company to make sure that this structure can evolve and scale
- Tools: Lucid.com or any other tools for charts
January 20:
-
Strategy and strategizing
- Building a technical strategy
- Strategy
- Repriotization and modification of strategy
- Project thinking
- Technical enabling
-
Crisis and scaling
- Crisis technical management
- Scaling the company: tasks for service stations
- Innovation - prediction, analysis and adaptation
- Theory of solving inventive problems
-
Antipatterns and ways to overcome them
- Fire extinguishing
- Permanent memory loss
- High index of power distance
-
Colloquium:
- Development of a strategy for the implementation of the transition to a new technological stack. Given: Results of strategical session for medium-size outsourcing company in form of OKRs.
-
Tasks:
- Develop KPIs for given OKRs
- Design potential action items for OKRs and KPIs
- Develop strategy of peers involvement in execution of technical strategy
- Highlight potential risks of strategy execution
- Tools: Miro board
Expert: Serhiy Gerasimov, CTO at OTP bank Ukraine.
— 15 years in the software development industry
— Participated and led the following areas: technical sales consulting, financial planning, recruitment and resourcing, architectural design and implementation, technical audit, business digitalization, adoption of cloud strategies , mentoring and coaching
— Acted as a developer, technical lead, architect, technical director and CTO
— Worked and works as a CTO in outsourcing and product companies
— Speaker at conferences, meetings, workshops, author of courses
— Scaled development departments from 20 to 350 developers
— Promoter and implementer of the concept of technology agnosticism, personal area of interest - functional programming languages, low code / no code movement
Feedback:
The course is being held again, we are sharing real reviews from the last time (with the permission of the participants)
"A great course to review the duties and work of a service station. good recommendations of books and what to pay attention to when promoting to this position. was useful for broadening the worldview"
"Aspects of STO work covered in the course were chosen interesting and relevant. For improvement, it would be possible to add more examples from life, examples of difficult situations, and analysis of decisions that worked and did not work in different cases."
"I liked the fact that I compared for myself what the STO does in other companies and what I do."
"I liked everything!"