3 ms·
When I made the switch from developer to product/program/project management, the biggest mistake I made was still trying to write code. It's one thing to keep
by munchbunny 10y ago
When I made the switch from developer to product/program/project management, the biggest mistake I made was still trying to write code.
It's one thing to keep your coding skills sharp, but there is so much to do as a PM other than writing code that will more than make up for the 40 hours a week you gave up by switching jobs. In theory your role as a PM at your company exists because the developers and designers are no longer able to sustain the managerial/organizational overhead coming from team and scope growth.
This really depends on the needs of the organization, but my rule of thumb is to only write code if (1) it's to get data you need or (2) you're bored and can't find anything to do.
- civilian 10y agoAnd if you're bored and can't find anything to do, please don't take the fun research task that I'm hoping to get to once I finish the important/boring tickets in my sprint. :(
- alistairSH 10y agoThat's one of the hardest thing I do - leaving "fun and interesting, but not critical" stuff in the backlog for my developers. As mentioned up the comments, I try to pick up some of the small and boring tasks. Or, as my test engineer is usually overbooked, I pick up test tasks.