Development Template - Revision history

Aidan Williamson at 18:54, 13 November 2019

2019-11-13T18:54:07Z

← Older revision		Revision as of 18:54, 13 November 2019
Line 1:		Line 1:
	#redirect [[Development Spreadsheet Template]]		#redirect [[Development Spreadsheet Template]]

			[[Category:Collaboration_Architecture]]

Marcin: Redirected page to Development Spreadsheet Template

2018-02-27T17:21:59Z

Redirected page to Development Spreadsheet Template

← Older revision		Revision as of 17:21, 27 February 2018
Line 1:		Line 1:
	#redirect [[Template]]		#redirect [[Development Spreadsheet Template]]

Marcin: Redirected page to Template

2018-02-27T17:21:39Z

Redirected page to Template

Show changes

Marcin at 00:17, 21 January 2018

2018-01-21T00:17:12Z

← Older revision		Revision as of 00:17, 21 January 2018
Line 1:		Line 1:
			{{Hint\|This page should be merged with [[Template]] and then deleted. [[Template]] is the more current version.}}

	=Introduction=		=Introduction=

Marcin: /* Links */

2018-01-21T00:16:20Z

Links

← Older revision		Revision as of 00:16, 21 January 2018
Line 148:		Line 148:

	=Links=		=Links=
			*'''[[Template]]''' is the current page
	*[[Development Template Log]]		*[[Development Template Log]]
	*Somewhat dated now - overview at http://opensourceecology.org/development/		*Somewhat dated now - overview at http://opensourceecology.org/development/
	*[[Development]]		*[[Development]]

Marcin: /* Usage */

2017-05-29T19:04:29Z

Usage

