DLF Wiki - User contributions [en]

DLF Project Managers Toolkit

2020-06-02T13:35:45Z

Robincpike: /* DLF-PMG Discussions and webinars */

This toolkit is a collaborative project, based on contributions by members of the [https://www.diglib.org/ Digital Library Federation's] Project Managers Group ([[DLF Project Managers Group |DLF PMG]]). First initiated by Jennifer Vinopal at New York University in February 2013, the toolkit has grown and evolved over the years as a living document to share experiences and link out to resources.

*'''What?''' A crowdsourced collection of information, tips, techniques, and tools for project managers working in digital libraries. Please contribute and share your knowledge.

*'''Why?''' Whether we realize it or not, librarians and library staff are managing projects all the time. These may be informal or formal projects, or we might not think of them as projects at all. Just the same, we could all stand to take a more organized and structured approach to planning and accomplishing our project work. Much of the project management literature and training frequently emphasizes a corporate perspective, which may not always be applicable to a library setting.

*'''Who?''' Anyone who wants to contribute. Feel free to post anonymously if you prefer, or sign the contributors list at the end of the document.

*'''How?''' Be generous with your knowledge and be respectful of what others have written. Share your experience and help others to learn from both your successes and failures.

To contribute, simply login then select the Edit tab. If you are a first time contributor, select ‘create account’ at the top right of the page. Then send a request to [mailto:info@diglib.org info@diglib.org] to get access to edit pages, add links or share documentation. Then add your name to the Contributors List at the bottom of this page.

== Getting started ==
[[File:ProjectBasics.png|thumb|right]]

=== Project Management Basics ===

Review a few '''[[Project Management Basics]]''' which are basic building blocks for the other sections of the toolkit.

=== Project Proposal Process ===
The [[Project Proposal Process]] initiates the project and is critical to planning.

=== Project Charters & Memorandum of Understandings ===

The goal of a [[Project Charter]] is to document agreement between all parties (sponsor, stakeholder, staff) about the goals, scope, and deliverables of the project. Ideally, the document defines time, scope and cost.

A Memorandum of Understanding can be used to build out a project charter and be used to manage expectations, project planning and increase transparency, communication and understanding. The University of Texas Arlington hosts a [https://rc.library.uta.edu/uta-ir/handle/10106/25646 Memorandum of Understanding Collection] which was developed by a group of librarians for library specific projects and includes a workbook and templates.

=== Project Plans ===

'''[[Project Plans]]''' flesh out more details of a project, such as scope; individual stakeholders; milestones and tasks, and roles and responsibilities within; and a timeline. It answers the same questions as a project charter, but often in more detail.

=== Project Scheduling ===

'''[[Project Scheduling]]''' captures the work that needs to be performed. It may also visualize the steps in the project. This section compares two methods: gantt charts versus kanban.

=== Workflows ===

A workflow is a sequence of steps toward the completion of a defined task used to manage repetitive processes. Workflow modelling helps participants and stakeholders understand the sequence of steps and their roles in the process. It can also help identify patterns, gaps, and bottlenecks to enhance efficiency and improve team dynamics.<ref>Shaw, E., Garcia-Spitz, C., Bragg, M., Hagedorn, K., & Porter, E. (2018). Finding the balance: Modelling successful workflows for digital library collections. Journal of Digital Media Management, 6(3), 295-311. Retrieved from [[https://escholarship.org/uc/item/9h17g7fh https://escholarship.org/uc/item/9h17g7fh]]</ref>

Included are '''[[Examples of workflows]]''' contributed by different institutions and references.

=== Project Templates ===

'''[[Project Templates]]''' are useful for expressing information in a systematic manner, streamlining processes and saving time and energy. Templates can provide clearer communication and consistency across project. Included are templates provided by different institutions.

=== Project Retrospective ===
A project retrospective is held at the end of a development sprint as part of the agile process. It can also be held by project teams not following the agile methodology. It is a meeting where the purpose is for the project team to provide feedback on what went well and what didn’t go as well during the course of the project. Qualitative feedback is given on sticky notes in the form of Happy / Sad / Angry or Start / Stop / Continue - as examples, and clustered to identify themes. The themes are used to improve the work process going forward to the next cycle or phase of the project.

=== Project Sunsetting ===
For a wide variety of reasons, you may need to stop investing time and resources in a project before completion. In these cases, it is important to consider how to document the project close-out and communicate to the team and stakeholders.

Jason Ronallo, Bret Davidson. NCSU Libraries. Sunsetting: Strategies for Portfolio Management and Decommissioning Projects. https://ronallo.com/presentations/sunsetting-dlf/slides-single-page.html Digital Library Federation Forum, Pittsburgh, PA, October 23, 2017. https://sched.co/BzsO

=== Project Portfolio Management ===

Project portfolio management is the centralized management of processes, methods, and technologies used by project managers to analyze and collectively carry out current or proposed projects.
Vinopal, Jennifer. Using Confluence for Project Portfolio Management at New York University. DLF Fall 2008. [[File:DLF2008Vinopal.pdf|thumb]]

=== Service Management ===

Service management refers to the broader strategies, policies, procedures to design, deliver, support, and manage services that bring value to an organization. Consider the four key components of value, outcomes, costs and risks.

== Project Management Software ==
This section contains a list of tools for project management, with pros and cons for each.

{| class="wikitable sortable"
|-
! Name !! Uses and Overview !! Pro || Con
|-
| [https://asana.com/ Asana] || Asana allows team members to collaborate on projects and track the progress of tasks. It works both for software development projects and other more generic projects.

||
*Free (up to 15 members)
*Great for task-based work
*Works on mobile

||
*If your team has over 15 members, you need to pay
*Doesn't do as well with project discussion
*Does not allow for private teams in the free version
*No bug/issue tracking
|-
| [https://basecamp.com/ Basecamp]
|| Basecamp allows collaborators to post messages, organize to-do lists and documents, and create group schedules. Related App: goplan
||
*intuitive design
*easy-to-use features
*email integration
*some calendar integration

||
* the first project is free, but you need to pay after that point
*scheduling support is limited
|-
| [https://trello.com/ Trello]
|| Trello is an application for tracking tasks. It allows you to move individual cards (representing tasks) as they enter different phases. Trello allows you to assign tasks to different collaborators, create due dates, and provide contextual information for the tasks to be completed.
Used by: [https://github.com/fsulib/project-managers-toolkit/blob/master/project-managers-toolkit.md#section FSU Libraries]
||
*very similar to analog/paper SCRUM boards
*feature-specific prioritization
*bug tracking
*useful for tracking action/discussion items from meetings
*able to link or attach supporting documents to cards
||
*showing the hierarchy of tasks not really possible
*not able to easily produce a to-do list (i.e. from the user's end, a list of tasks that the user is assigned to)

|-
| [https://gsuite.google.com/ Google Suite]
|| Google applications (specifically, Google Drive) is a suite of tools for creating documents collaboratively and sharing information. Google Apps include a text, spreadsheet, and slide editor, as well as applications for drawing, organizing calendars, and sharing (but not editing) other types of files.
Used by: [https://github.com/fsulib/project-managers-toolkit/blob/master/project-managers-toolkit.md#section FSU Libraries]
||
* easy to share documents with large teams for collaboration
* easily searchable and organizable
||
* you may need to use another tool to track/organize relevant documents, especially if there are a lot of them
* can be worthwhile to set up standard naming conventions for files since it is so easy to create files and folders
* if wireless is inconsistent, some files can be hard to access. use the desktop app to ensure off-line access and to organize or sync files
|

|-
| [https://www.pivotaltracker.com/ Pivotal Tracker]
|| Pivotal Tracker allows users to organize tasks by project and stories while integrating release dates and prioritization into the workflow.
||
* helps organize agile project teams that cannot meet in person
||
* only free for thirty days (paid plans)
|

|-
| [https://www.atlassian.com/software/jira Jira]
|| Issue tracking and project tracking software. JIRA allows teams to "create and estimate stories, build a sprint backlog, visualize activity, measure team velocity, and report on progress."
||
* works well for teams who use Scrum project management methods
||
* [https://www.atlassian.com/software/jira/pricing paid service] ($10 for teams of up to 10; $75 and more for 15 teams and up)
|

|-
| [https://www.redmine.org/ Redmine]
|| Redmine allows you to track issues, latest project news, and organize projects by members and contributors. You can associate files with given projects, create Gantt charts and calendars, and create wikis to document projects. Redmine has a demo site that allows you to see how it looks in action.
||
* open source
* plug-ins allow for extensibility
* Ability to manage multiple simultaneous projects
||
* doesn't work well with projects that aren't typical software development projects
|

|-
| [https://slack.com/ Slack]
|| Slack is a communication app for teams. It integrates with several of the project management tools on this list, and allows team members to communicate more easily and informally than through email.
Used by: [https://github.com/fsulib/project-managers-toolkit/blob/master/project-managers-toolkit.md#section FSU Libraries]
||
* allows for easy communication between entire organizations, small groups within the organization, and individual members
* integrates with many other applications (e.g. Google Docs, JIRA, Trello, GitHub, etc.)
* allows members to easily set up reminders, take notes-to-self, customize alerts
* can be used on the web or via desktop app across devices
||
* free version only has a 10,000 message capacity (older messages get deleted)
* paid version has additional integrations such as single sign-on, customizable message retention period (ex. 90 day retention period or longer)
* Slack users sharing files (on free or paid versions) may not understand that it is not a system of record to store information; if retaining message history is important for project documentation, threads can be exported and copied to project documentation
|

|-
| [https://www.smartsheet.com/ Smartsheet]
|| Smartsheet allows a team to collaborate and communicate with a spreadsheet-style interface. It allows for file sharing, alerts and reminders, the creation of Gantt charts, and other features that will help to organize your projects.
||
* relatively simple (based on spreadsheets)
* Customizable and flexible
* links to other tools and services (like Google Docs)
||
* paid service
|

|-
| [https://freedcamp.com/ FreedCamp]
|| FreedCamp allows a team to collaborate and communicate on projects through tasks and discussion boards. It allows for file sharing, alerts and reminders, time tracking and milestones as well as other features that will help to organize your projects.
||
* relatively simple and easy to get started on a new project
* robust free service - a free account allows for unlimited users, projects, tasks, and storage
* allows for you to assign tasks, leave comments on tasks and use the system as a project tracker over time
||
* cannot assign a task to multiple people - it can be assigned to one person or everyone
* in the free version, subtasks are very basic and you cannot assign them to specific people
|

|}

=== Other general software-independent recommendations for project management ===

*Wikis for project documents and documentation
*Google Docs or another collaborative document editor for the creation of project charter, meeting notes, etc. with separate document (or folder) for meeting notes
*Ticket-trackers
*Planning Poker
*After-Action Reviews or Retrospectives vis tools such as [https://funretro.github.io/distributed/ FunRetro] or [https://stormboard.com/ Stormboard]
*Scheduling using Doodle or Google Sheets is useful for tracking team members' schedules

== Professional Development ==
Professional development is an ongoing part of a project management career. A successful project manager possesses a blended set of hard and soft skills acquired over time. Training is offered by the [https://www.pmi.org Project Management Institute] and various local education providers.

== Resources and Other Toolkits ==
There are lots of great articles, presentations and grey lit out there on project management and digital libraries.

We've created a Zotero Group library at https://www.zotero.org/groups/2205688/dlf_pmg? and encourage you to add more when you read something good.

*[https://dhlab.yale.edu/guides/project-planning.html Yale DHLab Toolkit]

== DLF-PMG Discussions and webinars ==
{| class="wikitable" border="1"
|-
! Topic
! Date
! Facilitator(s)
! Format
|-
| Labor in Digital Work
| February 12-16, 2018
| Robin Pike & Sarah Severson
| Multi-day discussion available through the [https://lists.clir.org/cgi-bin/wa?SUBED1=DLF-PM-GROUP&A=1 listserv archive] and [https://lists.clir.org/cgi-bin/wa?A2=DLF-PM-GROUP;c1c093d7.1802 summary]
|-
| Tools for Project Management
| April 3-10, 2018
| Christine Quirion
| Multi-day discussion available in full through the [https://lists.clir.org/cgi-bin/wa?SUBED1=DLF-PM-GROUP&A=1 listserv archive] and [https://docs.google.com/document/d/1by9MSoaA6nlnKjmlOkQUwoMQ2RTzd_CmgPM38xpemCo/edit?usp=sharing summary]
|-
| Service and Portfolio Management
| August 13-17, 2018
| Elizabeth German
| Multi-day discussion available through the [https://lists.clir.org/cgi-bin/wa?SUBED1=DLF-PM-GROUP&A=1 listserv archive] and [https://docs.google.com/document/d/1A2RhJxn32ihj08AjMruoofLK8Gc6s7MiSGcPsXU_irY/edit?usp=sharing summary]
|-
| Project Portfolio Management Demo
| April 5, 2019
| Cristela Garcia-Spitz
| Digital Initiatives Librarian Cristela Garcia-Spitz discussed project portfolio management and shared a demo of how digital projects are being tracked by the UC San Diego Library's Digital Library Development Program using Confluence and JIRA. She also covered some of the goals and challenges of portfolio management. The presentation recording is available at: https://www.youtube.com/watch?v=UtLLmFWQeQ8 and the slides are available at: https://escholarship.org/uc/item/2bf7n6tp
|-
| Before Action Review
| January 10, 2020
| Melissa Wisner
| The hour session provides an introduction to Before Action Reviews and how to facilitate meaningful intake collection with stakeholders by Melissa Wisner, the IT Project and Portfolio Management Librarian at NCSU Libraries. The presentation recording is available at: https://www.youtube.com/watch?v=UPq-6Zgh6kM
|-
| How managers, project managers, and others are adjusting to telework and closures
| April 10, 2020
| Robin Pike
| As managers and project managers, we’ve had to quickly adjust priorities and protocols during the past month as many of our institutions move to full-time telework. The Project Managers Group invites you to a moderated discussion to share practices, challenges, ingenious solutions, and more, with the goal of better preparing ourselves and the people we manage for continued telework and even confirming that what we’re doing is the best we can do in this uncertain situation. [https://lists.clir.org/cgi-bin/wa?A0=DLF-PM-GROUP Listserv archive].
|-
|}

== Contributors ==
To contribute to the Project Managers Toolkit login at the top right of the page, then select the Edit tab. If you are a first-time contributor, select ‘create account’ at the top right of the page and send a request to info@diglib.org to get access to edit pages, add links, or share documentation. (We had to add in this step because the bots were getting us.) Then add your name to the Contributors List.
*Andy Ashton, Brown University
*Carolyn Caizzi, Northwestern University
*Kathleen Cameron
*Jason Casden, North Carolina State University
*Tim Clarke, Muhlenberg College
*Tom Cramer, Stanford University
*Cristela Garcia-Spitz, UC San Diego Library
*Joshua Honn, Northwestern University
*Katherine Kott, Independent Consultant
*Christine Malinowski, Massachusetts Institute of Technology
*Rafia Mirza, UT Arlington, TX
*Lisa McAulay, UCLA
*Sandra McIntyre, Mountain West Digital Library
*Alan Pike, Emory Center for Digital Scholarship
*Robin C. Pike, University of Maryland
*Christine Quirion, Massachusetts Institute of Technology
*Sarah Severson, McGill University Library
*Sarah Stanley, Florida State University
*Joan Starr, California Digital Library
*Becky Thoms, Utah State University Libraries
*Micah Vandegrift, Florida State University Libraries
*Jennifer Vinopal, New York University
*Cliff Wulfman, Princeton University
*Cynthia York, Johns Hopkins University

{| class="wikitable" border="1"
|'''Interested in related resources?''' Check out DLF's [[About DLF and the Organizers' Toolkit | Organizers' Toolkit]]!
|}

DLF Project Managers Toolkit

2020-03-27T19:39:41Z

Robincpike: /* DLF-PMG Discussions and webinars */

This toolkit is a collaborative project, based on contributions by members of the [https://www.diglib.org/ Digital Library Federation's] Project Managers Group ([[DLF Project Managers Group |DLF PMG]]). First initiated by Jennifer Vinopal at New York University in February 2013, the toolkit has grown and evolved over the years as a living document to share experiences and link out to resources.

*'''What?''' A crowdsourced collection of information, tips, techniques, and tools for project managers working in digital libraries. Please contribute and share your knowledge.

*'''Why?''' Whether we realize it or not, librarians and library staff are managing projects all the time. These may be informal or formal projects, or we might not think of them as projects at all. Just the same, we could all stand to take a more organized and structured approach to planning and accomplishing our project work. Much of the project management literature and training frequently emphasizes a corporate perspective, which may not always be applicable to a library setting.

*'''Who?''' Anyone who wants to contribute. Feel free to post anonymously if you prefer, or sign the contributors list at the end of the document.

*'''How?''' Be generous with your knowledge and be respectful of what others have written. Share your experience and help others to learn from both your successes and failures.

To contribute, simply login then select the Edit tab. If you are a first time contributor, select ‘create account’ at the top right of the page. Then send a request to [mailto:info@diglib.org info@diglib.org] to get access to edit pages, add links or share documentation. Then add your name to the Contributors List at the bottom of this page.

== Getting started ==
[[File:ProjectBasics.png|thumb|right]]

=== Project Management Basics ===

Review a few '''[[Project Management Basics]]''' which are basic building blocks for the other sections of the toolkit.

=== Project Proposal Process ===
The [[Project Proposal Process]] initiates the project and is critical to planning.

=== Project Charters & Memorandum of Understandings ===

The goal of a [[Project Charter]] is to document agreement between all parties (sponsor, stakeholder, staff) about the goals, scope, and deliverables of the project. Ideally, the document defines time, scope and cost.

A Memorandum of Understanding can be used to build out a project charter and be used to manage expectations, project planning and increase transparency, communication and understanding. The University of Texas Arlington hosts a [https://rc.library.uta.edu/uta-ir/handle/10106/25646 Memorandum of Understanding Collection] which was developed by a group of librarians for library specific projects and includes a workbook and templates.

=== Project Plans ===

'''[[Project Plans]]''' flesh out more details of a project, such as scope; individual stakeholders; milestones and tasks, and roles and responsibilities within; and a timeline. It answers the same questions as a project charter, but often in more detail.

=== Project Scheduling ===

'''[[Project Scheduling]]''' captures the work that needs to be performed. It may also visualize the steps in the project. This section compares two methods: gantt charts versus kanban.

=== Workflows ===

A workflow is a sequence of steps toward the completion of a defined task used to manage repetitive processes. Workflow modelling helps participants and stakeholders understand the sequence of steps and their roles in the process. It can also help identify patterns, gaps, and bottlenecks to enhance efficiency and improve team dynamics.<ref>Shaw, E., Garcia-Spitz, C., Bragg, M., Hagedorn, K., & Porter, E. (2018). Finding the balance: Modelling successful workflows for digital library collections. Journal of Digital Media Management, 6(3), 295-311. Retrieved from [[https://escholarship.org/uc/item/9h17g7fh https://escholarship.org/uc/item/9h17g7fh]]</ref>

Included are '''[[Examples of workflows]]''' contributed by different institutions and references.

=== Project Templates ===

'''[[Project Templates]]''' are useful for expressing information in a systematic manner, streamlining processes and saving time and energy. Templates can provide clearer communication and consistency across project. Included are templates provided by different institutions.

=== Project Retrospective ===
A project retrospective is held at the end of a development sprint as part of the agile process. It can also be held by project teams not following the agile methodology. It is a meeting where the purpose is for the project team to provide feedback on what went well and what didn’t go as well during the course of the project. Qualitative feedback is given on sticky notes in the form of Happy / Sad / Angry or Start / Stop / Continue - as examples, and clustered to identify themes. The themes are used to improve the work process going forward to the next cycle or phase of the project.

=== Project Sunsetting ===
For a wide variety of reasons, you may need to stop investing time and resources in a project before completion. In these cases, it is important to consider how to document the project close-out and communicate to the team and stakeholders.

Jason Ronallo, Bret Davidson. NCSU Libraries. Sunsetting: Strategies for Portfolio Management and Decommissioning Projects. https://ronallo.com/presentations/sunsetting-dlf/slides-single-page.html Digital Library Federation Forum, Pittsburgh, PA, October 23, 2017. https://sched.co/BzsO

=== Project Portfolio Management ===

Project portfolio management is the centralized management of processes, methods, and technologies used by project managers to analyze and collectively carry out current or proposed projects.
Vinopal, Jennifer. Using Confluence for Project Portfolio Management at New York University. DLF Fall 2008. [[File:DLF2008Vinopal.pdf|thumb]]

=== Service Management ===

Service management refers to the broader strategies, policies, procedures to design, deliver, support, and manage services that bring value to an organization. Consider the four key components of value, outcomes, costs and risks.

== Project Management Software ==
This section contains a list of tools for project management, with pros and cons for each.

{| class="wikitable sortable"
|-
! Name !! Uses and Overview !! Pro || Con
|-
| [https://asana.com/ Asana] || Asana allows team members to collaborate on projects and track the progress of tasks. It works both for software development projects and other more generic projects.

||
*Free (up to 15 members)
*Great for task-based work
*Works on mobile

||
*If your team has over 15 members, you need to pay
*Doesn't do as well with project discussion
*Does not allow for private teams in the free version
*No bug/issue tracking
|-
| [https://basecamp.com/ Basecamp]
|| Basecamp allows collaborators to post messages, organize to-do lists and documents, and create group schedules. Related App: goplan
||
*intuitive design
*easy-to-use features
*email integration
*some calendar integration

||
* the first project is free, but you need to pay after that point
*scheduling support is limited
|-
| [https://trello.com/ Trello]
|| Trello is an application for tracking tasks. It allows you to move individual cards (representing tasks) as they enter different phases. Trello allows you to assign tasks to different collaborators, create due dates, and provide contextual information for the tasks to be completed.
Used by: [https://github.com/fsulib/project-managers-toolkit/blob/master/project-managers-toolkit.md#section FSU Libraries]
||
*very similar to analog/paper SCRUM boards
*feature-specific prioritization
*bug tracking
*useful for tracking action/discussion items from meetings
*able to link or attach supporting documents to cards
||
*showing the hierarchy of tasks not really possible
*not able to easily produce a to-do list (i.e. from the user's end, a list of tasks that the user is assigned to)

|-
| [https://gsuite.google.com/ Google Suite]
|| Google applications (specifically, Google Drive) is a suite of tools for creating documents collaboratively and sharing information. Google Apps include a text, spreadsheet, and slide editor, as well as applications for drawing, organizing calendars, and sharing (but not editing) other types of files.
Used by: [https://github.com/fsulib/project-managers-toolkit/blob/master/project-managers-toolkit.md#section FSU Libraries]
||
* easy to share documents with large teams for collaboration
* easily searchable and organizable
||
* you may need to use another tool to track/organize relevant documents, especially if there are a lot of them
* can be worthwhile to set up standard naming conventions for files since it is so easy to create files and folders
* if wireless is inconsistent, some files can be hard to access. use the desktop app to ensure off-line access and to organize or sync files
|

|-
| [https://www.pivotaltracker.com/ Pivotal Tracker]
|| Pivotal Tracker allows users to organize tasks by project and stories while integrating release dates and prioritization into the workflow.
||
* helps organize agile project teams that cannot meet in person
||
* only free for thirty days (paid plans)
|

|-
| [https://www.atlassian.com/software/jira Jira]
|| Issue tracking and project tracking software. JIRA allows teams to "create and estimate stories, build a sprint backlog, visualize activity, measure team velocity, and report on progress."
||
* works well for teams who use Scrum project management methods
||
* [https://www.atlassian.com/software/jira/pricing paid service] ($10 for teams of up to 10; $75 and more for 15 teams and up)
|

|-
| [https://www.redmine.org/ Redmine]
|| Redmine allows you to track issues, latest project news, and organize projects by members and contributors. You can associate files with given projects, create Gantt charts and calendars, and create wikis to document projects. Redmine has a demo site that allows you to see how it looks in action.
||
* open source
* plug-ins allow for extensibility
* Ability to manage multiple simultaneous projects
||
* doesn't work well with projects that aren't typical software development projects
|

|-
| [https://slack.com/ Slack]
|| Slack is a communication app for teams. It integrates with several of the project management tools on this list, and allows team members to communicate more easily and informally than through email.
Used by: [https://github.com/fsulib/project-managers-toolkit/blob/master/project-managers-toolkit.md#section FSU Libraries]
||
* allows for easy communication between entire organizations, small groups within the organization, and individual members
* integrates with many other applications (e.g. Google Docs, JIRA, Trello, GitHub, etc.)
* allows members to easily set up reminders, take notes-to-self, customize alerts
* can be used on the web or via desktop app across devices
||
* free version only has a 10,000 message capacity (older messages get deleted)
* paid version has additional integrations such as single sign-on, customizable message retention period (ex. 90 day retention period or longer)
* Slack users sharing files (on free or paid versions) may not understand that it is not a system of record to store information; if retaining message history is important for project documentation, threads can be exported and copied to project documentation
|

|-
| [https://www.smartsheet.com/ Smartsheet]
|| Smartsheet allows a team to collaborate and communicate with a spreadsheet-style interface. It allows for file sharing, alerts and reminders, the creation of Gantt charts, and other features that will help to organize your projects.
||
* relatively simple (based on spreadsheets)
* Customizable and flexible
* links to other tools and services (like Google Docs)
||
* paid service
|

|-
| [https://freedcamp.com/ FreedCamp]
|| FreedCamp allows a team to collaborate and communicate on projects through tasks and discussion boards. It allows for file sharing, alerts and reminders, time tracking and milestones as well as other features that will help to organize your projects.
||
* relatively simple and easy to get started on a new project
* robust free service - a free account allows for unlimited users, projects, tasks, and storage
* allows for you to assign tasks, leave comments on tasks and use the system as a project tracker over time
||
* cannot assign a task to multiple people - it can be assigned to one person or everyone
* in the free version, subtasks are very basic and you cannot assign them to specific people
|

|}

=== Other general software-independent recommendations for project management ===

*Wikis for project documents and documentation
*Google Docs or another collaborative document editor for the creation of project charter, meeting notes, etc. with separate document (or folder) for meeting notes
*Ticket-trackers
*Planning Poker
*After-Action Reviews or Retrospectives vis tools such as [https://funretro.github.io/distributed/ FunRetro] or [https://stormboard.com/ Stormboard]
*Scheduling using Doodle or Google Sheets is useful for tracking team members' schedules

== Professional Development ==
Professional development is an ongoing part of a project management career. A successful project manager possesses a blended set of hard and soft skills acquired over time. Training is offered by the [https://www.pmi.org Project Management Institute] and various local education providers.

== Resources and Other Toolkits ==
There are lots of great articles, presentations and grey lit out there on project management and digital libraries.

We've created a Zotero Group library at https://www.zotero.org/groups/2205688/dlf_pmg? and encourage you to add more when you read something good.

*[https://dhlab.yale.edu/guides/project-planning.html Yale DHLab Toolkit]

== DLF-PMG Discussions and webinars ==
{| class="wikitable" border="1"
|-
! Topic
! Date
! Facilitator(s)
! Format
|-
| Labor in Digital Work
| February 12-16, 2018
| Robin Pike & Sarah Severson
| Multi-day discussion available through the [https://lists.clir.org/cgi-bin/wa?SUBED1=DLF-PM-GROUP&A=1 listserv archive] and [https://lists.clir.org/cgi-bin/wa?A2=DLF-PM-GROUP;c1c093d7.1802 summary]
|-
| Tools for Project Management
| April 3-10, 2018
| Christine Quirion
| Multi-day discussion available in full through the [https://lists.clir.org/cgi-bin/wa?SUBED1=DLF-PM-GROUP&A=1 listserv archive] and [https://docs.google.com/document/d/1by9MSoaA6nlnKjmlOkQUwoMQ2RTzd_CmgPM38xpemCo/edit?usp=sharing summary]
|-
| Service and Portfolio Management
| August 13-17, 2018
| Elizabeth German
| Multi-day discussion available through the [https://lists.clir.org/cgi-bin/wa?SUBED1=DLF-PM-GROUP&A=1 listserv archive] and [https://docs.google.com/document/d/1A2RhJxn32ihj08AjMruoofLK8Gc6s7MiSGcPsXU_irY/edit?usp=sharing summary]
|-
| Project Portfolio Management Demo
| April 5, 2019
| Cristela Garcia-Spitz
| Digital Initiatives Librarian Cristela Garcia-Spitz discussed project portfolio management and shared a demo of how digital projects are being tracked by the UC San Diego Library's Digital Library Development Program using Confluence and JIRA. She also covered some of the goals and challenges of portfolio management. The presentation recording is available at: https://www.youtube.com/watch?v=UtLLmFWQeQ8 and the slides are available at: https://escholarship.org/uc/item/2bf7n6tp
|-
| Before Action Review
| January 10, 2020
| Melissa Wisner
| The hour session provides an introduction to Before Action Reviews and how to facilitate meaningful intake collection with stakeholders by Melissa Wisner, the IT Project and Portfolio Management Librarian at NCSU Libraries. The presentation recording is available at: https://www.youtube.com/watch?v=UPq-6Zgh6kM
|-
| How managers, project managers, and others are adjusting to telework and closures
| April 10, 2020
| Robin Pike
| As managers and project managers, we’ve had to quickly adjust priorities and protocols during the past month as many of our institutions move to full-time telework. The Project Managers Group invites you to a moderated discussion to share practices, challenges, ingenious solutions, and more, with the goal of better preparing ourselves and the people we manage for continued telework and even confirming that what we’re doing is the best we can do in this uncertain situation. Join Zoom Meeting: https://clirdlf.zoom.us/j/815230807
|-
|}

== Contributors ==
To contribute to the Project Managers Toolkit login at the top right of the page, then select the Edit tab. If you are a first-time contributor, select ‘create account’ at the top right of the page and send a request to info@diglib.org to get access to edit pages, add links, or share documentation. (We had to add in this step because the bots were getting us.) Then add your name to the Contributors List.
*Andy Ashton, Brown University
*Carolyn Caizzi, Northwestern University
*Kathleen Cameron
*Jason Casden, North Carolina State University
*Tim Clarke, Muhlenberg College
*Tom Cramer, Stanford University
*Cristela Garcia-Spitz, UC San Diego Library
*Joshua Honn, Northwestern University
*Katherine Kott, Independent Consultant
*Christine Malinowski, Massachusetts Institute of Technology
*Rafia Mirza, UT Arlington, TX
*Lisa McAulay, UCLA
*Sandra McIntyre, Mountain West Digital Library
*Alan Pike, Emory Center for Digital Scholarship
*Robin C. Pike, University of Maryland
*Christine Quirion, Massachusetts Institute of Technology
*Sarah Severson, McGill University Library
*Sarah Stanley, Florida State University
*Joan Starr, California Digital Library
*Becky Thoms, Utah State University Libraries
*Micah Vandegrift, Florida State University Libraries
*Jennifer Vinopal, New York University
*Cliff Wulfman, Princeton University
*Cynthia York, Johns Hopkins University

{| class="wikitable" border="1"
|'''Interested in related resources?''' Check out DLF's [[About DLF and the Organizers' Toolkit | Organizers' Toolkit]]!
|}

DLF Project Managers Group

2020-01-31T20:02:39Z

Robincpike: /* 2018-2019 Steering Committee */

The DLF Project Managers group is an informal community within the larger DLF community. The group provides a forum for sharing project management methodologies and tools, alongside broader discussions that consider issues such as portfolio management and cross-organizational communication. The group also looks to keep pace with the dynamic digital library landscape, by bringing new and evolving project management practices to the attention and mutual benefit of our colleagues.

== Background ==
The [https://www.diglib.org/groups/pmg/ Digital Library Federation Project Managers Group (DLF PMG)] was formed in 2008 to acknowledge the intersection of the disciplines of project management and library technology. [https://www.diglib.org/groups/pmg/ Past meeting presentations and notes 2008-2017] are available on the DLF website.

== Project Management Toolkit ==
The [[DLF Project Managers Toolkit]] is a collaborative project, based on contributions by members of DLF PMG and the public. The Toolkit offers crowdsourced information, tips, techniques, and tools for project managers working in or with digital libraries. First initiated as a Google doc by Jennifer Vinopal at New York University in February 2013, the toolkit has grown and evolved over the years as a living document to share experiences and link out to resources.

To contribute to the Project Managers Toolkit login at the top right of the page, then select the Edit tab. If you are a first-time contributor, select ‘create account’ at the top right of the page and send a request to [mailto:info@diglib.org info@diglib.org] to get access to edit pages, add links, or share documentation. (We had to add in this step because the bots were getting us.) Then add your name to the Contributors List.

== Get Involved ==
1. Join the [https://lists.clir.org/cgi-bin/wa?SUBED1=DLF-PM-GROUP&A=1 DLF PMG listserv] open to anyone interested in digital library project management.

2. Contribute to the [[DLF Project Managers Toolkit]]. See instructions in the section above.

3. Join in the 2018 DLF-PM Group Bi-Monthly Discussion. To volunteer to moderate a discussion or suggest a topic edit the table below or email anyone on the steering committee.
{| class="wikitable" border="1"
|-
! Topic
! Date
! Facilitator(s)
! Format
|-
| Labor in Digital Work
| February 12-16, 2018
| Robin Pike & Sarah Severson
| Multi-day discussion available through the [https://lists.clir.org/cgi-bin/wa?SUBED1=DLF-PM-GROUP&A=1 listserv archive] and [https://lists.clir.org/cgi-bin/wa?A2=DLF-PM-GROUP;c1c093d7.1802 summary]
|-
| Tools for Project Management
| April 3-10, 2018
| Christine Quirion
| Multi-day discussion available in full through the [https://lists.clir.org/cgi-bin/wa?SUBED1=DLF-PM-GROUP&A=1 listserv archive] and [https://docs.google.com/document/d/1by9MSoaA6nlnKjmlOkQUwoMQ2RTzd_CmgPM38xpemCo/edit?usp=sharing summary]
|-
| Service and Portfolio Management
| August 13-17, 2018
| Elizabeth German
| Multi-day discussion available through the [https://lists.clir.org/cgi-bin/wa?SUBED1=DLF-PM-GROUP&A=1 listserv archive] and [https://docs.google.com/document/d/1A2RhJxn32ihj08AjMruoofLK8Gc6s7MiSGcPsXU_irY/edit?usp=sharing summary]
|-
| Scope Creep
| TBD
| Brett Currier
| TBD
|-
| Sunsetting for Projects
| TBD
| TBD
|
|-

| Agile Development
| TBD
| TBD
|}

4. Attend the Project Managers Working Meeting at the DLF Forum each year, where members of the group discuss various needs and topics and work to identify ways to support them. We've just confirmed we will be hosting a working breakfast/lunch at the 2018 Forum so you there [https://sched.co/FVBr on Monday, October 15 • 12:00pm - 1:30pm] ! You can see past years programs below.

5. Join the DLF-PM Steering Committee.
The steering committee meets online throughout the year to work on projects and organizes the annual forum working breakfast/lunch session. Anyone is welcome to join throughout the year. Email the Chair for more information or to join future meetings.

=== 2018-2019 Steering Committee ===
::[mailto:rpike@umd.edu Robin Pike], University of Maryland, College Park, Chair 
::Cristela Garcia Spitz, UC San Diego 
::Allyssa Guzman, University of Texas at Austin 
::Peter Herdrich, The Antiquities Coalition 
::Anu Paul, Yale University 
::Christine Quirion, MIT, Chair 
::Krystal Thomas, Florida State University 
::Becky Thoms, Utah State University 
::Kate Thornhill, University of Oregon 
::Angela Waarala, University of Illinois 
::Cynthia York, Johns Hopkins University 

== Past meetings ==

* [https://sched.co/FVBr/ DLF 2018, PMG Meeting, Las Vegas, Nevada] / [https://docs.google.com/document/d/1XjW530Nj_yJGUCOIBJ_Qwk-EPj8EjIorrsCYST4cp7o/edit / DLF PMG 2018 Shared Notes]
* [https://dlfforum2017.sched.com/event/Bzt9 DLF 2017, PMG Meeting, Pittsburgh, Pennsylvania] / [https://docs.google.com/document/d/1jnkUwe5vSFOEoGQ5G8vBwtqH59NWgexolbfhWN_pXN0/edit#/ DLF PMG 2017 Shared Notes]
* [http://sched.co/8LGm DLF 2016, PMG Meeting, Milwaukee, Wisconsin] / [https://docs.google.com/document/d/1SITeNgNEWoqML4xKZ3FS5TOayFxhrGEfNn4kBmTCuhs/edit DLF PMG 2016 Shared Notes]
* [http://sched.co/4H10 DLF 2015, PMG Meeting, Vancouver, British Columbia, Canada] / [https://docs.google.com/document/d/1bOyf2JWLRLl2UUshosA5CwWGiv0yw3nAIwQG5XoCzRs/edit#heading=h.c6q1qq3h66in DLF PMG 2015 Shared Notes]
* [https://www.diglib.org/dlf-events/2014forum/program/21z/ DLF 2014, PMG Meeting, Atlanta, Georgia, October 28, 2014] / [https://docs.google.com/document/d/1gB3qA1tTPmbOh1_fXMoH9UyKHOTjnCUXVVeXr930FpE/edit DLF PMG 2014 Shared Notes]
* [https://www.diglib.org/project-managers-group-annual-meeting-building-alliances/ DLF 2013, Post-Conference PMG Meeting, Austin, Texas, November 7, 2013] / [https://docs.google.com/document/d/1bnfWxwZrrWKxlaP2bLyRV0FR0p0nRht44_v20KDke98/edit DLF PMG 2013 Shared Notes]
* [https://www.diglib.org/dlf-events/2012forum/2012-dlf-forum-schedule/project-managers-meeting/ DLF 2012, Pre-Conference PMG Meeting, Denver, Colorado, November 3, 2012] / [https://docs.google.com/document/d/1gClTm_UlbV2dN7vrVK79QTozoj4nFXsAvkEN33CkFVI/edit DLF PMG 2012 Shared Notes]
* [https://www.diglib.org/dlf-events/2011forum/schedule/project-managers-meeting/ DLF 2011, Post-Conference PMG Meeting, DLF 2011, Baltimore, Maryland, November 2, 2011] / [https://docs.google.com/document/d/1WZvQzi-WUoUWGm7lUveSaGlUvho6PaEioCUiOWcQq5I/edit DLF PMG 2011 Shared Notes]
* [https://www.diglib.org/wp-content/uploads/sites/3/2011/01/schedule0917.pdf DLF Fall Forum 2010, Pre-Conference PMG Meeting, Palo Alto, California, November 1, 2010] / [https://www.diglib.org/dlf-events/fall2010/presentations/ DLF PMG Fall 2010 Presentations]
* [https://old.diglib.org/forums/fall2009/2009fallschedule.htm DLF Fall Forum 2009, PMG Meeting, Long Beach, California, November 12, 2009] / [https://docs.google.com/document/d/15_ZHHrQzXyHX4QPcyNS57LBtn4kKfNX_cXvKUAGkue8/edit DLF PMG Fall 2009 Shared Notes]
* [http://old.diglib.org/forums/spring2009/2009springprogram.htm DLF Spring Forum 2009, Pre-Conference PMG Meeting, Raleigh, North Carolina, May 4, 2009]
* [http://old.diglib.org/forums/fall2008/2008fallprogram.htm DLF Fall Forum 2008, Post-Conference PMG Meeting, Providence, Rhode Island, November 14, 2008]

DLF Project Managers Toolkit

2018-10-12T22:51:26Z

Robincpike:

This toolkit is a collaborative project, based on contributions by members of the [https://www.diglib.org/ Digital Library Federation's] Project Managers Group ([[DLF Project Managers Group |DLF PMG]]). First initiated by Jennifer Vinopal at New York University in February 2013, the toolkit has grown and evolved over the years as a living document to share experiences and link out to resources.

*'''What?''' A crowdsourced collection of information, tips, techniques, and tools for project managers working in digital libraries. Please contribute and share your knowledge.

*'''Why?''' Whether we realize it or not, librarians and library staff are managing projects all the time. These may be informal or formal projects, or we might not think of them as projects at all. Just the same, we could all stand to take a more organized and structured approach to planning and accomplishing our project work. Much of the project management literature and training frequently emphasizes a corporate perspective, which may not always be applicable to a library setting.

*'''Who?''' Anyone who wants to contribute. Feel free to post anonymously if you prefer, or sign the contributors list at the end of the document.

*'''How?''' Be generous with your knowledge and be respectful of what others have written. Share your experience and help others to learn from both your successes and failures.

To contribute, simply login then select the Edit tab. If you are a first time contributor, select ‘create account’ at the top right of the page. Then send a request to [mailto:info@diglib.org info@diglib.org] to get access to edit pages, add links or share documentation.

== Getting started ==
[[File:ProjectBasics.png|thumb|right]]
=== Project Management Basics ===

Review a few '''[[Project Management Basics]]''' which are basic building blocks for the other sections of the toolkit.

=== Project Charters & Memorandum of Understandings ===

The goal of a project charter is to document agreement between all parties (sponsor, stakeholder, staff) about the goals, scope, and deliverables of the project. Ideally, the document defines time, scope and cost.

It is useful to use this time to answer questions about cost/benefit and the extent to which people can actually reasonably contribute to the project. The Project Management Group recommends discussing the following questions at this stage:

'''Why?'''
What are the objectives of the project?
What are the expected benefits of the project?
'''Scope?'''
What is the scope of the project? (specifically, what's not in scope...)
How will we know the the project is done?
'''Who are the stakeholders?'''
Who is the end user audience?Who?
Who is going to work on the project?
Who is managing the project?
Who is/are the sponsors of the project?
'''How much time can participants reasonably spend on the project'''

After the answers to these questions have been decided upon, the Project Charter itself should be drafted. The following is the basic format of a Project Charter:

Project name
Description (high-level statement of your project goal)
Success criteria (how will we know when the project is done?) – SMART goals
Requirements (deliverables, options, & out of scope)
Project team (including roles)
Milestones/Schedule (high-level + proposed dates)

Drafting the charter is an iterative process:

Write a draft
Share it with project team
Share it with stakeholders
Rewrite
Repeat until consensus

The [https://project-charter-template.casual.pm/ Project Charter Toolkit] can be a useful resource whether you are looking to understand what a project charter is or you’re just looking for some fresh ideas on laying out/structuring your particular charter. They have free templates to download, samples, etc.

A Memorandum of Understanding can be used to build out a project charter and be used to manage expectations, project planning and increase transparency, communication and understanding. The University of Texas Arlington hosts a [https://rc.library.uta.edu/uta-ir/handle/10106/25646 Memorandum of Understanding Collection] which was developed by a group of librarians for library specific projects and includes a workbook and templates.

=== Project Plans ===

'''[[Project Plans]]''' flesh out more details of a project, such as scope; individual stakeholders; milestones and tasks, and roles and responsibilities within; and a timeline. It answers the same questions as a project charter, but often in more detail.

=== Project Scheduling ===

'''[[Project Scheduling]]''' captures the work that needs to be performed. It may also visualize the steps in the project. This section compares two methods: gantt charts versus kanban.

=== Workflows ===

A workflow is a sequence of steps toward the completion of a defined task used to manage repetitive processes. Workflow modelling helps participants and stakeholders understand the sequence of steps and their roles in the process. It can also help identify patterns, gaps, and bottlenecks to enhance efficiency and improve team dynamics.<ref>Shaw, E., Garcia-Spitz, C., Bragg, M., Hagedorn, K., & Porter, E. (2018). Finding the balance: Modelling successful workflows for digital library collections. Journal of Digital Media Management, 6(3), 295-311. Retrieved from [[https://escholarship.org/uc/item/9h17g7fh https://escholarship.org/uc/item/9h17g7fh]]</ref>

Included are '''[[Examples of workflows]]''' contributed by different institutions and references.

=== Project Templates ===

'''[[Project Templates]]''' are useful for expressing information in a systematic manner, streamlining processes and saving time and energy. Templates can provide clearer communication and consistency across project. Included are templates provided by different institutions.

=== Project Retrospectives ===

== Project Management Software ==
This section contains a list of tools for project management, with pros and cons for each.

{| class="wikitable sortable"
|-
! Name !! Uses and Overview !! Pro || Con
|-
| [https://asana.com/ Asana] || Asana allows team members to collaborate on projects and track the progress of tasks. It works both for software development projects and other more generic projects.

||
*Free (up to 15 members)
*Great for task-based work
*Works on mobile

||
*If your team has over 15 members, you need to pay
*Doesn't do as well with project discussion
*Does not allow for private teams in the free version
*No bug/issue tracking
|-
| [https://basecamp.com/ Basecamp]
|| Basecamp allows collaborators to post messages, organize to-do lists and documents, and create group schedules. Related App: goplan
||
*intuitive design
*easy-to-use features
*email integration
*some calendar integration

||
* the first project is free, but you need to pay after that point
*scheduling support is limited
|-
| [https://trello.com/ Trello]
|| Trello is an application for tracking tasks. It allows you to move individual cards (representing tasks) as they enter different phases. Trello allows you to assign tasks to different collaborators, create due dates, and provide contextual information for the tasks to be completed.
Used by: [https://github.com/fsulib/project-managers-toolkit/blob/master/project-managers-toolkit.md#section FSU Libraries]
||
*very similar to analog/paper SCRUM boards
*feature-specific prioritization
*bug tracking
*useful for tracking action/discussion items from meetings
*able to link or attach supporting documents to cards
||
*showing the hierarchy of tasks not really possible
*not able to easily produce a to-do list (i.e. from the user's end, a list of tasks that the user is assigned to)

|-
| [https://gsuite.google.com/ Google Suite]
|| Google applications (specifically, Google Drive) is a suite of tools for creating documents collaboratively and sharing information. Google Apps include a text, spreadsheet, and slide editor, as well as applications for drawing, organizing calendars, and sharing (but not editing) other types of files.
Used by: [https://github.com/fsulib/project-managers-toolkit/blob/master/project-managers-toolkit.md#section FSU Libraries]
||
* easy to share documents with large teams for collaboration
* easily searchable and organizable
||
* you may need to use another tool to track/organize relevant documents, especially if there are a lot of them
* can be worthwhile to set up standard naming conventions for files since it is so easy to create files and folders
* if wireless is inconsistent, some files can be hard to access. use the desktop app to ensure off-line access and to organize or sync files
|

|-
| [https://www.pivotaltracker.com/ Pivotal Tracker]
|| Pivotal Tracker allows users to organize tasks by project and stories while integrating release dates and prioritization into the workflow.
||
* helps organize agile project teams that cannot meet in person
||
* only free for thirty days (paid plans)
|

|-
| [https://www.atlassian.com/software/jira Jira]
|| Issue tracking and project tracking software. JIRA allows teams to "create and estimate stories, build a sprint backlog, visualize activity, measure team velocity, and report on progress."
||
* works well for teams who use Scrum project management methods
||
* [https://www.atlassian.com/software/jira/pricing paid service] ($10 for teams of up to 10; $75 and more for 15 teams and up)
|

|-
| [https://www.redmine.org/ Redmine]
|| Redmine allows you to track issues, latest project news, and organize projects by members and contributors. You can associate files with given projects, create Gantt charts and calendars, and create wikis to document projects. Redmine has a demo site that allows you to see how it looks in action.
||
* open source
* plug-ins allow for extensibility
* Ability to manage multiple simultaneous projects
||
* doesn't work well with projects that aren't typical software development projects
|

|-
| [https://slack.com/ Slack]
|| Slack is a communication app for teams. It integrates with several of the project management tools on this list, and allows team members to communicate more easily and informally than through email.
Used by: [https://github.com/fsulib/project-managers-toolkit/blob/master/project-managers-toolkit.md#section FSU Libraries]
||
* allows for easy communication between entire organizations, small groups within the organization, and individual members
* integrates with many other applications (e.g. Google Docs, JIRA, Trello, GitHub, etc.)
* allows members to easily set up reminders, take notes-to-self, customize alerts
* can be used on the web or via desktop app across devices
||
* free version only has a 10,000 message capacity (older messages get deleted)
* paid version has additional integrations such as single sign-on, customizable message retention period (ex. 90 day retention period or longer)
* Slack users sharing files (on free or paid versions) may not understand that it is not a system of record to store information; if retaining message history is important for project documentation, threads can be exported and copied to project documentation
|

|-
| [https://www.smartsheet.com/ Smartsheet]
|| Smartsheet allows a team to collaborate and communicate with a spreadsheet-style interface. It allows for file sharing, alerts and reminders, the creation of Gantt charts, and other features that will help to organize your projects.
||
* relatively simple (based on spreadsheets)
* Customizable and flexible
* links to other tools and services (like Google Docs)
||
* paid service
|

|}

=== Other general software-independent recommendations for project management ===

*Wikis for project documents and documentation
*Google Docs or another collaborative document editor for the creation of project charter, meeting notes, etc. with separate document (or folder) for meeting notes
*Ticket-trackers
*Planning Poker
*After-Action Reviews or Retrospectives vis tools such as [https://funretro.github.io/distributed/ FunRetro]
*Scheduling using Doodle or Google Sheets is useful for tracking team members' schedules

== Professional Development ==
Professional development is an ongoing part of a project management career. A successful project manager possesses a blended set of hard and soft skills acquired over time. Training is offered by the [https://pmi.org Project Management Institute] and various local education providers.

== Resources and further reading ==
There are lots of great articles, presentations and grey lit out there on project management and digital libraries. We've created a Zotero Group library at https://www.zotero.org/groups/2205688/dlf_pmg? and encourage you to add more when you read something good.

== Contributors ==
*Andy Ashton, Brown University
*Carolyn Caizzi, Northwestern University
*Kathleen Cameron
*Jason Casden, North Carolina State University
*Tim Clarke, Muhlenberg College
*Tom Cramer, Stanford University
*Cristela Garcia-Spitz, UC San Diego Library
*Joshua Honn, Northwestern University
*Katherine Kott, Independent Consultant
*Christine Malinowski, Massachusetts Institute of Technology
*Rafia Mirza, UT Arlington, TX
*Lisa McAulay, UCLA
*Sandra McIntyre, Mountain West Digital Library
*Alan Pike, Emory Center for Digital Scholarship
*Robin C. Pike, University of Maryland
*Christine Quirion, Massachusetts Institute of Technology
*Sarah Severson, McGill University Library
*Sarah Stanley, Florida State University
*Joan Starr, California Digital Library
*Micah Vandegrift, Florida State University Libraries
*Jennifer Vinopal, New York University
*Cliff Wulfman, Princeton University
*Cynthia York, Johns Hopkins University

{| class="wikitable" border="1"
|'''Interested in related resources?''' Check out DLF's [[About DLF and the Organizers' Toolkit | Organizers' Toolkit]]!
|}

Project Plans

2018-10-12T22:48:50Z

Robincpike:

Project plans flesh out more details of a project. It answers the same questions as a project charter, but often in more detail. Please contribute project plan examples to the '''[[DLF Project Managers Toolkit]]'''.

Some sections of a project plan could include:
* History or description
* Justification or rationale
* Scope
* Funding source(s)
* Stakeholders list
* Technical requirements (in-house or vendor)
* Roles and responsibilities by project milestone
* Operations of managing project documentation and communication
* Timeline

[[File:FY19MPTVideoDigitizationProject-Example.docx|Project Plan Example]]

Project Plans

2018-10-12T22:47:57Z

Robincpike:

Project plans flesh out more details of a project. It answers the same questions as a project charter, but often in more detail. Please contribute project plan examples to the '''[[DLF Project Managers Toolkit]]'''.

Some sections of a project plan could include:
* History or description
* Justification or rationale
* Scope
* Funding source(s)
* Stakeholders list
* Technical requirements (in-house or vendor)
* Roles and responsibilities by project milestone
* Operations of managing project documentation and communication
* Timeline

'''[[File:FY19MPTVideoDigitizationProject-Example.docx|Project Plan Example]]'''

Project Plans

2018-10-12T22:47:12Z

Robincpike:

File:FY19MPTVideoDigitizationProject-Example.docx

2018-10-12T22:45:46Z

Robincpike: An example of a project plan for an outsourced digitization project from the University of Maryland Libraries, 2018.

== Summary ==
An example of a project plan for an outsourced digitization project from the University of Maryland Libraries, 2018.
== Licensing ==
{{CC-by-sa-2.5}}

Project Plans

2018-10-12T22:44:24Z

Robincpike: Created page with "Project plans flesh out more details of a project. It answers the same questions as a project charter, but often in more detail. Please contribute project plan examples to the..."

DLF Project Managers Toolkit

2018-10-12T22:35:26Z

Robincpike: /* Project Plans */

This toolkit is a collaborative project, based on contributions by members of the [https://www.diglib.org/ Digital Library Federation's] Project Managers Group ([[DLF Project Managers Group |DLF PMG]]). First initiated by Jennifer Vinopal at New York University in February 2013, the toolkit has grown and evolved over the years as a living document to share experiences and link out to resources.

*'''What?''' A crowdsourced collection of information, tips, techniques, and tools for project managers working in digital libraries. Please contribute and share your knowledge.

*'''Why?''' Whether we realize it or not, librarians and library staff are managing projects all the time. These may be informal or formal projects, or we might not think of them as projects at all. Just the same, we could all stand to take a more organized and structured approach to planning and accomplishing our project work. Much of the project management literature and training frequently emphasizes a corporate perspective, which may not always be applicable to a library setting.

*'''Who?''' Anyone who wants to contribute. Feel free to post anonymously if you prefer, or sign the contributors list at the end of the document.

*'''How?''' Be generous with your knowledge and be respectful of what others have written. Share your experience and help others to learn from both your successes and failures.

To contribute, simply login then select the Edit tab. If you are a first time contributor, select ‘create account’ at the top right of the page. Then send a request to [mailto:info@diglib.org info@diglib.org] to get access to edit pages, add links or share documentation.

== Getting started ==
[[File:ProjectBasics.png|thumb|right]]
=== Project Management Basics ===

Review a few '''[[Project Management Basics]]''' which are basic building blocks for the other sections of the toolkit.

=== Project Charters & Memorandum of Understandings ===

The goal of a project charter is to document agreement between all parties (sponsor, stakeholder, staff) about the goals, scope, and deliverables of the project. Ideally, the document defines time, scope and cost.

It is useful to use this time to answer questions about cost/benefit and the extent to which people can actually reasonably contribute to the project. The Project Management Group recommends discussing the following questions at this stage:

'''Why?'''
What are the objectives of the project?
What are the expected benefits of the project?
'''Scope?'''
What is the scope of the project? (specifically, what's not in scope...)
How will we know the the project is done?
'''Who are the stakeholders?'''
Who is the end user audience?Who?
Who is going to work on the project?
Who is managing the project?
Who is/are the sponsors of the project?
'''How much time can participants reasonably spend on the project'''

After the answers to these questions have been decided upon, the Project Charter itself should be drafted. The following is the basic format of a Project Charter:

Project name
Description (high-level statement of your project goal)
Success criteria (how will we know when the project is done?) – SMART goals
Requirements (deliverables, options, & out of scope)
Project team (including roles)
Milestones/Schedule (high-level + proposed dates)

Drafting the charter is an iterative process:

Write a draft
Share it with project team
Share it with stakeholders
Rewrite
Repeat until consensus

The [https://project-charter-template.casual.pm/ Project Charter Toolkit] can be a useful resource whether you are looking to understand what a project charter is or you’re just looking for some fresh ideas on laying out/structuring your particular charter. They have free templates to download, samples, etc.

A Memorandum of Understanding can be used to build out a project charter and be used to manage expectations, project planning and increase transparency, communication and understanding. The University of Texas Arlington hosts a [https://rc.library.uta.edu/uta-ir/handle/10106/25646 Memorandum of Understanding Collection] which was developed by a group of librarians for library specific projects and includes a workbook and templates.

=== Project Plans ===

'''[[Project Plans]]''' flesh out more details of a project, such as scope; individual stakeholders; milestones and tasks, and roles and responsibilities within; and a timeline. It answers the same questions as a project charter, but often in more detail.

=== Project Scheduling ===

'''[[Project Scheduling]]''' captures the work that needs to be performed. It may also visualize the steps in the project. This section compares two methods: gantt charts versus kanban.

=== Workflows ===

A workflow is a sequence of steps toward the completion of a defined task used to manage repetitive processes. Workflow modelling helps participants and stakeholders understand the sequence of steps and their roles in the process. It can also help identify patterns, gaps, and bottlenecks to enhance efficiency and improve team dynamics.<ref>Shaw, E., Garcia-Spitz, C., Bragg, M., Hagedorn, K., & Porter, E. (2018). Finding the balance: Modelling successful workflows for digital library collections. Journal of Digital Media Management, 6(3), 295-311. Retrieved from [[https://escholarship.org/uc/item/9h17g7fh https://escholarship.org/uc/item/9h17g7fh]]</ref>

Included are '''[[Examples of workflows]]''' contributed by different institutions and references.

=== Project Templates ===

'''[[Project Templates]]''' are useful for expressing information in a systematic manner, streamlining processes and saving time and energy. Templates can provide clearer communication and consistency across project. Included are templates provided by different institutions.

=== Project Retrospectives ===

== Project Management Software ==
This section contains a list of tools for project management, with pros and cons for each.

{| class="wikitable sortable"
|-
! Name !! Uses and Overview !! Pro || Con
|-
| [https://asana.com/ Asana] || Asana allows team members to collaborate on projects and track the progress of tasks. It works both for software development projects and other more generic projects.

||
*Free (up to 15 members)
*Great for task-based work
*Works on mobile

||
*If your team has over 15 members, you need to pay
*Doesn't do as well with project discussion
*Does not allow for private teams in the free version
*No bug/issue tracking
|-
| [https://basecamp.com/ Basecamp]
|| Basecamp allows collaborators to post messages, organize to-do lists and documents, and create group schedules. Related App: goplan
||
*intuitive design
*easy-to-use features
*email integration
*some calendar integration

||
* the first project is free, but you need to pay after that point
*scheduling support is limited
|-
| [https://trello.com/ Trello]
|| Trello is an application for tracking tasks. It allows you to move individual cards (representing tasks) as they enter different phases. Trello allows you to assign tasks to different collaborators, create due dates, and provide contextual information for the tasks to be completed.
Used by: [https://github.com/fsulib/project-managers-toolkit/blob/master/project-managers-toolkit.md#section FSU Libraries]
||
*very similar to analog/paper SCRUM boards
*feature-specific prioritization
*bug tracking
*useful for tracking action/discussion items from meetings
*able to link or attach supporting documents to cards
||
*showing the hierarchy of tasks not really possible
*not able to easily produce a to-do list (i.e. from the user's end, a list of tasks that the user is assigned to)

|-
| [https://gsuite.google.com/ Google Suite]
|| Google applications (specifically, Google Drive) is a suite of tools for creating documents collaboratively and sharing information. Google Apps include a text, spreadsheet, and slide editor, as well as applications for drawing, organizing calendars, and sharing (but not editing) other types of files.
Used by: [https://github.com/fsulib/project-managers-toolkit/blob/master/project-managers-toolkit.md#section FSU Libraries]
||
* easy to share documents with large teams for collaboration
* easily searchable and organizable
||
* you may need to use another tool to track/organize relevant documents, especially if there are a lot of them
* can be worthwhile to set up standard naming conventions for files since it is so easy to create files and folders
* if wireless is inconsistent, some files can be hard to access. use the desktop app to ensure off-line access and to organize or sync files
|

|-
| [https://www.pivotaltracker.com/ Pivotal Tracker]
|| Pivotal Tracker allows users to organize tasks by project and stories while integrating release dates and prioritization into the workflow.
||
* helps organize agile project teams that cannot meet in person
||
* only free for thirty days (paid plans)
|

|-
| [https://www.atlassian.com/software/jira Jira]
|| Issue tracking and project tracking software. JIRA allows teams to "create and estimate stories, build a sprint backlog, visualize activity, measure team velocity, and report on progress."
||
* works well for teams who use Scrum project management methods
||
* [https://www.atlassian.com/software/jira/pricing paid service] ($10 for teams of up to 10; $75 and more for 15 teams and up)
|

|-
| [https://www.redmine.org/ Redmine]
|| Redmine allows you to track issues, latest project news, and organize projects by members and contributors. You can associate files with given projects, create Gantt charts and calendars, and create wikis to document projects. Redmine has a demo site that allows you to see how it looks in action.
||
* open source
* plug-ins allow for extensibility
* Ability to manage multiple simultaneous projects
||
* doesn't work well with projects that aren't typical software development projects
|

|-
| [https://slack.com/ Slack]
|| Slack is a communication app for teams. It integrates with several of the project management tools on this list, and allows team members to communicate more easily and informally than through email.
Used by: [https://github.com/fsulib/project-managers-toolkit/blob/master/project-managers-toolkit.md#section FSU Libraries]
||
* allows for easy communication between entire organizations, small groups within the organization, and individual members
* integrates with many other applications (e.g. Google Docs, JIRA, Trello, GitHub, etc.)
* allows members to easily set up reminders, take notes-to-self, customize alerts
* can be used on the web or via desktop app across devices
||
* free version only has a 10,000 message capacity (older messages get deleted)
* paid version has additional integrations such as single sign-on, customizable message retention period (ex. 90 day retention period or longer)
* Slack users sharing files (on free or paid versions) may not understand that it is not a system of record to store information; if retaining message history is important for project documentation, threads can be exported and copied to project documentation
|

|-
| [https://www.smartsheet.com/ Smartsheet]
|| Smartsheet allows a team to collaborate and communicate with a spreadsheet-style interface. It allows for file sharing, alerts and reminders, the creation of Gantt charts, and other features that will help to organize your projects.
||
* relatively simple (based on spreadsheets)
* Customizable and flexible
* links to other tools and services (like Google Docs)
||
* paid service
|

|}

=== Other general software-independent recommendations for project management ===

*Wikis for project documents and documentation
*Google Docs or another collaborative document editor for the creation of project charter, meeting notes, etc. with separate document (or folder) for meeting notes
*Ticket-trackers
*Planning Poker
*After-Action Reviews or Retrospectives vis tools such as [https://funretro.github.io/distributed/ FunRetro]
*Scheduling using Doodle or Google Sheets is useful for tracking team members' schedules

== Professional Development ==
Professional development is an ongoing part of a project management career. A successful project manager possesses a blended set of hard and soft skills acquired over time. Training is offered by the [https://pmi.org Project Management Institute] and various local education providers.

== Resources and further reading ==
There are lots of great articles, presentations and grey lit out there on project management and digital libraries. We've created a Zotero Group library at https://www.zotero.org/groups/2205688/dlf_pmg? and encourage you to add more when you read something good.

== Contributors ==
*Andy Ashton, Brown University
*Carolyn Caizzi, Northwestern University
*Kathleen Cameron
*Jason Casden, North Carolina State University
*Tim Clarke, Muhlenberg College
*Tom Cramer, Stanford University
*Cristela Garcia-Spitz, UC San Diego Library
*Joshua Honn, Northwestern University
*Katherine Kott, Independent Consultant
*Christine Malinowski, Massachusetts Institute of Technology
*Rafia Mirza, UT Arlington, TX
*Lisa McAulay, UCLA
*Sandra McIntyre, Mountain West Digital Library
*Alan Pike, Emory Center for Digital Scholarship
*Christine Quirion, Massachusetts Institute of Technology
*Sarah Severson, McGill University Library
*Sarah Stanley, Florida State University
*Joan Starr, California Digital Library
*Micah Vandegrift, Florida State University Libraries
*Jennifer Vinopal, New York University
*Cliff Wulfman, Princeton University
*Cynthia York, Johns Hopkins University

{| class="wikitable" border="1"
|'''Interested in related resources?''' Check out DLF's [[About DLF and the Organizers' Toolkit | Organizers' Toolkit]]!
|}

DLF Project Managers Toolkit

2018-10-12T22:33:40Z

Robincpike:

This toolkit is a collaborative project, based on contributions by members of the [https://www.diglib.org/ Digital Library Federation's] Project Managers Group ([[DLF Project Managers Group |DLF PMG]]). First initiated by Jennifer Vinopal at New York University in February 2013, the toolkit has grown and evolved over the years as a living document to share experiences and link out to resources.

*'''What?''' A crowdsourced collection of information, tips, techniques, and tools for project managers working in digital libraries. Please contribute and share your knowledge.

*'''Why?''' Whether we realize it or not, librarians and library staff are managing projects all the time. These may be informal or formal projects, or we might not think of them as projects at all. Just the same, we could all stand to take a more organized and structured approach to planning and accomplishing our project work. Much of the project management literature and training frequently emphasizes a corporate perspective, which may not always be applicable to a library setting.

*'''Who?''' Anyone who wants to contribute. Feel free to post anonymously if you prefer, or sign the contributors list at the end of the document.

*'''How?''' Be generous with your knowledge and be respectful of what others have written. Share your experience and help others to learn from both your successes and failures.

To contribute, simply login then select the Edit tab. If you are a first time contributor, select ‘create account’ at the top right of the page. Then send a request to [mailto:info@diglib.org info@diglib.org] to get access to edit pages, add links or share documentation.

== Getting started ==
[[File:ProjectBasics.png|thumb|right]]
=== Project Management Basics ===

Review a few '''[[Project Management Basics]]''' which are basic building blocks for the other sections of the toolkit.

=== Project Charters & Memorandum of Understandings ===

The goal of a project charter is to document agreement between all parties (sponsor, stakeholder, staff) about the goals, scope, and deliverables of the project. Ideally, the document defines time, scope and cost.

It is useful to use this time to answer questions about cost/benefit and the extent to which people can actually reasonably contribute to the project. The Project Management Group recommends discussing the following questions at this stage:

'''Why?'''
What are the objectives of the project?
What are the expected benefits of the project?
'''Scope?'''
What is the scope of the project? (specifically, what's not in scope...)
How will we know the the project is done?
'''Who are the stakeholders?'''
Who is the end user audience?Who?
Who is going to work on the project?
Who is managing the project?
Who is/are the sponsors of the project?
'''How much time can participants reasonably spend on the project'''

After the answers to these questions have been decided upon, the Project Charter itself should be drafted. The following is the basic format of a Project Charter:

Project name
Description (high-level statement of your project goal)
Success criteria (how will we know when the project is done?) – SMART goals
Requirements (deliverables, options, & out of scope)
Project team (including roles)
Milestones/Schedule (high-level + proposed dates)

Drafting the charter is an iterative process:

Write a draft
Share it with project team
Share it with stakeholders
Rewrite
Repeat until consensus

The [https://project-charter-template.casual.pm/ Project Charter Toolkit] can be a useful resource whether you are looking to understand what a project charter is or you’re just looking for some fresh ideas on laying out/structuring your particular charter. They have free templates to download, samples, etc.

A Memorandum of Understanding can be used to build out a project charter and be used to manage expectations, project planning and increase transparency, communication and understanding. The University of Texas Arlington hosts a [https://rc.library.uta.edu/uta-ir/handle/10106/25646 Memorandum of Understanding Collection] which was developed by a group of librarians for library specific projects and includes a workbook and templates.

=== Project Plans ===

'''[[Project Plans]]''' flesh out more details of a project, such as scope; individual stakeholders; milestones and tasks, and roles and responsibilities within; and a timeline.

=== Project Scheduling ===

'''[[Project Scheduling]]''' captures the work that needs to be performed. It may also visualize the steps in the project. This section compares two methods: gantt charts versus kanban.

=== Workflows ===

A workflow is a sequence of steps toward the completion of a defined task used to manage repetitive processes. Workflow modelling helps participants and stakeholders understand the sequence of steps and their roles in the process. It can also help identify patterns, gaps, and bottlenecks to enhance efficiency and improve team dynamics.<ref>Shaw, E., Garcia-Spitz, C., Bragg, M., Hagedorn, K., & Porter, E. (2018). Finding the balance: Modelling successful workflows for digital library collections. Journal of Digital Media Management, 6(3), 295-311. Retrieved from [[https://escholarship.org/uc/item/9h17g7fh https://escholarship.org/uc/item/9h17g7fh]]</ref>

Included are '''[[Examples of workflows]]''' contributed by different institutions and references.

=== Project Templates ===

'''[[Project Templates]]''' are useful for expressing information in a systematic manner, streamlining processes and saving time and energy. Templates can provide clearer communication and consistency across project. Included are templates provided by different institutions.

=== Project Retrospectives ===

== Project Management Software ==
This section contains a list of tools for project management, with pros and cons for each.

{| class="wikitable sortable"
|-
! Name !! Uses and Overview !! Pro || Con
|-
| [https://asana.com/ Asana] || Asana allows team members to collaborate on projects and track the progress of tasks. It works both for software development projects and other more generic projects.

||
*Free (up to 15 members)
*Great for task-based work
*Works on mobile

||
*If your team has over 15 members, you need to pay
*Doesn't do as well with project discussion
*Does not allow for private teams in the free version
*No bug/issue tracking
|-
| [https://basecamp.com/ Basecamp]
|| Basecamp allows collaborators to post messages, organize to-do lists and documents, and create group schedules. Related App: goplan
||
*intuitive design
*easy-to-use features
*email integration
*some calendar integration

||
* the first project is free, but you need to pay after that point
*scheduling support is limited
|-
| [https://trello.com/ Trello]
|| Trello is an application for tracking tasks. It allows you to move individual cards (representing tasks) as they enter different phases. Trello allows you to assign tasks to different collaborators, create due dates, and provide contextual information for the tasks to be completed.
Used by: [https://github.com/fsulib/project-managers-toolkit/blob/master/project-managers-toolkit.md#section FSU Libraries]
||
*very similar to analog/paper SCRUM boards
*feature-specific prioritization
*bug tracking
*useful for tracking action/discussion items from meetings
*able to link or attach supporting documents to cards
||
*showing the hierarchy of tasks not really possible
*not able to easily produce a to-do list (i.e. from the user's end, a list of tasks that the user is assigned to)

|-
| [https://gsuite.google.com/ Google Suite]
|| Google applications (specifically, Google Drive) is a suite of tools for creating documents collaboratively and sharing information. Google Apps include a text, spreadsheet, and slide editor, as well as applications for drawing, organizing calendars, and sharing (but not editing) other types of files.
Used by: [https://github.com/fsulib/project-managers-toolkit/blob/master/project-managers-toolkit.md#section FSU Libraries]
||
* easy to share documents with large teams for collaboration
* easily searchable and organizable
||
* you may need to use another tool to track/organize relevant documents, especially if there are a lot of them
* can be worthwhile to set up standard naming conventions for files since it is so easy to create files and folders
* if wireless is inconsistent, some files can be hard to access. use the desktop app to ensure off-line access and to organize or sync files
|

|-
| [https://www.pivotaltracker.com/ Pivotal Tracker]
|| Pivotal Tracker allows users to organize tasks by project and stories while integrating release dates and prioritization into the workflow.
||
* helps organize agile project teams that cannot meet in person
||
* only free for thirty days (paid plans)
|

|-
| [https://www.atlassian.com/software/jira Jira]
|| Issue tracking and project tracking software. JIRA allows teams to "create and estimate stories, build a sprint backlog, visualize activity, measure team velocity, and report on progress."
||
* works well for teams who use Scrum project management methods
||
* [https://www.atlassian.com/software/jira/pricing paid service] ($10 for teams of up to 10; $75 and more for 15 teams and up)
|

|-
| [https://www.redmine.org/ Redmine]
|| Redmine allows you to track issues, latest project news, and organize projects by members and contributors. You can associate files with given projects, create Gantt charts and calendars, and create wikis to document projects. Redmine has a demo site that allows you to see how it looks in action.
||
* open source
* plug-ins allow for extensibility
* Ability to manage multiple simultaneous projects
||
* doesn't work well with projects that aren't typical software development projects
|

|-
| [https://slack.com/ Slack]
|| Slack is a communication app for teams. It integrates with several of the project management tools on this list, and allows team members to communicate more easily and informally than through email.
Used by: [https://github.com/fsulib/project-managers-toolkit/blob/master/project-managers-toolkit.md#section FSU Libraries]
||
* allows for easy communication between entire organizations, small groups within the organization, and individual members
* integrates with many other applications (e.g. Google Docs, JIRA, Trello, GitHub, etc.)
* allows members to easily set up reminders, take notes-to-self, customize alerts
* can be used on the web or via desktop app across devices
||
* free version only has a 10,000 message capacity (older messages get deleted)
* paid version has additional integrations such as single sign-on, customizable message retention period (ex. 90 day retention period or longer)
* Slack users sharing files (on free or paid versions) may not understand that it is not a system of record to store information; if retaining message history is important for project documentation, threads can be exported and copied to project documentation
|

|-
| [https://www.smartsheet.com/ Smartsheet]
|| Smartsheet allows a team to collaborate and communicate with a spreadsheet-style interface. It allows for file sharing, alerts and reminders, the creation of Gantt charts, and other features that will help to organize your projects.
||
* relatively simple (based on spreadsheets)
* Customizable and flexible
* links to other tools and services (like Google Docs)
||
* paid service
|

|}

=== Other general software-independent recommendations for project management ===

*Wikis for project documents and documentation
*Google Docs or another collaborative document editor for the creation of project charter, meeting notes, etc. with separate document (or folder) for meeting notes
*Ticket-trackers
*Planning Poker
*After-Action Reviews or Retrospectives vis tools such as [https://funretro.github.io/distributed/ FunRetro]
*Scheduling using Doodle or Google Sheets is useful for tracking team members' schedules

== Professional Development ==
Professional development is an ongoing part of a project management career. A successful project manager possesses a blended set of hard and soft skills acquired over time. Training is offered by the [https://pmi.org Project Management Institute] and various local education providers.

== Resources and further reading ==
There are lots of great articles, presentations and grey lit out there on project management and digital libraries. We've created a Zotero Group library at https://www.zotero.org/groups/2205688/dlf_pmg? and encourage you to add more when you read something good.

== Contributors ==
*Andy Ashton, Brown University
*Carolyn Caizzi, Northwestern University
*Kathleen Cameron
*Jason Casden, North Carolina State University
*Tim Clarke, Muhlenberg College
*Tom Cramer, Stanford University
*Cristela Garcia-Spitz, UC San Diego Library
*Joshua Honn, Northwestern University
*Katherine Kott, Independent Consultant
*Christine Malinowski, Massachusetts Institute of Technology
*Rafia Mirza, UT Arlington, TX
*Lisa McAulay, UCLA
*Sandra McIntyre, Mountain West Digital Library
*Alan Pike, Emory Center for Digital Scholarship
*Christine Quirion, Massachusetts Institute of Technology
*Sarah Severson, McGill University Library
*Sarah Stanley, Florida State University
*Joan Starr, California Digital Library
*Micah Vandegrift, Florida State University Libraries
*Jennifer Vinopal, New York University
*Cliff Wulfman, Princeton University
*Cynthia York, Johns Hopkins University

{| class="wikitable" border="1"
|'''Interested in related resources?''' Check out DLF's [[About DLF and the Organizers' Toolkit | Organizers' Toolkit]]!
|}

DLF Project Managers Group

2018-02-07T18:21:51Z

Robincpike: Added bi-monthly discussion topics table.

== Background ==
The [https://www.diglib.org/groups/pmg/ Digital Library Federation Project Managers Group (DLF PMG)] was formed in 2008 to acknowledge the intersection of the disciplines of project management and library technology. The group provides a forum for sharing project management methodologies and tools, alongside broader discussions that consider issues such as portfolio management and cross-organizational communication. The group also looks to keep pace with the dynamic digital library landscape, by bringing new and evolving project management practices to the attention and mutual benefit of our colleagues.

[https://www.diglib.org/groups/pmg/ Past meeting presentations and notes] are available on the DLF website.

== Crowdsourced Project Management Toolkit ==
The [[DLF Project Managers Toolkit]] is a collaborative project, based off contributions by members of DLF PMG. The Toolkit offers crowdsourced information, tips, techniques, and tools for project managers working in or with digital libraries. First initiated as a Google doc by Jennifer Vinopal at New York University in February 2013, the toolkit has grown and evolved over the years as a living document to share experiences and link out to resources.

== Get Involved ==
*Attend the Project Managers Working Meeting at the DLF Forum each year, where members of the group discuss various needs and topics, and work to identify ways to support them.
**[https://www.diglib.org/groups/pmg/ Past meeting presentations and notes]
**[https://docs.google.com/document/d/1jnkUwe5vSFOEoGQ5G8vBwtqH59NWgexolbfhWN_pXN0/edit#/ 2017 Project Managers Breakfast Meeting notes]

*Join the [https://lists.clir.org/cgi-bin/wa?SUBED1=DLF-PM-GROUP&A=1 DLF PMG listserv] open to anyone interested in digital library project management.

*Contribute to the Project Managers Toolkit. Simply login at the top right of the page, then select the Edit tab. If you are a first time contributor, select ‘create account’ at the top right of the page and send a request to [mailto:info@diglib.org info@diglib.org] to get access to edit pages, add links, or share documentation.

*Join in the 2018 DLF-PM Group Bi-Monthly Discussion
{| class="wikitable" border="1"
|-
! Topic
! Date
! Format
|-
| Labor in Digital Work
| February 12-16, 2018
| Multi-day discussion and summary
|-
| Service and Portfolio Management
| TBD
| TBD
|-
| Tools for Project Management
| TBD
| TBD
|-
| Sunsetting for Projects
| TBD
| TBD
|-
| Scope Creep
| TBD
| TBD
|-
| Agile Development
| TBD
| TBD
|}

Please send any additional topic ideas to the DLF Project Manager's Steering Committee.