Planning and Review Strategy - Revision history

Marcin: /* Specific Implementation Concept */

2012-08-24T13:50:04Z

Specific Implementation Concept

Marcin: /* Specific Implementation Concept */

2012-08-24T13:47:16Z

Specific Implementation Concept

← Older revision		Revision as of 13:47, 24 August 2012
Line 23:		Line 23:

	*Parker sets up all calendars - GVCS, Organizational, Infrastructure, and Agriculture - both planning and done - so 8 calendars		*Parker sets up all calendars - GVCS, Organizational, Infrastructure, and Agriculture - both planning and done - so 8 calendars
	*Parker sets up and manages a Milestones Calendar. Milestones are placed on calendar and		*Parker sets up and manages a Milestones Calendar. Milestones are placed on calendar for transparency. Accountability is endorsed by Leaders and Managers.
			*Participates in a weekly or biweekly planning meeting.
	**Participates in a weekly or biweekly planning meeting.		*Logs tasks done in Status Log (daily)
	**Logs tasks done in Status Log (daily)		*Vlogging of progress and results (daily)
	**Vlogging of progress and results (daily)		*Keeping a Gantt chart of ongoing activities and milestones (weekly)
	**Keeping a Gantt chart of ongoing activities and milestones (weekly)		*Weekly planning of calendar on wiki
	**Weekly planning of calendar on wiki		*Monthly priority planning on wiki and review of tasks done
	**Monthly priority planning on wiki and review of tasks done		*Logging of microtasks on Scrumy
	**Logging of microtasks on Scrumy		*Biweekly blogging of progress updates
	**Biweekly blogging of progress updates

	=Planning and Review Specification=		=Planning and Review Specification=

Marcin: /* Specific Implementation Concept */

2012-08-24T13:46:20Z

Specific Implementation Concept

← Older revision		Revision as of 13:46, 24 August 2012
Line 21:		Line 21:

	=Specific Implementation Concept=		=Specific Implementation Concept=

			*Parker sets up all calendars - GVCS, Organizational, Infrastructure, and Agriculture - both planning and done - so 8 calendars
			*Parker sets up and manages a Milestones Calendar. Milestones are placed on calendar and

	**Participates in a weekly or biweekly planning meeting.		**Participates in a weekly or biweekly planning meeting.

Marcin: /* Introduction */

2012-08-23T13:48:15Z

Introduction

← Older revision		Revision as of 13:48, 23 August 2012
Line 5:		Line 5:
	We are interested in innovative project management via use of wikis, google docs, and other simple web-embeddable content accesses at [[One-Click Level]]. The intent of this platform is to allow for effective, decentralized oversight of accountability on project progress - where even remote participants can serve the role of Reviewer/Task Manager. We are testing the limits of rhozome network organization coupled with well-structured institutions. The institution is OSE, and the rhizomatic organization refers to allowing remote participants to engage in meaningful collaboration on both organizational development and remote prototyping. This is highly experimental.		We are interested in innovative project management via use of wikis, google docs, and other simple web-embeddable content accesses at [[One-Click Level]]. The intent of this platform is to allow for effective, decentralized oversight of accountability on project progress - where even remote participants can serve the role of Reviewer/Task Manager. We are testing the limits of rhozome network organization coupled with well-structured institutions. The institution is OSE, and the rhizomatic organization refers to allowing remote participants to engage in meaningful collaboration on both organizational development and remote prototyping. This is highly experimental.

	One ~~specific~~ implementation of a planning review process ~~is this~~:		One implementation of a planning review process may include:

	**Weekly or biweekly planning meeting.		**Weekly or biweekly planning meeting.
Line 19:		Line 19:
	**Biweekly blogging of progress updates		**Biweekly blogging of progress updates
	**6 Month Plan outline		**6 Month Plan outline

			=Specific Implementation Concept=

			**Participates in a weekly or biweekly planning meeting.
			**Logs tasks done in Status Log (daily)
			**Vlogging of progress and results (daily)
			**Keeping a Gantt chart of ongoing activities and milestones (weekly)
			**Weekly planning of calendar on wiki
			**Monthly priority planning on wiki and review of tasks done
			**Logging of microtasks on Scrumy
			**Biweekly blogging of progress updates

	=Planning and Review Specification=		=Planning and Review Specification=

Marcin: /* Planning and Review Specification */

2012-08-23T13:47:33Z

Planning and Review Specification

← Older revision		Revision as of 13:47, 23 August 2012
Line 24:		Line 24:
	*Platform provides straightforward assessment of performance on a weekly basis.		*Platform provides straightforward assessment of performance on a weekly basis.
	*Platform provides straightforward assessment of performance on a monthly basis.		*Platform provides straightforward assessment of performance on a monthly basis.
			*Transparency allows for review from non-solicited sources
	[[Category:Standards]]		[[Category:Standards]]

Marcin at 01:09, 23 August 2012

2012-08-23T01:09:48Z

← Older revision		Revision as of 01:09, 23 August 2012
Line 1:		Line 1:
	See also [[Flashy XM Specification]]		See also [[Flashy XM Specification]]
	*People record major milestones (achieved and future) in Gantt Chart
	*Gantt chart links to 6 month work plan for each person


	=Introduction=		=Introduction=

Marcin at 01:08, 23 August 2012

2012-08-23T01:08:20Z

