Project management methodology (PMM) - Revision history

Sarubi: Added Scrum, Kanban links

2022-07-08T19:47:58Z

Added Scrum, Kanban links

← Older revision		Revision as of 15:47, 8 July 2022
Line 31:		Line 31:


	[[File:Agile.png\|150px\|left]] ~~agile~~ (software development)		[[File:Agile.png\|150px\|left]] Agile (software development)
	* reaction to waterfall method http://agilemanifesto.org/		* reaction to waterfall method http://agilemanifesto.org/
	* "early and often, adjust and iterate"		* "early and often, adjust and iterate"
Line 41:		Line 41:


	There are many agile approaches including ~~scrum~~, ~~kanban~~, feature-driven development, and extreme programming.		There are many agile approaches including Scrum, Kanban, feature-driven development, and extreme programming (XP).


	[[File:Scrum.png\|350px\|left]] ~~scrum~~ (software development)		[[File:Scrum.png\|350px\|left]] Scrum (software development)
	* small, cross functional teams		* focus on continuous improvement https://scrumguides.org/scrum-guide.html
	* ~~short sprints~~		* small, cross-functional teams
	* ~~regular~~ "stand-up" ~~meeting~~		* work is organized in iterations
			* daily "stand-up" meetings
	* retrospectives after each sprint		* retrospectives after each sprint
	* focus on continual optimization and improvements
	* harder to do with fixed budgets and timelines		* harder to do with fixed budgets and timelines
	* self-managing teams can have issues with scope creep		* self-managing teams can have issues with scope creep


	[[File:Kanban.png\|300px\|left]] ~~kanban~~ (industry)		[[File:Kanban.png\|300px\|left]] Kanban (industry)
	* billboard in Japanese		* focus on flow https://kanbanguides.org/english/
			* ''billboard'' in Japanese
	* simple, clear framework		* simple, clear framework
	* visualize workflow and tasks		* visualize workflow and tasks
Line 73:		Line 74:
	[[File:SixSigma.png\|200px\|left]]		[[File:SixSigma.png\|200px\|left]]
	Lean Six Sigma (industry)		Lean Six Sigma (industry)
	* ~~Define~~, ~~Measure~~, ~~Analyze~~, ~~Improve~~, ~~Control~~		* define, measure, analyze, improve, control
	* cut waste and maximize efficiency		* cut waste and maximize efficiency
	* quality management, continuous improvement		* quality management, continuous improvement
Line 97:		Line 98:
	Approaches also worth noting:		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.		* 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 decision-making - creative approach to enabling the entire group ownership and participation in decisions. It includes an emphasis on facilitation and consensus-building.
	* Participatory Action Research (PAR) is an approach to research emphasizing co-creation, participation, and action by members of communities affected by the research.		* Participatory Action Research (PAR) is an approach to research emphasizing co-creation, participation, and action by members of communities affected by the research.

Cristelags at 18:29, 6 November 2021

2021-11-06T18:29:50Z

← Older revision		Revision as of 14:29, 6 November 2021
Line 44:		Line 44:


	[[File:Scrum.png\|~~300px~~\|left]] scrum (software development)		[[File:Scrum.png\|350px\|left]] scrum (software development)
	* small, cross functional teams		* small, cross functional teams
	* short sprints		* short sprints

Cristelags at 18:29, 6 November 2021

2021-11-06T18:29:27Z

← Older revision		Revision as of 14:29, 6 November 2021
Line 39:		Line 39:
	* not focused on comprehensive documentation		* not focused on comprehensive documentation

	~~<br />~~

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

Cristelags at 18:29, 6 November 2021

2021-11-06T18:29:07Z

← Older revision		Revision as of 14:29, 6 November 2021
Line 12:		Line 12:


	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]~~		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)		[[File:Waterfall.png\|200px\|left]] waterfall (software development)
Line 20:		Line 21:
	* focus on documentation		* focus on documentation
	* good for large projects with multiple stakeholders		* good for large projects with multiple stakeholders
	* not flexible, if assumptions are wrong, hard to pivot~~[br]~~		* not flexible, if assumptions are wrong, hard to pivot


	[[File:CPM.png\|350px\|left]] critical path method (CPM) (industry)		[[File:CPM.png\|350px\|left]] critical path method (CPM) (industry)

Cristelags at 18:28, 6 November 2021

2021-11-06T18:28:46Z

