Books for timblides and project managers
What properties should a good timblid have? He undoubtedly must be a techie, have a diverse experience, be able to establish a dialogue within the team and with the boss, lead discussions and make decisions, take responsibility, understand business processes, think like a customer and a business owner. Well, be a bit of a psychologist.
In domestic IT, I often observe the following picture: the best (?) Developer from the team (aka 23-year-old senior) often became the team leader. And in order to become a project manager (project manager), sometimes it’s enough just to know English and “power point” at the user level. This is the reality of domestic outsourcing and we need to somehow live with it.
The result is often something like this:
To become a good team leader, you need to shovel a very large number of business cases, to go into the shoes of not only the developer, but also the product owner and business owner. But how can this be done by an ordinary developer? This is where specialized literature comes to the rescue. It is clear that she will not add real experience, but the initial background can give.
')
I have never seen books on project management or personnel on the desks of developers. But, in my opinion, every middle level specialist should read this kind of literature. And yes, the initiative at this stage should come more from the company (or the current team leader), i.e. the developer is still unlikely to seriously think about the future career of a manager.
Below I gave a list of books that, in my opinion, every developer who wants to become a good manager in the foreseeable future should read.
In addition to technical literature, it is advisable to read something on psychology (philosophy), HR, finance and risk, as well as biographies of successful people. I do not in any way claim to be 100% complete of this list, so I’ll ask in the comments to share my recommendations and feedback.
Thanks for attention!
PS As an experiment, I made a small questionnaire on the topic “What books did you read?” . Please spend 30 seconds to fill out, and I, in turn, after a while lay out the results of the survey.
In domestic IT, I often observe the following picture: the best (?) Developer from the team (aka 23-year-old senior) often became the team leader. And in order to become a project manager (project manager), sometimes it’s enough just to know English and “power point” at the user level. This is the reality of domestic outsourcing and we need to somehow live with it.
The result is often something like this:
Because on ten seniors, according to statistics, nine are stupid.
To become a good team leader, you need to shovel a very large number of business cases, to go into the shoes of not only the developer, but also the product owner and business owner. But how can this be done by an ordinary developer? This is where specialized literature comes to the rescue. It is clear that she will not add real experience, but the initial background can give.
')
I have never seen books on project management or personnel on the desks of developers. But, in my opinion, every middle level specialist should read this kind of literature. And yes, the initiative at this stage should come more from the company (or the current team leader), i.e. the developer is still unlikely to seriously think about the future career of a manager.
Below I gave a list of books that, in my opinion, every developer who wants to become a good manager in the foreseeable future should read.
- Tom DeMarco. Deadline. A novel about project management.
- Tom DeMarco and Timothy Lister. Human factor. Successful projects and teams.
- Tom DeMarco, Timothy Lister. Bald with adrenaline and zombie patterns. Patterns of behavior of project teams.
- Tom DeMarco, Timothy Lister. Waltzing with the Bears: risk management in software development projects.
- Patrick Lensioni. Five vices of the team. Parables about leadership.
- Patrick Lensioni. Five temptations of the leader: parables about leadership.
- Patrick Lensioni. Three signs of dull work. A story with meaning for managers (and their subordinates).
- Patrick Lensioni. Death from meetings.
- Jason Fried, David Heinemeyer Hensson. Rework. Business without prejudice.
- Frederick Brooks. Mythical man-month, or How software systems are created.
- Jeffrey Young and William Simon. iCona. Steve Jobs.
- Carmine Gallo. iPresentation. Lessons of conviction from Apple leader Steve Jobs.
- Joel Spolsky. Joel is about programming.
In addition to technical literature, it is advisable to read something on psychology (philosophy), HR, finance and risk, as well as biographies of successful people. I do not in any way claim to be 100% complete of this list, so I’ll ask in the comments to share my recommendations and feedback.
Thanks for attention!
PS As an experiment, I made a small questionnaire on the topic “What books did you read?” . Please spend 30 seconds to fill out, and I, in turn, after a while lay out the results of the survey.
Source: https://habr.com/ru/post/163113/
All Articles