Are you think of developing or customizing your own software? Get strategies for managing your non-library technical staff!
If you were fortunate, you took at least one basic management class during your library or information science education. Although that provides a foundational understanding of personal, group and team dynamics, managing developers, programmers and system administrators can be quite different. In a large library, there are usually existing management structures in place. For smaller libraries that would like to "spread their wings", there will be a culture shock. Working in a purely technical environment is quite different from working in a library.
What changes should a library be expected to make to include non-library technical staff? What expectations should be set for the technical staff? Is there anything you learned in library school that is still relevant, or do we need to immerse ourselves into agile?
Christine has worked as the project lead for several technical teams in libraries and consortia. As a librarian that had just that basic management class, she has tried and failed, tried and succeeded, and continues to make changes in how she manages her technical staff, all while trying to stay true to library management policies. She'll discuss her experience, bringing experiences of others that have managed similar types of teams in smaller to mid-sized libraries and consortia.
Identify 5 of the primary principles of the agile methodology.
Discuss at least 3 expectations that non-library technical have that are different from your current library's expectations.
Summarize at least 1 way your library could modify its existing management policies to include non-library technical staff.