DLF Wiki - User contributions [en]

Project Proposal Process

2022-06-21T20:46:31Z

Cristelags:

The project proposal process aims to provide a transparent framework and formal process for selecting and prioritizing projects while improving the overall workflow and workload of those involved.

Determine who will be approving project proposals and how often.

Consider the selection criteria. Possible criteria might include:
* Programmatic Value: the project supports current or emerging research and instruction in one or more specific subject areas or supports the academic work of one or more defined user groups or information communities
* Accessibility/Added Value: the project enhances the value and/or the preservation of the existing collection(s) by making it more accessible, better integrated, and/or more likely to be used
* Open Access for research and teaching: the copyright status of the collection makes this project available for open access
* Historical/Cultural Value: the project contributes to the existing collections, history and culture of the organization, the region, national or international communities
* Intrinsic Value: the materials are rare or there is some other self-evident value that the project would contribute to the organization
* Collaborative Value: the project promotes internal collaboration between or among units of the organization, and/or external collaboration with other institutions
* Developmental Value: the project promotes a specific developmental or stewardship initiative
* Public Service Value: the project serves users in the organization or a specific community
* Viability: the project has a demonstrated commitment and support from the project proposing unit, and avoids duplication of effort

Also consider:
* Is this project fully defined with a specific objective with a start and end date?
* What impact might the project have on the daily work of the team, the program, or other programs?
* What technical capabilities and services might be involved in this project and require to maintain?
* Are there specific funding or resources requirements?
* Are there any scheduling issues or obstacles that need to be addressed?

== Examples ==
At the UC San Diego Library, digital project proposals are submitted to the Digital Collections Group, which consists of the program directors for special collections & archives, metadata services, and digital initiatives. Curators, subject specialists and technical consultants are also members on a rotating basis. The Chair rotates every two years reporting to the Assistant University Librarian for Collections, and has a seat on the Digital Library Steering Committee. A project proposal requiring significant resources or a new technology goes to the Digital Library Steering Committee.
* [[Media:UCSD_projproposal_form.docx|Project proposals]] must be submitted with a [[Media:UCSD_Checklist_AccessOptions.docx | Checklist to Determine Access Options]] and are reviewed on an ongoing basis at the Digital Collections Group quarterly meetings or via email.

Please contribute additional information or other examples to the '''[[DLF Project Managers Toolkit]]'''. If you have examples to share, please provide some context, such as the purpose or goal, institution, teams and team size, etc.

== References ==
* Project Management Institute. 2018. A guide to the project management body of knowledge: (PMBOK® guide). Newtown Square, Pennsylvania, USA: Project Management Institute.

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.

DLF Project Managers Toolkit

2022-06-21T15:46:33Z

Cristelags:

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 Management Methodologies ===

'''[[Project management methodology (PMM)]]''' is a system of principles, techniques, and procedures.

=== 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.

* When considering cost, refer to the Digitization Cost Calculator: https://dashboard.diglib.org/

=== 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://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

|-
| [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.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.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.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://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)

|}

=== 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. Obtaining [[professional certification]] can enhance a person's career path and provide additional opportunities.

== 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].
|-
| User Experience and Service Design: A Brief Introduction
| May 15, 2020
| Jenn Nolte
| User experience (UX) is not a new discipline, and in fact has been around for many years under different names (human factors, usability, user-centered design), even before the internet! Still, many people conflate UX with web and visual design even though UX is useful in many more contexts, including the design of services. Service design shows us how to put and keep the user at the center of our planning for new or enhanced services.
Jenn Nolte worked in library information technology at Yale University for over a decade before shifting over to user experience research. She holds an MLIS from Southern Connecticut State University and is currently pursuing an MS in Organizational Psychology at the University of Hartford. She recently served on the Connecticut UX Professionals Association board, currently serves on the New Haven IO board of directors, and hosts a monthly informal meetup for UX practitioners and enthusiasts in CT. Say hello and connect with Jenn at linkedin.com/in/jennnolte.
The presentation recording is available at: https://www.youtube.com/watch?v=FLtFCiRAL0k and [[:File:Service Design & Service Blueprinting.pdf|Presentation Slides]]
|-
| Working Remotely During a Global Pandemic: Strengthening Impact, Communication, and Empathy in Times of Crises
| August 14, 2020
| Casey Davis Kaufman
| The COVID-19 pandemic has dramatically transformed the way we live, work, and interact with our colleagues. Reflecting on her experiences working remotely since July 2019, and more specifically since mid-March 2020 when COVID-19 upended our sense of normality and required swift and radical responses within our workplaces, Casey Davis Kaufman will offer a webinar that focuses on leading teams and projects while working remotely during the ongoing global crises. The presentation will cover a range of topics relevant to the present remote-working environment -- from effective communication and support, managing expectations, and 'holding space' for team members who may be experiencing incredibly challenging and emotionally difficult situations within and/or outside of work. Additionally, Casey will share recommendations for planning and managing digitization projects during the COVID-19 pandemic, and she will offer ideas for remotely engaging our communities while continually demonstrating the value of libraries and archives amidst our present challenges.
Casey Davis Kaufman (she/her) is the Associate Director of the WGBH Media Library and Archives and Project Manager for the American Archive of Public Broadcasting. In her role, Casey supports a team that includes a repository manager, web developers, and outreach staff to undertake collections management, access, curatorial work, metadata management, engagement, and special projects. She served as Project Director for the NEH-funded PBCore Development and Training Project, as well as the IMLS-funded Public Broadcasting Preservation Fellowship, which is being sustained through a new collaboration with the University of Alabama. She has served as AAPB's project manager for multiple digitization projects, including the PBS NewsHour Digitization Project, and the current Riverside Church/WRVR-FM Digitization Project and New Mexico Public Media and Kansas Public Media Digitization Projects (all CLIR-funded). Casey is also Project Manager for the University of Tennessee Libraries' "Rising from the Ashes: The Chimney Tops II Wildfires Oral History Project." Casey is an active member of AMIA and serves on the AMIA Continuing Education Advisory Task Force, AMIA Advocacy Committee of the Board, AMIA Diversity and Inclusion Fellowship Task Force, and is Co-Chair of the AMIA Oral History Committee. Casey served on the AMIA Board from 2017-2019. She works remotely from her home in Murfreesboro, TN, with her canine assistant Romsey.
The presentation recording is available at: https://www.youtube.com/watch?v=7D9JdypyR1c
|-
|}

== 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]]!
|}

Project Proposal Process

2022-06-19T20:00:57Z

Cristelags:

The project proposal process aims to provide a transparent framework and formal process for selecting and prioritizing projects while improving the overall workflow and workload of those involved.

Determine who will be approving project proposals and how often.

Consider the selection criteria. Possible criteria might include:
* Programmatic Value: the project supports current or emerging research and instruction in one or more specific subject areas or supports the academic work of one or more defined user groups or information communities
* Accessibility/Added Value: the project enhances the value and/or the preservation of the existing collection(s) by making it more accessible, better integrated, and/or more likely to be used
* Open Access for research and teaching: the copyright status of the collection makes this project available for open access
* Historical/Cultural Value: the project contributes to the existing collections, history and culture of the organization, the region, national or international communities
* Intrinsic Value: the materials are rare or there is some other self-evident value that the project would contribute to the organization
* Collaborative Value: the project promotes internal collaboration between or among units of the organization, and/or external collaboration with other institutions
* Developmental Value: the project promotes a specific developmental or stewardship initiative
* Public Service Value: the project serves users in the organization or a specific community
* Viability: the project has a demonstrated commitment and support from the project proposing unit, and avoids duplication of effort

Also consider:
* Is this project fully defined with a specific objective with a start and end date?
* What impact the project might have on the daily work of the team, the program, or other programs?
* What technical capabilities and services might be involved in this project and require to maintain?
* Are there specific funding or resources requirements?
* Are there any scheduling issues or obstacles that need to be addressed?

== Examples ==
At the UC San Diego Library, digital project proposals are submitted to the Digital Collections Group, which consists of the program directors for special collections & archives, metadata services, and digital initiatives. Curators, subject specialists and technical consultants are also members on a rotating basis. The Chair rotates every two years reporting to the Assistant University Librarian for Collections, and has a seat on the Digital Library Steering Committee. A project proposal requiring significant resources or a new technology goes to the Digital Library Steering Committee.
* [[Media:UCSD_projproposal_form.docx|Project proposals]] must be submitted with a [[Media:UCSD_Checklist_AccessOptions.docx | Checklist to Determine Access Options]] and are reviewed on an ongoing basis at the Digital Collections Group quarterly meetings or via email.

Please contribute additional information or other examples to the '''[[DLF Project Managers Toolkit]]'''. If you have examples to share, please provide some context, such as the purpose or goal, institution, teams and team size, etc.

== References ==
* Project Management Institute. 2018. A guide to the project management body of knowledge: (PMBOK® guide). Newtown Square, Pennsylvania, USA: Project Management Institute.

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.

Project Proposal Process

2022-06-19T19:58:07Z

Cristelags:

The project proposal process aims to provide a transparent framework and formal process for selecting and prioritizing projects while improving the overall workflow and workload of those involved.

Determine who will be approving project proposals and how often.

Consider the selection criteria. Possible criteria might include:
* Programmatic Value: the project supports current or emerging research and instruction in one or more specific subject areas or supports the academic work of one or more defined user groups or information communities
* Instructional Support: the project is intended for eReserves or campus-use only
* Accessibility/Added Value: the project enhances the value and/or the preservation of the existing collection(s) by making it more accessible, better integrated, and/or more likely to be used
* Open Access for research and teaching: the copyright status of the collection makes this project available for open access
* Historical/Cultural Value: the project contributes to the existing collections, history and culture of the University, the region, national or international communities
* Intrinsic Value: the materials are rare or there is some other self-evident value that the project would contribute to the University and the Libraries
* Collaborative Value: the project promotes internal collaboration between or among units of the Libraries, between the Libraries and other University units, and/or external collaboration with other institutions
* Developmental Value: the project promotes a specific developmental or stewardship initiative
* Public Service Value: the project serves users in the Libraries, the University, and beyond the immediate University community
* Viability: the project has a demonstrated commitment and support from the project proposing unit, and avoids duplication of effort

Also consider:
* Is this project fully defined with a specific objective with a start and end date?
* What impact the project might have on the daily work of the team, the program, or other programs?
* What technical capabilities and services might be involved in this project and require to maintain?
* Are there specific funding or resources requirements?
* Are there any scheduling issues or obstacles that need to be addressed?

== Examples ==
At the UC San Diego Library, digital project proposals are submitted to the Digital Collections Group, which consists of the program directors for special collections & archives, metadata services, and digital initiatives. Curators, subject specialists and technical consultants are also members on a rotating basis. The Chair rotates every two years reporting to the Assistant University Librarian for Collections, and has a seat on the Digital Library Steering Committee. A project proposal requiring significant resources or a new technology goes to the Digital Library Steering Committee.
* [[Media:UCSD_projproposal_form.docx|Project proposals]] must be submitted with a [[Media:UCSD_Checklist_AccessOptions.docx | Checklist to Determine Access Options]] and are reviewed on an ongoing basis at the Digital Collections Group quarterly meetings or via email.

Please contribute additional information or other examples to the '''[[DLF Project Managers Toolkit]]'''. If you have examples to share, please provide some context, such as the purpose or goal, institution, teams and team size, etc.

== References ==
* Project Management Institute. 2018. A guide to the project management body of knowledge: (PMBOK® guide). Newtown Square, Pennsylvania, USA: Project Management Institute.

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.

Project Proposal Process

2022-06-19T19:57:29Z

Cristelags:

The project proposal process aims to provide a transparent framework and formal process for selecting and prioritizing projects while improving the overall workflow and workload of those involved.

Determine who will be approving project proposals and how often.

Consider the selection criteria. Possible criteria might include:
* Programmatic Value: the project supports current or emerging research and instruction in one or more specific subject areas or supports the academic work of one or more defined user groups or information communities
* Instructional Support: the project is intended for eReserves or campus-use only
* Accessibility/Added Value: the project enhances the value and/or the preservation of the existing collection(s) by making it more accessible, better integrated, and/or more likely to be used
* Open Access for research and teaching: the copyright status of the collection makes this project available for open access
* Historical/Cultural Value: the project contributes to the existing collections, history and culture of the University, the region, national or international communities
* Intrinsic Value: the materials are rare or there is some other self-evident value that the project would contribute to the University and the Libraries
* Collaborative Value: the project promotes internal collaboration between or among units of the Libraries, between the Libraries and other University units, and/or external collaboration with other institutions
* Developmental Value: the project promotes a specific developmental or stewardship initiative
* Public Service Value: the project serves users in the Libraries, the University, and beyond the immediate University community
* Viability: the project has a demonstrated commitment and support from the project proposing unit, and avoids duplication of effort

Also consider:
* Is this project fully defined with a specific objective with a start and end date?
* What impact the project might have on the daily work of the team, the program, or other programs?
* What technical capabilities and services might be involved in this project and require to maintain?
* Are there specific funding or resources requirements?
* Are there any scheduling issues or obstacles that need to be addressed?

== Examples ==
At the UC San Diego Library, digital project proposals are submitted to the Digital Collections Group, which consists of the program directors for special collections & archives, metadata services, and digital initiatives. Curators, subject specialists and technical consultants are also members on a rotating basis. The Chair rotates every two years reporting to the Assistant University Librarian for Collections, and has a seat on the Digital Library Steering Committee. A project proposal requiring significant resources or a new technology goes to the Digital Library Steering Committee.
[[Media:UCSD_projproposal_form.docx|Project proposals]] must be submitted with a [[Media:UCSD_Checklist_AccessOptions.docx | Checklist to Determine Access Options]] and are reviewed on an ongoing basis at the Digital Collections Group quarterly meetings or via email.

Please contribute additional information or other examples to the '''[[DLF Project Managers Toolkit]]'''. If you have examples to share, please provide some context, such as the purpose or goal, institution, teams and team size, etc.

== References ==
* Project Management Institute. 2018. A guide to the project management body of knowledge: (PMBOK® guide). Newtown Square, Pennsylvania, USA: Project Management Institute.

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.

Project Proposal Process

2022-06-19T19:56:49Z

Cristelags:

The project proposal process aims to provide a transparent framework and formal process for selecting and prioritizing projects while improving the overall workflow and workload of those involved.

Determine who will be approving project proposals and how often.

Consider the selection criteria. Possible criteria might include:
* Programmatic Value: the project supports current or emerging research and instruction in one or more specific subject areas or supports the academic work of one or more defined user groups or information communities
* Instructional Support: the project is intended for eReserves or campus-use only
* Accessibility/Added Value: the project enhances the value and/or the preservation of the existing collection(s) by making it more accessible, better integrated, and/or more likely to be used
* Open Access for research and teaching: the copyright status of the collection makes this project available for open access
* Historical/Cultural Value: the project contributes to the existing collections, history and culture of the University, the region, national or international communities
* Intrinsic Value: the materials are rare or there is some other self-evident value that the project would contribute to the University and the Libraries
* Collaborative Value: the project promotes internal collaboration between or among units of the Libraries, between the Libraries and other University units, and/or external collaboration with other institutions
* Developmental Value: the project promotes a specific developmental or stewardship initiative
* Public Service Value: the project serves users in the Libraries, the University, and beyond the immediate University community
* Viability: the project has a demonstrated commitment and support from the project proposing unit, and avoids duplication of effort

