DEV Community

Discussion on: Delivering in time is a matter of observing the details

Collapse
ivancrneto profile image
Ivan Neto Author • Edited on

Thanks for your input. Avoiding too much context switching is also really important. I think each team has its own characteristics and can find its synergy and then a developer will strike a good balance between working on her/his task and switching to helping other tasks to move.

If we make all developers able to observe the situations where the team is wasting time and eliminate them, that's a very good step forward, but indeed trying to reach a "100% CPU usage" will hurt.

Collapse
craser profile image
Chris Raser

Yep. The team will naturally find an equilibrium that works for them. But I've seen through hard experience that when a team is under pressure to meet certain metrics, other metrics will be sacrificed, even if that sacrifice is self-defeating in the long-term. Team values and goals need to be explicitly stated, and repeated, or they get lost in the day-to-day work of trying to pay the bills.

There's a really good discussion of Agile and thinking about velocity in Ep. 15 of Tech Done Right.