10:00: programming
11:00: quick meeting
12:00: #### getting back into the zone
13:00: ####
14:00: ####
I would react the same way if my scrum meeting was 1 hour long!
About a year ago, I was working with an east coast customer while working remote on the west coast. Scrum was at 7am my time, with the customer on the call.
Probably should have been a stressful situation as they were a tough customer, our largest account in terms of ARR and PS dollars, and they loved to tell us which Data Enginners or PMs they didn’t like, who would promptly get reassigned. But honestly, having that call so early was the least stressful thing ever.
I would roll out of bed at 6:30a and make a cup of coffee, just to get my computer tuned on and ready to join the meeting by about 6:57.
Worked out great, cuz I never spent time thinking about scrum beforehand, and frankly always felt a bit energized afterwards cuz it was now time to start my work day.
Ended up working out well I guess, cuz the customer kept me on the team the entire length of the engagement.
Why is your scrum 1 hour long?
Because that’s how it often goes. I find there are two types of scrums in practice. First is when it goes fast, and everybody just says they’re working. There’s no time to give any detail or context so the status update is largely meaningless. Second is when people start giving details about what they’re working on, and that quickly explodes to an hour long meeting.
Participants need to find the right balance of information. I noticed it is productive when developers give just enough information for other to understand but not too much to confuse them and loose time. This is not easy to achieve…
Indeed it’s not, I also find developers tend to be really bad at this task in particular.
Tf is scrum