Also consider:
* Is this project fully defined with a specific objective with a start and end date?
* What impact the project might have on the daily work of the team, the program, or other programs?
* What technical capabilities and services might be involved in this project and require to maintain?
* Are there specific funding or resources requirements?
* Are there any scheduling issues or obstacles that need to be addressed?

At the UC San Diego Library, digital project proposals are submitted to the Digital Collections Group, which consists of the program directors for special collections & archives, metadata services, and digital initiatives. Curators, subject specialists and technical consultants are also members on a rotating basis. The Chair rotates every two years reporting to the Assistant University Librarian for Collections, and has a seat on the Digital Library Steering Committee. A project proposal requiring significant resources or a new technology goes to the Digital Library Steering Committee.
[[Media:UCSD_projproposal_form.docx|Project proposals]] must be submitted with a [[Media:UCSD_Checklist_AccessOptions.docx | Checklist to Determine Access Options]] and are reviewed on an ongoing basis at the Digital Collections Group quarterly meetings or via email.

Please contribute additional information or other examples to the '''[[DLF Project Managers Toolkit]]'''. If you have examples to share, please provide some context, such as the purpose or goal, institution, teams and team size, etc.

== References ==
* Project Management Institute. 2018. A guide to the project management body of knowledge: (PMBOK® guide). Newtown Square, Pennsylvania, USA: Project Management Institute.

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.

Project Proposal Process

2022-06-19T19:54:14Z

Cristelags:

The project proposal process aims to provide a transparent framework and formal process for selecting and prioritizing projects while improving the overall workflow and workload of those involved.

Determine who will be approving project proposals and how often.

Consider the selection criteria. Possible criteria might include:
* Programmatic Value: the project supports current or emerging research and instruction in one or more specific subject areas or supports the academic work of one or more defined user groups or information communities
* Instructional Support: the project is intended for eReserves or campus-use only
* Accessibility/Added Value: the project enhances the value and/or the preservation of the existing collection(s) by making it more accessible, better integrated, and/or more likely to be used
* Open Access for research and teaching: the copyright status of the collection makes this project available for open access
* Historical/Cultural Value: the project contributes to the existing collections, history and culture of the University, the region, national or international communities
* Intrinsic Value: the materials are rare or there is some other self-evident value that the project would contribute to the University and the Libraries
* Collaborative Value: the project promotes internal collaboration between or among units of the Libraries, between the Libraries and other University units, and/or external collaboration with other institutions
* Developmental Value: the project promotes a specific developmental or stewardship initiative
* Public Service Value: the project serves users in the Libraries, the University, and beyond the immediate University community
* Viability: the project has a demonstrated commitment and support from the project proposing unit, and avoids duplication of effort

Also consider:
* Is this project fully defined with a specific objective with a start and end date?
* What impact the project might have on the daily work of the team, the program, or other programs?
* What technical capabilities and services might be involved in this project and require to maintain?
* Are there specific funding or resources requirements?
* Are there any scheduling issues or obstacles that need to be addressed?

At the UC San Diego Library, digital project proposals are submitted to the Digital Collections Group, which consists of the program directors for special collections & archives, metadata services, and digital initiatives. Curators, subject specialists and technical consultants are also members on a rotating basis. The Chair rotates every two years reporting to the Assistant University Librarian for Collections, and has a seat on the Digital Library Steering Committee. A project proposal requiring significant resources or a new technology goes to the Digital Library Steering Committee.
[[File:UCSD_projproposal_form.docx | Project proposals]] must be submitted with a [[File:UCSD_Checklist_AccessOptions.docx | Checklist to Determine Access Options]] and are reviewed on an ongoing basis at the Digital Collections Group quarterly meetings or via email.

Please contribute additional information or other examples to the '''[[DLF Project Managers Toolkit]]'''. If you have examples to share, please provide some context, such as the purpose or goal, institution, teams and team size, etc.

== References ==
* Project Management Institute. 2018. A guide to the project management body of knowledge: (PMBOK® guide). Newtown Square, Pennsylvania, USA: Project Management Institute.

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.

Project Proposal Process

2022-06-19T19:52:52Z

Cristelags:

The project proposal process aims to provide a transparent framework and formal process for selecting and prioritizing projects while improving the overall workflow and workload of those involved.

Determine who will be approving project proposals and how often.

Consider the selection criteria. Possible criteria might include:
* Programmatic Value: the project supports current or emerging research and instruction in one or more specific subject areas or supports the academic work of one or more defined user groups or information communities
* Instructional Support: the project is intended for eReserves or campus-use only
* Accessibility/Added Value: the project enhances the value and/or the preservation of the existing collection(s) by making it more accessible, better integrated, and/or more likely to be used
* Open Access for research and teaching: the copyright status of the collection makes this project available for open access
* Historical/Cultural Value: the project contributes to the existing collections, history and culture of the University, the region, national or international communities
* Intrinsic Value: the materials are rare or there is some other self-evident value that the project would contribute to the University and the Libraries
* Collaborative Value: the project promotes internal collaboration between or among units of the Libraries, between the Libraries and other University units, and/or external collaboration with other institutions
* Developmental Value: the project promotes a specific developmental or stewardship initiative
* Public Service Value: the project serves users in the Libraries, the University, and beyond the immediate University community
* Viability: the project has a demonstrated commitment and support from the project proposing unit, and avoids duplication of effort

Also consider:
* Is this project fully defined with a specific objective with a start and end date?
* What impact the project might have on the daily work of the team, the program, or other programs?
* What technical capabilities and services might be involved in this project and require to maintain?
* Are there specific funding or resources requirements?
* Are there any scheduling issues or obstacles that need to be addressed?

At the UC San Diego Library, digital project proposals are submitted to the Digital Collections Group, which consists of the program directors for special collections & archives, metadata services, and digital initiatives. Curators, subject specialists and technical consultants are also members on a rotating basis. The Chair rotates every two years reporting to the Assistant University Librarian for Collections, and has a seat on the Digital Library Steering Committee. A project proposal requiring significant resources or a new technology goes to the Digital Library Steering Committee.
Project proposals must be submitted with a [[File:UCSD_Checklist_AccessOptions.docx|Checklist to Determine Access Options]] and are reviewed on an ongoing basis at the Digital Collections Group quarterly meetings or via email.

Please contribute additional information or other examples to the '''[[DLF Project Managers Toolkit]]'''. If you have examples to share, please provide some context, such as the purpose or goal, institution, teams and team size, etc.

== References ==
* Project Management Institute. 2018. A guide to the project management body of knowledge: (PMBOK® guide). Newtown Square, Pennsylvania, USA: Project Management Institute.

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.

File:UCSD Checklist AccessOptions.docx

2022-06-19T19:51:10Z

Cristelags: The UC San Diego Library checklist for determining access options is used in the project proposal process.

== Summary ==
The UC San Diego Library checklist for determining access options is used in the project proposal process.
== Licensing ==
{{CC-by-sa-2.5}}

File:UCSD projproposal form.docx

2022-06-19T19:47:09Z

Cristelags:

UC San Diego Library digital project proposal form

Project Proposal Process

2022-06-19T19:43:16Z

Cristelags:

The project proposal process aims to provide a transparent framework and formal process for selecting and prioritizing projects while improving the overall workflow and workload of those involved.

Determine who will be approving project proposals and how often.

Consider the selection criteria. Possible criteria might include:
* Programmatic Value: the project supports current or emerging research and instruction in one or more specific subject areas or supports the academic work of one or more defined user groups or information communities
* Instructional Support: the project is intended for eReserves or campus-use only
* Accessibility/Added Value: the project enhances the value and/or the preservation of the existing collection(s) by making it more accessible, better integrated, and/or more likely to be used
* Open Access for research and teaching: the copyright status of the collection makes this project available for open access
* Historical/Cultural Value: the project contributes to the existing collections, history and culture of the University, the region, national or international communities
* Intrinsic Value: the materials are rare or there is some other self-evident value that the project would contribute to the University and the Libraries
* Collaborative Value: the project promotes internal collaboration between or among units of the Libraries, between the Libraries and other University units, and/or external collaboration with other institutions
* Developmental Value: the project promotes a specific developmental or stewardship initiative
* Public Service Value: the project serves users in the Libraries, the University, and beyond the immediate University community
* Viability: the project has a demonstrated commitment and support from the project proposing unit, and avoids duplication of effort

Also consider:
* Is this project fully defined with a specific objective with a start and end date?
* What impact the project might have on the daily work of the team, the program, or other programs?
* What technical capabilities and services might be involved in this project and require to maintain?
* Are there specific funding or resources requirements?
* Are there any scheduling issues or obstacles that need to be addressed?

At the UC San Diego Library, digital project proposals are submitted to the Digital Collections Group, which consists of the program directors for special collections & archives, metadata services, and digital initiatives. Curators, subject specialists and technical consultants are also members on a rotating basis. The Chair rotates every two years reporting to the Assistant University Librarian for Collections, and has a seat on the Digital Library Steering Committee. A project proposal requiring significant resources or a new technology goes to the Digital Library Steering Committee.
Project proposals must be submitted with a checklist to determine access options and are reviewed on an ongoing basis at the Digital Collections Group quarterly meetings or via email.

Please contribute additional information or other examples to the '''[[DLF Project Managers Toolkit]]'''. If you have examples to share, please provide some context, such as the purpose or goal, institution, teams and team size, etc.

== References ==
* Project Management Institute. 2018. A guide to the project management body of knowledge: (PMBOK® guide). Newtown Square, Pennsylvania, USA: Project Management Institute.

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.

Project Proposal Process

2022-06-19T17:30:01Z

Cristelags: /* Project Proposal Process */

Project Proposal Process

2022-06-19T17:29:25Z

Cristelags: Created page with "=== Project Proposal Process === The project proposal process aims to provide a transparent framework and formal process for selecting and prioritizing projects while improving the overall workflow and workload of those involved. Consider who will be approving project proposals and how often. Also consider the selection criteria. Possible criteria might include: * Programmatic Value: the project supports current or emerging research and instruction in one or more speci..."

=== Project Proposal Process ===
The project proposal process aims to provide a transparent framework and formal process for selecting and prioritizing projects while improving the overall workflow and workload of those involved.

Consider who will be approving project proposals and how often.

Also consider the selection criteria. Possible criteria might include:
* Programmatic Value: the project supports current or emerging research and instruction in one or more specific subject areas or supports the academic work of one or more defined user groups or information communities
* Instructional Support: the project is intended for eReserves or campus-use only
* Accessibility/Added Value: the project enhances the value and/or the preservation of the existing collection(s) by making it more accessible, better integrated, and/or more likely to be used
* Open Access for research and teaching: the copyright status of the collection makes this project available for open access
* Historical/Cultural Value: the project contributes to the existing collections, history and culture of the University, the region, national or international communities
* Intrinsic Value: the materials are rare or there is some other self-evident value that the project would contribute to the University and the Libraries
* Collaborative Value: the project promotes internal collaboration between or among units of the Libraries, between the Libraries and other University units, and/or external collaboration with other institutions
* Developmental Value: the project promotes a specific developmental or stewardship initiative
* Public Service Value: the project serves users in the Libraries, the University, and beyond the immediate University community
* Viability: the project has a demonstrated commitment and support from the project proposing unit, and avoids duplication of effort

Please contribute additional information or other examples to the '''[[DLF Project Managers Toolkit]]'''. If you have examples to share, please provide some context, such as the purpose or goal, institution, teams and team size, etc.

== References ==
* Project Management Institute. 2018. A guide to the project management body of knowledge: (PMBOK® guide). Newtown Square, Pennsylvania, USA: Project Management Institute.

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.

Project management methodology (PMM)

2021-11-06T18:29:50Z

Cristelags:

Project management methodology (PMM) is a system of principles, techniques, and procedures.

Factors in choosing a PM Method
* Project goals, objectives, and complexity
* Team - size, level of experience/training, location - remote/on-site, specialization of roles
* Timeline
* Budget
* Stakeholder expectations
* Values/organizational culture
* Ability to take risk
* Flexibility for change

The following is an overview of a few different PMM that hopefully inspires curiosity to learn more. Please contribute additional PMM or other examples to the '''[[DLF Project Managers Toolkit]]'''.

[[File:Waterfall.png|200px|left]] waterfall (software development)
* detailed linear process of tasks in sequential order
* project flows downward like waterfall
* comprehensive, predictable and planned out
* focus on documentation
* good for large projects with multiple stakeholders
* not flexible, if assumptions are wrong, hard to pivot

[[File:CPM.png|350px|left]] critical path method (CPM) (industry)
* identify and schedule tasks, duration and dependencies
* good for tight timelines and repetitive activities
* not good if unsure of timelines, durations for tasks
* not flexible if there are major changes

[[File:Agile.png|150px|left]] agile (software development)
* reaction to waterfall method http://agilemanifesto.org/
* "early and often, adjust and iterate"
* flexible and responsive to change
* stakeholders must stay engaged and be available to provide timely feedback
* not always fast in practice if constantly changing deliverables
* not focused on comprehensive documentation

There are many agile approaches including scrum, kanban, feature-driven development, and extreme programming.

[[File:Scrum.png|350px|left]] scrum (software development)
* small, cross functional teams
* short sprints
* regular "stand-up" meeting
* retrospectives after each sprint
* focus on continual optimization and improvements
* harder to do with fixed budgets and timelines
* self-managing teams can have issues with scope creep

[[File:Kanban.png|300px|left]] kanban (industry)
* billboard in Japanese
* simple, clear framework
* visualize workflow and tasks
* large and small teams, remote or in person
* not detailed "at-a-glance"
* not if complex, lots of steps in the process

hybrid/structured agile
* combine waterfall and agile methods
* focus on gathering and analyzing requirements then rapid iterations
* best of both worlds - structure and flexibility
* best for medium-sized project with high complexity and fixed budgets

[[File:SixSigma.png|200px|left]]
Lean Six Sigma (industry)
* Define, Measure, Analyze, Improve, Control
* cut waste and maximize efficiency
* quality management, continuous improvement
* measuring > analyzing > improving
* large organizations or efficiency is an issue

Integrated Project Management (IPM)
* focus on documents like project charter, plan, execution, monitoring and change control
* meet regularly as team
* accountability
* time for planning

PRiSM Projects Integrating Sustainable Methods
* developed by Green Project Management Global
* account and minimize adverse environmental impacts
* extends beyond the end of the project
* factors in environmental costs and sustainability is key success criteria
* mostly geared to real estate and industrial projects

Approaches also worth noting:
* Human-centered design - creative approach to problem solving with three phases: inspiration, ideation, implementation; start with people in mind, try it out and test with people in an iterative process.
* Participatory decision-making - creative approach to enabling the entire group ownership and participation in decisions. It includes an emphasis on facilitation and concensus-building.
* Participatory Action Research (PAR) is an approach to research emphasizing co-creation, participation, and action by members of communities affected by the research.

== References ==
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.

Project management methodology (PMM)

2021-11-06T18:29:27Z

Cristelags:

Project management methodology (PMM) is a system of principles, techniques, and procedures.

Factors in choosing a PM Method
* Project goals, objectives, and complexity
* Team - size, level of experience/training, location - remote/on-site, specialization of roles
* Timeline
* Budget
* Stakeholder expectations
* Values/organizational culture
* Ability to take risk
* Flexibility for change

The following is an overview of a few different PMM that hopefully inspires curiosity to learn more. Please contribute additional PMM or other examples to the '''[[DLF Project Managers Toolkit]]'''.

