An MBA Oath – another non-profession’s search for a standard of ethical conduct

There’s a movement among the students of the MBA program of Harvard Business School for an MBA Oath of ethical conduct. Read the oath here.

From a June 4th article in the Economist:

The student oath is part of a larger effort to turn management from a trade into a profession…

This is the exact debate going on in Software Development — emerging profession or craft?

One of the two main criticisms of the oath and of the whole idea of turning management into a profession, particularly in business-school faculties, is that it is either unnecessary or actively harmful… (by) promising to “safeguard the interests” of colleagues, customers, and society, are the future captains of industry simply short-changing their shareholders?

Defenders of the oath reply that the goal of maximising shareholder value has become a justification for short-termism and, in particular, rapid personal enrichment. They are concerned about managers doing things that drive up the share price quickly at the expense of a firm’s lasting health.

The second complaint is that the oath’s fine words are toothless.

Even these cheerleaders admit there are differences between practising management and, say, medicine. They concede that no self-regulating professional body for managers could possibly monopolise entry to the profession

DSC00689 by Ivana BrosnicWe can debate that a practice has ethical consequences, i.e. that it has a larger array of stakeholders who can be harmed or benefited by the daily decisions of practitioners – without calling for accreditation, lincensing, certification, standards bodies, and regulation.

Developers should consider end users, society and our common reputation even as managers consider long-term investors, employees, their industry and the larger economy.

Name a widespread activity that isn’t abetted/enabled by software systems. Even the debate over an MBA Oath:

As for punishing unprofessional behaviour, Mr Khurana (Rakesh Khurana, a professor at Harvard Business School) is inspired by the internet rather than by a closed council of grandees. From open-source software to eBay and Wikipedia, new systems of self-regulation are emerging based on openness, constant feedback and the wisdom of crowds. These could be adapted, he thinks, to provide effective scrutiny of managers.

If anything about this strikes you as not true, I’d love to hear why.

More playing on – Learning Outcomes

Supplement to a doomed Agile 2009 proposal.

Learning Outcomes

  • To share with participants concepts in professional ethics
  • To tie the nature of ethical dilemmas to essential complexity and the means for tackling dilemmas to the practices of agile development
  • To emphasize the origins of agile practice in values and culture and to tie that to ethical imperatives
  • To identify gaps in agile values that prevent it from being a complete ethical framework – to broaden the definition of stakeholders
  • To challenge the common assertion that doing your job constitutes being ethical
  • To walk through real-world ethical dilemmas, and discuss possible actions and outcomes
  • To build the community of practitioners engaged in the topic and interested in supporting their peers through crises of conscience
  • To brainstorm tools and techniques for expanding the conversation to a broader community in a way that is safe, inviting, and does not violate our obligations
  • To engage the agile community in the larger development and academic community’s efforts to define ethical guidelines for us and potentially inflict them upon us
  • To discuss the growing potential for unintentional benefit and harm from non-safety critical systems
  • To discuss the potential for governmental intervention in response to some highly visible or damaging failure by software systems or software practitioners