Most of them don't read the code! And like not all PMs are engineers and most don't need to be, but even nontech PMs should be able to recite the architecture IMO. At GS many simply couldn't, and it made explaining project sizing very difficult without resorting to hand waving
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
The PM turns to the technical lead and says, I need a rundown of where we are behind and why, i can provide the business impact
This is a good model I think, and my point is that between the eng lead and product lead they should each share a basic level of knowledge about each other's domain of expertise just to make communication easier/more specific. That's all I meant about avoiding hand waving
-
-
The one aspect of my old gig I liked is that neither product manager or the tech lead were Project Manager so resource decisions were not made by the people making feature and technical decisions. PjM would ask priorities (which I would convert to revenue oppy)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.