Discussion about this post

User's avatar
AR's avatar

All nice and fluffy! Zooming out, we see the following key topics:

1) Reduced, normalized workload, sustainable pace. Unrealistic load / deadlikes is typically the key reason for such issues and it is hard to implement all the nice things listed, both for Dev and PM

2) Management skills and managers. Leadership. Without it, it's not gonna happen. PMs have a long history of trying to change the dynamics of management using guerilla methods. Very few succeed

3) Part basic management, part common sense. None of the nice things don't happen where you do not have

* clearly defined responsibilities and

* 'process' or more likely key steps in the would be process - who does what based on what

* this means you actually have sensible managers on key positions who can agree and they actually have management skills. You need to solve these problems because you have a problem with leadership

4) The common denominator of most of the suggestions is to embed developers into the PM/stakeholder space and possibly get a better insight of the Dev space. Some items are often rejected nobrainers that Dev should be involved in planning. First, all this takes extra resource / time and still, you need to keep the clear division of labor. You cannot make everything perfect quickly

4) Your mileage will vary. People are different. Some just do not care about stuff beyond their coding stuff. Sometimes it is a gentle pressure, sometimes just leave them alone. You cannot force-feed happiness

Expand full comment
1 more comment...

No posts