Peopleware or 5 Tips for PM How to Make It Possible for Developers to Work

5 Rules That Has to Be the Number One Priority for Each Project Manager

“Doesn’t matter what they say, it’s always people’s problem”— © Gerald Weinberg

Software and hardware are the most notable parts of development process and the main thing that everyone in IT companies is focused on. And this is the biggest mistake. The foundation of this triangle for each successful company should be peopleware. Or, simply put, the team and processes within the team.

Things that I talk about below are not new, but they are worth the extra time to think about them.

The biggest question now is how to make it possible for people to work?

First, let’s start with definition of peopleware. To my mind, everything should start with definition because then it’s easier to build a process and make conclusions.

Peopleware can refer to anything that has to do with the role of people in the development or use of computer software and hardware systems, including such issues as developer productivity, teamwork, group dynamics, the psychology of programming, project management, organizational factors, human interface design, and human-machine-interaction.

Development process is a very complicated and creative thing. That is why people who participate in this process need to have enough space and inspiration to make this ‘magic’ (that what we call web and mobile applications) and at the same time enough control to achieve goals.

For me I’ve highlighted 5 rules that has to be the number one priority for each PM (for juniors to learn, for seniors to remember) that are most important in keeping this delicate balance between our goals and developers’ needs.

#1. Don’t treat programmers like interchangeable, expandable, glorified typists.

Each dev in the team is not an instrument, but a person who has his or her own interests and points of view. Try not to forget about it while trying to square the circle.

#2. Testing is NOT something you do at the end of the project a week before it has to be delivered.

It’s not good for PM’s peace, QA’s results and developer’s temper.

#3. Development doesn’t always go right, sometimes architecture fails, bugs appear!

It’s like surgery, you don’t really know how long it will take until you are in it. Treat schedules with respect and focus on prioritization and iteration. Only in this way when deadline is coming, you will have all the most important features done.

#4. Try to speak the language of developers.

It’s absolutely not necessary to start coding JavaScript or PHP. But it’s possible for anyone to understand how the process goes and what is the difference between API and SDK (this was a little challenge for me :) )

#5. Developers appreciate logic.

And the main logic from your side should be when you set tasks and rules for your team. It’s very important to play by the same rules you’ve set. No exceptions.

At this point the quote from the beginning becomes the endpoint of this article: “… it’s always people’s problem”.

The problem of mine — always remember and apply these (and lots of other) tips in organisation of working process.

A problem of yours — to read this article and to investigate deeper the problem of peopleware in development process.

A problem of devs — be gentle to PMs, clients and code.

A problem of everyone — to communicate clearly.

And this all is just a little part of big system that we call Peopleware in development process.

If you liked this, show your support by clapping us to share with other people on Medium.

Follow us on Facebook, Instagram, LinkedIn, Behance, Medium and visit our corporate blog for more news and articles on smart solutions.

Any questions? Feel free to contact us!