Guarantee Enterprise-Wide Adoption of your Wiki

There are a number of best practices and strategies to ensure your organization widely adopts a wiki. However, the intrinsic nature of the wiki poses some challenges as more people use it. Wikidsmart enables you to overcome those challenges and guarantee widespread adoption of the wiki throughout your organization.

Your Expert “Wiki Gardener”          
If a wiki is not constantly and accurately updated, its reliability is questioned within the organization. Furthermore, erroneously entered information equally puts the viability of the wiki at risk. “Wiki gardening” describes those tasks necessary to keep information updated and accurate within the wiki. Wikidsmart is your expert wiki gardener, providing the following. 

  • Ensure consistent entry of content

One of the strengths of a wiki is that anyone with the proper access rights can freely enter content instantly. However, many times, particularly for repetitive data entry tasks such as writing requirements or specifications, data entry consistency is necessary each time a user enters the same type of data. Wikidsmart provides a choice of customizable templates to create forms so that data may be captured consistently. In addition, the content is captured semantically, so that the data’s underlying meaning is captured. The semantic capture of data means that the data may be more easily found in the future or even combined with other information to infer additional content.

  • Automate generation and maintenance of content and links

Even worse than not updating content and links on a timely basis is updating the content erroneously. Wikis lack the mechanisms to automatically update information. Links must be copied and pasted by hand. With Wikidsmart, links and content itself can be automatically generated with embedded queries within a wiki page, to ensure real-time update of content.

Your Organization’s Knowledge Repository

  • Easily find precise information

The wiki’s standard search feature is limited to string matches within the content and can best return non-specific result sets.  As the number of pages increases, this search method becomes increasingly inefficient. zAgile Wikidsmart’s smart search enables users to search for the type of content (e.g., a document) and category of content (e.g., specification).

Additionally, users can navigate through content contextually, having continual access to the tangential content. For example, in the software engineering domain, a user can navigate from Requirements, to Project, to Test Cases, etc. without having defined any such relationships because the knowledge of the relationship of the content is built into the underlying ontologies which drive the Wikidsmart solution.

 

Easy Software Engineering and Productivity Applications All Within Your Wiki

For Teams with Existing Software Engineering Tools
Your engineering team may wish to expose content from the application lifecycle management (ALM) tools inside the wiki and also achieve deep interoperability between the wiki and the ALM tools.  zAgile Teamwork provides a seamless way to integrate those tools into your existing processes, due to its infrastructure which is independent of the wiki, and it integrates any tool or application for deep interoperability amongst all tools and applications.

Easy Software Engineering Collaboration, All Within Your Wiki
For any engineering team, a key capability are the tools to help with managing Project, Requirements, and Test Cases. Better yet, the tools should be integrated with a centralized repository.  Wouldn’t it be great if the capabilities of managing Project, Requirements, and Test Cases in an integrated way were inherent in the wiki? Well, with zAgile Teamwork, powered by zAgile Wikidsmart, Atlassian Confluence, and Atlassian JIRA, those capabilities are built-in, thanks to the underlying software engineering ontologies that drive the solution. Forms are available for each area of Project, Requirements, and Test Cases, and each may be customized to fit the desired processes of the team.

 

Your Wiki Becomes Your Enterprise Information Portal

A single coherent view of your enterprise information
Your organization has many applications and tools, but you have no single, coherent view of all information. The CRM has its dashboard of sales and marketing information. Each engineering team may have different ways of providing the status of projects, but there is no comprehensive, real-time view of the status for the whole engineering team. With Wikidsmart, you have one coherent view of all information from all applications and tools.

Easily find precise information
Even if you use an enterprise search tool, it relies on brute force to deliver wild card search results of information. Likewise, the wiki’s standard search feature is limited to string matches within the content and can best return non-specific result sets.  As the number of pages increases, this search method becomes increasingly inefficient. zAgile Wikidsmart’s smart search enables users to search for the type of content (eg, a document) and category of content (eg, specification) of information not only in the wiki, but across all tools and appliations.

Additionally, users can navigate through content (within or outside the wiki) contextually, having continual access to the tangential content.

Integrate all tools, applications
zAgile’s infrastructure, which is independent of the wiki, integrates any tool or application. Therefore, any engineering tool or application can be semantically integrated with each other in a deep, contextual way.

Extreme traceability of information across organization
Due to Wikidsmart’s ability to semantically integrate all information across the organizations teams, tools, applications, and processes, for the first time, you have the ability to achieve “extreme traceability.” That means you can navigate information that crosses different engineering teams and even information across to the sales and marketing’s CRM. For example, you can navigate from Opportunities of the CRM to see what bug cost the most revenue, and then you can even drill down to the detail of the product feature specification, requirements definition, and the bug itself.




Wikidsmartís semantic wiki engine turns your enterprise wiki into an information dashboard:

  • Find precise information easily, across the wiki as well as other applications and tools
  • Generate and maintain new pages with embedded queries, pulling content from the wiki and other applications and tools
  • Achieve consistency of content across the wiki and other tools and applications
  • Easily capture semantic annotations of existing content 
  • Create new content using semantic templates and forms, and populate other systems if desired

zAgile seemed too good to be true, but they proved it to me. Before zAgile, we had the right tools, but we saw opportunities to gain more efficiency. … now we are even more productive across engineering, professional services, and product management teams.”
Niall Murphy
    VP of Engineering, Market6


Limitations of Other Semantic Wikis

  • Semantic wikis that are built natively from ground up do not offer much to organizations that have existing investments in wikis, unless they migrate their content and adopt the new wiki technology.  They also prevent users from leveraging the community-level support and feature extensions available in widely popular wikis.
  • Semantic extensions:  this approach supports popular wikis but have made the wiki itself a semantic repository, as opposed to one of many sources of semantic content



zAgile Wikidsmart provides semantic enablement of wikis and  leverages the following high-level functional components:

  • zAgile's Semantic Repository consisting of a set of ontologies and metamodels specific to a domain of interest.  Ontologies are for Software Engineering are included, and others are available through zAgile professional services or other ontology providers.
  • zAgile's Semantic Interface Layer provides wikis with access to the Semantic Repository via connectors
  • zAgile's Semantic Plugin for Confluence provides the interface between Confluence and the zAgile Semantic Layer and supports macros for creating templates and forms in Confluence for annotating wiki pages. 



Wikidsmart enables you to create semantically enabled forms within your wiki



Content may automatically linked with external systems. This example shows links automatically connected to Jira


About zAgile

Founded in 2006, zAgile is the open source leader in information collaboration. zAgile has solved one of the most long-standing and perplexing problems in collaboration: the problem of integrating teams, tools, processes, and knowledge. zAgile significantly reduces costs of collaboration on projects, instills consistency of methodologies across all projects, and instills confidence and predictability of delivery schedules.  



W
orld Headquarters

zAgile, Inc.
101 California Street, Suite 2450
San Francisco, CA 94111
+1 (415) 946-8910 (Office)
+1 (415) 358-5924 (Fax)
www.zAgile.com
info@zAgile.com