- Language: English
- 1091 Pages
- Published: October 2012
- Region: Global
Web Project Management for Academic Libraries
- Published: September 2009
- Region: Global
- 200 Pages
- Woodhead Publishing Ltd
Jody Condit Fagan and Jennifer A Keach, James Madison University, USA
- field-tested web project management guidance grounded in the literature of librarianship, project management and web development
- consideration of the special needs of academic libraries
- practical, step-by-step guidance for novices and experts in libraries of all sizes
- resources for further study through a bibliography of library web project management
Managing the process of building and maintaining an effective library website can be as challenging as designing the product itself. Web Project Management for Academic Libraries outlines best practices for managing successful projects related to the academic library website. This is a book of practical, real-world solutions to help web project managers and their teams plan, engage stakeholders, and lead organizations through change. Topics covered include the definition and responsibilities of a web project manager; necessary roles for the project team; effective communication practices; designing project workflow; executing the project; and usability testing and quality control. The techniques recommended in this book are drawn from the experiences of the authors and from library and project management literature. This book is an essential text not only for library staff working as project managers or on web teams, but also library administrators, library school faculty and students, and web consultants working with libraries. SHOW LESS READ MORE >
- Overview of the book’s contents and explains why web project management in academic libraries is different from other project management environments
The web project manager in academic libraries
- What is a web project manager?
- The role of web project manager
- Why academic libraries need them
- Qualifications and traits important for the job.
- What are the characteristics of academic and library environments that influence web projects?
- Institutional guidelines and requirements
- Working with the campus web office, faculty, and students
- managing projects without direct authority over staff or resources
Defining your project
- How do you distinguish projects from tasks?
- The concept of a project, how to define goals, and how to prioritize among multiple projects
- Project overviews, project sponsors, and project specifications
The academic library web team
- Why do libraries need project teams and who should be on yours?
- How project teams are different from other types of library web groups and proposes needed skills for your team
- Insufficient resources, competing work, and team size
Library web team dynamics
- Work and communication styles
- The stages of team development
- Personality types among librarians and programmers
- Making team member assignments
- Team activities to accommodate different personalities
- How do you keep your team informed and engaged?
- Early activities you can do with the team
- How to make routine meetings and one-on-one meetings successful
- How to establish good physical and virtual workspaces for your team
- The use of collaborative tools for regular communication with the team
Planning for organizational communication
- How do you plan to inform colleagues about your project?
- How will you solicit their input?
- Developing a communication plan
- The use of technology in organizations
- The challenge of forming consensus
- Ways to make decision-making transparent
Getting user input
- What are some ways to get input from users about your project?
- When you should, how you can, and who is responsible for doing so
- Methods for learning about users
- Advice for organizing, analyzing, and effectively reporting on user input
- Ethical issues related to user input, including the use of human subjects
Overall and design specifications
- What information does your team need to begin their work?
- Project specifications, feature lists, success criteria, and accessibility
- Use-case scenarios, wireframe mockups, and storyboarding
- Information architecture, accessibility, graphic standards, shared design content
- Working with designers.
- What details do you need to document for your technical team members?
- Technical requirements, application flow diagrams, and detailed specifications
- Communicating with programmers
- Testing the project
Web content specifications
- What details do you need to document about content for your project?
- Challenges specific to academic libraries' content
- Site maps, content inventories, style guides, and content plans
- Tips for writing for the web and working with graphics, audio, video, and third-party content and widgets
- Content management systems
Planning the work
- How and when can you finish your project?
- Work breakdown structures, assigning tasks, estimating time, network diagrams, and project schedules
- The relationship between scope, schedule, and resources
- Tracking the work and making changes to your plan.
Concluding your web project
- How do you end your project?
- Transition of the finished project to the final owner
- Launch communications
- Disbanding your team
- Evaluating your process.
Jody Condit Fagan is Digital Services Librarian at James Madison University, where she manages web projects relating to the library’s content systems. She has published numerous journal articles and book chapters relating to libraries and the Web and is editor of the Journal of Web Librarianship. Jennifer A Keach is Head of Digital Services at James Madison University, where she leads a department focused on web development, software and hardware for library users and staff. She has managed academic library web projects, both large and small, for more than 10 years.