Who is Who in Your IT Project Team: a Client-Friendly Manual

Regardless of who you are - customer, developer, QA or PM - it’s good to know what you can expect from those involved in the same project.
Who is responsible for what? Should you contact the PM or maybe some other members of the team? If you are a developer, can you ask the clients some questions?
The average customer usually has to stop and think about the difference between front-end and back-end developers. Is OS X different from iOS? What is going on and who is on top of it? Fear not - this article should give you an insight into the basics of who is who in a given project.
Let's start with the core members of a typical IT project team. There needs to be a client, of course, the developers, QAs, UX/UI designers and, last but not least, the Project Manager.
Who is the Project Manager? Sometimes he or she may seem like an outsider, somehow distanced from the rest of the team. You could not be further from the truth. S/he is the glue that cements the whole project, helping developers, QAs and clients to achieve their goals in the fastest and most effective way.
UX/UI
The UX/UI people step in during the first part of the project. Basically, they bring your vision to your eyes by designing the app or website and make things work along with developers, using their UX (user experience) and UI (user interface) magic. They also come up with hacks that help to save a lot of time.
The team of developers
This might sound glaringly obviously but they are responsible for writing the code. However, that’s really only the tip of the iceberg. They also review the code, help to specify the requirements and provide input and advice on the project from their perspective.
They will also be able to throw light on any obstacles that may occur during the project. You need to bear in mind that there are 2 types of devs - back-end developers and front-end developers. The former is responsible for the “engine” of the application. Front-end devs make sure that the visible components of the app look good, meaning that all the parts are in the right place, the right size and tailored for the client’s requirements.
Quality Assurance Specialists
Here we move on to the tricky part of the IT project team. In spite of appearances, they are there to help everyone. They will tirelessly look for bugs and then help to prioritize them. They will also schedule and coordinate bug bash meetings during which the whole team will test the application. They will also be the ones to give “the green light” for application deployments.
Project Manager
Project Managers are the communication bridge in the project. It is their role to mediate between team members and clients and by doing so they try their level best to make sure everyone is on the same page. They also have the sometimes unenviable job of keeping the team motivated at all times and delegating tasks effectively.
The Project Manager is not the client’s enemy, but rather his/her biggest ally. The PM will support both the team and the client by supervising the scope of work in the project, managing risks and other issues. The PM will also be the first one to step in and provide assistance whenever a problem or new priorities emerge.
The Client
Another key team member. The client is the one with the vision and, let’s be honest, the gold! We are happy to have you on board and will do all we can to help you achieve your goals.
How can we make this happen? Communication is king - the more we stay in touch, the better for the project. The Project Manager and the team will have a million questions to ask about the application. They will also provide the client with weekly reports to sum up the progress so far. There may also be issues that can be answered quickly and work doesn’t have to grind to a halt. Sometimes just one meeting per week is not enough. So, dear client, please don’t be a stranger.
Otherwise, if you have new priorities or tasks, please try to be as precise as possible in your description. Our team will, of course, guide you along the right path, but the better defined the tasks, the faster the work.
So there you have it - the IT Project Team in a nutshell. Any more questions? Once we start working together, we will have the chance to answer all of them while we help you to transform your idea into a stunning application.
Now you know who is who, but you probably would also like to know what exactly happens before you start a project. This stress-free project roadmap will answer all your questions!