Tag Archives: process

OCLUG and “The Art of Community” by Jono Bacon

I have started reading this book, I am about half way through.
I have already found useful info that I can use in OCLUG.

I consider my role as President of OCLUG to be similar to the role of Community Manager that Bacon describes. The committees that we struck at the AGM have “objectives” that would be “objectives” for the club, as the book defines them. We would need to add other objectives as defined at the AGM and in recent board meetings, but this is a great start on a “Strategic Plan”.

As someone said in a committee meeting recently, “talking about mission … again”. Well, maybe. Jono Bacon considers a Mission Statement to be useful, but I think we have one already. It’s somewhere in the minutes and I will make it more prominent Real Soon Now(tm, but not by me).

The book is a detailed how-to, a tool for planning, executing on the plan, tracking progress on the plan, and reporting. In fact, I intend to take his notes on “Reporting”, and use them at work. I will also apply his recommendations on reporting transparently at work and in the club.

Speaking of work – Bacon even tells a story of what not to take from work and apply to community, thereby highlighting that this can be an issue, and to remember it.

I appreciate the work that Jono Bacon has put into this book. It will be a reference that I will keep and refer to, and recommend to others involved in leadership of any sort of community, from festival to software project.

I must note that my copy is missing all its “Figures”, which probably means it is a pre-release copy. I am curious to see several of them, (What does the “dot” family look like?) but it has not hindered my learning.

I have learned about organising a group from one of the best – Toastmasters International – and from numerous short training courses. This book brings together a lot that I have learned, packages it for theoretical consistency, and adds new material that I can act on. And I still have half of it to read yet.

News from Agile Ottawa meeting

Yup, it was a good meeting, and I took away an idea or two…

But what I am most excited to tell you about are future events:

And the ideas I took away are centered around Dmitry’s suggestion that Agile design decisions should be documented with light-weight tools, such as the development team’s existing issue tracker.

CMM-1 is like ‘pray as you go’

Or at least I thought so when I saw it on the church sign. So here’s the pic!

And the links:

Corporate Memory is important

Migrated. Originally published: 2006-07-15

An article on Gamasutra.com reminds us that keeping staff over time is important for a high tech company. That’s why game development companies “keep making design errors”, according to Ernest Adams. It’s interesting to look at his list of game industry goofs. How many happen at non-game companies? Well, burning out your workers happens in many high tech companies, and the resulting problems are just as big as in the game industry.