We have shifted our blog to a new site. The new address is http://blog.akelesconsulting.com. Please update your bookmarks.
The new blog site will allow you to
- retweet those articles you want to share with your peers
- like the page for your Facebook friends
If you are an active Facebook user, you can follow us on our Facebook fan page where we will share interesting links and updates.
With these changes, you can now follow us at
Atlassian, the maker of Confluence & JIRA was featured recently on the CNBC – US National TV for a short interview.
Vodpod videos no longer available.
It’s an amazing feat that a company started by 2 university graduates with a $10k credit card loan has grown into a company with 225 employees worldwide and 59 million revenue in FY2010.
Kudos to Mike & Scott and the Atlassian Team 🙂
Posted in events
Last month, I shared a blogpost (How to enable active collaboration with your wiki) to share the benefits of using workflows together with wiki.
Recently, Roberto from Comalatech, the creators of Adhoc Workflows plugin for Confluence has also contributed a guest post too. In his post, he shared how people can use workflows to streamline the process of publishing Frequently Asked Questions into a knowledge base.
For details, check out Wiki Workflows: Publishing a Knowledge Base Article
Atlassian, our partner and the developers of JIRA and Confluence has been selected as a World Economic Forum Technology Pioneer.
The thirty-one winners of this year’s award hailed from 13 countries. Past winners include some of the most sensational names in business such as Google, Mozilla and Twitter.
This is a strong endorsement of Atlassian’s leadership in the collaboration and software development market.
We extend our congratulations to Atlassian and share the honour of being an Atlassian Partner.
Here’s a short interview with Scott Farquhar, Atlassian’s Co-CEO
What a wiki cannot do
Being a Confluence wiki user for several years, I have experienced the following difficulties:
- I have to email people after posting pages/comments to get their acknowledgement/approval/comments
- I got difficulty tracking which pages/comments that I need to reply after a few days elapsed
There is a lot of extra work duplicated between the wiki and emails. And when people conveniently reply to the email instead of posting to the page. The collaboration and knowledge leaves the wiki back into the emails.
As such, I observed that a lot of wikis are mostly used for passive collaboration like knowledge bases, FAQs and intranets.
However, Ad Hoc Workflows plugin for Confluence patches the gap and enables Confluence with the capabilities of:
- assigning of tasks
- defining workflows
How we use it
I will share one of the scenarios on how we use the Ad Hoc Workflows plugin to collaborative actively.
- After each meeting, one of us will draft the meeting minutes into our wiki
- Upon the completion of the draft, the author will assign the attendees a task to review the minutes
- We will receive an email notification to inform us of the task with a link to the wiki page
- Likewise, we can also see a list of our outstanding tasks on the dashboard for follow-up
- We will go to the wiki page to make minor changes or post comments
- Once everything is ok, we will mark the task as completed
- The wiki page is then marked as approved once everyone has completed their reviewing tasks
It can also support more sophisticated workflows as shown in the video below.
For more information, check out Ad hoc Workflows’ official website
The latest version of Confluence has been released with a faster and simpler editor.
Here’s a short video clip summary of the new features released.
For details, you can also release to Confluence 3.3 release notes
Almost every people hates writing documentation. It usually takes place only after everything is done where it is very difficult to recall all the tiny details. And it is likely that nobody else will read it since the person who wrote it has all the knowledge in their head. That’s why a lot of technical people dread writing documentations.
Sarah Maddox has given an very useful and interesting presentation with tips on making documentation more useful and engaging.
By increasing the engage-ability of the documentation, it increases the value of the documentation as
- more people is likely to read the documentation
- more people will be encouraged to contribute to the documentation
- more people will be encouraged to keep it updated
- more people will share their experiences too
A wiki helps to increase the engage-ability of the documentation by
- making it easier to create documentation during the project rather than end of the project
- making it easier to search (with a in-built search engine)
- making it easier to share and link related information (with threaded comments on the same page)
You can download the slides together with her notes at her blog.