Scrum, XP, Management and the Ethics of Agile Software Development

Agile 2008

toronto_skyline
Steven Doc List and I held a 20 minute presentation and 60 minute open space on software ethics.

I think the format works. Software ethics is not rules or reason, it is navigating essential complexity in building software and in moral choice. Descriptions that “abstract away its complexity often abstract away its essence” (Fred Brooks)

We embrace essential complexity using the values and practices of agile software development.

We can become better software developers using the same tools we use to build better software.

We can learn through practice to recognize and accept responsibility for the intended benefit and unintended harm we create.

We can retrospect on our actions and their consequences, engage in a conversation with our peers, learn from, challenge, and support each other.

Oops, sorry about your retirement fund

The New York Times describes what happened to United Airlines stock value on September 8th, How a Series of Mistakes Hurt Shares of United

Investors wiped out $1 billion of the market value of UAL, United’s parent, within minutes of an erroneous news flash on Bloomberg screens about a United bankruptcy. Google and the Tribune Company, the owner of The South Florida Sun-Sentinel, whose Web site was the source of the article that led to the headline, soon blamed each other for causing the fiasco.

United Airlines Stock ValueA chain of mistakes and vulnerabilities led to United Airlines six year old bankruptcy being reported as fresh news. Investors reacted, destroying value to the point that trading of UA stock had to be stopped until the situation could be cleared up.

Two features on a Tribune run website started the chain. One allowed an old article to appear in the most viewed box. The implementation apparently doesn’t prevent obscure articles from filtering to the top in off hours.

The second displayed the old article on the Sun-Sentinel site with today’s date but no original publish date.

Google crawled the article. It’s age and lack of original publish date confused the automated news search into interpreting the article as current.

Then a private analyst published it without independent verification. Then Bloomberg included that analyst’s report in their feed.

This led to the panic selling. Trading was resumed and the stock recovered much of its value but don’t mistake that many people lost alot of money.

The Times focuses on the relationship between newspapers and search engines. You can also focus on the pressure of news agencies to keep up with “breaking news” on various platforms. You can focus on a loss of discipline among editors.

I’d like to highlight how two casually implemented features on a website indirectly led to serious harm. I can’t imagine a print editor allowing an old article to appear without an original publish date. So how was it acceptable to allow online content to appear that way?

Given the relevancy algorithms Google is known to use, how much was the behavior of Tribune’s “most viewed” area intended to create exactly the behavior that backfired in this case, i.e. to create referential links back to Tribune for old content.

There’s plenty of blame to go around but how much sits with those who defined, accepted and implemented this behavior?

HICSS-42

DSCN0234.JPG

This week, I’m presenting a paper at the Hawaii International Conference on System Sciences. My goal is to engage academic ethicists in a conversation about agile software development.

Given the year in employment I’ve had in the last year and what’s going on at my current employer this week, it is a gift that I was able to attend and I’m grateful for it.

Year of {x} jobs…

resumeAfter eight years with the same company, I spent the last sixteen months with several.

For those of you interested in Agile software development in NY I can tell you first hand that there is work.

The best opportunities exist for people who can demonstrate they get it — not just the practices but the values behind the practice.

And the best way to find opportunities is to work alongside people who are good at what they do and earn their respect and trust.

Power, dissent, and bullying in software developer communities

Grassroots developer communities form around shared values in dissent against institutions and norms that dehumanize their work and diminish their efforts. They attack these orthodoxies with humor, heretical thinking, and hard work.

This benefits society when developers defy those with greater power. It harms society when developers bully people with less power.

At the ThoughtWorks sponsored Agile East, Martin Fowler spoke to his post, SmutOnRails.

Part of the community was offended by a presentation at the GoGaRuCo (Golden Gate Ruby Conference). Others fought back saying that no offense was meant, the presenter apologized, and that the tone was in the spirit of the Rails community.

(T)he view of the rails leadership seems to be this: that the objections to the presentation are yet another attempt to foist empty corporate values on the thriving Rails ecosystem… (more)

This debate is not unique to the Rails community. It reminds me of concerns my friend, Luke Melia, raised over jokes and behavior at the first Austin Alt.NET. Martin Fowler links off to a similar controversy in the Flash community.

It is also not unique to developer communities but developers in particular need to be concerned about the outcome.

Women, African Americans and Hispanics are under-represented in IT and even more so in software development. In 2001-2002 74.4% of software developers were men. 78% of those men were white.

In 1986 the percentage of women in CS programs peaked at 37%. The percentage of women in computer science programs has gone down since then.

In 2001-2, only 28 percent of all undergraduate degrees in computer science went to women. By 2004-5, the number had declined to only 22 percent. — What Has Driven Women Out of Computer Science?, NY Times

There were 15,000 women in CS progreams in 1986. Riding natural cycles this number was not matched again until 2003. This latter number contains a higher percentage of non-resident aliens who will not necessarily contribute to the US workforce.

This despite higher percentages and numbers of women acquiring college educations than men. In 2007, 33% of women 25-29 held a four year degree or higher versus 26% of men. 55% of graduates with four year degrees or higher aged 25-29 were women.

Women are even receiving the majority of degrees in science and technology. They have shown steady progress in biology, chemistry, physics, mathematics and engineering.

Metrics can be misinterpreted but these quantitative measures support a stunningly obvious anecdotal observation. US software developers are a white male enclave.

This is a power imbalance and we developers are part of the problem.

Isolation is a key factor for a higher attrition rate among women and minorities, said Teresa Dahlberg, director of the Diversity in Information Technology Institute at UNC Charlotte. People tend to associate with “like communities,” where people have similar backgrounds and interests, she explained. — Computer science lacks women, minorities, SD Times

So when we behave in a way that marginalizes and intimidates talented women and minorities, we abuse power. We become bullies. We are oppressors.

“There is a good amount of research that shows that women are judged more harshly than men, for hiring, evaluations and promotions,” she added. “Virginia Valian [author of "Why So Slow? The Advancement of Women"] shows this for women in science, technology, engineering and math faculty jobs.” Virginia Valian is a professor at Hunter College. — SD Times

Part of the problem may be a perception that software development doesn’t contribute enough to society. To the degree this perception is true it is damning. To the degree it is just a perception we have work to do as advocates.

Our actions need to be judged not by our intentions but by the outcome.

Requisite variety within our teams remains an essential enabling condition for sustained innovation.

Access to technology is growing across all tiers of class, race and gender both in the US and overseas. Diverse teams can better address our market and build software better adapted to our end users.

A more diverse workforce provides the kind of social change that will help us create a more humane workplace for developers.

Finally, anything that limits the number of able US software developers hurts our ability to compete.

When developer communities marginalize women and minorities, we conspire to isolate ourselves from the larger society. We defeat our own attempts to change the power structures around us and improve our lot and our output.

ken h. judyI am an executive manager, software developer, father and husband trying to do more good than harm.
Working to spend each day doing a little less crap and a little more not crap than the day before. Without delegating my crap to others.
Aspiring to pride in my accom- plishments and pride in who I become as I attain them.
IEEE CSDP
CSP
I'm speaking at Agile 2012

Papers

Presentations

 

Site menu:


Meta

Creative Commons License

Post text is licensed under a Creative Commons Attribution - Noncommercial - Share Alike 3.0 United States License.

Unless otherwise indicated, Images in posts are not cleared for redistribution under creative commons.

Copyright © 2006-2012
Ken H. Judy.

This is a personal weblog. Views expressed are my own and not those of my employer.