I’ll be presenting two talks at the November Scrum Gathering.

One of them is dear to my heart. I’ll be using this blog over the next few months to work up my ideas and document conversations I have around this topic.

The Ethics of Scrum and Agile Software Development.

Here’s what I proposed:

Presentation Description

Are Scrum and XP inherently ethical?

In the face of contradictory beliefs over what we do and how we do it, we software developers, agile or not, experience pressure to compromise our work and our due care for others. Meanwhile, as our products become more beneficial, more pervasive and inter-connected our potential to harm grows.

Attempts by the ACM and IEEE to engage us in a dialog on norms of conduct has resulted in a controversial code of ethics that borrows heavily from established engineering disciplines – mandating specifications to ensure effective software.

We, agile software developers are making an under-appreciated contribution to ethical practice in our field.

Whether our work is a profession or craft, we need to engage the larger community in a conversation about how our day to day actions affect our employers, our peers, and our society. This presentation will attempt to frame professional ethics in the context of agile values and practices.

Why is this topic of interest to Scrum Gathering attendees?

The discussion over norms of ethical conduct happens outside the earshot of most working developers. The day to day experience of Scrum practitioners is at a distance from those who concern themselves with software ethics.

As a Scrum community, we have a responsibility to help shape the expectations placed upon us by others. We cannot delegate our integrity. Nor can we defer concerns over negligence, recklessness, or intent to harm the human beings who use the systems we create. We openly discuss our projects, our working conditions, and our advancement but to protect those very interests we often deal with issues of conscience privately.

Yet the passion behind Scrum is, in part, an idealistic one – a hope that by dealing openly and responsively with our stakeholders we will build something of real value. We need to harness this idealism to encourage each other make better decisions in the interests of stakeholders who do not pay us and do not always have a seat at the project table.

Given the downstream effect ethical lapses large and small have on society, we need to engage in this discussion or have the wrong solutions imposed upon us by employers, institutions, and regulatory agencies.

Presentation Objectives

1. Is it important for us to establish a shared commitment to ethical conduct?
2. What obligations a software developer should feel beyond fulfilling the requirements of their employer?
3. How the Agile Manifesto and Scrum/XP practices suggest a partial set of norms of ethical conduct.
4. How agile organizations have started to provide their own statements of principles to extend agile values and encompass conduct towards our peers and society.

Short link: http://jkat.me/gvrGHp

Tag(s): agile, ethics, scrum, software developer, software developers, software ethics, wrong solutions, xp

Comments: none

There once was a carpenter building a metal box. Try as he might, he couldn’t get nails to stick into much less attach two pieces of metal.

Apparently, other people were having a lot of success using nuts and bolts. So he got some.

Hammer as he might, all he ended up with was dented metal and bent bolts.

So he consulted an expert. Careful observation indicated the expert used a screwdriver. Great! He happened to have one in his toolbox.

He noted that the useful part of a screwdriver was the slotted tip at the end. So, he cut it off and taped it to the head of his hammer.

After one strike, the tip broke off and fell to the floor.

“Boy, my hammer is really letting me down,” he thought to himself. “I guess I’ll have to use the whole screwdriver.”

He went to the store and bought another one.

Once he got home, the man held it in his hand. It didn’t feel right. Any decent tool has a grip that goes at right angles to the head. He found a piece of wood and attached the screwdriver to the end.

That felt a little better but the screwdriver was very light. No decent tool was that insubstantial. So he attached a weight to the tip. That felt better! Now he was making progress!

Confident in his tool, the man pounded away at more bolts.

He managed to make a dozen deep scratches and bend several bolts before the screwdriver broke.

“That was worse than before! Screwdrivers are really overrated and it took so much work before I could even use it, ” the man said to himself.

“I’m not making that mistake again. I’m going out and get a really good hammer!”

Short link: http://jkat.me/hUc5sW

Tag(s): agile, carpenter, decent tool, head, metal, metal and bent bolts, metal box

Comments: none

I’ve posted about why I need to encourage agile practices outside my department.

If Scrum is isolated within one team, its very success can be used to counter further adoption. “Agile works for you but what we do is different. You do X we do Y.”

This resistance is a direct result of what Andy Hargreaves calls balkanization — groups insulated from each other, with hard boundaries, loyalties and a political complexion.

Creating a culture where groups work together to improve the organization is core to lean and agile. So the best ways to counter balkanization are the very principles under challenge.

I’m tackling this top-down by lobbying senior executives to bring in an agile/lean coach, bottom-up by removing impediments for my team, and, perhaps most significantly, sideways by initiating a Scrum in another department.

I have tentative approval from another department’s senior managers. Now, I have to meet with line managers and identify a backlog of work. Then solicit volunteers for a team.

I’ve taken Ken Schwaber‘s words to heart and asked them to Scrum their hardest challenge or the work they think least suited to agile.

So many things can go wrong. Of course, nothing that isn’t already going wrong. That’s the point.

Scrum will highlight those problems and make solving them obvious and necessary if no easier.

More to come…

Short link: http://jkat.me/e2ZjZJ

Tag(s): agile, agile/lean coach, Andy Hargreaves, Ken Schwaber, management, scrum

Comments: none

It’s a privilege to be granted authority in another person’s company.

It’s easy to criticize. It’s hard to raise capital and make payroll.

I have never been an entrepreneur. My passion is to build teams. To be of service. To make things better.

I’m that second generation that feeds off founding vision and hopes to sustain an organization.

This has been a good week.

• We achieved our first business objective on our standard bearing product initiative, Ript™.
• My CEO is championing agile values in my division’s executive team – accountability to specific commitments within a time box.
• Managers in a peer group recognize the potential of self-directed, cross-functional teams and are interested in introducing the first scrum outside my department.

I am a cautious optimist. Success is far from inevitable. Actually, all this represents is an opportunity to start the really hard work.

Still some moments, especially ones years in the making, need to be savored.

Short link: http://jkat.me/dIzrFE

Tag(s): agile, CEO, entrepreneur, management, scrum

Comments: none

Wendy & Ilio participate in our daily standup. Note the talking tokens…

Short link: http://jkat.me/imd182

Tag(s): agile

Comments: 2