[[File:Waterfall.png|200px|left]] waterfall (software development)
* detailed linear process of tasks in sequential order
* project flows downward like waterfall
* comprehensive, predictable and planned out
* focus on documentation
* good for large projects with multiple stakeholders
* not flexible, if assumptions are wrong, hard to pivot

[[File:CPM.png|350px|left]] critical path method (CPM) (industry)
* identify and schedule tasks, duration and dependencies
* good for tight timelines and repetitive activities
* not good if unsure of timelines, durations for tasks
* not flexible if there are major changes

[[File:Agile.png|150px|left]] agile (software development)
* reaction to waterfall method http://agilemanifesto.org/
* "early and often, adjust and iterate"
* flexible and responsive to change
* stakeholders must stay engaged and be available to provide timely feedback
* not always fast in practice if constantly changing deliverables
* not focused on comprehensive documentation

There are many agile approaches including scrum, kanban, feature-driven development, and extreme programming.

[[File:Scrum.png|300px|left]] scrum (software development)
* small, cross functional teams
* short sprints
* regular "stand-up" meeting
* retrospectives after each sprint
* focus on continual optimization and improvements
* harder to do with fixed budgets and timelines
* self-managing teams can have issues with scope creep

[[File:Kanban.png|300px|left]] kanban (industry)
* billboard in Japanese
* simple, clear framework
* visualize workflow and tasks
* large and small teams, remote or in person
* not detailed "at-a-glance"
* not if complex, lots of steps in the process

hybrid/structured agile
* combine waterfall and agile methods
* focus on gathering and analyzing requirements then rapid iterations
* best of both worlds - structure and flexibility
* best for medium-sized project with high complexity and fixed budgets

[[File:SixSigma.png|200px|left]]
Lean Six Sigma (industry)
* Define, Measure, Analyze, Improve, Control
* cut waste and maximize efficiency
* quality management, continuous improvement
* measuring > analyzing > improving
* large organizations or efficiency is an issue

Integrated Project Management (IPM)
* focus on documents like project charter, plan, execution, monitoring and change control
* meet regularly as team
* accountability
* time for planning

PRiSM Projects Integrating Sustainable Methods
* developed by Green Project Management Global
* account and minimize adverse environmental impacts
* extends beyond the end of the project
* factors in environmental costs and sustainability is key success criteria
* mostly geared to real estate and industrial projects

Approaches also worth noting:
* Human-centered design - creative approach to problem solving with three phases: inspiration, ideation, implementation; start with people in mind, try it out and test with people in an iterative process.
* Participatory decision-making - creative approach to enabling the entire group ownership and participation in decisions. It includes an emphasis on facilitation and concensus-building.
* Participatory Action Research (PAR) is an approach to research emphasizing co-creation, participation, and action by members of communities affected by the research.

== References ==
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.

Project management methodology (PMM)

2021-11-06T18:29:07Z

Cristelags:

Project management methodology (PMM) is a system of principles, techniques, and procedures.

Factors in choosing a PM Method
* Project goals, objectives, and complexity
* Team - size, level of experience/training, location - remote/on-site, specialization of roles
* Timeline
* Budget
* Stakeholder expectations
* Values/organizational culture
* Ability to take risk
* Flexibility for change

The following is an overview of a few different PMM that hopefully inspires curiosity to learn more. Please contribute additional PMM or other examples to the '''[[DLF Project Managers Toolkit]]'''.

[[File:Waterfall.png|200px|left]] waterfall (software development)
* detailed linear process of tasks in sequential order
* project flows downward like waterfall
* comprehensive, predictable and planned out
* focus on documentation
* good for large projects with multiple stakeholders
* not flexible, if assumptions are wrong, hard to pivot

[[File:CPM.png|350px|left]] critical path method (CPM) (industry)
* identify and schedule tasks, duration and dependencies
* good for tight timelines and repetitive activities
* not good if unsure of timelines, durations for tasks
* not flexible if there are major changes

[[File:Agile.png|150px|left]] agile (software development)
* reaction to waterfall method http://agilemanifesto.org/
* "early and often, adjust and iterate"
* flexible and responsive to change
* stakeholders must stay engaged and be available to provide timely feedback
* not always fast in practice if constantly changing deliverables
* not focused on comprehensive documentation

 
There are many agile approaches including scrum, kanban, feature-driven development, and extreme programming.

[[File:Scrum.png|300px|left]] scrum (software development)
* small, cross functional teams
* short sprints
* regular "stand-up" meeting
* retrospectives after each sprint
* focus on continual optimization and improvements
* harder to do with fixed budgets and timelines
* self-managing teams can have issues with scope creep

[[File:Kanban.png|300px|left]] kanban (industry)
* billboard in Japanese
* simple, clear framework
* visualize workflow and tasks
* large and small teams, remote or in person
* not detailed "at-a-glance"
* not if complex, lots of steps in the process

hybrid/structured agile
* combine waterfall and agile methods
* focus on gathering and analyzing requirements then rapid iterations
* best of both worlds - structure and flexibility
* best for medium-sized project with high complexity and fixed budgets

[[File:SixSigma.png|200px|left]]
Lean Six Sigma (industry)
* Define, Measure, Analyze, Improve, Control
* cut waste and maximize efficiency
* quality management, continuous improvement
* measuring > analyzing > improving
* large organizations or efficiency is an issue

Integrated Project Management (IPM)
* focus on documents like project charter, plan, execution, monitoring and change control
* meet regularly as team
* accountability
* time for planning

PRiSM Projects Integrating Sustainable Methods
* developed by Green Project Management Global
* account and minimize adverse environmental impacts
* extends beyond the end of the project
* factors in environmental costs and sustainability is key success criteria
* mostly geared to real estate and industrial projects

Approaches also worth noting:
* Human-centered design - creative approach to problem solving with three phases: inspiration, ideation, implementation; start with people in mind, try it out and test with people in an iterative process.
* Participatory decision-making - creative approach to enabling the entire group ownership and participation in decisions. It includes an emphasis on facilitation and concensus-building.
* Participatory Action Research (PAR) is an approach to research emphasizing co-creation, participation, and action by members of communities affected by the research.

== References ==
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.

Project management methodology (PMM)

2021-11-06T18:28:46Z

Cristelags:

Project management methodology (PMM) is a system of principles, techniques, and procedures.

Factors in choosing a PM Method
* Project goals, objectives, and complexity
* Team - size, level of experience/training, location - remote/on-site, specialization of roles
* Timeline
* Budget
* Stakeholder expectations
* Values/organizational culture
* Ability to take risk
* Flexibility for change

The following is an overview of a few different PMM that hopefully inspires curiosity to learn more. Please contribute additional PMM or other examples to the '''[[DLF Project Managers Toolkit]]'''.[br]

[[File:Waterfall.png|200px|left]] waterfall (software development)
* detailed linear process of tasks in sequential order
* project flows downward like waterfall
* comprehensive, predictable and planned out
* focus on documentation
* good for large projects with multiple stakeholders
* not flexible, if assumptions are wrong, hard to pivot[br]

[[File:CPM.png|350px|left]] critical path method (CPM) (industry)
* identify and schedule tasks, duration and dependencies
* good for tight timelines and repetitive activities
* not good if unsure of timelines, durations for tasks
* not flexible if there are major changes

[[File:Agile.png|150px|left]] agile (software development)
* reaction to waterfall method http://agilemanifesto.org/
* "early and often, adjust and iterate"
* flexible and responsive to change
* stakeholders must stay engaged and be available to provide timely feedback
* not always fast in practice if constantly changing deliverables
* not focused on comprehensive documentation

 
There are many agile approaches including scrum, kanban, feature-driven development, and extreme programming.

[[File:Scrum.png|300px|left]] scrum (software development)
* small, cross functional teams
* short sprints
* regular "stand-up" meeting
* retrospectives after each sprint
* focus on continual optimization and improvements
* harder to do with fixed budgets and timelines
* self-managing teams can have issues with scope creep

[[File:Kanban.png|300px|left]] kanban (industry)
* billboard in Japanese
* simple, clear framework
* visualize workflow and tasks
* large and small teams, remote or in person
* not detailed "at-a-glance"
* not if complex, lots of steps in the process

hybrid/structured agile
* combine waterfall and agile methods
* focus on gathering and analyzing requirements then rapid iterations
* best of both worlds - structure and flexibility
* best for medium-sized project with high complexity and fixed budgets

[[File:SixSigma.png|200px|left]]
Lean Six Sigma (industry)
* Define, Measure, Analyze, Improve, Control
* cut waste and maximize efficiency
* quality management, continuous improvement
* measuring > analyzing > improving
* large organizations or efficiency is an issue

Integrated Project Management (IPM)
* focus on documents like project charter, plan, execution, monitoring and change control
* meet regularly as team
* accountability
* time for planning

PRiSM Projects Integrating Sustainable Methods
* developed by Green Project Management Global
* account and minimize adverse environmental impacts
* extends beyond the end of the project
* factors in environmental costs and sustainability is key success criteria
* mostly geared to real estate and industrial projects

Approaches also worth noting:
* Human-centered design - creative approach to problem solving with three phases: inspiration, ideation, implementation; start with people in mind, try it out and test with people in an iterative process.
* Participatory decision-making - creative approach to enabling the entire group ownership and participation in decisions. It includes an emphasis on facilitation and concensus-building.
* Participatory Action Research (PAR) is an approach to research emphasizing co-creation, participation, and action by members of communities affected by the research.

== References ==
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.

Project management methodology (PMM)

2021-11-06T18:26:38Z

Cristelags:

Project management methodology (PMM) is a system of principles, techniques, and procedures.

Factors in choosing a PM Method
* Project goals, objectives, and complexity
* Team - size, level of experience/training, location - remote/on-site, specialization of roles
* Timeline
* Budget
* Stakeholder expectations
* Values/organizational culture
* Ability to take risk
* Flexibility for change

The following is an overview of a few different PMM that hopefully inspires curiosity to learn more. Please contribute additional PMM or other examples to the '''[[DLF Project Managers Toolkit]]'''.

[[File:Waterfall.png|200px|left]] waterfall (software development)
* detailed linear process of tasks in sequential order
* project flows downward like waterfall
* comprehensive, predictable and planned out
* focus on documentation
* good for large projects with multiple stakeholders
* not flexible, if assumptions are wrong, hard to pivot

[[File:CPM.png|350px|left]] critical path method (CPM) (industry)
* identify and schedule tasks, duration and dependencies
* good for tight timelines and repetitive activities
* not good if unsure of timelines, durations for tasks
* not flexible if there are major changes

[[File:Agile.png|150px|left]] agile (software development)
* reaction to waterfall method http://agilemanifesto.org/
* "early and often, adjust and iterate"
* flexible and responsive to change
* stakeholders must stay engaged and be available to provide timely feedback
* not always fast in practice if constantly changing deliverables
* not focused on comprehensive documentation

 
There are many agile approaches including scrum, kanban, feature-driven development, and extreme programming.

[[File:Scrum.png|300px|left]] scrum (software development)
* small, cross functional teams
* short sprints
* regular "stand-up" meeting
* retrospectives after each sprint
* focus on continual optimization and improvements
* harder to do with fixed budgets and timelines
* self-managing teams can have issues with scope creep

[[File:Kanban.png|300px|left]] kanban (industry)
* billboard in Japanese
* simple, clear framework
* visualize workflow and tasks
* large and small teams, remote or in person
* not detailed "at-a-glance"
* not if complex, lots of steps in the process

hybrid/structured agile
* combine waterfall and agile methods
* focus on gathering and analyzing requirements then rapid iterations
* best of both worlds - structure and flexibility
* best for medium-sized project with high complexity and fixed budgets

[[File:SixSigma.png|200px|left]]
Lean Six Sigma (industry)
* Define, Measure, Analyze, Improve, Control
* cut waste and maximize efficiency
* quality management, continuous improvement
* measuring > analyzing > improving
* large organizations or efficiency is an issue

Integrated Project Management (IPM)
* focus on documents like project charter, plan, execution, monitoring and change control
* meet regularly as team
* accountability
* time for planning

PRiSM Projects Integrating Sustainable Methods
* developed by Green Project Management Global
* account and minimize adverse environmental impacts
* extends beyond the end of the project
* factors in environmental costs and sustainability is key success criteria
* mostly geared to real estate and industrial projects

Approaches also worth noting:
* Human-centered design - creative approach to problem solving with three phases: inspiration, ideation, implementation; start with people in mind, try it out and test with people in an iterative process.
* Participatory decision-making - creative approach to enabling the entire group ownership and participation in decisions. It includes an emphasis on facilitation and concensus-building.
* Participatory Action Research (PAR) is an approach to research emphasizing co-creation, participation, and action by members of communities affected by the research.

== References ==
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.

Project management methodology (PMM)

2021-11-06T18:23:32Z

Cristelags:

Project management methodology (PMM) is a system of principles, techniques, and procedures.

Factors in choosing a PM Method
* Project goals, objectives, and complexity
* Team - size, level of experience/training, location - remote/on-site, specialization of roles
* Timeline
* Budget
* Stakeholder expectations
* Values/organizational culture
* Ability to take risk
* Flexibility for change

The following is an overview of a few different PMM that hopefully inspires curiosity to learn more. Please contribute additional PMM or other examples to the '''[[DLF Project Managers Toolkit]]'''.

[[File:Waterfall.png|200px|left]] waterfall (software development)
* detailed linear process of tasks in sequential order
* project flows downward like waterfall
* comprehensive, predictable and planned out
* focus on documentation
* good for large projects with multiple stakeholders
* not flexible, if assumptions are wrong, hard to pivot

[[File:CPM.png|350px|left]] critical path method (CPM) (industry)
* identify and schedule tasks, duration and dependencies
* good for tight timelines and repetitive activities
* not good if unsure of timelines, durations for tasks
* not flexible if there are major changes

[[File:Agile.png|150px|left]] agile (software development)
* reaction to waterfall method http://agilemanifesto.org/
* "early and often, adjust and iterate"
* flexible and responsive to change
* stakeholders must stay engaged and be available to provide timely feedback
* not always fast in practice if constantly changing deliverables
* not focused on comprehensive documentation

There are many agile approaches including scrum, kanban, feature-driven development, and extreme programming.

[[File:Scrum.png|200px|left]] scrum (software development)
* small, cross functional teams
* short sprints
* regular "stand-up" meeting
* retrospectives after each sprint
* focus on continual optimization and improvements
* harder to do with fixed budgets and timelines
* self-managing teams can have issues with scope creep

[[File:Kanban.png|200px|left]] kanban (industry)
* billboard in Japanese
* simple, clear framework
* visualize workflow and tasks
* large and small teams, remote or in person
* not detailed "at-a-glance"
* not if complex, lots of steps in the process

hybrid/structured agile
* combine waterfall and agile methods
* focus on gathering and analyzing requirements then rapid iterations
* best of both worlds - structure and flexibility
* best for medium-sized project with high complexity and fixed budgets

[[File:SixSigma.png|200px|left]]
Lean Six Sigma (industry)
* Define, Measure, Analyze, Improve, Control
* cut waste and maximize efficiency
* quality management, continuous improvement
* measuring > analyzing > improving
* large organizations or efficiency is an issue

Integrated Project Management (IPM)
* focus on documents like project charter, plan, execution, monitoring and change control
* meet regularly as team
* accountability
* time for planning

PRiSM Projects Integrating Sustainable Methods
* developed by Green Project Management Global
* account and minimize adverse environmental impacts
* extends beyond the end of the project
* factors in environmental costs and sustainability is key success criteria
* mostly geared to real estate and industrial projects

