I'd love clarity on point 2 - [All project status updates must be channeled through the Engineering Lead. Product must never try to debrief individual engineers. Instead, the Product Lead and the Engineering Lead should meet regularly: Twice a week is usually about right. Use a matrix like the table above as a framework for discussing progress.] // Does this assume a well defined product or project? Early in projects, I feel like there is daily learning and you want to identify those issues as early as possible. How do you prevent individuals from being bottlenecks of communication? Isn't the purpose of good documentation and well written stories and good Jira or any other tasks platform to provide transparency? I think there is a middle ground between restricting communication in this fashion and being annoying as a PM on the status of tickets - no one likes that. This may be better suited to discussion over beers / whiskey 😁
I'd love clarity on point 2 - [All project status updates must be channeled through the Engineering Lead. Product must never try to debrief individual engineers. Instead, the Product Lead and the Engineering Lead should meet regularly: Twice a week is usually about right. Use a matrix like the table above as a framework for discussing progress.] // Does this assume a well defined product or project? Early in projects, I feel like there is daily learning and you want to identify those issues as early as possible. How do you prevent individuals from being bottlenecks of communication? Isn't the purpose of good documentation and well written stories and good Jira or any other tasks platform to provide transparency? I think there is a middle ground between restricting communication in this fashion and being annoying as a PM on the status of tickets - no one likes that. This may be better suited to discussion over beers / whiskey 😁