Larger Image

Jurgen Apello gave an interesting presentation about agile project management at the “Agile Eastern Europe Conference” in Kiev. His approach is a mixture of complexity theory, agile best practices, some psychology and "soft skills”.

His 12 laws of software development are: 

- Motivate People
- Empower Teams
- Align Results
- Optimize Communication
- Enforce Discipline
- Restrain Growth
- Reduce Risk
- Measure Performance
- Evaluate Feedback
- Acquire Knowledge
- Manage Uncertainty
- Evolve Practices

Those are not only valid for software development projects but for all projects with creative teams. His presentation is good, so check it out.

Dating is a process. So is losing weight, being a public company and building a brand.

On the other hand, putting up a trade show booth is an event. So are going public and having surgery.

Events are easier to manage, pay for and get excited about. Processes build results for the long haul.

This is one of the most fundamental things that organizations need to understand. A process requires persistence and patience. Two characteristics many organizations lack.

The decision for social media should always be a mid- to long-term decision. Of course it can/should be an iterative process and adjustments will be necessary. However, I believe the ROI of social media will show over time (and it might eventually show negative)...

Todays workforce is growing, mobilizing, connecting, aging and evolving. How will you manage?

1. Add reply buttons for YES, NO and MAYBE.

Some messages just don’t need a comprehensive reply. If someone e-mails me and asks if I’m available to attend a meeting, rather than take the time to write back with a detailed response, why can’t I just click a YES, NO, or MAYBE button? One click and the e-mail has been dealt with.

2. Use browsing history in a smart way.
When people send me news items or blog posts, my e-mail program could check my Web browser history to see if I’ve already been to this specific URL. If so, the message should skip my in-box.

3. Add the ability to take yourself out of the reply chain.

I regularly send messages to introduce friends or co-workers to each other. These introductions are usually the standard “Hi Jane, I’d like to introduce you to Bob.” After a connection is established, I’m often forced to sit on the sidelines getting a barrage of messages as Jane and Bob converse. It would be great if I could preemptively remove my address from these replies.

4. Crowdsource the problem.
O.K., I know this one is a stretch, but what about crowdsourcing my in-box — opening it up to the general public? Then, when I get that forwarded e-mail from a co-worker announcing that the government will start taxing people for every e-mail they send, someone else could respond explaining that, sadly, this is actually fake. This scheme would require correspondents to label personal or private notes that would then stay out of the crowdsourcing zone.

5. Eliminate the “reply-to-all” feature.

Ah, the reply-to-all e-mail faux pas: You’re invited to an event via a large group e-mail and one person responds to everyone with a pointless “Great, I’ll be there!” If a cold-blooded extermination of this feature is too radical, maybe we could require a stern CAUTION alert whenever someone attempts a reply-to-all.

6. If the e-mail is important, it will find me.

Real-time services like Twitter and FriendFeed illustrate the potential usefulness of a streaming interface. I don’t have to see all the tweets in my stream; if something is specifically important it will be re-tweeted by people in my network. The more this happens, the better the chance that I will eventually see it. What if we made e-mail into a stream? If a message is important, people can re-mail it, and it then moves back to the top of the list.

7. Cut off anything longer than 140 characters.
Speaking of Twitter, do we really need more than 140 characters for most messages? E-mail applications could add a button that would cut off all content longer than 140 characters.

8. E-mail software intelligence.
E-mail applications are essentially dumb clients. They don’t know much about you, or your e-mail, and if they do, they don’t use this data to help manage the content. There are people working on this problem and coming up with solutions like Kwaga, a semantic-language enhancement for your e-mail. But there could be other additions to these smart clients. For example, let’s say my e-mail application understands that I have an @nytimes.com address. During the day other @nytimes messages could receive higher levels of attention than mail from my wife or brother-in-law. In the evening, this rule could flip, placing work messages on the back burner.

9. Create an “Auto Filter” button.

Clay Shirky, author of the book “Here Comes Everybody: The Power of Organizing Without Organizations,” believes that “we don’t have information overload; we have filter failure.” I completely agree with this, but creating filters can become a chore too. My solution would add a single-click button called Auto Filter. Once pressed, it would do its best to analyze the message and create a new filter, and then file future messages into this new category.

10. A monthly word limit.
We have limits on Internet bandwidth, and surcharges to limit the number of minutes we can talk on our cellphones. Why not limit the number of words an e-mail account can pump out each month? (If you go over, that new government e-mail tax kicks in …)