Approaches also worth noting:
* Human-centered design - creative approach to problem solving with three phases: inspiration, ideation, implementation; start with people in mind, try it out and test with people in an iterative process.
* Participatory decision-making - creative approach to enabling the entire group ownership and participation in decisions. It includes an emphasis on facilitation and concensus-building.
* Participatory Action Research (PAR) is an approach to research emphasizing co-creation, participation, and action by members of communities affected by the research.

== References ==
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.

Project management methodology (PMM)

2021-11-06T18:22:23Z

Cristelags:

Project management methodology (PMM) is a system of principles, techniques, and procedures.

Factors in choosing a PM Method
* Project goals, objectives, and complexity
* Team - size, level of experience/training, location - remote/on-site, specialization of roles
* Timeline
* Budget
* Stakeholder expectations
* Values/organizational culture
* Ability to take risk
* Flexibility for change

The following is an overview of a few different PMM that hopefully inspires curiosity to learn more. Please contribute additional PMM or other examples to the '''[[DLF Project Managers Toolkit]]'''.

[[File:Waterfall.png|200px|left]] waterfall (software development)
* detailed linear process of tasks in sequential order
* project flows downward like waterfall
* comprehensive, predictable and planned out
* focus on documentation
* good for large projects with multiple stakeholders
* not flexible, if assumptions are wrong, hard to pivot

[[File:CPM.png|350px|left]] critical path method (CPM) (industry)
* identify and schedule tasks, duration and dependencies
* good for tight timelines and repetitive activities
* not good if unsure of timelines, durations for tasks
* not flexible if there are major changes

[[File:Agile.png|150px|left]] agile (software development)
* reaction to waterfall method http://agilemanifesto.org/
* "early and often, adjust and iterate"
* flexible and responsive to change
* stakeholders must stay engaged and be available to provide timely feedback
* not always fast in practice if constantly changing deliverables
* not focused on comprehensive documentation

There are many agile approaches including scrum, kanban, feature-driven development, and extreme programming.

[[File:Scrum.png|200px|left]] scrum (software development)
* small, cross functional teams
* short sprints
* regular "stand-up" meeting
* retrospectives after each sprint
* focus on continual optimization and improvements
* harder to do with fixed budgets and timelines
* self-managing teams can have issues with scope creep

[[File:Kanban.png|200px|left]] kanban (industry)
* billboard in Japanese
* simple, clear framework
* visualize workflow and tasks
* large and small teams, remote or in person
* not detailed "at-a-glance"
* not if complex, lots of steps in the process

hybrid/structured agile
* combine waterfall and agile methods
* focus on gathering and analyzing requirements then rapid iterations
* best of both worlds - structure and flexibility
* best for medium-sized project with high complexity and fixed budgets

[[File:SixSigma.png|200px|left]]
Lean Six Sigma (industry)
* Define, Measure, Analyze, Improve, Control
* cut waste and maximize efficiency
* quality management, continuous improvement
* measuring > analyzing > improving
* large organizations or efficiency is an issue

Integrated Project Management (IPM)
* focus on documents like project charter, plan, execution, monitoring and change control
* meet regularly as team
* accountability
* time for planning

PRiSM Projects Integrating Sustainable Methods
* developed by Green Project Management Global
* account and minimize adverse environmental impacts
* extends beyond the end of the project
* factors in environmental costs and sustainability is key success criteria
* mostly geared to real estate and industrial projects

Approaches also worth noting:
* Human-centered design - creative approach to problem solving with three phases: inspiration, ideation, implementation; start with people in mind, try it out and test with people in an iterative process.
* Participatory decision-making - creative approach to enabling the entire group ownership and participation in decisions. It includes an emphasis on facilitation and concensus-building.
* Participatory Action Research (PAR) is an approach to research emphasizing co-creation, participation, and action by members of communities affected by the research.

== References ==
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.

File:SixSigma.png

2021-11-06T18:21:54Z

Cristelags:

Lean Six Sigma PMM

File:Kanban.png

2021-11-06T18:21:03Z

Cristelags:

Kanban PMM

File:Scrum.png

2021-11-06T18:20:05Z

Cristelags:

Scrum PMM

Project management methodology (PMM)

2021-11-06T18:11:30Z

Cristelags:

Project management methodology (PMM) is a system of principles, techniques, and procedures.

Factors in choosing a PM Method
* Project goals, objectives, and complexity
* Team - size, level of experience/training, location - remote/on-site, specialization of roles
* Timeline
* Budget
* Stakeholder expectations
* Values/organizational culture
* Ability to take risk
* Flexibility for change

The following is an overview of a few different PMM that hopefully inspires curiosity to learn more. Please contribute additional PMM or other examples to the '''[[DLF Project Managers Toolkit]]'''.

[[File:Waterfall.png|200px|left]] waterfall (software development)
* detailed linear process of tasks in sequential order
* project flows downward like waterfall
* comprehensive, predictable and planned out
* focus on documentation
* good for large projects with multiple stakeholders
* not flexible, if assumptions are wrong, hard to pivot

[[File:CPM.png|350px|left]] critical path method (CPM) (industry)
* identify and schedule tasks, duration and dependencies
* good for tight timelines and repetitive activities
* not good if unsure of timelines, durations for tasks
* not flexible if there are major changes

[[File:Agile.png|150px|left]] agile (software development)
* reaction to waterfall method http://agilemanifesto.org/
* "early and often, adjust and iterate"
* flexible and responsive to change
* stakeholders must stay engaged and be available to provide timely feedback
* not always fast in practice if constantly changing deliverables
* not focused on comprehensive documentation

There are many agile approaches including scrum, kanban, feature-driven development, and extreme programming.

scrum (software development)
* small, cross functional teams
* short sprints
* regular "stand-up" meeting
* retrospectives after each sprint
* focus on continual optimization and improvements
* harder to do with fixed budgets and timelines
* self-managing teams can have issues with scope creep

kanban (industry)
* billboard in Japanese
* simple, clear framework
* visualize workflow and tasks
* large and small teams, remote or in person
* not detailed "at-a-glance"
* not if complex, lots of steps in the process

hybrid/structured agile
* combine waterfall and agile methods
* focus on gathering and analyzing requirements then rapid iterations
* best of both worlds - structure and flexibility
* best for medium-sized project with high complexity and fixed budgets

Lean Six Sigma (industry)
* Define, Measure, Analyze, Improve, Control
* cut waste and maximize efficiency
* quality management, continuous improvement
* measuring > analyzing > improving
* large organizations or efficiency is an issue

Integrated Project Management (IPM)
* focus on documents like project charter, plan, execution, monitoring and change control
* meet regularly as team
* accountability
* time for planning

PRiSM Projects Integrating Sustainable Methods
* developed by Green Project Management Global
* account and minimize adverse environmental impacts
* extends beyond the end of the project
* factors in environmental costs and sustainability is key success criteria
* mostly geared to real estate and industrial projects

Approaches also worth noting:
* Human-centered design - creative approach to problem solving with three phases: inspiration, ideation, implementation; start with people in mind, try it out and test with people in an iterative process.
* Participatory decision-making - creative approach to enabling the entire group ownership and participation in decisions. It includes an emphasis on facilitation and concensus-building.
* Participatory Action Research (PAR) is an approach to research emphasizing co-creation, participation, and action by members of communities affected by the research.

== References ==
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.

Project management methodology (PMM)

2021-11-06T18:10:46Z

Cristelags:

Project management methodology (PMM) is a system of principles, techniques, and procedures.

Factors in choosing a PM Method
* Project goals, objectives, and complexity
* Team - size, level of experience/training, location - remote/on-site, specialization of roles
* Timeline
* Budget
* Stakeholder expectations
* Values/organizational culture
* Ability to take risk
* Flexibility for change

The following is an overview of a few different PMM that hopefully inspires curiosity to learn more. Please contribute additional PMM or other examples to the '''[[DLF Project Managers Toolkit]]'''.

[[File:Waterfall.png|200px|left]] waterfall (software development)
* detailed linear process of tasks in sequential order
* project flows downward like waterfall
* comprehensive, predictable and planned out
* focus on documentation
* good for large projects with multiple stakeholders
* not flexible, if assumptions are wrong, hard to pivot 

[[File:CPM.png|350px|left]] critical path method (CPM) (industry)
* identify and schedule tasks, duration and dependencies
* good for tight timelines and repetitive activities
* not good if unsure of timelines, durations for tasks
* not flexible if there are major changes 

[[File:Agile.png|150px|left]] agile (software development)
* reaction to waterfall method http://agilemanifesto.org/
* "early and often, adjust and iterate"
* flexible and responsive to change
* stakeholders must stay engaged and be available to provide timely feedback
* not always fast in practice if constantly changing deliverables
* not focused on comprehensive documentation 

There are many agile approaches including scrum, kanban, feature-driven development, and extreme programming.

scrum (software development)
* small, cross functional teams
* short sprints
* regular "stand-up" meeting
* retrospectives after each sprint
* focus on continual optimization and improvements
* harder to do with fixed budgets and timelines
* self-managing teams can have issues with scope creep

kanban (industry)
* billboard in Japanese
* simple, clear framework
* visualize workflow and tasks
* large and small teams, remote or in person
* not detailed "at-a-glance"
* not if complex, lots of steps in the process

hybrid/structured agile
* combine waterfall and agile methods
* focus on gathering and analyzing requirements then rapid iterations
* best of both worlds - structure and flexibility
* best for medium-sized project with high complexity and fixed budgets

Lean Six Sigma (industry)
* Define, Measure, Analyze, Improve, Control
* cut waste and maximize efficiency
* quality management, continuous improvement
* measuring > analyzing > improving
* large organizations or efficiency is an issue

Integrated Project Management (IPM)
* focus on documents like project charter, plan, execution, monitoring and change control
* meet regularly as team
* accountability
* time for planning

PRiSM Projects Integrating Sustainable Methods
* developed by Green Project Management Global
* account and minimize adverse environmental impacts
* extends beyond the end of the project
* factors in environmental costs and sustainability is key success criteria
* mostly geared to real estate and industrial projects

Approaches also worth noting:
* Human-centered design - creative approach to problem solving with three phases: inspiration, ideation, implementation; start with people in mind, try it out and test with people in an iterative process.
* Participatory decision-making - creative approach to enabling the entire group ownership and participation in decisions. It includes an emphasis on facilitation and concensus-building.
* Participatory Action Research (PAR) is an approach to research emphasizing co-creation, participation, and action by members of communities affected by the research.

== References ==
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.

Project management methodology (PMM)

2021-11-06T18:07:57Z

Cristelags:

Project management methodology (PMM) is a system of principles, techniques, and procedures.

Factors in choosing a PM Method
* Project goals, objectives, and complexity
* Team - size, level of experience/training, location - remote/on-site, specialization of roles
* Timeline
* Budget
* Stakeholder expectations
* Values/organizational culture
* Ability to take risk
* Flexibility for change

The following is an overview of a few different PMM that hopefully inspires curiosity to learn more. Please contribute additional PMM or other examples to the '''[[DLF Project Managers Toolkit]]'''.

[[File:Waterfall.png|200px|left]] waterfall (software development)
* detailed linear process of tasks in sequential order
* project flows downward like waterfall
* comprehensive, predictable and planned out
* focus on documentation
* good for large projects with multiple stakeholders
* not flexible, if assumptions are wrong, hard to pivot 

[[File:CPM.png|350px|left]] critical path method (CPM) (industry)
* identify and schedule tasks, duration and dependencies
* good for tight timelines and repetitive activities
* not good if unsure of timelines, durations for tasks
* not flexible if there are major changes 

[[File:Agile.png|150px|left]] agile (software development)
* reaction to waterfall method http://agilemanifesto.org/
* "early and often, adjust and iterate"
* flexible and responsive to change
* stakeholders must stay engaged and be available to provide timely feedback
* not always fast in practice if constantly changing deliverables
* not focused on comprehensive documentation 

There are many agile approaches including scrum, kanban, feature-driven development, and extreme programming.

scrum (software development)
* small, cross functional teams
* short sprints
* regular "stand-up" meeting
* retrospectives after each sprint
* focus on continual optimization and improvements
* harder to do with fixed budgets and timelines
* self-managing teams can have issues with scope creep

kanban (industry)
* billboard in Japanese
* simple, clear framework
* visualize workflow and tasks
* large and small teams, remote or in person
* not detailed "at-a-glance"
* not if complex, lots of steps in the process

hybrid/structured agile
* combine waterfall and agile methods
* focus on gathering and analyzing requirements then rapid iterations
* best of both worlds - structure and flexibility
* best for medium-sized project with high complexity and fixed budgets

Lean Six Sigma (industry)
* Define, Measure, Analyze, Improve, Control
* cut waste and maximize efficiency
* quality management, continuous improvement
* measuring > analyzing > improving
* large organizations or efficiency is an issue

Integrated Project Management (IPM)
* focus on documents like project charter, plan, execution, monitoring and change control
* meet regularly as team
* accountability
* time for planning

PRiSM Projects Integrating Sustainable Methods
* developed by Green Project Management Global
* account and minimize adverse environmental impacts
* extends beyond the end of the project
* factors in environmental costs and sustainability is key success criteria
* mostly geared to real estate and industrial projects

Approaches also worth noting:
* Human-centered design - creative approach to problem solving with three phases: inspiration, ideation, implementation; start with people in mind, try it out and test with people in an iterative process.
* Participatory decision-making - creative approach to enabling the entire group ownership and participation in decisions. It includes an emphasis on facilitation and concensus-building.
* Participatory Action Research (PAR) is an approach to research emphasizing co-creation, participation, and action by members of communities affected by the research.

== References ==
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.

Project management methodology (PMM)

2021-11-06T18:07:24Z

Cristelags:

Project management methodology (PMM) is a system of principles, techniques, and procedures.

Factors in choosing a PM Method
* Project goals, objectives, and complexity
* Team - size, level of experience/training, location - remote/on-site, specialization of roles
* Timeline
* Budget
* Stakeholder expectations
* Values/organizational culture
* Ability to take risk
* Flexibility for change

The following is an overview of a few different PMM that hopefully inspires curiosity to learn more. Please contribute additional PMM or other examples to the '''[[DLF Project Managers Toolkit]]'''.

[[File:Waterfall.png|200px|left]] waterfall (software development)
* detailed linear process of tasks in sequential order
* project flows downward like waterfall
* comprehensive, predictable and planned out
* focus on documentation
* good for large projects with multiple stakeholders
* not flexible, if assumptions are wrong, hard to pivot 

[[File:CPM.png|350px|left]] critical path method (CPM) (industry)
* identify and schedule tasks, duration and dependencies
* good for tight timelines and repetitive activities
* not good if unsure of timelines, durations for tasks
* not flexible if there are major changes

[[File:Agile.png|150px|left]]agile (software development)
* reaction to waterfall method http://agilemanifesto.org/
* "early and often, adjust and iterate"
* flexible and responsive to change
* stakeholders must stay engaged and be available to provide timely feedback
* not always fast in practice if constantly changing deliverables
* not focused on comprehensive documentation

There are many agile approaches including scrum, kanban, feature-driven development, and extreme programming.

scrum (software development)
* small, cross functional teams
* short sprints
* regular "stand-up" meeting
* retrospectives after each sprint
* focus on continual optimization and improvements
* harder to do with fixed budgets and timelines
* self-managing teams can have issues with scope creep

kanban (industry)
* billboard in Japanese
* simple, clear framework
* visualize workflow and tasks
* large and small teams, remote or in person
* not detailed "at-a-glance"
* not if complex, lots of steps in the process

