Date

Attendees

Goals

Discussion items

TimeItemWhoNotes
    

Page structure: all in one vs breaking up into sub-pages

Nice to have everything in one place - could edit and see everything all at once.

When teams are doing simultaneous multi-person editing at the same time, people working in different places can cause content to be bumped around. 

Live multi-person editing is a huge plus.

Can break page up into sections. Can have 2-column format


Lots of templates built into Confluence - teams didn't dig too deeply, but could accomplish what they wanted/needed.

Example: Used "User Mention" to some extent.

Didn't use changelog to document updates. Can opt to turn off notifications so people don't get emailed every time a page you follow is updated.

Directory/file structure

EDGE: need to hunt for files sometimes - files are placed in a particular folder and then linked. Without a link, hard to find.

Confluence: documents are attached to a page, either as a link or as a thumbnail.

Some documents may be irrelevant in the future as we move to embedded tables for things like risks, requirements, schedule, etc.

Link out to Google docs.

Images display and can be formatted much more easily. Zooming can be tricky (keeping consistent aspect ratio)

Sandia team recreated nearly all templates in Confluence/Google docs

Most tables can be recreated using Confluence features.

Didn't use tags, just cross-linked pages. Didn't duplicate information. Revised information each time, which gives you a clearer snapshot of the decisions that were made in each phase. Ex: requirements updates, schedule updates.


If you leave it open (for a long time), in the edit view, it would sometimes undo what one of your team members had done. When one of multiple users publishes, it publishes everyone's changes up to that point. You get notified if someone publishes, whether you're viewing or editing.

ME students were already familiar with Confluence, EE/CE students picked it up pretty quickly. Hot Wheelz team used EDGE for MSD Phase I and team appreciated the move.

Chromebook - can't use subversion

Meeting notes: Team concerns about making team member look bad if task items aren't complete.  Action items from review roll into project schedule.


Guide Perspective: Easy to use and navigate. Depending on page structure, could take an extra button to navigate.

Question: now sure how this would change for full-class deployment.


Tesla uses Jira and Confluence integrated, for tracking tickets (testing).

Action items

  • Elizabeth DeBartolo add Ken to template and see what happens when I add him to the meeting notes invitee list.