My experience in a self-organizing team

Hello! I want to tell you about my experience in a self-organizing team. For a year and a half, it had from 3 to 5 developers, I did not hire them, but I built all the processes and development from scratch. I'll tell you what a self-organizing team is, what benefits it brings to the company, the team, and its members.





Self-organizing team

The team has no division into specializations, roles, and anyone other than developers. There are no separate people for client (front-end), server (back-end), infrastructure, testing, project management. Each developer participates in every iteration of the software development cycle: getting a task, clarifying requirements, writing code, testing, deploying, monitoring, supporting.





The team itself chooses technologies, researches them (about relevance, for example), implementation and support - Go or Python, Jenkins or Github Actions, whether Kubernetes is needed.





Backlog preparation, prioritization of tasks and subtasks, distribution of tasks among team members, meetings, retrospectives are the responsibility of the team.





: , , .





, , . , .





. , , . , , , .





1-to-1 , . , - - โ€” , , .





โ€” , .





, , (, ) .





Trunk-based, , -master (develop) GitFlow Workflow. master, , , , deploy preview (feature branch, review app) โ€” . โ€” master โ€” .





:





  • , , ,





  • ,





  • , ยซยป (, , ).





:





  • , , ,





  • , , , , ,





  • , .





, - , - .





, , . , . , . , . , win-win ( ), , .





- โ€” .





:





  • ,





  • ,





  • I like it when each member of the team has the same responsibility, it unites and brings results.





Thank you for your attention, I will update the article if I forgot to mention something. If you have questions or want to discuss something, Iโ€™m waiting in the comments or private messages.








All Articles