[1/3] The Engineering Executive's Primer (Category Management)

Continue. zero-post With a review of the book, I would like to say that Will did not stint on content and generated whole stories. 24 Chapter, introduction, conclusion and five additional materials. To disassemble all this good at once will not work, so there will be many posts, but we will start with the first:)

0) Preface In the introduction, the author describes how he came up with the idea of this book after previous books.Staff EngineerandAn Elegant Puzzle. Systems of Engineering Management" The first is a great source of career information for engineers who have outgrown the senior level and set out to conquer new seas. I told you about her before. 1 and 2. The second book is good for engineering managers. told There were two episodes of the Code of Leadership podcast with Eugene Sergueev, senior engineering manager at Flo Health. 1 and 2 1) Getting the Job The author begins the book with the idea of how to get a job as an engineering executive. To begin with, you should answer the question, but is it really worth it to fit in? Then there are the questions, and where to do it: inside the current company or external. Next, the author discusses the chaotic process of hiring tops, which differs from company to company, and then there is a discussion of the terms. Well, it all ends with how to think about whether to accept offers or not. Overall, the chapter is a really good description of this complex process and provides a structure and approach for informed decision-making. 2) Your First 90 Days The author says that in the first 90 You will have to work hard to figure out how the business works and where the money comes from, what determines the culture of the company, how to establish healthy relationships with stakeholders and their peers, how well the engineering team functions in terms of delivery, how high the technical quality of software and tools to support the development processes, what is the morality of the engineering team and how stable the team itself is for the chosen pace of development of the team. Next, it’s important to limit the amount of early changes you make in the first place. 90 days. In addition, it is important to build trust with colleagues and take care of their support. In general, it is cool to understand how the company works and how technology looks like. (including code and depot, duty, incident handling, ...) 3) Writing Your Engineering Strategy This chapter. handler It was just an article on the author’s blog. The article was excellent and it didn't get any worse after it became a book chapter:) 4) How to Plan The author describes the standard approach to planning in companies: Annual financial planning (including a headcount plan) Semi-annual or quarterly plans, such as OKRs for teams. These plans target business results or a list of projects to do. Intra-command work management processes (Kanban, Scrum, etc)to meet quarterly/semi-annual plans Separately, the author says that there may also be periodic revueLike every month. These reviews are aimed at tracking progress toward meeting the company’s goals.

Continuation at the following posts: 2

#Engineering #Management #Leadership #Processes #SystemDesign #SystemThinking #SystemEngineering