Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

there should be only 3 regular meetings in an agile engineering team - weekly iteration planning (1-2 hours max) - daily standup (15 mins max) - weekly demo & retro (1-2 hours max)

literally everything else is work off the kanban board or backlog.

in my teams everyone was told to decline all meetings unless it explicitly led to the completion of a weekly planned story/task. this way all meetings for the team have a clear agenda and end in mind.

for mandatory external meetings & running interference with external parties, there are ways to insulate the majority of the team from that.



Is that three kinds of regular meetings? Because I count 8 meetings (and four kinds, as I don't think I've ever had demo and retro combined due to different groups of people being in both).


Sure, I was being loose with my terminology, you are right to correct this.

the point was in a 40 hour work week, it's reasonable for 15% of it to spent in coordination meetings, while 85% is directly related to progress.

Usually the retro is after the demo when other folks leave the room / drop from the zoom :-)


Not correcting, just clarifying for myself. I sure wish I had such a controlled environment with only 15% of time in coordination and where standup actually was 15 mins and not a segue into the everything meeting.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: