POs write tickets and assign them to sprints. All tickets must be approved by a PO before added to a sprint. No code can merge unless its associated with an approved ticket. Since POs have no idea what technical debt even is, this PO-driven setup guarantees that technical debt will never be allowed to be worked on, even if the engineer wants to spend his weekend doing so. This results in features being cranked out as fast as possible and to earn “story points” and impress businesspeople, but a technical architecture that spirals out of control until everything is FUBAR and then velocity slows down and nobody in the business side understands why.
You’d think that the development process would be owned more by developers, since they are the ones doing the work and understand the details best, but everywhere I have ever worked, businesspeople eventually insert themselves into a project and start controlling everything and preventing developers from doing what they need to do. Then the project eventually reaches a risk-averse “production” state where hardly any changes are allowed unless they go through a rigorous human-driven QA process, which requires business approval to allocate QA’s time. The result is that technical debt gets completely ignored.
submitted by /u/Professional-Day9384
[link] [comments]
r/cscareerquestions POs write tickets and assign them to sprints. All tickets must be approved by a PO before added to a sprint. No code can merge unless its associated with an approved ticket. Since POs have no idea what technical debt even is, this PO-driven setup guarantees that technical debt will never be allowed to be worked on, even if the engineer wants to spend his weekend doing so. This results in features being cranked out as fast as possible and to earn “story points” and impress businesspeople, but a technical architecture that spirals out of control until everything is FUBAR and then velocity slows down and nobody in the business side understands why. You’d think that the development process would be owned more by developers, since they are the ones doing the work and understand the details best, but everywhere I have ever worked, businesspeople eventually insert themselves into a project and start controlling everything and preventing developers from doing what they need to do. Then the project eventually reaches a risk-averse “production” state where hardly any changes are allowed unless they go through a rigorous human-driven QA process, which requires business approval to allocate QA’s time. The result is that technical debt gets completely ignored. submitted by /u/Professional-Day9384 [link] [comments]
POs write tickets and assign them to sprints. All tickets must be approved by a PO before added to a sprint. No code can merge unless its associated with an approved ticket. Since POs have no idea what technical debt even is, this PO-driven setup guarantees that technical debt will never be allowed to be worked on, even if the engineer wants to spend his weekend doing so. This results in features being cranked out as fast as possible and to earn “story points” and impress businesspeople, but a technical architecture that spirals out of control until everything is FUBAR and then velocity slows down and nobody in the business side understands why.
You’d think that the development process would be owned more by developers, since they are the ones doing the work and understand the details best, but everywhere I have ever worked, businesspeople eventually insert themselves into a project and start controlling everything and preventing developers from doing what they need to do. Then the project eventually reaches a risk-averse “production” state where hardly any changes are allowed unless they go through a rigorous human-driven QA process, which requires business approval to allocate QA’s time. The result is that technical debt gets completely ignored.
submitted by /u/Professional-Day9384
[link] [comments]