← Older revision		Revision as of 19:04, 29 May 2017
Line 11:		Line 11:
	Note that the template below mixes process and technical development steps somewhat, and this needs to be reconciled.		Note that the template below mixes process and technical development steps somewhat, and this needs to be reconciled.

	<html><iframe src="https://docs.google.com/spreadsheets/d/~~1LPR7_ksJ_hvMxvgZAH~~-~~DSz1MGzbzkX4nnFjg1TVQ8h0~~/pubhtml?widget=true&headers=false"height=900 width=500>></iframe></html>		<html><iframe src="https://docs.google.com/spreadsheets/d/1tOpd6turRVkiu3LHZ72o98MZziBLp-kUVRxjHMo1ix0/pubhtml?widget=true&headers=false" height=900 width=500>></iframe></html>

	[https://docs.google.com/spreadsheets/d/~~1LPR7_ksJ_hvMxvgZAH~~-~~DSz1MGzbzkX4nnFjg1TVQ8h0~~/edit#gid=1 edit]

			[https://docs.google.com/spreadsheets/d/1tOpd6turRVkiu3LHZ72o98MZziBLp-kUVRxjHMo1ix0/edit#gid=1 edit]

	=Process Map=		=Process Map=

Marcin: /* Process Management Checklist */

2017-02-28T21:06:27Z

Process Management Checklist

← Older revision		Revision as of 21:06, 28 February 2017
Line 40:		Line 40:
	The checklist for the Process Manager's role is assuring that these tasks are accomplished:		The checklist for the Process Manager's role is assuring that these tasks are accomplished:

	*Helps orient new Working Team members.		*Helps orient new Working Team members - Welcome Email
	*Pairs up developers in groups of 2 as the basic unit of team organization. Pairs collaborate on working tasks. Working in pairs comes from software's [[Extreme Programming]] agile methodology, and assures that visible progress is occuring even if one person is not availabe. This method also allows a Working Team to reach 24 members while remaining manageable. Both team members are expected to participate in the Weekly Project Meeting (typically Monday 11 AM CST) .		*Pairs up developers in groups of 2 as the basic unit of team organization. Pairs collaborate on working tasks. Working in pairs comes from software's [[Extreme Programming]] agile methodology, and assures that visible progress is occuring even if one person is not availabe. This method also allows a Working Team to reach 24 members while remaining manageable. Both team members are expected to participate in the Weekly Project Meeting (typically Monday 11 AM CST) .
	*Maintenance of the [[Logs]] page. Both New OSE Developers' logs and any new project logs are added to the [[Logs]] page.		*Maintenance of the [[Logs]] page. Both New OSE Developers' logs and any new project logs are added to the [[Logs]] page.

Richard White: /* Process Management Checklist */

2017-02-28T21:06:14Z

Process Management Checklist

← Older revision		Revision as of 21:06, 28 February 2017
Line 41:		Line 41:

	*Helps orient new Working Team members.		*Helps orient new Working Team members.
	*Pairs up developers in groups of 2 as the basic unit of team organization. Pairs collaborate on working ~~tasksk~~. Working in pairs comes from software's [[Extreme Programming]] agile methodology, and assures that visible progress is occuring even if one person is not availabe. This method also allows a Working Team to reach 24 members while remaining manageable. Both team members are expected to participate in the Weekly Project Meeting (typically Monday 11 AM CST) .		*Pairs up developers in groups of 2 as the basic unit of team organization. Pairs collaborate on working tasks. Working in pairs comes from software's [[Extreme Programming]] agile methodology, and assures that visible progress is occuring even if one person is not availabe. This method also allows a Working Team to reach 24 members while remaining manageable. Both team members are expected to participate in the Weekly Project Meeting (typically Monday 11 AM CST) .
	*Maintenance of the [[Logs]] page. Both New OSE Developers' logs and any new project logs are added to the [[Logs]] page.		*Maintenance of the [[Logs]] page. Both New OSE Developers' logs and any new project logs are added to the [[Logs]] page.
	*Each OSE Developer maintains a log of their weekly activity as<nowiki>[[Developer Name Log]]</nowiki>		*Each OSE Developer maintains a log of their weekly activity as<nowiki>[[Developer Name Log]]</nowiki>

Marcin: /* Process Manager */

2017-02-16T21:46:24Z

Process Manager

← Older revision		Revision as of 21:46, 16 February 2017
Line 35:		Line 35:

	=Process Manager=		=Process Manager=
	The Process Manager is someone selected from the OSE Developer team who takes on additional management responsibility. The Process Manager is ~~expected~~ to ~~use any of~~ their ~~remaining time~~ of ~~their weekly volunteer schedule to engage in regular product development with~~ the ~~rest~~ of ~~the Development~~ Teams.. The checklist for the Process Manager's role is assuring that these tasks are accomplished:		The Process Manager is someone selected from the OSE Developer team who takes on additional management responsibility in addition to normal development tasks. There are 2 main aspects. First, is a checklist of day-to-day tasks, and the second is guiding a Working Team in terms of overall direction. The goal of the Process Manager's role in guiding Working Teams is to free the Heavyweight Product Manager (HPM) as much as possible so that the HPM can fulfill their role of managing the overall project, consisting of many Working Teams. A Working Team could in principle be started for each of the different [[GVCS Modules]], of which there is a total of approximately 500.

			==Process Management Checklist==
			The checklist for the Process Manager's role is assuring that these tasks are accomplished:

	*Helps orient new Working Team members.		*Helps orient new Working Team members.
	*Pairs up developers in groups of 2 as the basic unit of team organization. Pairs collaborate on working tasksk. Working in pairs comes from software's [[Extreme Programming]] agile methodology, and assures that visible progress is occuring even if one person is not availabe. This method also allows a Working Team to reach 24 members while remaining manageable. Both team members are expected to participate in the Weekly Project Meeting (typically Monday 11 AM CST) .		*Pairs up developers in groups of 2 as the basic unit of team organization. Pairs collaborate on working tasksk. Working in pairs comes from software's [[Extreme Programming]] agile methodology, and assures that visible progress is occuring even if one person is not availabe. This method also allows a Working Team to reach 24 members while remaining manageable. Both team members are expected to participate in the Weekly Project Meeting (typically Monday 11 AM CST) .
	Maintenance of the [[Logs]] page. Both New OSE Developers' logs and any new project logs are added to the [[Logs]] page.Each OSE Developer maintains a log of their weekly activity as<nowiki>[[Developer Name Log]]</nowiki>		*Maintenance of the [[Logs]] page. Both New OSE Developers' logs and any new project logs are added to the [[Logs]] page.
			*Each OSE Developer maintains a log of their weekly activity as<nowiki>[[Developer Name Log]]</nowiki>
	*Each OSE Developer fills out a weekly [[Time Sheet]]		*Each OSE Developer fills out a weekly [[Time Sheet]]
	*Coordinates with HR on additional roles/members needed for each team. Coordinates with HR on hiring/firing decisions. Any firing decisions are made upon the OSE Developer missing 3 or more of the 12 weekly assignments in any 90 day development period.		*Coordinates with HR on additional roles/members needed for each team. Coordinates with HR on hiring/firing decisions. Any firing decisions are made upon the OSE Developer missing 3 or more of the 12 weekly assignments in any 90 day development period.
Line 48:		Line 53:
	*maintains a burndown graph based on the [[Development Template]] completion status		*maintains a burndown graph based on the [[Development Template]] completion status
	*Adds links to the Work Product column of Development Template		*Adds links to the Work Product column of Development Template

			==Process Management Training==
			While the Process Management Checklist above is relatively straightforward, and can be carried out relatively easily, guiding the development process itself according to the Development Template can be much more challenging. For this, a detailed narrative and extensive hands-on training (3 months minimum) is required. Here is a draft of the Process Management Traiing.

			<html><iframe src="https://docs.google.com/presentation/d/1lwE1I_4j69hxWkZhX1-DKS-jAjqSqVzwv0f3yZem3TU/embed?start=false&loop=false&delayms=3000" frameborder="0" width="960" height="569" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe></html>

	=Development Template Requirements=		=Development Template Requirements=

Marcin: /* Process Manager */

2017-02-03T21:46:25Z

Process Manager

← Older revision		Revision as of 21:46, 3 February 2017
Line 46:		Line 46:
	*If team reaches 12 pairs, a new team should be started. The Process Manager facilitates training of a new Process Manager for a new team.		*If team reaches 12 pairs, a new team should be started. The Process Manager facilitates training of a new Process Manager for a new team.
	*Process Managers study the Development Template on an ongoing basis to understand the development workflow. The [[Process Manager Certification]] will be released after the first 90-day development cycle. Certified Process Managers are responsible for selecting and training new process managers. OSE's goal is to double the number of 12 pair working teams after every 90 day Development Cycle.		*Process Managers study the Development Template on an ongoing basis to understand the development workflow. The [[Process Manager Certification]] will be released after the first 90-day development cycle. Certified Process Managers are responsible for selecting and training new process managers. OSE's goal is to double the number of 12 pair working teams after every 90 day Development Cycle.
	*maintains a burndown graph based on the Development Template completion status		*maintains a burndown graph based on the [[Development Template]] completion status
	*Adds links to the Work Product column of Development Template		*Adds links to the Work Product column of Development Template