hybrid/structured agile
* combine waterfall and agile methods
* focus on gathering and analyzing requirements then rapid iterations
* best of both worlds - structure and flexibility
* best for medium-sized project with high complexity and fixed budgets

Lean Six Sigma (industry)
* Define, Measure, Analyze, Improve, Control
* cut waste and maximize efficiency
* quality management, continuous improvement
* measuring > analyzing > improving
* large organizations or efficiency is an issue

Integrated Project Management (IPM)
* focus on documents like project charter, plan, execution, monitoring and change control
* meet regularly as team
* accountability
* time for planning

PRiSM Projects Integrating Sustainable Methods
* developed by Green Project Management Global
* account and minimize adverse environmental impacts
* extends beyond the end of the project
* factors in environmental costs and sustainability is key success criteria
* mostly geared to real estate and industrial projects

Approaches also worth noting:
* Human-centered design - creative approach to problem solving with three phases: inspiration, ideation, implementation; start with people in mind, try it out and test with people in an iterative process.
* Participatory decision-making - creative approach to enabling the entire group ownership and participation in decisions. It includes an emphasis on facilitation and concensus-building.
* Participatory Action Research (PAR) is an approach to research emphasizing co-creation, participation, and action by members of communities affected by the research.

== References ==
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.

Project management methodology (PMM)

2021-11-06T18:05:05Z

Cristelags:

Project management methodology (PMM) is a system of principles, techniques, and procedures.

Factors in choosing a PM Method
* Project goals, objectives, and complexity
* Team - size, level of experience/training, location - remote/on-site, specialization of roles
* Timeline
* Budget
* Stakeholder expectations
* Values/organizational culture
* Ability to take risk
* Flexibility for change

The following is an overview of a few different PMM that hopefully inspires curiosity to learn more. Please contribute additional PMM or other examples to the '''[[DLF Project Managers Toolkit]]'''.

[[File:Waterfall.png|200px|left]] p waterfall (software development)
* detailed linear process of tasks in sequential order
* project flows downward like waterfall
* comprehensive, predictable and planned out
* focus on documentation
* good for large projects with multiple stakeholders
* not flexible, if assumptions are wrong, hard to pivot

[[File:CPM.png|350px|left]] p critical path method (CPM) (industry)
* identify and schedule tasks, duration and dependencies
* good for tight timelines and repetitive activities
* not good if unsure of timelines, durations for tasks
* not flexible if there are major changes

[[File:Agile.png|150px|left]]agile (software development)
* reaction to waterfall method http://agilemanifesto.org/
* "early and often, adjust and iterate"
* flexible and responsive to change
* stakeholders must stay engaged and be available to provide timely feedback
* not always fast in practice if constantly changing deliverables
* not focused on comprehensive documentation

There are many agile approaches including scrum, kanban, feature-driven development, and extreme programming.

scrum (software development)
* small, cross functional teams
* short sprints
* regular "stand-up" meeting
* retrospectives after each sprint
* focus on continual optimization and improvements
* harder to do with fixed budgets and timelines
* self-managing teams can have issues with scope creep

kanban (industry)
* billboard in Japanese
* simple, clear framework
* visualize workflow and tasks
* large and small teams, remote or in person
* not detailed "at-a-glance"
* not if complex, lots of steps in the process

hybrid/structured agile
* combine waterfall and agile methods
* focus on gathering and analyzing requirements then rapid iterations
* best of both worlds - structure and flexibility
* best for medium-sized project with high complexity and fixed budgets

Lean Six Sigma (industry)
* Define, Measure, Analyze, Improve, Control
* cut waste and maximize efficiency
* quality management, continuous improvement
* measuring > analyzing > improving
* large organizations or efficiency is an issue

Integrated Project Management (IPM)
* focus on documents like project charter, plan, execution, monitoring and change control
* meet regularly as team
* accountability
* time for planning

PRiSM Projects Integrating Sustainable Methods
* developed by Green Project Management Global
* account and minimize adverse environmental impacts
* extends beyond the end of the project
* factors in environmental costs and sustainability is key success criteria
* mostly geared to real estate and industrial projects

Approaches also worth noting:
* Human-centered design - creative approach to problem solving with three phases: inspiration, ideation, implementation; start with people in mind, try it out and test with people in an iterative process.
* Participatory decision-making - creative approach to enabling the entire group ownership and participation in decisions. It includes an emphasis on facilitation and concensus-building.
* Participatory Action Research (PAR) is an approach to research emphasizing co-creation, participation, and action by members of communities affected by the research.

== References ==
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.

Project management methodology (PMM)

2021-11-06T18:01:49Z

Cristelags:

Project management methodology (PMM) is a system of principles, techniques, and procedures.

Factors in choosing a PM Method
* Project goals, objectives, and complexity
* Team - size, level of experience/training, location - remote/on-site, specialization of roles
* Timeline
* Budget
* Stakeholder expectations
* Values/organizational culture
* Ability to take risk
* Flexibility for change

The following is an overview of a few different PMM that hopefully inspires curiosity to learn more. Please contribute additional PMM or other examples to the '''[[DLF Project Managers Toolkit]]'''.

[[File:Waterfall.png|200px|left]]waterfall (software development)
* detailed linear process of tasks in sequential order
* project flows downward like waterfall
* comprehensive, predictable and planned out
* focus on documentation
* good for large projects with multiple stakeholders
* not flexible, if assumptions are wrong, hard to pivot

[[File:CPM.png|350px|left]] critical path method (CPM) (industry)
* identify and schedule tasks, duration and dependencies
* good for tight timelines and repetitive activities
* not good if unsure of timelines, durations for tasks
* not flexible if there are major changes

[[File:Agile.png|150px|left]]agile (software development)
* reaction to waterfall method http://agilemanifesto.org/
* "early and often, adjust and iterate"
* flexible and responsive to change
* stakeholders must stay engaged and be available to provide timely feedback
* not always fast in practice if constantly changing deliverables
* not focused on comprehensive documentation

There are many agile approaches including scrum, kanban, feature-driven development, and extreme programming.

scrum (software development)
* small, cross functional teams
* short sprints
* regular "stand-up" meeting
* retrospectives after each sprint
* focus on continual optimization and improvements
* harder to do with fixed budgets and timelines
* self-managing teams can have issues with scope creep

kanban (industry)
* billboard in Japanese
* simple, clear framework
* visualize workflow and tasks
* large and small teams, remote or in person
* not detailed "at-a-glance"
* not if complex, lots of steps in the process

hybrid/structured agile
* combine waterfall and agile methods
* focus on gathering and analyzing requirements then rapid iterations
* best of both worlds - structure and flexibility
* best for medium-sized project with high complexity and fixed budgets

Lean Six Sigma (industry)
* Define, Measure, Analyze, Improve, Control
* cut waste and maximize efficiency
* quality management, continuous improvement
* measuring > analyzing > improving
* large organizations or efficiency is an issue

Integrated Project Management (IPM)
* focus on documents like project charter, plan, execution, monitoring and change control
* meet regularly as team
* accountability
* time for planning

PRiSM Projects Integrating Sustainable Methods
* developed by Green Project Management Global
* account and minimize adverse environmental impacts
* extends beyond the end of the project
* factors in environmental costs and sustainability is key success criteria
* mostly geared to real estate and industrial projects

Approaches also worth noting:
* Human-centered design - creative approach to problem solving with three phases: inspiration, ideation, implementation; start with people in mind, try it out and test with people in an iterative process.
* Participatory decision-making - creative approach to enabling the entire group ownership and participation in decisions. It includes an emphasis on facilitation and concensus-building.
* Participatory Action Research (PAR) is an approach to research emphasizing co-creation, participation, and action by members of communities affected by the research.

== References ==
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.

Project management methodology (PMM)

2021-11-06T18:00:21Z

Cristelags:

Project management methodology (PMM) is a system of principles, techniques, and procedures.

Factors in choosing a PM Method
* Project goals, objectives, and complexity
* Team - size, level of experience/training, location - remote/on-site, specialization of roles
* Timeline
* Budget
* Stakeholder expectations
* Values/organizational culture
* Ability to take risk
* Flexibility for change

The following is an overview of a few different PMM that hopefully inspires curiosity to learn more. Please contribute additional PMM or other examples to the '''[[DLF Project Managers Toolkit]]'''.

[[File:Waterfall.png|200px|left]]waterfall (software development)
* detailed linear process of tasks in sequential order
* project flows downward like waterfall
* comprehensive, predictable and planned out
* focus on documentation
* good for large projects with multiple stakeholders
* not flexible, if assumptions are wrong, hard to pivot

[[File:CPM.png|300px|left]] critical path method (CPM) (industry)
* identify and schedule tasks, duration and dependencies
* good for tight timelines and repetitive activities
* not good if unsure of timelines, durations for tasks
* not flexible if there are major changes

[[File:Agile.png|150px|left]]agile (software development)
* reaction to waterfall method http://agilemanifesto.org/
* "early and often, adjust and iterate"
* flexible and responsive to change
* stakeholders must stay engaged and be available to provide timely feedback
* not always fast in practice if constantly changing deliverables
* not focused on comprehensive documentation

There are many agile approaches including scrum, kanban, feature-driven development, and extreme programming.

scrum (software development)
* small, cross functional teams
* short sprints
* regular "stand-up" meeting
* retrospectives after each sprint
* focus on continual optimization and improvements
* harder to do with fixed budgets and timelines
* self-managing teams can have issues with scope creep

kanban (industry)
* billboard in Japanese
* simple, clear framework
* visualize workflow and tasks
* large and small teams, remote or in person
* not detailed "at-a-glance"
* not if complex, lots of steps in the process

hybrid/structured agile
* combine waterfall and agile methods
* focus on gathering and analyzing requirements then rapid iterations
* best of both worlds - structure and flexibility
* best for medium-sized project with high complexity and fixed budgets

Lean Six Sigma (industry)
* Define, Measure, Analyze, Improve, Control
* cut waste and maximize efficiency
* quality management, continuous improvement
* measuring > analyzing > improving
* large organizations or efficiency is an issue

Integrated Project Management (IPM)
* focus on documents like project charter, plan, execution, monitoring and change control
* meet regularly as team
* accountability
* time for planning

PRiSM Projects Integrating Sustainable Methods
* developed by Green Project Management Global
* account and minimize adverse environmental impacts
* extends beyond the end of the project
* factors in environmental costs and sustainability is key success criteria
* mostly geared to real estate and industrial projects

Approaches also worth noting:
* Human-centered design - creative approach to problem solving with three phases: inspiration, ideation, implementation; start with people in mind, try it out and test with people in an iterative process.
* Participatory decision-making - creative approach to enabling the entire group ownership and participation in decisions. It includes an emphasis on facilitation and concensus-building.
* Participatory Action Research (PAR) is an approach to research emphasizing co-creation, participation, and action by members of communities affected by the research.

== References ==
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.

Project management methodology (PMM)

2021-11-06T17:59:59Z

Cristelags:

Project management methodology (PMM) is a system of principles, techniques, and procedures.

Factors in choosing a PM Method
* Project goals, objectives, and complexity
* Team - size, level of experience/training, location - remote/on-site, specialization of roles
* Timeline
* Budget
* Stakeholder expectations
* Values/organizational culture
* Ability to take risk
* Flexibility for change

The following is an overview of a few different PMM that hopefully inspires curiosity to learn more. Please contribute additional PMM or other examples to the '''[[DLF Project Managers Toolkit]]'''.

[[File:Waterfall.png|200px|left]]waterfall (software development)
* detailed linear process of tasks in sequential order
* project flows downward like waterfall
* comprehensive, predictable and planned out
* focus on documentation
* good for large projects with multiple stakeholders
* not flexible, if assumptions are wrong, hard to pivot

[[File:CPM.png|200px|left]] critical path method (CPM) (industry)
* identify and schedule tasks, duration and dependencies
* good for tight timelines and repetitive activities
* not good if unsure of timelines, durations for tasks
* not flexible if there are major changes

[[File:Agile.png|150px|left]]agile (software development)
* reaction to waterfall method http://agilemanifesto.org/
* "early and often, adjust and iterate"
* flexible and responsive to change
* stakeholders must stay engaged and be available to provide timely feedback
* not always fast in practice if constantly changing deliverables
* not focused on comprehensive documentation

There are many agile approaches including scrum, kanban, feature-driven development, and extreme programming.

scrum (software development)
* small, cross functional teams
* short sprints
* regular "stand-up" meeting
* retrospectives after each sprint
* focus on continual optimization and improvements
* harder to do with fixed budgets and timelines
* self-managing teams can have issues with scope creep

kanban (industry)
* billboard in Japanese
* simple, clear framework
* visualize workflow and tasks
* large and small teams, remote or in person
* not detailed "at-a-glance"
* not if complex, lots of steps in the process

hybrid/structured agile
* combine waterfall and agile methods
* focus on gathering and analyzing requirements then rapid iterations
* best of both worlds - structure and flexibility
* best for medium-sized project with high complexity and fixed budgets

Lean Six Sigma (industry)
* Define, Measure, Analyze, Improve, Control
* cut waste and maximize efficiency
* quality management, continuous improvement
* measuring > analyzing > improving
* large organizations or efficiency is an issue

Integrated Project Management (IPM)
* focus on documents like project charter, plan, execution, monitoring and change control
* meet regularly as team
* accountability
* time for planning

PRiSM Projects Integrating Sustainable Methods
* developed by Green Project Management Global
* account and minimize adverse environmental impacts
* extends beyond the end of the project
* factors in environmental costs and sustainability is key success criteria
* mostly geared to real estate and industrial projects

Approaches also worth noting:
* Human-centered design - creative approach to problem solving with three phases: inspiration, ideation, implementation; start with people in mind, try it out and test with people in an iterative process.
* Participatory decision-making - creative approach to enabling the entire group ownership and participation in decisions. It includes an emphasis on facilitation and concensus-building.
* Participatory Action Research (PAR) is an approach to research emphasizing co-creation, participation, and action by members of communities affected by the research.

== References ==
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.

File:CPM.png

2021-11-06T17:58:58Z

Cristelags: Cristelags uploaded a new version of File:CPM.png

critical path method

Project management methodology (PMM)

2021-11-06T17:56:23Z

Cristelags:

Project management methodology (PMM) is a system of principles, techniques, and procedures.

Factors in choosing a PM Method
* Project goals, objectives, and complexity
* Team - size, level of experience/training, location - remote/on-site, specialization of roles
* Timeline
* Budget
* Stakeholder expectations
* Values/organizational culture
* Ability to take risk
* Flexibility for change

The following is an overview of a few different PMM that hopefully inspires curiosity to learn more. Please contribute additional PMM or other examples to the '''[[DLF Project Managers Toolkit]]'''.

[[File:Waterfall.png|200px|left]]waterfall (software development)
* detailed linear process of tasks in sequential order
* project flows downward like waterfall
* comprehensive, predictable and planned out
* focus on documentation
* good for large projects with multiple stakeholders
* not flexible, if assumptions are wrong, hard to pivot

[[File:CPM.png|thumb|left]]
critical path method (CPM) (industry)
* identify and schedule tasks, duration and dependencies
* good for tight timelines and repetitive activities
* not good if unsure of timelines, durations for tasks
* not flexible if there are major changes

[[File:Agile.png|150px|left]]agile (software development)
* reaction to waterfall method http://agilemanifesto.org/
* "early and often, adjust and iterate"
* flexible and responsive to change
* stakeholders must stay engaged and be available to provide timely feedback
* not always fast in practice if constantly changing deliverables
* not focused on comprehensive documentation

