| ▲ | whstl 3 hours ago | |||||||
This was already a reality for a years. In several companies I have seen product managers joining teams and failing to even have minor requirement ready for months during “onboarding” of the PM. And then code being ready but taking months to release because DevOps is busy or QA can’t find time. The pace of release of software has been disconnected from the coding part for the longest time, and we have been quiet about it. | ||||||||
| ▲ | tedd4u 2 hours ago | parent [-] | |||||||
The solution I've seen work is have engineers and designers that can take much of the detailed spec writing on, and have the PMs spend time with users/prospective users, partners, etc, understanding the market and users better. When you pull PMs in to all the details, often they turn into project managers, shuffling bug tickets around etc, taking time away from owning the user and the problem and shifting them too much to the solution side. Have a lead engineer own much / most of that. Every org / product is different of course. | ||||||||
| ||||||||