← Older revision		Revision as of 01:08, 23 August 2012
Line 1:		Line 1:
			See also [[Flashy XM Specification]]
	*People record major milestones (achieved and future) in Gantt Chart		*People record major milestones (achieved and future) in Gantt Chart
	*Gantt chart links to 6 month work plan for each person		*Gantt chart links to 6 month work plan for each person

Marcin: /* Introduction */

2012-08-23T00:21:35Z

Introduction

← Older revision		Revision as of 00:21, 23 August 2012
Line 19:		Line 19:
	**Daily automated form sent for logging Hours-Tasks-Accomplishments to account for a minimum of 8 hours of productivity		**Daily automated form sent for logging Hours-Tasks-Accomplishments to account for a minimum of 8 hours of productivity
	**Logging of microtasks on Scrumy		**Logging of microtasks on Scrumy
	**Biweekly blogging of progress ~~updatesrequester~~		**Biweekly blogging of progress updates
	**6 Month Plan outline		**6 Month Plan outline

Marcin: /* Planning and Review Specification */

2012-08-23T00:21:19Z

Planning and Review Specification

← Older revision		Revision as of 00:21, 23 August 2012
Line 24:		Line 24:
	=Planning and Review Specification=		=Planning and Review Specification=
	*Platform allows transparent, [[One-Click Level]] viewing of a person's tasks and it should allow for easy assessment of time taken on tasks and product delivered on a daily basis, 5 days a week. For planning and review - everybody sees what another person is doing at one-click level. Every person has a forum to evaluate what another person is doing.		*Platform allows transparent, [[One-Click Level]] viewing of a person's tasks and it should allow for easy assessment of time taken on tasks and product delivered on a daily basis, 5 days a week. For planning and review - everybody sees what another person is doing at one-click level. Every person has a forum to evaluate what another person is doing.
			*Platform provides straightforward assessment of performance on a weekly basis.
			*Platform provides straightforward assessment of performance on a monthly basis.

	[[Category:Standards]]		[[Category:Standards]]

Marcin: /* Introduction */

2012-08-23T00:20:09Z

Introduction

← Older revision		Revision as of 00:20, 23 August 2012
Line 4:		Line 4:

	=Introduction=		=Introduction=
	*Specifically
			We are interested in innovative project management via use of wikis, google docs, and other simple web-embeddable content accesses at [[One-Click Level]]. The intent of this platform is to allow for effective, decentralized oversight of accountability on project progress - where even remote participants can serve the role of Reviewer/Task Manager. We are testing the limits of rhozome network organization coupled with well-structured institutions. The institution is OSE, and the rhizomatic organization refers to allowing remote participants to engage in meaningful collaboration on both organizational development and remote prototyping. This is highly experimental.

			One specific implementation of a planning review process is this:

	**Weekly or biweekly planning meeting.		**Weekly or biweekly planning meeting.
	**Logging of tasks done (daily)		**Logging of tasks done (daily)
Line 11:		Line 15:
	**Weekly planning of calendar on wiki.		**Weekly planning of calendar on wiki.
	**Every agreement that leads to a promise of performance is placed on Calendar by requester (customer), shared with the person who makes promise (performer)		**Every agreement that leads to a promise of performance is placed on Calendar by requester (customer), shared with the person who makes promise (performer)
	**Monthly priority planning on wiki ~~and~~ review of tasks done		**Monthly priority planning on wiki submitted automatically via a Google form
			**Monthly review of tasks done:
			**Daily automated form sent for logging Hours-Tasks-Accomplishments to account for a minimum of 8 hours of productivity
	**Logging of microtasks on Scrumy		**Logging of microtasks on Scrumy
	**Biweekly blogging of progress updatesrequester		**Biweekly blogging of progress updatesrequester

← Older revision		Revision as of 13:50, 24 August 2012
Line 24:		Line 24:
	*Parker sets up all calendars - GVCS, Organizational, Infrastructure, and Agriculture - both planning and done - so 8 calendars		*Parker sets up all calendars - GVCS, Organizational, Infrastructure, and Agriculture - both planning and done - so 8 calendars
	*Parker sets up and manages a Milestones Calendar. Milestones are placed on calendar for transparency. Accountability is endorsed by Leaders and Managers.		*Parker sets up and manages a Milestones Calendar. Milestones are placed on calendar for transparency. Accountability is endorsed by Leaders and Managers.
	*~~Participates~~ in a weekly or biweekly planning meeting.		*Project Directors and Managers participate in a weekly or biweekly planning meeting. Milestones are recorded.
			*Weekly planning of calendar on wiki on their own by every Leader

			Logging:

	*Logs tasks done in Status Log (daily)		*Logs tasks done in Status Log (daily)
	*Vlogging of progress and results (daily)		*Vlogging of progress and results (daily)
	*Keeping a Gantt chart of ongoing activities and milestones (weekly)		*Keeping a Gantt chart of ongoing activities and milestones (weekly)
	*Weekly planning of calendar on wiki		*Monthly priority planning on wiki - via Google form and logged in spreadsheet - and review of tasks done
	*Monthly priority planning on wiki and review of tasks done
	*Logging of microtasks on Scrumy		*Logging of microtasks on Scrumy
	*Biweekly blogging of progress updates		*Biweekly blogging of progress updates by all Developers and Directors, and 1 monthly blog post by Video Communications Director

	=Planning and Review Specification=		=Planning and Review Specification=