DEV Community

Discussion on: Day in the life of a Scrum team

Collapse
 
danjfletcher profile image
Dan Fletcher

Hey David, thanks for the thoughtful comment!

This is all hypothetical of course 😊

  1. The design meeting could have been any meeting.
  2. Pulling new work into "in progress" doesn't have to equate to being "not in the current sprint".
  3. Code review can still raise issues even if everyone thought they agreed to a direction before work began. People misunderstand or misinterpret people all the time. People miss edge cases. They underestimate complexity. Ultimately if the code wasn't built in collaboration, there will be disagreements with the end result from time to time.
  4. This doesn't even have to be a SCRUM team, they could have been working with KanBan or any other play on "agile" that involves releasing continuously in small increments.

There are so many things this team could try to improve on but what I think is interesting is that a lot of the issues really stem from this idea that work needs to be broken up to be worked on in parallel by multiple individuals as apposed to a group.

I still have to finish the follow up post to this (in the middle of getting ready for a move right now so I'm pretty busy 😅) but my idea is to try and communicate the benefits of mob programming.

Collapse
 
uclusion profile image
David Israel

That fits in well with the meetup I am trying to organize on team structure meetup.com/san-jose-collaboration-... If you have time pop in and we can discuss your idea.