Project Review - Revision history

Marcin: /* 2021 */

2021-02-24T15:08:36Z

2021

← Older revision		Revision as of 15:08, 24 February 2021
Line 2:		Line 2:
	New Critical Path Template:		New Critical Path Template:

	<html> ~~________________________________~~ </html>		<html> <iframe src="https://docs.google.com/presentation/d/e/2PACX-1vSX_9FUzWlKx3YgCiwrt_HA7CeohUjyUPVLS2fUUhghS-iWUn5wRJeW_SsAbkLTRH544apKUw0YvOZx/embed?start=false&loop=false&delayms=3000" frameborder="0" width="701" height="423" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe> </html>

	[~~_______________________________________~~ edit]		[https://docs.google.com/presentation/d/14J3xuvXAivm50xqoRgklK06F0ZeVcsU_eDvoQF6BaWY/edit#slide=id.gbff9626abc_1_0 edit]

	=Introduction: Extreme Management=		=Introduction: Extreme Management=

Marcin: /* Introduction: Extreme Management */

2021-02-24T15:08:12Z

Introduction: Extreme Management

← Older revision		Revision as of 15:08, 24 February 2021
Line 1:		Line 1:
			=2021=
			New Critical Path Template:

			<html> ________________________________ </html>

			[_______________________________________ edit]

	=Introduction: Extreme Management=		=Introduction: Extreme Management=

Marcin: /* Commentary */

2018-07-07T08:55:24Z

Commentary

← Older revision		Revision as of 08:55, 7 July 2018
Line 58:		Line 58:
	*[[Review Process]]		*[[Review Process]]

	=Commentary=		=Commentary on Agile Waterfall=
	MJ's discussion on a healthy hybrid of agile and waterfall project management methods that OSE thinks can tap the advantages of each development method while mitigating the shortcomings of each method.		MJ's discussion on a healthy hybrid of agile and waterfall project management methods that OSE thinks can tap the advantages of each development method while mitigating the shortcomings of each method.

	The above is not exactly agile, because it imposes timelines, which are typically not used in the [[Scrum]] methodology. Typical agile management just works with a backlog and expected times for tasks, so a burn down velocity can be used to deduce the project completion date. In the Critical Path Method, we are doing a mix of agile and waterfall. My learnings from last year are that agile is limited because it does not easily show easy-to-follow timelines, which prevents proper assessment whether things are on track. So are we going to waterfall? Not really. By using Cloud-embeddable-linkable format (google docs), we are able to make changes on the fly, with minimal effort. This allows us to manage the project like an agile project, but it also allows to capture the learnings - by comparing expected progress to actual progress. Such learnings are not possible in agile, because agile does not document predicted progress, so organizational learning can happen only within the team, eliminating the possibility of external feedback. External feedback is critical for OSE open methods - which to me is the shortcoming of the scrum method for OSE. Another major shortcoming is poor planning on resource allocation in the way we have been doing scrum. To me the key to effective OSE management is combining the benefits of waterfall and agile - by integrating the benefits of waterfall (organizational learning, good planning) with the agility injected by using modern tools (cloud-embeddable-linkable platforms). Maybe we should call it Agile Waterfall, an oxymoron.		The above is not exactly agile, because it imposes timelines, which are typically not used in the [[Scrum]] methodology. Typical agile management just works with a backlog and expected times for tasks, so a burn down velocity can be used to deduce the project completion date. In the Critical Path Method, we are doing a mix of agile and waterfall. My learnings from last year are that agile is limited because it does not easily show easy-to-follow timelines, which prevents proper assessment whether things are on track. So are we going to waterfall? Not really. By using Cloud-embeddable-linkable format (google docs), we are able to make changes on the fly, with minimal effort. This allows us to manage the project like an agile project, but it also allows to capture the learnings - by comparing expected progress to actual progress. Such learnings are not possible in agile, because agile does not document predicted progress, so organizational learning can happen only within the team, eliminating the possibility of external feedback. External feedback is critical for OSE open methods - which to me is the shortcoming of the scrum method for OSE. Another major shortcoming is poor planning on resource allocation in the way we have been doing scrum. To me the key to effective OSE management is combining the benefits of waterfall and agile - by integrating the benefits of waterfall (organizational learning, good planning) with the agility injected by using modern tools (cloud-embeddable-linkable platforms). Maybe we should call it Agile Waterfall, an oxymoron.

Marcin: /* Sample Critical Path Diagram */

2014-01-29T18:10:12Z

Sample Critical Path Diagram

← Older revision		Revision as of 18:10, 29 January 2014
Line 14:		Line 14:

	==Sample Critical Path Diagram==		==Sample Critical Path Diagram==
	<html><img src="https://docs.google.com/drawings/d/~~1DjGZtzylMKoY3tvrAJPlOJrJk2Bki5GP_VjZK6xP00A~~/pub?w=701&h=394"></html>		<html><img src="https://docs.google.com/drawings/d/163x1JK1uDHlmWsLReWWIF3Z-szHD1aZDh1vaPvJWQyE/pub?w=701&h=394"></html>

	[https://docs.google.com/a/opensourceecology.org/drawings/d/163x1JK1uDHlmWsLReWWIF3Z-szHD1aZDh1vaPvJWQyE/edit edit]		[https://docs.google.com/a/opensourceecology.org/drawings/d/163x1JK1uDHlmWsLReWWIF3Z-szHD1aZDh1vaPvJWQyE/edit edit]

Marcin: /* Sample Critical Path Diagram */

2014-01-29T18:09:36Z

Sample Critical Path Diagram

← Older revision		Revision as of 18:09, 29 January 2014
Line 16:		Line 16:
	<html><img src="https://docs.google.com/drawings/d/1DjGZtzylMKoY3tvrAJPlOJrJk2Bki5GP_VjZK6xP00A/pub?w=701&h=394"></html>		<html><img src="https://docs.google.com/drawings/d/1DjGZtzylMKoY3tvrAJPlOJrJk2Bki5GP_VjZK6xP00A/pub?w=701&h=394"></html>

	[https://docs.google.com/a/opensourceecology.org/drawings/d/~~1DjGZtzylMKoY3tvrAJPlOJrJk2Bki5GP_VjZK6xP00A~~/edit edit]		[https://docs.google.com/a/opensourceecology.org/drawings/d/163x1JK1uDHlmWsLReWWIF3Z-szHD1aZDh1vaPvJWQyE/edit edit]

	==Sample Tracking Spreadsheet with Gantt Chart==		==Sample Tracking Spreadsheet with Gantt Chart==

Marcin: /* Introduction: Extreme Management */

2014-01-29T17:53:38Z

Introduction: Extreme Management

← Older revision		Revision as of 17:53, 29 January 2014
Line 9:		Line 9:
	*Project status and work product can be viewed from anywhere and updated readily		*Project status and work product can be viewed from anywhere and updated readily
	*Platform can be embedded into any other platform and that the updates in the display are updated readily		*Platform can be embedded into any other platform and that the updates in the display are updated readily
	*Work product ~~can be~~ linked to ~~a graphical index of~~ the ~~Extreme Management platform~~. ~~This adds a focus of documenting work product~~		*Work product is linked in a one-stop-shop to the Milestone and Task Spreadsheet.
	*Budget, timeline, sequence, duration are visible		*Budget, timeline, sequence, duration are visible in a Milestone and Task Spreadsheet.
			*Collaborators self-assess themselves via a monthly review, documented in a person's work log.

	==Sample Critical Path Diagram==		==Sample Critical Path Diagram==

Marcin: /* Links */

2014-01-29T02:37:32Z

Links

← Older revision		Revision as of 02:37, 29 January 2014
Line 55:		Line 55:
	*[[Gantt Chart]]		*[[Gantt Chart]]
	*[[Critical Deliverables for Product Development]]		*[[Critical Deliverables for Product Development]]
			*[[Review Process]]

	=Commentary=		=Commentary=

Marcin: /* Sample PERT Index */

2014-01-29T01:57:13Z

Sample PERT Index

← Older revision		Revision as of 01:57, 29 January 2014
Line 12:		Line 12:
	*Budget, timeline, sequence, duration are visible		*Budget, timeline, sequence, duration are visible

	==Sample ~~PERT Index~~==		==Sample Critical Path Diagram==
	<html><img src="https://docs.google.com/drawings/d/~~1lOTt_fFHh909YX15EmEGpmBfwYPo4wU3mVz5HVNpcjU~~/pub?w=~~800~~&h=~~500~~"></html>		<html><img src="https://docs.google.com/drawings/d/1DjGZtzylMKoY3tvrAJPlOJrJk2Bki5GP_VjZK6xP00A/pub?w=701&h=394"></html>

	[https://docs.google.com/a/opensourceecology.org/drawings/d/1DjGZtzylMKoY3tvrAJPlOJrJk2Bki5GP_VjZK6xP00A/edit edit]		[https://docs.google.com/a/opensourceecology.org/drawings/d/1DjGZtzylMKoY3tvrAJPlOJrJk2Bki5GP_VjZK6xP00A/edit edit]

Marcin: /* Sample PERT Index */

2014-01-29T01:56:14Z

Sample PERT Index

← Older revision		Revision as of 01:56, 29 January 2014
Line 15:		Line 15:
	<html><img src="https://docs.google.com/drawings/d/1lOTt_fFHh909YX15EmEGpmBfwYPo4wU3mVz5HVNpcjU/pub?w=800&h=500"></html>		<html><img src="https://docs.google.com/drawings/d/1lOTt_fFHh909YX15EmEGpmBfwYPo4wU3mVz5HVNpcjU/pub?w=800&h=500"></html>

	[https://docs.google.com/a/opensourceecology.org/drawings/d/~~1lOTt_fFHh909YX15EmEGpmBfwYPo4wU3mVz5HVNpcjU~~/edit edit]		[https://docs.google.com/a/opensourceecology.org/drawings/d/1DjGZtzylMKoY3tvrAJPlOJrJk2Bki5GP_VjZK6xP00A/edit edit]

	==Sample Tracking Spreadsheet with Gantt Chart==		==Sample Tracking Spreadsheet with Gantt Chart==

Marcin: /* Links */

2014-01-29T01:46:02Z

Links

← Older revision		Revision as of 01:46, 29 January 2014
Line 54:		Line 54:
	*[[Work Breakdown Structure]]		*[[Work Breakdown Structure]]
	*[[Gantt Chart]]		*[[Gantt Chart]]
			*[[Critical Deliverables for Product Development]]

	=Commentary=		=Commentary=