There are many agile approaches including scrum, kanban, feature-driven development, and extreme programming.

scrum (software development)
* small, cross functional teams
* short sprints
* regular "stand-up" meeting
* retrospectives after each sprint
* focus on continual optimization and improvements
* harder to do with fixed budgets and timelines
* self-managing teams can have issues with scope creep

kanban (industry)
* billboard in Japanese
* simple, clear framework
* visualize workflow and tasks
* large and small teams, remote or in person
* not detailed "at-a-glance"
* not if complex, lots of steps in the process

hybrid/structured agile
* combine waterfall and agile methods
* focus on gathering and analyzing requirements then rapid iterations
* best of both worlds - structure and flexibility
* best for medium-sized project with high complexity and fixed budgets

Lean Six Sigma (industry)
* Define, Measure, Analyze, Improve, Control
* cut waste and maximize efficiency
* quality management, continuous improvement
* measuring > analyzing > improving
* large organizations or efficiency is an issue

Integrated Project Management (IPM)
* focus on documents like project charter, plan, execution, monitoring and change control
* meet regularly as team
* accountability
* time for planning

PRiSM Projects Integrating Sustainable Methods
* developed by Green Project Management Global
* account and minimize adverse environmental impacts
* extends beyond the end of the project
* factors in environmental costs and sustainability is key success criteria
* mostly geared to real estate and industrial projects

Approaches also worth noting:
* Human-centered design - creative approach to problem solving with three phases: inspiration, ideation, implementation; start with people in mind, try it out and test with people in an iterative process.
* Participatory decision-making - creative approach to enabling the entire group ownership and participation in decisions. It includes an emphasis on facilitation and concensus-building.
* Participatory Action Research (PAR) is an approach to research emphasizing co-creation, participation, and action by members of communities affected by the research.

== References ==
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.

File:CPM.png

2021-11-06T17:56:00Z

Cristelags:

critical path method

Project management methodology (PMM)

2021-11-06T17:50:42Z

Cristelags:

Project management methodology (PMM) is a system of principles, techniques, and procedures.

Factors in choosing a PM Method
* Project goals, objectives, and complexity
* Team - size, level of experience/training, location - remote/on-site, specialization of roles
* Timeline
* Budget
* Stakeholder expectations
* Values/organizational culture
* Ability to take risk
* Flexibility for change

The following is an overview of a few different PMM that hopefully inspires curiosity to learn more. Please contribute additional PMM or other examples to the '''[[DLF Project Managers Toolkit]]'''.

[[File:Waterfall.png|200px|left]]waterfall (software development)
* detailed linear process of tasks in sequential order
* project flows downward like waterfall
* comprehensive, predictable and planned out
* focus on documentation
* good for large projects with multiple stakeholders
* not flexible, if assumptions are wrong, hard to pivot

critical path method (CPM) (industry)
* identify and schedule tasks, duration and dependencies
* good for tight timelines and repetitive activities
* not good if unsure of timelines, durations for tasks
* not flexible if there are major changes

[[File:Agile.png|150px|left]]agile (software development)
* reaction to waterfall method http://agilemanifesto.org/
* "early and often, adjust and iterate"
* flexible and responsive to change
* stakeholders must stay engaged and be available to provide timely feedback
* not always fast in practice if constantly changing deliverables
* not focused on comprehensive documentation

There are many agile approaches including scrum, kanban, feature-driven development, and extreme programming.

scrum (software development)
* small, cross functional teams
* short sprints
* regular "stand-up" meeting
* retrospectives after each sprint
* focus on continual optimization and improvements
* harder to do with fixed budgets and timelines
* self-managing teams can have issues with scope creep

kanban (industry)
* billboard in Japanese
* simple, clear framework
* visualize workflow and tasks
* large and small teams, remote or in person
* not detailed "at-a-glance"
* not if complex, lots of steps in the process

hybrid/structured agile
* combine waterfall and agile methods
* focus on gathering and analyzing requirements then rapid iterations
* best of both worlds - structure and flexibility
* best for medium-sized project with high complexity and fixed budgets

Lean Six Sigma (industry)
* Define, Measure, Analyze, Improve, Control
* cut waste and maximize efficiency
* quality management, continuous improvement
* measuring > analyzing > improving
* large organizations or efficiency is an issue

Integrated Project Management (IPM)
* focus on documents like project charter, plan, execution, monitoring and change control
* meet regularly as team
* accountability
* time for planning

PRiSM Projects Integrating Sustainable Methods
* developed by Green Project Management Global
* account and minimize adverse environmental impacts
* extends beyond the end of the project
* factors in environmental costs and sustainability is key success criteria
* mostly geared to real estate and industrial projects

Approaches also worth noting:
* Human-centered design - creative approach to problem solving with three phases: inspiration, ideation, implementation; start with people in mind, try it out and test with people in an iterative process.
* Participatory decision-making - creative approach to enabling the entire group ownership and participation in decisions. It includes an emphasis on facilitation and concensus-building.
* Participatory Action Research (PAR) is an approach to research emphasizing co-creation, participation, and action by members of communities affected by the research.

== References ==
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.

Project management methodology (PMM)

2021-11-06T17:49:43Z

Cristelags:

Project management methodology (PMM) is a system of principles, techniques, and procedures.

Factors in choosing a PM Method
* Project goals, objectives, and complexity
* Team - size, level of experience/training, location - remote/on-site, specialization of roles
* Timeline
* Budget
* Stakeholder expectations
* Values/organizational culture
* Ability to take risk
* Flexibility for change

The following is an overview of a few different PMM that hopefully inspires curiosity to learn more. Please contribute additional PMM or other examples to the '''[[DLF Project Managers Toolkit]]'''.

[[File:Waterfall.png|200px|left|Waterfall PMM]]waterfall (software development)
* detailed linear process of tasks in sequential order
* project flows downward like waterfall
* comprehensive, predictable and planned out
* focus on documentation
* good for large projects with multiple stakeholders
* not flexible, if assumptions are wrong, hard to pivot

critical path method (CPM) (industry)
* identify and schedule tasks, duration and dependencies
* good for tight timelines and repetitive activities
* not good if unsure of timelines, durations for tasks
* not flexible if there are major changes

[[File:Agile.png|200px|left|Agile approach is iterative]]agile (software development)
* reaction to waterfall method http://agilemanifesto.org/
* "early and often, adjust and iterate"
* flexible and responsive to change
* stakeholders must stay engaged and be available to provide timely feedback
* not always fast in practice if constantly changing deliverables
* not focused on comprehensive documentation

There are many agile approaches including scrum, kanban, feature-driven development, and extreme programming.

scrum (software development)
* small, cross functional teams
* short sprints
* regular "stand-up" meeting
* retrospectives after each sprint
* focus on continual optimization and improvements
* harder to do with fixed budgets and timelines
* self-managing teams can have issues with scope creep

kanban (industry)
* billboard in Japanese
* simple, clear framework
* visualize workflow and tasks
* large and small teams, remote or in person
* not detailed "at-a-glance"
* not if complex, lots of steps in the process

hybrid/structured agile
* combine waterfall and agile methods
* focus on gathering and analyzing requirements then rapid iterations
* best of both worlds - structure and flexibility
* best for medium-sized project with high complexity and fixed budgets

Lean Six Sigma (industry)
* Define, Measure, Analyze, Improve, Control
* cut waste and maximize efficiency
* quality management, continuous improvement
* measuring > analyzing > improving
* large organizations or efficiency is an issue

Integrated Project Management (IPM)
* focus on documents like project charter, plan, execution, monitoring and change control
* meet regularly as team
* accountability
* time for planning

PRiSM Projects Integrating Sustainable Methods
* developed by Green Project Management Global
* account and minimize adverse environmental impacts
* extends beyond the end of the project
* factors in environmental costs and sustainability is key success criteria
* mostly geared to real estate and industrial projects

Approaches also worth noting:
* Human-centered design - creative approach to problem solving with three phases: inspiration, ideation, implementation; start with people in mind, try it out and test with people in an iterative process.
* Participatory decision-making - creative approach to enabling the entire group ownership and participation in decisions. It includes an emphasis on facilitation and concensus-building.
* Participatory Action Research (PAR) is an approach to research emphasizing co-creation, participation, and action by members of communities affected by the research.

== References ==
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.

File:Waterfall.png

2021-11-06T17:48:47Z

Cristelags:

waterfall project management methodology

Project management methodology (PMM)

2021-11-06T17:48:17Z

Cristelags:

Project management methodology (PMM) is a system of principles, techniques, and procedures.

Factors in choosing a PM Method
* Project goals, objectives, and complexity
* Team - size, level of experience/training, location - remote/on-site, specialization of roles
* Timeline
* Budget
* Stakeholder expectations
* Values/organizational culture
* Ability to take risk
* Flexibility for change

The following is an overview of a few different PMM that hopefully inspires curiosity to learn more. Please contribute additional PMM or other examples to the '''[[DLF Project Managers Toolkit]]'''.

[[File:Waterfall.png|200px||left|Waterfall PMM]]waterfall (software development)
* detailed linear process of tasks in sequential order
* project flows downward like waterfall
* comprehensive, predictable and planned out
* focus on documentation
* good for large projects with multiple stakeholders
* not flexible, if assumptions are wrong, hard to pivot

critical path method (CPM) (industry)
* identify and schedule tasks, duration and dependencies
* good for tight timelines and repetitive activities
* not good if unsure of timelines, durations for tasks
* not flexible if there are major changes

[[File:Agile.png|200px||Agile approach is iterative]]agile (software development)
* reaction to waterfall method http://agilemanifesto.org/
* "early and often, adjust and iterate"
* flexible and responsive to change
* stakeholders must stay engaged and be available to provide timely feedback
* not always fast in practice if constantly changing deliverables
* not focused on comprehensive documentation

There are many agile approaches including scrum, kanban, feature-driven development, and extreme programming.

scrum (software development)
* small, cross functional teams
* short sprints
* regular "stand-up" meeting
* retrospectives after each sprint
* focus on continual optimization and improvements
* harder to do with fixed budgets and timelines
* self-managing teams can have issues with scope creep

kanban (industry)
* billboard in Japanese
* simple, clear framework
* visualize workflow and tasks
* large and small teams, remote or in person
* not detailed "at-a-glance"
* not if complex, lots of steps in the process

hybrid/structured agile
* combine waterfall and agile methods
* focus on gathering and analyzing requirements then rapid iterations
* best of both worlds - structure and flexibility
* best for medium-sized project with high complexity and fixed budgets

Lean Six Sigma (industry)
* Define, Measure, Analyze, Improve, Control
* cut waste and maximize efficiency
* quality management, continuous improvement
* measuring > analyzing > improving
* large organizations or efficiency is an issue

Integrated Project Management (IPM)
* focus on documents like project charter, plan, execution, monitoring and change control
* meet regularly as team
* accountability
* time for planning

PRiSM Projects Integrating Sustainable Methods
* developed by Green Project Management Global
* account and minimize adverse environmental impacts
* extends beyond the end of the project
* factors in environmental costs and sustainability is key success criteria
* mostly geared to real estate and industrial projects

Approaches also worth noting:
* Human-centered design - creative approach to problem solving with three phases: inspiration, ideation, implementation; start with people in mind, try it out and test with people in an iterative process.
* Participatory decision-making - creative approach to enabling the entire group ownership and participation in decisions. It includes an emphasis on facilitation and concensus-building.
* Participatory Action Research (PAR) is an approach to research emphasizing co-creation, participation, and action by members of communities affected by the research.

== References ==
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.

Project management methodology (PMM)

2021-11-06T17:47:45Z

Cristelags:

Project management methodology (PMM) is a system of principles, techniques, and procedures.

Factors in choosing a PM Method
* Project goals, objectives, and complexity
* Team - size, level of experience/training, location - remote/on-site, specialization of roles
* Timeline
* Budget
* Stakeholder expectations
* Values/organizational culture
* Ability to take risk
* Flexibility for change

The following is an overview of a few different PMM that hopefully inspires curiosity to learn more. Please contribute additional PMM or other examples to the '''[[DLF Project Managers Toolkit]]'''.

[[File:Waterfall.png|200px||left|Waterfall PMM]]waterfall (software development)
* detailed linear process of tasks in sequential order
* project flows downward like waterfall
* comprehensive, predictable and planned out
* focus on documentation
* good for large projects with multiple stakeholders
* not flexible, if assumptions are wrong, hard to pivot

critical path method (CPM) (industry)
* identify and schedule tasks, duration and dependencies
* good for tight timelines and repetitive activities
* not good if unsure of timelines, durations for tasks
* not flexible if there are major changes

[[File:Agile.png|200px||Agile approach is iterative]]
agile (software development)
* reaction to waterfall method http://agilemanifesto.org/
* "early and often, adjust and iterate"
* flexible and responsive to change
* stakeholders must stay engaged and be available to provide timely feedback
* not always fast in practice if constantly changing deliverables
* not focused on comprehensive documentation

There are many agile approaches including scrum, kanban, feature-driven development, and extreme programming.

scrum (software development)
* small, cross functional teams
* short sprints
* regular "stand-up" meeting
* retrospectives after each sprint
* focus on continual optimization and improvements
* harder to do with fixed budgets and timelines
* self-managing teams can have issues with scope creep

kanban (industry)
* billboard in Japanese
* simple, clear framework
* visualize workflow and tasks
* large and small teams, remote or in person
* not detailed "at-a-glance"
* not if complex, lots of steps in the process

hybrid/structured agile
* combine waterfall and agile methods
* focus on gathering and analyzing requirements then rapid iterations
* best of both worlds - structure and flexibility
* best for medium-sized project with high complexity and fixed budgets

Lean Six Sigma (industry)
* Define, Measure, Analyze, Improve, Control
* cut waste and maximize efficiency
* quality management, continuous improvement
* measuring > analyzing > improving
* large organizations or efficiency is an issue

Integrated Project Management (IPM)
* focus on documents like project charter, plan, execution, monitoring and change control
* meet regularly as team
* accountability
* time for planning

PRiSM Projects Integrating Sustainable Methods
* developed by Green Project Management Global
* account and minimize adverse environmental impacts
* extends beyond the end of the project
* factors in environmental costs and sustainability is key success criteria
* mostly geared to real estate and industrial projects

Approaches also worth noting:
* Human-centered design - creative approach to problem solving with three phases: inspiration, ideation, implementation; start with people in mind, try it out and test with people in an iterative process.
* Participatory decision-making - creative approach to enabling the entire group ownership and participation in decisions. It includes an emphasis on facilitation and concensus-building.
* Participatory Action Research (PAR) is an approach to research emphasizing co-creation, participation, and action by members of communities affected by the research.

== References ==
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.

Project management methodology (PMM)

2021-11-06T17:47:18Z

Cristelags:

Project management methodology (PMM) is a system of principles, techniques, and procedures.

Factors in choosing a PM Method
* Project goals, objectives, and complexity
* Team - size, level of experience/training, location - remote/on-site, specialization of roles
* Timeline
* Budget
* Stakeholder expectations
* Values/organizational culture
* Ability to take risk
* Flexibility for change

The following is an overview of a few different PMM that hopefully inspires curiosity to learn more. Please contribute additional PMM or other examples to the '''[[DLF Project Managers Toolkit]]'''.

[[File:Waterfall.png|100px||left|Waterfall PMM]]waterfall (software development)
* detailed linear process of tasks in sequential order
* project flows downward like waterfall
* comprehensive, predictable and planned out
* focus on documentation
* good for large projects with multiple stakeholders
* not flexible, if assumptions are wrong, hard to pivot

