|
||||||||||||||||||||
|
||||||||||||||||||||
|
||||||||||||||||||||
商品の説明
内容説明
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. The book is a collection of practical, real-world solutions to help web project managers 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 are drawn from the experiences of the authors and from library and project management literature. The book is an essential text for library staff working as project managers or on web teams, library administrators, library school faculty and students, and web consultants working with libraries.
著者について
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.
登録情報
|
この商品にタグをつける(詳細)タグは、商品との関連性が非常に強いキーワードまたはラベルのようなものです。
タグにより、すべてのお客様がお気に入りの商品の整理と確認を行うことができます。 ※タグは初期設定で公開になっています。詳しくはこちら |
カスタマーレビュー
Amazon.com で最も参考になったカスタマーレビュー (beta)
Amazon.com:
2件のカスタマーレビュー
A review from one of the authors
2010/4/10
形式:ペーパーバック
I agree with everything that my co-author wrote in an earlier review--including running the risk of tooting my own horn by writing a review!
One of our goals was to create the book that we wished we had when we were leading our first web projects. What would I want to know if I had no idea where to start, if web projects at my library frequently created anxiety or ran amok, if I had never seen usability testing or project specifications in action? So, Jody and I included plenty of examples and advice based on both our experiences and our research.
Now that the book is published, I've been referring to it regularly. Last week, I needed a quick list of possible project team member roles. I checked the book (p.65). The week before, I helped a colleague create a draft work breakdown and project schedule for her project. I checked the book (p.240). Not long before that, I needed a way to describe a project sponsor to a potential project sponsor. I checked the book (p.45). Next time I need an example of a testing script (p.191-192), a reminder of how to best lead a meeting of librarians and programmers (p.107-108), an overview of ways to get user input (p. 139-147), or a group exercise for creating a realistic project schedule (p.236-237), I'll check the book.
One of our goals was to create the book that we wished we had when we were leading our first web projects. What would I want to know if I had no idea where to start, if web projects at my library frequently created anxiety or ran amok, if I had never seen usability testing or project specifications in action? So, Jody and I included plenty of examples and advice based on both our experiences and our research.
Now that the book is published, I've been referring to it regularly. Last week, I needed a quick list of possible project team member roles. I checked the book (p.65). The week before, I helped a colleague create a draft work breakdown and project schedule for her project. I checked the book (p.240). Not long before that, I needed a way to describe a project sponsor to a potential project sponsor. I checked the book (p.45). Next time I need an example of a testing script (p.191-192), a reminder of how to best lead a meeting of librarians and programmers (p.107-108), an overview of ways to get user input (p. 139-147), or a group exercise for creating a realistic project schedule (p.236-237), I'll check the book.
Information from one of the authors
2010/3/13
形式:ペーパーバック
Since I am one of the co-authors of this book, this review runs the risk of tooting my own horn, but I want to be sure to provide information on this page that might help potential readers make this decision: there are several outstanding core texts on web project management out there (see below) - why should you buy this one?
Jennifer and I wrote this book because libraries and similar organizations (non-profits, government agenvies) are *different* than the commercial sector. First of all, most libraries don't have dedicated web project managers, but rather people are expected to take on projects as well as their original job. Second, the library environment has numerous internal stakeholders that can make the job of moving a project forward more challenging. Third, most libraries are new to both project management techniques and formal web development practices. Finally, the institutional environment can present restrictions, such as web templates, style guides, etc. that commercial web sites don't have to deal with.
Here are some topics our book addresses that the core texts may not:
- Balancing "buy-in" from internal stakeholders with end-user input
- Effectively communicating about the project with the larger organization
- Working with library administration and in the institutional context
- Making time for selected web project techniques (knowing you may only have time to add just one technique to your repetoire)
- Working with projec team colleagues who have full-time, non-web jobs.
If you identify with any of the above challenges, I urge you to buy our book. More than anything else, I hope this book inspires conversations across the library world about effective web project management. When I started out in a major research library 10 years ago, the library had no dedicated web staff, and all projects were run by a committee of well-intentioned librarians. Things are beginning to change, but many problems have stayed the same.
If you are in the commercial sector, you probably don't need our book, and I'd recommend either of these books. For that matter, they make great reads for any project manager:
Web Project Management: Delivering Successful Commercial Web Sites
Real Web Project Management: Case Studies and Best Practices from the Trenches
Jennifer and I wrote this book because libraries and similar organizations (non-profits, government agenvies) are *different* than the commercial sector. First of all, most libraries don't have dedicated web project managers, but rather people are expected to take on projects as well as their original job. Second, the library environment has numerous internal stakeholders that can make the job of moving a project forward more challenging. Third, most libraries are new to both project management techniques and formal web development practices. Finally, the institutional environment can present restrictions, such as web templates, style guides, etc. that commercial web sites don't have to deal with.
Here are some topics our book addresses that the core texts may not:
- Balancing "buy-in" from internal stakeholders with end-user input
- Effectively communicating about the project with the larger organization
- Working with library administration and in the institutional context
- Making time for selected web project techniques (knowing you may only have time to add just one technique to your repetoire)
- Working with projec team colleagues who have full-time, non-web jobs.
If you identify with any of the above challenges, I urge you to buy our book. More than anything else, I hope this book inspires conversations across the library world about effective web project management. When I started out in a major research library 10 years ago, the library had no dedicated web staff, and all projects were run by a committee of well-intentioned librarians. Things are beginning to change, but many problems have stayed the same.
If you are in the commercial sector, you probably don't need our book, and I'd recommend either of these books. For that matter, they make great reads for any project manager:
Web Project Management: Delivering Successful Commercial Web Sites
Real Web Project Management: Case Studies and Best Practices from the Trenches
これらのレビューは参考になりましたか？
ご意見はクチコミでお聞かせください。
リストマニア
関連商品を探す
同じキーワードの商品を探す
フィードバック
- カタログ情報、または画像について報告
- 著者からのコメント
- 出版社からのコメント
|
