57225RE: [scrumdevelopment] Why do the "values" matter?
- Sep 20, 2013
Focusing on the Manifesto is a good technique as it gets you to those values. (Thank you for the reminder.) It’s a less direct route, and perhaps I’m just getting a bit tired and wanting to be more direct. And, yes, some people really don’t want to think about their work more holistically and the whole on-the-bus/off-the-bus thing is worth looking at and planning the organization around.
I remain willing to work with people whose values are skewed from mine. It’s good for both me and them and causes growth. I’m not sure avoiding situations where agile adoptions have run aground for any variety of reasons—including a less than generative way of valuing human beings—is quite where I want to be, yet. I know plenty of people who are there, though, and to my mind, this means there are more teams out there in need of support than are going to get it. One view speaks to courage, and some would say the other view speaks to wisdom.
Someone asked me a really hard question in Q1 of this year (and it was in an interview): “Do you really enjoy going into these situations where people aren’t getting along, projects are failing, and turning the situation around?” They wanted a “yes” or “no” answer, and I just didn’t have it for them. Overnight I realized that firemen likely don’t enjoy running into burning buildings; they enjoy putting fires out. Arsonists enjoy burning buildings.
Maybe what I need here is a bigger hose or a more reliable water supply. I’m off to yet another week long workshop next week to get a sharper bit and drill a deeper well.
Personally, I always go back to the XP values: courage, communication, feedback, simplicity, and respect. Those resonate with me.
Beyond that, I try to make sure that the folks I work with can agree to respect the values and principles in the Agile Manifesto. Some people don't really want to. For example, some people like designing things and not necessarily building them. Others like to build things but don't necessarily care what value they have or to whom; it is the act of building things that are cool to them personally that they enjoy. The only solution I have found is to not work with those people.
There is nothing wrong with having values that are different than someone else, but there is also nothing wrong with making decisions about who you want to hire or who you want to be hired by based on those values. Since you are moving on anyway, perhaps you should think about what questions you could ask to your next client to make sure that their values are compatible with yours. If they aren't compatible, perhaps no amount of effort on your part is going to change them in any meaningful way.
On Fri, Sep 20, 2013 at 8:59 AM, Jean Richardson <jean@...> wrote:
I’ve had my head down in a challenging problem for several months. Now that I’m “waking up” to the world again, I hope to be able to spend more time engaged in this list.
I’m thinking of you all this morning because, as I exit this engagement, I’m writing up a couple of organizational impediments at the behest of the sponsor for these last six months of work to improve this Scrum adoption. I’ve been socializing these impediments to ensure they retain traction in my absence, and one doesn’t seem to be getting the kind of traction I was hoping for. Essentially, it’s about the lack of the Scrum Values being present on the Teams and in the division as a whole. I’m getting the response “I just don’t understand what you’re talking about.”
Do others here see the same confusion about why respect, commitment, courage, openness, and focus are important to an effective Scrum adoption? Do I need to be talking about professionalism, instead? I’m concerned that will gloss the issue, frankly. Have any of you been able to tie this to real numbers (dollars) through external case studies?
Azure Gate Consulting
~ Repatterning the Human Experience of Work
- << Previous post in topic Next post in topic >>