Hey Elisabeth! Excellent video. You captured my attention and held it throughout. I've never considered building simulations with software to investigate outcomes under different contexts. Very cool! I particularly love the conclusion/definition of a team at the end
This is great Elisabeth, I think the point is well shown. The one thing I don't see is the complexity of development level as well. Juniors vs Seniors and all the mentoring that can happen. I completely agree with the Generalists approach but mentoring and teaching need to be incorporated as well and have no idea how this would be incorporated.
So great! It stopped just short of the scenario I thought it was headed for: The T-shaped folks, by virtue of sometimes working on stuff they know less about, slowly accrete more expertise in those weak areas over time. In other words the simulation doesn't account for learning and skills transfer. Once that's in place then I'd like to see a simulation of what happens when you keep changing the makeup of the team and losing people who have special knowledge specific to that team/product.
Very interesting simulation and visualisation, Liz. Thank you for sharing this. I was wondering what happens if bugs show up during the release/iteration? How would it impact the teams? The reason I want to focus on bugs as compared to new work, is generally with bugs, you might want the same developer to pick up the bug who worked on the feature that introduced the bug.
Hey Elisabeth! Excellent video. You captured my attention and held it throughout. I've never considered building simulations with software to investigate outcomes under different contexts. Very cool! I particularly love the conclusion/definition of a team at the end
This is great Elisabeth, I think the point is well shown. The one thing I don't see is the complexity of development level as well. Juniors vs Seniors and all the mentoring that can happen. I completely agree with the Generalists approach but mentoring and teaching need to be incorporated as well and have no idea how this would be incorporated.
Dear Élisabeth, your présentation reminds me of the book from Eliahu Goldratt on Critical Chain.
Good présentation, thank you
What a great video and explanation! Good job! ❤
So great!
It stopped just short of the scenario I thought it was headed for: The T-shaped folks, by virtue of sometimes working on stuff they know less about, slowly accrete more expertise in those weak areas over time. In other words the simulation doesn't account for learning and skills transfer.
Once that's in place then I'd like to see a simulation of what happens when you keep changing the makeup of the team and losing people who have special knowledge specific to that team/product.
Love this so much!
This is fantastic. Great way to visualize teams.
Very interesting simulation and visualisation, Liz. Thank you for sharing this.
I was wondering what happens if bugs show up during the release/iteration? How would it impact the teams? The reason I want to focus on bugs as compared to new work, is generally with bugs, you might want the same developer to pick up the bug who worked on the feature that introduced the bug.