Popular Wiki Products
There are several wiki products out there that are worth considering, such as:
Confluence - developed by Atlassian, this is by far the most popular wiki
Notion - a wiki with great design, and free to use until a certain number of pieces of content have been created
If you get a job as a product manager tomorrow, it is likely that if the company has a wiki, it will be a Confluence wiki. For that reason, we're going to use Confluence in the following lessons to store our user stories and acceptance tests.
There are a few steps to creating a wiki with Confluence:
Create an account on Confluence using this link.
Make sure to keep a note of your password somewhere secure. You'll get a confirmation email that you will need to open to click the link within.
Start a Confluence trial using this link.
Choose a site name. It can be anything you like and will appear in your wiki URL (e.g. if your company were called Google, then you could use the name 'google' and the URL to your wiki would be http://google.atlassian.net).
Create a space called "Product". Spaces are just 'areas' in Confluence (e.g. the marketing documentation could be stored in a 'marketing' space and the product documentation could be stored in a 'product' space).
Create your first wiki page and save!
Creating your first wiki page
Let's use what we did in previous lessons:
We decided to look at a feature (called a Quiz).
We went through a process to write 14 user stories for this Quiz feature.
We then wrote acceptance tests for some of these user stories.
Now, we want to use a wiki (Confluence) to store this information so that our entire team can access it.
Therefore, we will now:
Create a wiki page for our feature called "Quiz".
Create 14 user story pages.
On the Quiz page, write down the user stories and add a link to each individual user story page.
Add the acceptance tests (which belong to a given user story) on that user story's page.
Create a feature page for our Quizzes
Typically for a feature page, I begin by creating the following sections on the wiki page and then fill them in as I go:
Background - I'll just add some general text description of the feature in question.
Screenshots - A picture can tell a thousand words, so I'll try to put one or two screenshots (graphic designs) here.
User Stories - I will create a table with one row per user story and beside each user story will be a link to a full wiki page (which will eventually include all the details of that user story).
Links - Normally for corporate or product documentation, there are some existing related wiki pages that may be useful to link to here in order to provide more context.
The following general wiki concepts were demonstrated in the screencast, but try them out for yourself:
Linking from any wiki page to any other
Text formatting into Heading1, Heading2, paragraph etc. (which helps you make nice heading sections)
Creating tables to present information (we put our user stories into a table)
Inserting images or documents (this is easily done, which means that you can store all relevant documentation (including Microsoft Powerpoint slides, Microsoft Word/Excel documents, or PDF documents) all in one central place - your wiki!