So, how do you manage a team with a variety of values and expectations from their interactions with management?
You know theory X and theory Y.
(X - managers and workers are adversaries, Y - Managers just nee to support worklers and they will do their best.)
I hope that we projects managers tend to fall into the Theory Y zone. Our teams have interesting work, usually good management and people are focused around common goals in a context of a cohesive team. I suspect we are much more Theory X than we think. For instance, my direction to my team to adopt scrum practices is not optional. Until reflecting you wouldn't neccessarily recognise this as a theory X appraoch to work. And we don't expect we are espousing values that say we don't trust our team members.
In fact, any time we mandate a process or control technique, that's exactly what we are doing. I want to be a coach of faciliatator, but I keep demanding certain practices and standards are followed. Deep down I know this is a problem, but how can I let go of the tiller when we are in rough seas? I don't think I can unless I know I have sipport from my sponsors. And my sponsors are in the same boat - manging expectations and dealing with a portfolio of risky investments.
Who makes the call that it's okay to experiment and fail? At what scale?
What are your stories?
3 November 2010
Subscribe to:
Post Comments (Atom)
Popular Posts
-
Due to popular demand I have aggregated some information on User Stories and created a simple template. If you feel this would be useful to...
-
I have been having a bit of a discussion over at the IIBA blog with Kevin (VP BOK) and Julian (Chief architect.) It’s migrated over to ...
-
Better Projects Templates I am uploading a couple of project document templates to Google Docs. As I add more I'll post them up here. You...
-
You've heard many reasons why project fail. Here is a discussion hosted by BCS on why projects work. The discussion covers four dimensio...
-
The Precedence Diagramming Method ( PDM ) was developed in the early 1960s by H.B. Zachry in cooperation with IBM. It has largely repla...
-
In the below video some of the #10yrsagile participants discuss the role of the Business Analyst. A question for you; Do you agree or di...
-
This is a guest post by Jeff Hobbs. Jeff is a project manager at ActiveState Software who provide pm and collaboration software. Email, ...
-
In one of the Carnivals of Business Analysts the theme was “ Requirements Analysis ." I searched the web far and wide and came up with a n...
-
I'm a massive Lord of the Rings fan. Every year, I spend part of my holiday vacation rewatching the 12 hours of the blu-ray extended edit...
-
The definition of a stakeholder is controversial. For example, project team members are generally not considered stakeholders, but in virtua...
As SW PMs and developer we MUST be doing Theory W
ReplyDeletehttp://sunset.usc.edu/classes/cs510_2001/notes/ec-files/theoryw.pdf
The difficulty, Craig, is that Theory Y requires both participants be of the appropriate maturity and far enough up Maslow's needs hierarchy in order for it to succeed.
ReplyDeleteIf either side isn't in the right place, Theory Y falls flat on its backside.
Steve, when you are in a low trust environment who's job is it to begin he journey to trust and partnership?
ReplyDelete