| I respectfully disagree. Manager's job here would be to: - work with devs to make sure whatever gets into the work pipeline is well understood - everybody agrees on the planned work scope - prevent anyone from adding "just this tiny thing" into planned scope|
- visualise all of this tough, tough dev work, especially the ad-hoc work (putting out fires, for example) - keeping both management and devs accountable - and more! Also I disagree with the bridge metaphor; while true, you can't use the bridge when it's 50% done, you should ideally be able to to use 5% of the planned feature. If you can't, then maybe it was planned out badly and shouldn't go into planning in the first place? If there's a person that's "working hard" in a team and a person that's "hardly working", then the team has a big issue and should do everything to fix that. However, This takes a lots of guts on part of (both!) the manager and developers and always has an emotional toll. |