3 ms·
It's the job of the PM to decide what to build. It's your job how to build it, which includes taking time for an appropriate level of quality. It's easiest to
by Lutger 4y ago
It's the job of the PM to decide what to build. It's your job how to build it, which includes taking time for an appropriate level of quality.
It's easiest to improve the codebase where and when you alter it for feature work. This is also a good control for yourself to stick to relevant refactorings. This should be your professional autonomy.
The remaining like, 5 to 10 percent of the time that you need 'dedicated' tasks, should be explained to and supported by the PM because he trusts you due to having a track record of delivering.
Of course, reality isn't always ideal
- pojzon 4y ago> It's the job of the PM to decide what to build. It's your job how to build it, which includes taking time for an appropriate level of quality. Cyting my current Project Manager: „We are short on deadlines, dont care about quality, just deliver crap and we will fix it overtime (we will not /s)” You live in some unrealistic world. Companies have deadlines set together with clients. Deadlines are signed by the ppl who have no idea about how technically challenging it can be to build something. You are hired to deliver ON TIME. Nobody gives a demn about quality when new client is banging on the doors. Thats the sad reality of 90% of IT.
- iostream24 4y agoProvide feedback. Actual reality is technical debt, it’s your poor management that is living in a dreamworld