I
I
idreamhuman2022-01-10 14:06:12
Project management
idreamhuman, 2022-01-10 14:06:12

Command for creating a WEB-platform. Writing a diploma, from the academic side. What should be the organizational structure and composition of the project?

I am writing a diploma (4th course) on the introduction of the agile kanban methodology in the development of an IT project.

The task is to create a book site that sells books in Moscow through online delivery. Like a Labyrinth - https://www.labirint.ru

What should be the composition of the project team? I found the following on the Internet:

1. Teamlead - 1 person
2. Project manager - 1 person
3. Front-end developers - how many should there be in the project?
4. Backend developers - how many should there be in a project?
5. UI/UX designers - how many should there be in a project?
6. QA engineers (testers) - how many should there be in the project?
7. Business analyst - how many of them should be in the project?
8. Marketer - how many of them should be in the project?

Who could I ignore?

Answer the question

In order to leave comments, you need to log in

1 answer(s)
V
Vasily Bannikov, 2022-01-10
@idreamhuman


3. Front-end developers - how many should there be in a project?
4. Backend developers - how many should there be in a project?
5. UI/UX designers - how many should there be in a project?
6. QA engineers (testers) - how many should there be in the project?
7. Business analyst - how many of them should be in the project?
8. Marketer - how many of them should be in the project?

As much as needs. That is, if 1 person cannot cope with the number of tasks, and at the same time they can be parallelized, you can try adding another one and see.
From 0 to infinity, depending on the tasks.
For example, if the product is not supposed to be sold (in principle, to make a profit from it) - a marketer is not needed.
BA is not needed if the PM already sets tasks normally, and there is no need for any deep analytics (or developers can handle it)
QA is not needed if the project is so small that developers can handle testing it.
UI/UX is not needed if there is no design.
The front/back split is not necessary if the full stack can handle it.
Teamlead is not needed if there is no team (the team consists of one person)
Who could I ignore?

Head of pencil erasers. No project can do without it.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question