Answer the question
In order to leave comments, you need to log in
What to do if the project manager goes on about the client?
I am currently working in a small web studio in Kyiv. I am engaged in layout and integration into CMS wordpress. As in all web studios, there is a lot of work, as always there are not enough hands, projects are on fire, in general, a standard situation. But that's half the trouble, it's like that everywhere.
The problem is different, the problem is that we have all project managers (of which there are 1 per developer, which is generally nonsense.), Always, if I may say so, go on about clients (it can be rude to say - they lick one place ). Part of the problem is in the technical task, which is always molded into a quick hand from standard phrases, without specifics. Because of what there is a constant stream of "Wishlists" from customers (of course, everything is done for THANK YOU) and the project is delayed for months. You could put up with it, do your job and that's all ... But because of this, salary is very often delayed, sometimes the boss may not pay extra at all and say that you didn’t close the project where the money came from, and stuff like that.
Question:
How to convey to project managers and management that the path that the web studio is taking is clearly wrong and not only developers who sometimes work for 10 hours for $ 300 sometimes suffer from this, but the whole studio as a whole?
Answer the question
In order to leave comments, you need to log in
Don't bother, it's completely pointless. Nobody will understand you, because they have a different outlook.
Not satisfied - change your job or open your own web studio.
I will add an interesting book , which you must read, if you understand it, then you yourself will answer the question correctly. Read in a couple of evenings and very interesting
Prior to the start of the project, write down all non-obvious points and demand that this be agreed with the client.
Well, if it comes to salary delays - master something more decent than wordpress and change jobs.
On the one hand, there is a wild staff shortage in IT, on the other hand, there are no interesting projects / customers on wordpress.
What do you want? It's not the developers who give money, but the customers! If you want money, then you need to think about the client and understand well the saying "Any whim for your money." BUT. At the same time, it is necessary to clearly convey to the manager about the timing of implementation with a CLEAR explanation of why! At the same time, make sure that he is very well aware of these risks and understands them as well as the development team
look for a new job.
the rest is meaningless. you will not change anything, and why do you need it? judging by your story, this firm is not a "dream company" in which you would like to work for years - what do you care about their crooked work processes? nah.
just look for a new job, and immediately.
PS underpaying is savagery. enough tolerating this
The job of a project manager is two things:
1. Licking the customer's ass
2. Writing quality specifications
It looks like your project managers only manage the first part of their job.
If you can’t change anything, you can either reconcile (some feel better in a mess), or change jobs and live in peace
The general rule here is: do everything that you can do yourself to solve the problem, and if this is not enough, and the problem remains critical, then you need to change your place of work. The latter is an extreme and highly undesirable activity that should be avoided. It always raises questions about the professionalism of someone who changes jobs. Therefore, you need to focus on the first.
Here we must immediately understand that changes in requirements, especially in web projects, are an inevitable and even desirable thing. Desirable, because changes in requirements can and should be profitable for the studio. Inevitable, because everything in the world is changing very rapidly, and www is a place where changes occur more often and on a larger scale than anywhere else. Demanding the stability of requirements for web projects is very wrong, if not naive.
Hence the number one question: how does the architecture of your solutions take into account the nature of the requirements for the projects that the studio is engaged in? Perhaps the technical solutions are too rigid, which turns into a headache for developers. An article developing the topic: "I'm a developer, not a lawyer" . And my thoughts: "Make sure you do your job before... .
Do not see each other on the occasion of the managers, openly show your attitude, perhaps directly say that you won’t do something, that you have enough work and you don’t care about any shit. You may just have to leave in the end, or you may not, in any case, an honest approach is the best.
Perhaps hackneyed, but
1) In normal firms, the deadlines for completing the task are set by the programmer, and not by the project manager. (in our country, for example, the project manager even adds a little later to this period when he negotiates it with the client) Thus, the programmer is responsible for his words, and not for the words of the manager, and there is an additional incentive for the programmer, since most people value their in a word ;-)
2) Slavery has been abolished for more than 100 years, but you can always change your job. Especially now, programmers have no problem finding a new job.
3) Also at one time there was a problem with deadlines imposed from above, etc. Personally, the book "The Pragmatic Programmer" helped me to put everything back on its feet. I highly recommend reading :)
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question