The software IDE and the non-software technical team

I very much like integrated development environments (IDE). Like most engineers, I suspect, I scratch a little while using them because they don't work just the way I want. However, the productivity increase is enormous in comparison to the small irritations. Yesterday, I watched the View Case Study: USDA Maximizing Collaboration with NetBeans and Codebeamer presentation. CodeBeemer adds to the NetBeans IDE development collaboration features like revision control, issue tracking, discussions, etc and all surfaced and integrated in the NetBeans approach to information design and use.

This posting is not, however, about software development but about other non-software technical groups outside of the software industry. Do these groups know about these rich tools? I would really like to see a print shop or an archeologist's dig or a municipal planning department use these tools. Perhaps the leap from the common ecology of Word documents + Excel spreadsheets + remote file system is too big a one.

Does anyone have experience with non-software teams using software IDEs to manage their work and materials?

No comments: