RIT will permanently shut down the RIT Wiki (Confluence wiki) on February 2, 2024. Review the Wiki Shut Down Overview for information on alternative tools, exporting content from the wiki, and other FAQs.
Notes from May 2019 wiki debrief:
Hot Wheelz was spammed – were trying to set up a page linked from a QR code at Imagine so that anyone in the public could view their page. Not sure if that’s what caused it.
Sandia page is public
TurnAbout is private – even client can’t see.
On EDGE, anybody can find any project. With Confluence, you can only see the pages that you have access to.
How is customer communication handled? Via email, send design review info. Email is less detailed that wiki content, design reviews are conducted in person with client, using powerpoint that contains same content as wiki. Also used a google drive.
All four teams (Hot Wheelz, Sandia, Turnabout, water purifier) used google drive. Did working part on Drive, put final documents in wiki.
Documents that were changing were maintained as google docs, either linked or screenshotted and pasted into wiki. Google docs had permissions controlled.
Potential to eliminate some templates from MSD by embedding them in the wiki – for example, make the requirements or risks a table right in the wiki as opposed to an external template.
Or create a File list for each team (that’s correct, unlike current MSD I)
Or create a master MSD File list that holds all the templates.
Team Drives becoming more popular, but who owns them?
Can be a little bit glitchy, especially with collaborative editing – might override changes. Hot Wheelz: not a big enough problem to be a concern, didn’t lose significant progress. Turnabout: did have an issue but was able to use the page history to revert to a prior version.
Team collaborated on the wiki (Hot Wheelz, Sandia). Especially helpful in MSD II, when team members had more individual work (e.g., testing of the subsystems that you own). TurnAbout had one person do most of the updates, but the role rotated – whoever got to it first was able to do the edits. No Special knowledge.
Page layout tools are really handy – blocking tools let you lay out pages in a report format.
File download is a lot easier, can click on images and view larger, can adjust size of thumbnails, etc.
Gave us more time to focus on the content, rather than fighting with the software (like on EDGE or with subversion)
Looks like there are lots of useful macros. This is a benefit over the Drive, which has no PM tools built in.
Turnabout used Wrike for PM. Wrike is kind of like Trello, but builds it into a Gantt chart.
Hot Wheelz club uses Clubhouse (Clubhouse serves similar purpose to Jira)
Sam used Project for MSD
There are lots of options – how does MSD allow teams to customize these.
On Co-Op: One student used Confluence, others: sharepoint, SAP, Tortoise, lots of sharing individual documents via local servers.
Comment: the MSD I & II section of the front page – Hot Wheelz didn’t use any of that.
There seem to be a lot of tools built in that we haven’t used – we just scratched the surface.
Guides:
Steve – easier to review documentation on Confluence. How about having clients set up a Google Drive for teams to dump to (rather than pulling from) – would eliminate issues with giving customers access.
Ken – information on wiki is easy to walk through, still relies on team discipline to some extent (in terms of linking to prior work, etc.). Look at tools that CE/SE might bring in (ex, Jira) to integrate with Confluence. Some documents on edge, when you hit “display”, it downloads, and all you really wanted to do was take a quick look. In Confluence, it previews everything.
Harold – easier to view images.
An example of a good Confluence page would be helpful (for teams and guides).
Consider how to archive projects, and what to do with continuation projects.