| 
  • If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • Stop wasting time looking for files and revisions. Connect your Gmail, DriveDropbox, and Slack accounts and in less than 2 minutes, Dokkio will automatically organize all your file attachments. Learn more and claim your free account.

View
 

FrontPage

Page history last edited by Jon Verville 8 years, 5 months ago
For more information, see this link: http://open.nasa.gov/maker/wiki/index.php/Wiki_Case_Study_Library

 

 

 

Comments (2)

Shannon Lantzy said

at 11:18 am on Apr 8, 2010

Trac provided an amazing set of capabilities for me and my software development team a few years back. Not only was it useful as a bug tracker and code repository, but a task tracker, decisions management tool, the wiki pages were used for all project information and planning, etc. Slap a WYSIWYG on Trac (the wiki syntax was a little troubling for non-coders) and I think you have a potentially great PM tool.

Furthermore, I think Trac can be used as more of an integrated system into work processes, rather than a repository of knowledge. Tickets have more of a back and forth (in the form of discussion and state changes). If used to project decisions, discussions, and really get embedded in work tasks, a TON of knowledge gets preserved. What's more, the context of the knowledge is there. (Unlike wikis, where people often post the end result of a decision or piece of knowledge.) This has some roots in information use and behavior literature. I'd love to chat more!

Jon Verville said

at 9:48 am on May 13, 2010

Excellent, thanks for the feedback Shannon! I like the idea of a KM tool embedded in work tasks...let's talk.

You don't have permission to comment on this page.