From 9f3023d7317837a65c20e9712b57be69a204da35 Mon Sep 17 00:00:00 2001 From: "Amy J. Ko" Date: Tue, 10 Oct 2023 10:49:19 -0700 Subject: [PATCH] Fixed #158, removing reference to missing podcast. --- chapters/quality.bd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/chapters/quality.bd b/chapters/quality.bd index f07432e..25c35d8 100644 --- a/chapters/quality.bd +++ b/chapters/quality.bd @@ -48,4 +48,4 @@ Although the lists above are not complete, you might have already noticed some t These external notions of quality are not the only qualities that matter. For example, developers often view projects as successful if they offer intrinsically rewarding work. That may sound selfish, but if developers _aren't_ enjoying their work, they're probably not going to achieve any of the qualities very well. Moreover, there are many organizational factors that can inhibit developers' ability to obtain these rewards. Project complexity, internal and external dependencies that are out of a developers control, process barriers, budget limitations, deadlines, poor HR planning, and pressure to ship can all interfere with project success. -As I've noted before, the person most responsible for isolating developers from these organizational problems, and most responsible for prioritizing software qualities is a product manager. Check out the podcast below for one product manager's perspectives on the challenges of balancing these different priorities. \ No newline at end of file +As I've noted before, the person most responsible for isolating developers from these organizational problems, and most responsible for prioritizing software qualities is a product manager. \ No newline at end of file