critical path method (CPM) (industry)
* identify and schedule tasks, duration and dependencies
* good for tight timelines and repetitive activities
* not good if unsure of timelines, durations for tasks
* not flexible if there are major changes

[[File:Agile.png|100px||Agile approach is iterative]]
agile (software development)
* reaction to waterfall method http://agilemanifesto.org/
* "early and often, adjust and iterate"
* flexible and responsive to change
* stakeholders must stay engaged and be available to provide timely feedback
* not always fast in practice if constantly changing deliverables
* not focused on comprehensive documentation

There are many agile approaches including scrum, kanban, feature-driven development, and extreme programming.

scrum (software development)
* small, cross functional teams
* short sprints
* regular "stand-up" meeting
* retrospectives after each sprint
* focus on continual optimization and improvements
* harder to do with fixed budgets and timelines
* self-managing teams can have issues with scope creep

kanban (industry)
* billboard in Japanese
* simple, clear framework
* visualize workflow and tasks
* large and small teams, remote or in person
* not detailed "at-a-glance"
* not if complex, lots of steps in the process

hybrid/structured agile
* combine waterfall and agile methods
* focus on gathering and analyzing requirements then rapid iterations
* best of both worlds - structure and flexibility
* best for medium-sized project with high complexity and fixed budgets

Lean Six Sigma (industry)
* Define, Measure, Analyze, Improve, Control
* cut waste and maximize efficiency
* quality management, continuous improvement
* measuring > analyzing > improving
* large organizations or efficiency is an issue

Integrated Project Management (IPM)
* focus on documents like project charter, plan, execution, monitoring and change control
* meet regularly as team
* accountability
* time for planning

PRiSM Projects Integrating Sustainable Methods
* developed by Green Project Management Global
* account and minimize adverse environmental impacts
* extends beyond the end of the project
* factors in environmental costs and sustainability is key success criteria
* mostly geared to real estate and industrial projects

Approaches also worth noting:
* Human-centered design - creative approach to problem solving with three phases: inspiration, ideation, implementation; start with people in mind, try it out and test with people in an iterative process.
* Participatory decision-making - creative approach to enabling the entire group ownership and participation in decisions. It includes an emphasis on facilitation and concensus-building.
* Participatory Action Research (PAR) is an approach to research emphasizing co-creation, participation, and action by members of communities affected by the research.

== References ==
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.

Project management methodology (PMM)

2021-11-06T17:46:48Z

Cristelags:

Project management methodology (PMM) is a system of principles, techniques, and procedures.

Factors in choosing a PM Method
* Project goals, objectives, and complexity
* Team - size, level of experience/training, location - remote/on-site, specialization of roles
* Timeline
* Budget
* Stakeholder expectations
* Values/organizational culture
* Ability to take risk
* Flexibility for change

The following is an overview of a few different PMM that hopefully inspires curiosity to learn more. Please contribute additional PMM or other examples to the '''[[DLF Project Managers Toolkit]]'''.

[[File:Waterfall.png|100px||left|Waterfall PMM]]waterfall (software development)
* detailed linear process of tasks in sequential order
* project flows downward like waterfall
* comprehensive, predictable and planned out
* focus on documentation
* good for large projects with multiple stakeholders
* not flexible, if assumptions are wrong, hard to pivot

critical path method (CPM) (industry)
* identify and schedule tasks, duration and dependencies
* good for tight timelines and repetitive activities
* not good if unsure of timelines, durations for tasks
* not flexible if there are major changes

[[File:Agile.png|thumb|100px||Agile approach is iterative]]
agile (software development)
* reaction to waterfall method http://agilemanifesto.org/
* "early and often, adjust and iterate"
* flexible and responsive to change
* stakeholders must stay engaged and be available to provide timely feedback
* not always fast in practice if constantly changing deliverables
* not focused on comprehensive documentation

There are many agile approaches including scrum, kanban, feature-driven development, and extreme programming.

scrum (software development)
* small, cross functional teams
* short sprints
* regular "stand-up" meeting
* retrospectives after each sprint
* focus on continual optimization and improvements
* harder to do with fixed budgets and timelines
* self-managing teams can have issues with scope creep

kanban (industry)
* billboard in Japanese
* simple, clear framework
* visualize workflow and tasks
* large and small teams, remote or in person
* not detailed "at-a-glance"
* not if complex, lots of steps in the process

hybrid/structured agile
* combine waterfall and agile methods
* focus on gathering and analyzing requirements then rapid iterations
* best of both worlds - structure and flexibility
* best for medium-sized project with high complexity and fixed budgets

Lean Six Sigma (industry)
* Define, Measure, Analyze, Improve, Control
* cut waste and maximize efficiency
* quality management, continuous improvement
* measuring > analyzing > improving
* large organizations or efficiency is an issue

Integrated Project Management (IPM)
* focus on documents like project charter, plan, execution, monitoring and change control
* meet regularly as team
* accountability
* time for planning

PRiSM Projects Integrating Sustainable Methods
* developed by Green Project Management Global
* account and minimize adverse environmental impacts
* extends beyond the end of the project
* factors in environmental costs and sustainability is key success criteria
* mostly geared to real estate and industrial projects

Approaches also worth noting:
* Human-centered design - creative approach to problem solving with three phases: inspiration, ideation, implementation; start with people in mind, try it out and test with people in an iterative process.
* Participatory decision-making - creative approach to enabling the entire group ownership and participation in decisions. It includes an emphasis on facilitation and concensus-building.
* Participatory Action Research (PAR) is an approach to research emphasizing co-creation, participation, and action by members of communities affected by the research.

== References ==
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.

Project management methodology (PMM)

2021-11-06T17:46:14Z

Cristelags:

Project management methodology (PMM) is a system of principles, techniques, and procedures.

Factors in choosing a PM Method
* Project goals, objectives, and complexity
* Team - size, level of experience/training, location - remote/on-site, specialization of roles
* Timeline
* Budget
* Stakeholder expectations
* Values/organizational culture
* Ability to take risk
* Flexibility for change

The following is an overview of a few different PMM that hopefully inspires curiosity to learn more. Please contribute additional PMM or other examples to the '''[[DLF Project Managers Toolkit]]'''.

[[File:Waterfall.png|thumb|left|Waterfall PMM]]waterfall (software development)
* detailed linear process of tasks in sequential order
* project flows downward like waterfall
* comprehensive, predictable and planned out
* focus on documentation
* good for large projects with multiple stakeholders
* not flexible, if assumptions are wrong, hard to pivot

critical path method (CPM) (industry)
* identify and schedule tasks, duration and dependencies
* good for tight timelines and repetitive activities
* not good if unsure of timelines, durations for tasks
* not flexible if there are major changes

[[File:Agile.png|thumb|left|Agile approach is iterative]]
agile (software development)
* reaction to waterfall method http://agilemanifesto.org/
* "early and often, adjust and iterate"
* flexible and responsive to change
* stakeholders must stay engaged and be available to provide timely feedback
* not always fast in practice if constantly changing deliverables
* not focused on comprehensive documentation

There are many agile approaches including scrum, kanban, feature-driven development, and extreme programming.

scrum (software development)
* small, cross functional teams
* short sprints
* regular "stand-up" meeting
* retrospectives after each sprint
* focus on continual optimization and improvements
* harder to do with fixed budgets and timelines
* self-managing teams can have issues with scope creep

kanban (industry)
* billboard in Japanese
* simple, clear framework
* visualize workflow and tasks
* large and small teams, remote or in person
* not detailed "at-a-glance"
* not if complex, lots of steps in the process

hybrid/structured agile
* combine waterfall and agile methods
* focus on gathering and analyzing requirements then rapid iterations
* best of both worlds - structure and flexibility
* best for medium-sized project with high complexity and fixed budgets

Lean Six Sigma (industry)
* Define, Measure, Analyze, Improve, Control
* cut waste and maximize efficiency
* quality management, continuous improvement
* measuring > analyzing > improving
* large organizations or efficiency is an issue

Integrated Project Management (IPM)
* focus on documents like project charter, plan, execution, monitoring and change control
* meet regularly as team
* accountability
* time for planning

PRiSM Projects Integrating Sustainable Methods
* developed by Green Project Management Global
* account and minimize adverse environmental impacts
* extends beyond the end of the project
* factors in environmental costs and sustainability is key success criteria
* mostly geared to real estate and industrial projects

Approaches also worth noting:
* Human-centered design - creative approach to problem solving with three phases: inspiration, ideation, implementation; start with people in mind, try it out and test with people in an iterative process.
* Participatory decision-making - creative approach to enabling the entire group ownership and participation in decisions. It includes an emphasis on facilitation and concensus-building.
* Participatory Action Research (PAR) is an approach to research emphasizing co-creation, participation, and action by members of communities affected by the research.

== References ==
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.

Project management methodology (PMM)

2021-11-06T17:45:41Z

Cristelags:

Project management methodology (PMM) is a system of principles, techniques, and procedures.

Factors in choosing a PM Method
* Project goals, objectives, and complexity
* Team - size, level of experience/training, location - remote/on-site, specialization of roles
* Timeline
* Budget
* Stakeholder expectations
* Values/organizational culture
* Ability to take risk
* Flexibility for change

The following is an overview of a few different PMM that hopefully inspires curiosity to learn more. Please contribute additional PMM or other examples to the '''[[DLF Project Managers Toolkit]]'''.

[[File:Waterfall.png|thumb|left|Waterfall PMM]]waterfall (software development)
* detailed linear process of tasks in sequential order
* project flows downward like waterfall
* comprehensive, predictable and planned out
* focus on documentation
* good for large projects with multiple stakeholders
* not flexible, if assumptions are wrong, hard to pivot

critical path method (CPM) (industry)
* identify and schedule tasks, duration and dependencies
* good for tight timelines and repetitive activities
* not good if unsure of timelines, durations for tasks
* not flexible if there are major changes

[[File:Agile.png|thumb|Agile approach is iterative]]
agile (software development)
* reaction to waterfall method http://agilemanifesto.org/
* "early and often, adjust and iterate"
* flexible and responsive to change
* stakeholders must stay engaged and be available to provide timely feedback
* not always fast in practice if constantly changing deliverables
* not focused on comprehensive documentation

There are many agile approaches including scrum, kanban, feature-driven development, and extreme programming.

scrum (software development)
* small, cross functional teams
* short sprints
* regular "stand-up" meeting
* retrospectives after each sprint
* focus on continual optimization and improvements
* harder to do with fixed budgets and timelines
* self-managing teams can have issues with scope creep

kanban (industry)
* billboard in Japanese
* simple, clear framework
* visualize workflow and tasks
* large and small teams, remote or in person
* not detailed "at-a-glance"
* not if complex, lots of steps in the process

hybrid/structured agile
* combine waterfall and agile methods
* focus on gathering and analyzing requirements then rapid iterations
* best of both worlds - structure and flexibility
* best for medium-sized project with high complexity and fixed budgets

Lean Six Sigma (industry)
* Define, Measure, Analyze, Improve, Control
* cut waste and maximize efficiency
* quality management, continuous improvement
* measuring > analyzing > improving
* large organizations or efficiency is an issue

Integrated Project Management (IPM)
* focus on documents like project charter, plan, execution, monitoring and change control
* meet regularly as team
* accountability
* time for planning

PRiSM Projects Integrating Sustainable Methods
* developed by Green Project Management Global
* account and minimize adverse environmental impacts
* extends beyond the end of the project
* factors in environmental costs and sustainability is key success criteria
* mostly geared to real estate and industrial projects

Approaches also worth noting:
* Human-centered design - creative approach to problem solving with three phases: inspiration, ideation, implementation; start with people in mind, try it out and test with people in an iterative process.
* Participatory decision-making - creative approach to enabling the entire group ownership and participation in decisions. It includes an emphasis on facilitation and concensus-building.
* Participatory Action Research (PAR) is an approach to research emphasizing co-creation, participation, and action by members of communities affected by the research.

== References ==
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.

Project management methodology (PMM)

2021-11-06T17:44:26Z

Cristelags:

Project management methodology (PMM) is a system of principles, techniques, and procedures.

Factors in choosing a PM Method
* Project goals, objectives, and complexity
* Team - size, level of experience/training, location - remote/on-site, specialization of roles
* Timeline
* Budget
* Stakeholder expectations
* Values/organizational culture
* Ability to take risk
* Flexibility for change

The following is an overview of a few different PMM that hopefully inspires curiosity to learn more. Please contribute additional PMM or other examples to the '''[[DLF Project Managers Toolkit]]'''.

[[File:Waterfall.png|thumb|Waterfall PMM]]waterfall (software development)
* detailed linear process of tasks in sequential order
* project flows downward like waterfall
* comprehensive, predictable and planned out
* focus on documentation
* good for large projects with multiple stakeholders
* not flexible, if assumptions are wrong, hard to pivot

critical path method (CPM) (industry)
* identify and schedule tasks, duration and dependencies
* good for tight timelines and repetitive activities
* not good if unsure of timelines, durations for tasks
* not flexible if there are major changes

[[File:Agile.png|thumb|Agile approach is iterative]]
agile (software development)
* reaction to waterfall method http://agilemanifesto.org/
* "early and often, adjust and iterate"
* flexible and responsive to change
* stakeholders must stay engaged and be available to provide timely feedback
* not always fast in practice if constantly changing deliverables
* not focused on comprehensive documentation

There are many agile approaches including scrum, kanban, feature-driven development, and extreme programming.

scrum (software development)
* small, cross functional teams
* short sprints
* regular "stand-up" meeting
* retrospectives after each sprint
* focus on continual optimization and improvements
* harder to do with fixed budgets and timelines
* self-managing teams can have issues with scope creep

kanban (industry)
* billboard in Japanese
* simple, clear framework
* visualize workflow and tasks
* large and small teams, remote or in person
* not detailed "at-a-glance"
* not if complex, lots of steps in the process

hybrid/structured agile
* combine waterfall and agile methods
* focus on gathering and analyzing requirements then rapid iterations
* best of both worlds - structure and flexibility
* best for medium-sized project with high complexity and fixed budgets

Lean Six Sigma (industry)
* Define, Measure, Analyze, Improve, Control
* cut waste and maximize efficiency
* quality management, continuous improvement
* measuring > analyzing > improving
* large organizations or efficiency is an issue

Integrated Project Management (IPM)
* focus on documents like project charter, plan, execution, monitoring and change control
* meet regularly as team
* accountability
* time for planning

PRiSM Projects Integrating Sustainable Methods
* developed by Green Project Management Global
* account and minimize adverse environmental impacts
* extends beyond the end of the project
* factors in environmental costs and sustainability is key success criteria
* mostly geared to real estate and industrial projects

Approaches also worth noting:
* Human-centered design - creative approach to problem solving with three phases: inspiration, ideation, implementation; start with people in mind, try it out and test with people in an iterative process.
* Participatory decision-making - creative approach to enabling the entire group ownership and participation in decisions. It includes an emphasis on facilitation and concensus-building.
* Participatory Action Research (PAR) is an approach to research emphasizing co-creation, participation, and action by members of communities affected by the research.

== References ==
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.

Project management methodology (PMM)

2021-11-06T17:42:32Z

Cristelags:

Project management methodology (PMM) is a system of principles, techniques, and procedures.

Factors in choosing a PM Method
* Project goals, objectives, and complexity
* Team - size, level of experience/training, location - remote/on-site, specialization of roles
* Timeline
* Budget
* Stakeholder expectations
* Values/organizational culture
* Ability to take risk
* Flexibility for change

