![\"Image](\"https:\/\/cdn.pixabay.com\/photo\/2018\/08\/11\/19\/07\/cat-3599255_960_720.jpg\")
<\/figure><\/div>\n\n\n\nObservation 1 \u2013 meetings get longer<\/strong><\/p>\n\n\n\n Let\u2019s start with a daily scrum. It should last no longer than 15 minutes. As long as the team is just a few developers big – it\u2019s easy. But when we have 15 devs we can give everyone only one minute to speak. It\u2019s pretty impossible. Either we will destroy the idea of the daily meeting \u2013 where the team members can properly describe what they worked on and ask for help (by forcing them to speak extremely short) either we\u2019ll extend the time. In the team of 14 developers, I\u2019ve seen daily scrum to grow up to 25 minutes.<\/p>\n\n\n\n Exactly the same is the situation with every other meeting. But in case of refinements or sprint review, it\u2019s getting even worse because these meetings are naturally longer than daily scrum.<\/p>\n\n\n\n Observation 2 – meetings become full of things you don\u2019t need to hear<\/strong><\/p>\n\n\n\n As the team grows, the scope of work grows. Naturally – as in any big enough group – the subgroups form up. It can be any kind of division \u2013 front-end and back-end devs; people who work on feature A, and another group working on feature B; Java, and JavaScript programmers. When they work on the everyday tasks they almost don\u2019t talk to each other unless they need to discuss some API or contract which is necessary for the parts of the system to communicate. But if the scrum team doesn\u2019t split they\u2019re forced to participate in the meetings together.<\/p>\n\n\n\n Then you find yourself in a meeting where half of the time is spent on discussing the things you don’t need to hear. You\u2019re let’s say a JavaScript developer and last 30 minutes of a meeting was a discussion about back-end, or you\u2019re developing database structure while implementation of the UI of the system is estimated.<\/p>\n\n\n\n Observation 3 \u2013 productivity plummets<\/strong><\/p>\n\n\n\n You want to code. That’s why you became a software engineer. You like to focus, you love to create lines of instructions. This is also why, all in all, you\u2019re getting paid. You automate processes, therefore, people don\u2019t need to be employed to make them manually and the company is more effective. The money saved on automation goes to your pocket. Everybody is happy.<\/p>\n\n\n\n Unless you can\u2019t code.<\/p>\n\n\n\n When the length of scrum meetings get longer it consumes your coding time. When the meetings get boring it consumes your mental energy. You become less productive. Not cool.<\/p>\n\n\n\n