What kind of people make up an effective web development team?

Question

Startups

Please name the positions and the approximate number of people required to create an effective and high-quality web development team. PS I'm not going to open the Studio, the question is just for fun and because of interest

Answer 1

UX
Every project starts with a design. For cool projects, when the designer is not able to move in, the help of a business analyst may be required. Alas, there are very few such people in Russia, so this is a rarity. However, projects of this kind are also rare.
Often in companies this function is performed by:
This is the name in Russia for those who can embody an idea in pictures. Even if the designer is not engaged in design, he must study this area.
However, if there is no designer, and the designer is not yet able to do it himself, then all hope for:
The person who will implement complex interactions designed by the designer (or the designer, or himself). Without knowledge of JS and a number of libraries, no one is interested. It's just that HTML and CSS are rarely required by anyone, only if you work in the wings at the frontend.
If the front-end cannot design, then there is already a very weak hope that the Back-end can
In this variant, programming solutions are predominantly obtained. The work of the backend can be not only difficult to evaluate, but very difficult, unlike the frontend, the work of which ordinary people can evaluate (although the criteria for ordinary people are very strange and unexpected).
Well, it’s absolutely incredible that the design will be able to carry out:
Its functions can vary greatly, from organizing a team, to fighting off clients (for example, when everything went down). Even if he doesn’t know how to design (and who in their right mind expects this from him?), he is needed in a startup. Practice shows that technical specialists are often addicted to trees, and the forest follows the forest.
And here he is - a man with a capital B:
Making a project is only the beginning. Then you need to bring customers to it, which means that SEO requirements should be taken into account by everyone from the very beginning.
Server administrators (otherwise they come up with anything, but it causes that same crash)
Writers (content becomes very important)
Testers (so that jambs do not surface after the release of the product)
Content managers (who will shovel tons of text and graphics)
Perhaps technical designers with the prospect of growth On
and on, down to the cute fairies in the bar who always pour hot coffee

Answer 2

a minimum
of design, a hanger and a back-end programmer,
then if fat, then menager, UI, QA and other parasites are added)

Answer 3

Everything is relative here. What needs to be developed? Facebook? Then two programmers will not be enough for you. Maybe a designer-implementer-programmer all rolled into one, then in this situation you will get a gvono project. The second option: a designer and a coder-programmer is an acceptable option, but still it is better to divide the second one into a coder and a programmer. In my opinion, the most effective bundle will be:
Designer (who understands the principles of layout)
Layout designer (having basic knowledge of JS / jQuery)
2 programmers (if it's a web, then PHP / Ruby / JS)
Project manager or leader (glue person who makes you move each member of the team, otherwise, one by one, the above-mentioned individuals in the team do not work well)

Answer 4

More important criteria, these are not those. skills, but a set of human qualities.
A couple of dis .... in / inadequate can not only ruin the work, but also demoralize the team in the long run. However, they may well be good specialists.

Answer 5

Jeff Bezos Two Pizza Rule: No team should be larger than can be fed with two large pizzas
www.businessinsider.com/jeff-bezos-two-pizza-rule-...

Answer 6

If minimally effective:
Manager-analyst - researches, collects requirements, writes docks, draws up information in a form that is understandable to everyone, designs interfaces, plans work within the budget and deadlines, organizes work, deals with communications, controls the progress of work, looks for replacements, maintains communications with everyone outside the team.
Developer-teamlead-sysadmin - defines the framework, technologies, configures a server, deploys a project, designs a database, writes code, checks the code of others, typesets
more further,
just a developer - enters a ready-made, deployed project. reads docks, runs everything on locale, listens to morals from the first two roles, receives tasks for a while, saws, uploads, fixes, typesets
front-end developer - typesets the design, gives it to coders, pulls the project locally, fixes styles and everything that goes on the front, connects plugins, customizes them, changes configs, sets up a seo
tester - reads the docks, checks the functionality for performance, looks for bugs, checks the project for compliance with the requirements in the docks, confirms that all the functionality is working and the project can be released by the
analyst - he takes all technical documents from the manager, designing the interface, writing new docks, smoking guests, drawing diagrams for complex requirements, thinking about how to wind up in acc. to the business logic and requirements from the customer, the
CEO bursts into the project, makes a fuss, shouts that everything is lost,
such a modest family leaves.
the designer is trite ordered. it is not profitable to keep a drawing around the neck in a team where development is in full swing, it is better to buy an intern, another tester to fix bugs, click functionality