Key Functions As a Tech Leader

Do you get a headache whenever you see unfamiliar roles or titles like Principal, Tech Leader or Engineer Manager in your project?

I had the same issue when I started my journey with the Tech Leader role, but I’m wondering if you have the same issue now.

Does your organization have a Tech Leader role? Is there a job description for this role? What was your experience with this role?

👍НравитсяПонравилось0
В избранноеВ избранном0
LinkedIn
Допустимые теги: blockquote, a, pre, code, ul, ol, li, b, i, del.
Ctrl + Enter
Допустимые теги: blockquote, a, pre, code, ul, ol, li, b, i, del.
Ctrl + Enter
I had the same issue when I started my journey with the Tech Leader role

It’s a good role to start. June role is made for slabakov only :)

Tech Leader = Technical Leader is useful and straight forward role (if not messed with other role responsibilities). Basically is what Lead Developer do on the project. Setup development process, choose technologies, build architecture, participate in requirement management, do task breakdown, estimation, coordinate other developers, do code review, apply best practices, etc.
The most important is that this role shall remain pure technical. Technical specialists are not great in communication with the client, in people management, in business analysis, in corporate bureaucracy. So Project Manager is still needed. The good point is: having strong Tech Leader the Project Manager can have no technical background at all. This is separation of concerns principle in action!

The whole product is always a concern of product owner. There is one very stupid problem I have seen in IT projects — the product owner is missing! Customers ready to pay money — but they do not want to play product owner role. For me it looks exactly like “shut up and take my money” picture. What next? BA or PM or event scrum master are trying to play PO role. It is as stupid as buying a factory full of workers and letting them decide what to produce! Nobody knows what the goal and what the expected result — everybody just doing something they think is important. The actual result is usually the agile process of endless requirements changes and modifications — without any finished product. You may have seen a lot of such mobile applications: raw and ugly, but with huge ambitions to became “{popular name} killer”.

I get a headache whenever in a company with 5 members i see titles like president or vice president of engineering, so on.

Подписаться на комментарии