← Older revision		Revision as of 14:28, 6 November 2021
Line 12:		Line 12:


	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]]'''.		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)		[[File:Waterfall.png\|200px\|left]] waterfall (software development)
Line 21:		Line 20:
	* focus on documentation		* focus on documentation
	* good for large projects with multiple stakeholders		* good for large projects with multiple stakeholders
	* not flexible, if assumptions are wrong, hard to pivot		* not flexible, if assumptions are wrong, hard to pivot[br]


	[[File:CPM.png\|350px\|left]] critical path method (CPM) (industry)		[[File:CPM.png\|350px\|left]] critical path method (CPM) (industry)

Cristelags at 18:26, 6 November 2021

2021-11-06T18:26:38Z

← Older revision		Revision as of 14:26, 6 November 2021
Line 39:		Line 39:
	* not focused on comprehensive documentation		* not focused on comprehensive documentation

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


	[[File:Scrum.png\|~~200px~~\|left]] scrum (software development)		[[File:Scrum.png\|300px\|left]] scrum (software development)
	* small, cross functional teams		* small, cross functional teams
	* short sprints		* short sprints
Line 53:		Line 53:


	[[File:Kanban.png\|~~200px~~\|left]] kanban (industry)		[[File:Kanban.png\|300px\|left]] kanban (industry)
	* billboard in Japanese		* billboard in Japanese
	* simple, clear framework		* simple, clear framework

Cristelags at 18:23, 6 November 2021

2021-11-06T18:23:32Z

← Older revision		Revision as of 14:23, 6 November 2021
Line 60:		Line 60:
	* not detailed "at-a-glance"		* not detailed "at-a-glance"
	* not if complex, lots of steps in the process		* not if complex, lots of steps in the process



Line 97:		Line 98:
	* 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 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.		* Participatory Action Research (PAR) is an approach to research emphasizing co-creation, participation, and action by members of communities affected by the research.


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

Cristelags at 18:22, 6 November 2021

2021-11-06T18:22:23Z

← Older revision		Revision as of 14:22, 6 November 2021
Line 42:		Line 42:
	There are many agile approaches including scrum, kanban, feature-driven development, and extreme programming.		There are many agile approaches including scrum, kanban, feature-driven development, and extreme programming.

	scrum (software development)
			[[File:Scrum.png\|200px\|left]] scrum (software development)
	* small, cross functional teams		* small, cross functional teams
	* short sprints		* short sprints
Line 51:		Line 52:
	* self-managing teams can have issues with scope creep		* self-managing teams can have issues with scope creep

	kanban (industry)
			[[File:Kanban.png\|200px\|left]] kanban (industry)
	* billboard in Japanese		* billboard in Japanese
	* simple, clear framework		* simple, clear framework
Line 58:		Line 60:
	* not detailed "at-a-glance"		* not detailed "at-a-glance"
	* not if complex, lots of steps in the process		* not if complex, lots of steps in the process


	hybrid/structured agile		hybrid/structured agile
Line 65:		Line 68:
	* best for medium-sized project with high complexity and fixed budgets		* best for medium-sized project with high complexity and fixed budgets


			[[File:SixSigma.png\|200px\|left]]
	Lean Six Sigma (industry)		Lean Six Sigma (industry)
	* Define, Measure, Analyze, Improve, Control		* Define, Measure, Analyze, Improve, Control
Line 71:		Line 76:
	* measuring > analyzing > improving		* measuring > analyzing > improving
	* large organizations or efficiency is an issue		* large organizations or efficiency is an issue


	Integrated Project Management (IPM)		Integrated Project Management (IPM)
Line 77:		Line 83:
	* accountability		* accountability
	* time for planning		* time for planning


	PRiSM Projects Integrating Sustainable Methods		PRiSM Projects Integrating Sustainable Methods
Line 84:		Line 91:
	* factors in environmental costs and sustainability is key success criteria		* factors in environmental costs and sustainability is key success criteria
	* mostly geared to real estate and industrial projects		* mostly geared to real estate and industrial projects


	Approaches also worth noting:		Approaches also worth noting:

Cristelags at 18:11, 6 November 2021

2021-11-06T18:11:30Z

Cristelags at 18:10, 6 November 2021

2021-11-06T18:10:46Z

← Older revision		Revision as of 14:10, 6 November 2021
Line 10:		Line 10:
	* Ability to take risk		* Ability to take risk
	* Flexibility for change		* 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]]'''.		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]]'''.
Line 20:		Line 21:
	* good for large projects with multiple stakeholders		* good for large projects with multiple stakeholders
	* not flexible, if assumptions are wrong, hard to pivot </p>		* not flexible, if assumptions are wrong, hard to pivot </p>


	[[File:CPM.png\|350px\|left]] <p>critical path method (CPM) (industry)		[[File:CPM.png\|350px\|left]] <p>critical path method (CPM) (industry)
Line 26:		Line 28:
	* not good if unsure of timelines, durations for tasks		* not good if unsure of timelines, durations for tasks
	* not flexible if there are major changes </p>		* not flexible if there are major changes </p>


	[[File:Agile.png\|150px\|left]] <p>agile (software development)		[[File:Agile.png\|150px\|left]] <p>agile (software development)
Line 34:		Line 37:
	* not always fast in practice if constantly changing deliverables		* not always fast in practice if constantly changing deliverables
	* not focused on comprehensive documentation </p>		* not focused on comprehensive documentation </p>


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

← Older revision		Revision as of 14:11, 6 November 2021
Line 14:		Line 14:
	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]]'''.		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)
			[[File:Waterfall.png\|200px\|left]] waterfall (software development)
	* detailed linear process of tasks in sequential order		* detailed linear process of tasks in sequential order
	* project flows downward like waterfall		* project flows downward like waterfall
Line 20:		Line 21:
	* focus on documentation		* focus on documentation
	* good for large projects with multiple stakeholders		* good for large projects with multiple stakeholders
	* not flexible, if assumptions are wrong, hard to pivot ~~</p>~~		* not flexible, if assumptions are wrong, hard to pivot


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


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