In the video from Sun that was posted on Atlassian's blog recently the following comment, that to me is the real power of wikis, was made.
"Publishing now belongs to the community"
I completely agree. The problem I see however is that the content authored, while mostly aimed for publishing on the web, is authored or stored as "Wiki Text". Like Doug, I'm amazed that wiki markup is not seen as "arcane" in the same way as the original layout languages.
Tagged Ephox
At Ephox we've always had a culture of fun and doing things as a team, it's one of the things that make this a great place to work.
Tagged Ephox
I was reading an article by Jean Tabaka on the 11 Ways Agile Adoptions Fail and her number 5 reason "Product Owner is Consistently Unavailable" hit a cord. In it she states
An unavailable product owner perpetuates the wait time and creates waste
Having experienced this in the past, I can't agree more.
Tagged Ephox
A few posts ago I talked about competency versus capability and recently I've seen a few posts supporting my assertion that the "tick in the box" approach to hiring isn't going to guarantee you get capable people.
You will often hear the terms "People Independence" or "Institutional Memory" used as a management reason for the creation of the huge volumes of paperwork often created in a BDUF (Big Design Up Front) project. The idea of course is that the presence of the documentation allows the organisation to use developers interchangeably.
For developers, documentation is extremely useful for the those who come after, even if it's you in 12 months time. This documentation however is only useful if it's up-to-date. Unfortunately in most cases it's written, read and never looked at again.
