Yet Another Manifesto

When we set out to build consumer software, I pulled together sentiments from our CEO, lessons learned, and principles behind the Agile Manifesto into our own set of principles.

Since I’ve already received permission from my employer to publish it in a paper, Agile Practices and Innovation, I thought I’d include it here.

Oxygen Software Product Development Manifesto

Building consumer software is a joyous and daunting challenge. We, software developers, owe Oxygen and Oxygen’s customers every chance at success. We believe success springs from the following principles:

It’s all for the end user

The most important relationship is between us, the people building these tools and the women and men who are our customers. We must continually refine our products based on ever increasing knowledge of our customers.

Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. — http://agilemanifesto.org/principles.html

People own their identity and information

We respect our customers. We respect their privacy. We believe people own their virtual selves.

To that end, we will never misuse data, we will always provide a way to keep personal information private, we will always give our customers a way to export their assets and remove their identity from our systems.

Each tool we build helps people do a specific thing better than anything else available

Build the best solution for a specific need felt by a broad range of women.

Build simple tools that are useful, elegant and fun and go from there

First build a specific solution and then abet our customers using that tool in ways we never imagined.

This is both a cause and a business

We must remember that this is a business proposition. As our products evolve, we need to understand the revenue models and targets. We need to help define and measure appropriate metrics. We need to do everything we can without sacrificing the other values in this manifesto to achieve the business aim of the company.

Gerry Laybourne is the product owner

If our most important relationship is with our customers, our most important collaboration is with our product owner. Gerry sets our priorities. She must embrace what we are doing. Our relationship must remain direct. The best way to convey information is face-to-face.

These tools spring first and foremost from Gerry’s imagination. Direct connection between Gerry’s vision and our team’s creative efforts leads to success.

We are inventors

We must imagine solutions outside current limitations and ask ourselves, “what of this can be done now”. We must build something never seen before that when handed to the right consumer feels inevitable and obvious.

We must engage creativity, empathy with our customers, resolute professionalism and an inspired sense of play.

If we don’t love our inventions, no one else will.

We have authority, we are responsible, we are accountable

We are a self-organizing team in the best spirit of Agility.

If we, the people doing the work, allow this project to drift from its founding principles it will fail – with consequences for all concerned. In the face of that possibility, we must have courage to speak truth to power.

Specific technologies and mediums are just tools. Get over them.

This project is about helping our customer get more out of computing and making a profit for our company. We must not let assumptions or affection for specific tools, technologies and platforms on anyone’s part distract us from our mission.

Admit failure and move on

Resources are limited. Set specific, measurable goals. Face the truth and course correct. Don’t knowingly waste time or effort. Don’t use lack of knowledge as an excuse for wasted time or effort.

Love of Craft

My wife is a trained Ringling Brothers Clown College Clown.

Clowning is a difficult profession. It doesn’t receive much respect. It’s hard work. Physical comedy can easily wreck your health as quickly as it drives you broke. Material success means getting to work.

But clowning is a craft with roots as old as performance itself. True practitioners bring great discipline and joy to their work. A talented clown relates to their audience with the spontaneity and innate intelligence of a child while employing a mastery of performance honed by years of training. Good clowning is surprising, stunning, human and hilarious.

However, the level of talent, skill and training vary to extremes. There is no official apprenticeship process. When people think of clowns, they’re often thinking about amateurs who’ve had very little exposure to the work of veteran performers.

It’s easy to be a frighteningly bad clown. Many amateurs paint both the top and bottom of their mouth with a broad stripe of red makeup. They turn their character’s mouth into a gaping maw large enough to devour a child’s head.

If you ever get a chance to hang out with experienced clowns you’ll find out how embarrassed they are by bad performers with horrifying makeup and costume, few skills and little respect for the history and rituals of clowning.

I’d say the difference between what I do and what my wife does is that software developers earn a lot more money and are a lot less fun to watch. Still, what I do is also a craft. To do it well requires aptitude, discipline and apprenticeship. Just as in clowning, there are common mistakes perpetrated by bad or inexperienced developers.

Similar to my wife’s clown college class mates, I feel great pride in my craft and in those who take it up with talent and integrity. I also feel frustration, disappointment and a little outrage at peers who strive for less.