The following is an overview of a few different PMM that hopefully inspires curiosity to learn more. Please contribute additional PMM or other examples to the '''[[DLF Project Managers Toolkit]]'''.

[[File:Waterfall.png|thumb|Waterfall PMM]]waterfall (software development)
* detailed linear process of tasks in sequential order
* project flows downward like waterfall
* comprehensive, predictable and planned out
* focus on documentation
* good for large projects with multiple stakeholders
* not flexible, if assumptions are wrong, hard to pivot

critical path method (CPM) (industry)
* identify and schedule tasks, duration and dependencies
* good for tight timelines and repetitive activities
* not good if unsure of timelines, durations for tasks
* not flexible if there are major changes

[[File:Agile.png|thumb|right|Agile approach is iterative]]
agile (software development)
* reaction to waterfall method http://agilemanifesto.org/
* "early and often, adjust and iterate"
* flexible and responsive to change
* stakeholders must stay engaged and be available to provide timely feedback
* not always fast in practice if constantly changing deliverables
* not focused on comprehensive documentation

There are many agile approaches including scrum, kanban, feature-driven development, and extreme programming.

scrum (software development)
* small, cross functional teams
* short sprints
* regular "stand-up" meeting
* retrospectives after each sprint
* focus on continual optimization and improvements
* harder to do with fixed budgets and timelines
* self-managing teams can have issues with scope creep

kanban (industry)
* billboard in Japanese
* simple, clear framework
* visualize workflow and tasks
* large and small teams, remote or in person
* not detailed "at-a-glance"
* not if complex, lots of steps in the process

hybrid/structured agile
* combine waterfall and agile methods
* focus on gathering and analyzing requirements then rapid iterations
* best of both worlds - structure and flexibility
* best for medium-sized project with high complexity and fixed budgets

Lean Six Sigma (industry)
* Define, Measure, Analyze, Improve, Control
* cut waste and maximize efficiency
* quality management, continuous improvement
* measuring > analyzing > improving
* large organizations or efficiency is an issue

Integrated Project Management (IPM)
* focus on documents like project charter, plan, execution, monitoring and change control
* meet regularly as team
* accountability
* time for planning

PRiSM Projects Integrating Sustainable Methods
* developed by Green Project Management Global
* account and minimize adverse environmental impacts
* extends beyond the end of the project
* factors in environmental costs and sustainability is key success criteria
* mostly geared to real estate and industrial projects

Approaches also worth noting:
* Human-centered design - creative approach to problem solving with three phases: inspiration, ideation, implementation; start with people in mind, try it out and test with people in an iterative process.
* Participatory decision-making - creative approach to enabling the entire group ownership and participation in decisions. It includes an emphasis on facilitation and concensus-building.
* Participatory Action Research (PAR) is an approach to research emphasizing co-creation, participation, and action by members of communities affected by the research.

== References ==
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.

Project management methodology (PMM)

2021-11-06T17:42:08Z

Cristelags:

Project management methodology (PMM) is a system of principles, techniques, and procedures.

Factors in choosing a PM Method
* Project goals, objectives, and complexity
* Team - size, level of experience/training, location - remote/on-site, specialization of roles
* Timeline
* Budget
* Stakeholder expectations
* Values/organizational culture
* Ability to take risk
* Flexibility for change

The following is an overview of a few different PMM that hopefully inspires curiosity to learn more. Please contribute additional PMM or other examples to the '''[[DLF Project Managers Toolkit]]'''.

[[File:Waterfall.png|thumb|Waterfall PMM]]
waterfall (software development)
* detailed linear process of tasks in sequential order
* project flows downward like waterfall
* comprehensive, predictable and planned out
* focus on documentation
* good for large projects with multiple stakeholders
* not flexible, if assumptions are wrong, hard to pivot

critical path method (CPM) (industry)
* identify and schedule tasks, duration and dependencies
* good for tight timelines and repetitive activities
* not good if unsure of timelines, durations for tasks
* not flexible if there are major changes

[[File:Agile.png|thumb|right|Agile approach is iterative]]
agile (software development)
* reaction to waterfall method http://agilemanifesto.org/
* "early and often, adjust and iterate"
* flexible and responsive to change
* stakeholders must stay engaged and be available to provide timely feedback
* not always fast in practice if constantly changing deliverables
* not focused on comprehensive documentation

There are many agile approaches including scrum, kanban, feature-driven development, and extreme programming.

scrum (software development)
* small, cross functional teams
* short sprints
* regular "stand-up" meeting
* retrospectives after each sprint
* focus on continual optimization and improvements
* harder to do with fixed budgets and timelines
* self-managing teams can have issues with scope creep

kanban (industry)
* billboard in Japanese
* simple, clear framework
* visualize workflow and tasks
* large and small teams, remote or in person
* not detailed "at-a-glance"
* not if complex, lots of steps in the process

hybrid/structured agile
* combine waterfall and agile methods
* focus on gathering and analyzing requirements then rapid iterations
* best of both worlds - structure and flexibility
* best for medium-sized project with high complexity and fixed budgets

Lean Six Sigma (industry)
* Define, Measure, Analyze, Improve, Control
* cut waste and maximize efficiency
* quality management, continuous improvement
* measuring > analyzing > improving
* large organizations or efficiency is an issue

Integrated Project Management (IPM)
* focus on documents like project charter, plan, execution, monitoring and change control
* meet regularly as team
* accountability
* time for planning

PRiSM Projects Integrating Sustainable Methods
* developed by Green Project Management Global
* account and minimize adverse environmental impacts
* extends beyond the end of the project
* factors in environmental costs and sustainability is key success criteria
* mostly geared to real estate and industrial projects

Approaches also worth noting:
* Human-centered design - creative approach to problem solving with three phases: inspiration, ideation, implementation; start with people in mind, try it out and test with people in an iterative process.
* Participatory decision-making - creative approach to enabling the entire group ownership and participation in decisions. It includes an emphasis on facilitation and concensus-building.
* Participatory Action Research (PAR) is an approach to research emphasizing co-creation, participation, and action by members of communities affected by the research.

== References ==
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.

Project management methodology (PMM)

2021-11-06T17:41:29Z

Cristelags:

Project management methodology (PMM) is a system of principles, techniques, and procedures.

Factors in choosing a PM Method
* Project goals, objectives, and complexity
* Team - size, level of experience/training, location - remote/on-site, specialization of roles
* Timeline
* Budget
* Stakeholder expectations
* Values/organizational culture
* Ability to take risk
* Flexibility for change

The following is an overview of a few different PMM that hopefully inspires curiosity to learn more. Please contribute additional PMM or other examples to the '''[[DLF Project Managers Toolkit]]'''.

[[File:Waterfall.png|thumb|right|Waterfall PMM]]
waterfall (software development)
* detailed linear process of tasks in sequential order
* project flows downward like waterfall
* comprehensive, predictable and planned out
* focus on documentation
* good for large projects with multiple stakeholders
* not flexible, if assumptions are wrong, hard to pivot

critical path method (CPM) (industry)
* identify and schedule tasks, duration and dependencies
* good for tight timelines and repetitive activities
* not good if unsure of timelines, durations for tasks
* not flexible if there are major changes

[[File:Agile.png|thumb|right|Agile approach is iterative]]
agile (software development)
* reaction to waterfall method http://agilemanifesto.org/
* "early and often, adjust and iterate"
* flexible and responsive to change
* stakeholders must stay engaged and be available to provide timely feedback
* not always fast in practice if constantly changing deliverables
* not focused on comprehensive documentation

There are many agile approaches including scrum, kanban, feature-driven development, and extreme programming.

scrum (software development)
* small, cross functional teams
* short sprints
* regular "stand-up" meeting
* retrospectives after each sprint
* focus on continual optimization and improvements
* harder to do with fixed budgets and timelines
* self-managing teams can have issues with scope creep

kanban (industry)
* billboard in Japanese
* simple, clear framework
* visualize workflow and tasks
* large and small teams, remote or in person
* not detailed "at-a-glance"
* not if complex, lots of steps in the process

hybrid/structured agile
* combine waterfall and agile methods
* focus on gathering and analyzing requirements then rapid iterations
* best of both worlds - structure and flexibility
* best for medium-sized project with high complexity and fixed budgets

Lean Six Sigma (industry)
* Define, Measure, Analyze, Improve, Control
* cut waste and maximize efficiency
* quality management, continuous improvement
* measuring > analyzing > improving
* large organizations or efficiency is an issue

Integrated Project Management (IPM)
* focus on documents like project charter, plan, execution, monitoring and change control
* meet regularly as team
* accountability
* time for planning

PRiSM Projects Integrating Sustainable Methods
* developed by Green Project Management Global
* account and minimize adverse environmental impacts
* extends beyond the end of the project
* factors in environmental costs and sustainability is key success criteria
* mostly geared to real estate and industrial projects

Approaches also worth noting:
* Human-centered design - creative approach to problem solving with three phases: inspiration, ideation, implementation; start with people in mind, try it out and test with people in an iterative process.
* Participatory decision-making - creative approach to enabling the entire group ownership and participation in decisions. It includes an emphasis on facilitation and concensus-building.
* Participatory Action Research (PAR) is an approach to research emphasizing co-creation, participation, and action by members of communities affected by the research.

== References ==
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.

Project management methodology (PMM)

2021-11-06T17:39:10Z

Cristelags:

Project management methodology (PMM) is a system of principles, techniques, and procedures.

The following is an overview of a few different PMM that hopefully inspires curiosity to learn more. Please contribute additional PMM or other examples to the '''[[DLF Project Managers Toolkit]]'''.

[[File:Waterfall.png|thumb|right|Waterfall PMM]]
waterfall (software development)
* detailed linear process of tasks in sequential order
* project flows downward like waterfall
* comprehensive, predictable and planned out
* focus on documentation
* good for large projects with multiple stakeholders
* not flexible, if assumptions are wrong, hard to pivot

critical path method (CPM) (industry)
* identify and schedule tasks, duration and dependencies
* good for tight timelines and repetitive activities
* not good if unsure of timelines, durations for tasks
* not flexible if there are major changes

agile (software development)
* reaction to waterfall method http://agilemanifesto.org/
* "early and often, adjust and iterate"
* flexible and responsive to change
* stakeholders must stay engaged and be available to provide timely feedback
* not always fast in practice if constantly changing deliverables
* not focused on comprehensive documentation

There are many agile approaches including scrum, kanban, feature-driven development, and extreme programming.

scrum (software development)
* small, cross functional teams
* short sprints
* regular "stand-up" meeting
* retrospectives after each sprint
* focus on continual optimization and improvements
* harder to do with fixed budgets and timelines
* self-managing teams can have issues with scope creep

kanban (industry)
* billboard in Japanese
* simple, clear framework
* visualize workflow and tasks
* large and small teams, remote or in person
* not detailed "at-a-glance"
* not if complex, lots of steps in the process

hybrid/structured agile
* combine waterfall and agile methods
* focus on gathering and analyzing requirements then rapid iterations
* best of both worlds - structure and flexibility
* best for medium-sized project with high complexity and fixed budgets

Lean Six Sigma (industry)
* Define, Measure, Analyze, Improve, Control
* cut waste and maximize efficiency
* quality management, continuous improvement
* measuring > analyzing > improving
* large organizations or efficiency is an issue

Integrated Project Management (IPM)
* focus on documents like project charter, plan, execution, monitoring and change control
* meet regularly as team
* accountability
* time for planning

PRiSM Projects Integrating Sustainable Methods
* developed by Green Project Management Global
* account and minimize adverse environmental impacts
* extends beyond the end of the project
* factors in environmental costs and sustainability is key success criteria
* mostly geared to real estate and industrial projects

Approaches also worth noting:
Human-centered design - creative approach to problem solving with three phases: inspiration, ideation, implementation; start with people in mind, try it out and test with people in an iterative process.
Participatory decision-making - creative approach to enabling the entire group ownership and participation in decisions. It includes an emphasis on facilitation and concensus-building.
Participatory Action Research (PAR) is an approach to research emphasizing co-creation, participation, and action by members of communities affected by the research.

Factors in choosing a PM Method
* Project goals, objectives, and complexity
* Team - size, level of experience/training, location - remote/on-site, specialization of roles
* Timeline
* Budget
* Stakeholder expectations
* Values/organizational culture
* Ability to take risk
* Flexibility for change

== References ==
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.

File:Agile.png

2021-11-06T17:38:46Z

Cristelags:

Image for agile approach

Project management methodology (PMM)

2021-11-06T17:36:03Z

Cristelags:

Project management methodology (PMM) is a system of principles, techniques, and procedures.

The following is an overview of a few different PMM that hopefully inspires curiosity to learn more. Please contribute additional PMM or other examples to the '''[[DLF Project Managers Toolkit]]'''.

[[File:Waterfall.png|thumb|right|thumb|Waterfall PMM]]
waterfall (software development)
* detailed linear process of tasks in sequential order
* project flows downward like waterfall
* comprehensive, predictable and planned out
* focus on documentation
* good for large projects with multiple stakeholders
* not flexible, if assumptions are wrong, hard to pivot

critical path method (CPM) (industry)
* identify and schedule tasks, duration and dependencies
* good for tight timelines and repetitive activities
* not good if unsure of timelines, durations for tasks
* not flexible if there are major changes

agile (software development)
* reaction to waterfall method http://agilemanifesto.org/
* "early and often, adjust and iterate"
* flexible and responsive to change
* stakeholders must stay engaged and be available to provide timely feedback
* not always fast in practice if constantly changing deliverables
* not focused on comprehensive documentation

There are many agile approaches including scrum, kanban, feature-driven development, and extreme programming.

scrum (software development)
* small, cross functional teams
* short sprints
* regular "stand-up" meeting
* retrospectives after each sprint
* focus on continual optimization and improvements
* harder to do with fixed budgets and timelines
* self-managing teams can have issues with scope creep

kanban (industry)
* billboard in Japanese
* simple, clear framework
* visualize workflow and tasks
* large and small teams, remote or in person
* not detailed "at-a-glance"
* not if complex, lots of steps in the process

hybrid/structured agile
* combine waterfall and agile methods
* focus on gathering and analyzing requirements then rapid iterations
* best of both worlds - structure and flexibility
* best for medium-sized project with high complexity and fixed budgets

Lean Six Sigma (industry)
* Define, Measure, Analyze, Improve, Control
* cut waste and maximize efficiency
* quality management, continuous improvement
* measuring > analyzing > improving
* large organizations or efficiency is an issue

Integrated Project Management (IPM)
* focus on documents like project charter, plan, execution, monitoring and change control
* meet regularly as team
* accountability
* time for planning

PRiSM Projects Integrating Sustainable Methods
* developed by Green Project Management Global
* account and minimize adverse environmental impacts
* extends beyond the end of the project
* factors in environmental costs and sustainability is key success criteria
* mostly geared to real estate and industrial projects

Approaches also worth noting:
Human-centered design - creative approach to problem solving with three phases: inspiration, ideation, implementation; start with people in mind, try it out and test with people in an iterative process.
Participatory decision-making - creative approach to enabling the entire group ownership and participation in decisions. It includes an emphasis on facilitation and concensus-building.
Participatory Action Research (PAR) is an approach to research emphasizing co-creation, participation, and action by members of communities affected by the research.

Factors in choosing a PM Method
* Project goals, objectives, and complexity
* Team - size, level of experience/training, location - remote/on-site, specialization of roles
* Timeline
* Budget
* Stakeholder expectations
* Values/organizational culture
* Ability to take risk
* Flexibility for change

== References ==
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.