Process Management - Revision history

Marcin: /* HR */

2017-06-13T16:48:56Z

← Older revision		Revision as of 16:48, 13 June 2017
Line 10:		Line 10:
	*Participates in team meetings to understand the subject matter		*Participates in team meetings to understand the subject matter
	*Awards Stars		*Awards Stars
	*Tracks participant dev time		*Tracks participant dev time by person - this needs to be automated


	=Training=		=Training=

Marcin: /* Meetings */

2017-06-13T16:46:19Z

Meetings

← Older revision		Revision as of 16:46, 13 June 2017
Line 25:		Line 25:
	#Review all logs and summarize		#Review all logs and summarize
	#check in with people for clarification on how that fits with the critical path		#check in with people for clarification on how that fits with the critical path
			#Update hours graph

	=Development Spreadsheet=		=Development Spreadsheet=

Marcin: /* Development spreadsheet */

2017-06-13T16:45:36Z

Development spreadsheet

← Older revision		Revision as of 16:45, 13 June 2017
Line 26:		Line 26:
	#check in with people for clarification on how that fits with the critical path		#check in with people for clarification on how that fits with the critical path

	=Development ~~spreadsheet~~=		=Development Spreadsheet=
	*Seed ~~one~~ for every project		*Seed a Dev Spreadsheet for every project
	*Adapt it to the project at hand. For wxample, hydraulics diagrams for a house mean "plumbing diagrams".		*Adapt it to the project at hand. For wxample, hydraulics diagrams for a house mean "plumbing diagrams".
	*Understand when it's appropriate to set up a new development spreadsheet and to do so as needed		*Understand when it's appropriate to set up a new development spreadsheet and to do so as needed
	*Maintain a burndown graph for each project. This does tricky as there are 50 major burn down diagrams and one overall burned down diagram and other ones depending on the phase such as design versus Enterprise development.		*Maintain a burndown graph for each project. This does tricky as there are 50 major burn down diagrams and one overall burned down diagram and other ones depending on the phase such as design versus Enterprise development.

Marcin: /* Intro */

2017-06-13T16:44:49Z

Intro

← Older revision		Revision as of 16:44, 13 June 2017
Line 4:		Line 4:

	These are broken into the following areas.		These are broken into the following areas.

			=HR=
			*Conducts Interviews
			*Sends welcome emails
			*Participates in team meetings to understand the subject matter
			*Awards Stars
			*Tracks participant dev time


			=Training=
			*Train leaders as needed - have a regular process Management training meeting
			*Technical community manager

	=Meetings=		=Meetings=

Marcin: /* Development spreadsheet */

2017-06-13T16:38:36Z

Development spreadsheet

← Older revision		Revision as of 16:38, 13 June 2017
Line 16:		Line 16:
	=Development spreadsheet=		=Development spreadsheet=
	*Seed one for every project		*Seed one for every project
			*Adapt it to the project at hand. For wxample, hydraulics diagrams for a house mean "plumbing diagrams".
	*Understand when it's appropriate to set up a new development spreadsheet and to do so as needed		*Understand when it's appropriate to set up a new development spreadsheet and to do so as needed
			*Maintain a burndown graph for each project. This does tricky as there are 50 major burn down diagrams and one overall burned down diagram and other ones depending on the phase such as design versus Enterprise development.

Marcin: /* Intro */

2017-06-13T16:36:02Z

Intro

← Older revision		Revision as of 16:36, 13 June 2017
Line 5:		Line 5:
	These are broken into the following areas.		These are broken into the following areas.

	=		=Meetings=
			*Reporting shouldn't be a focus as everyone can see each other's work.
			*However, it is useful to task someone with assimilating that info - and giving that person a 5 minutes window during the team meeting.
			*This fosters leadership

			Proposed regular task:
			#Review all logs and summarize
			#check in with people for clarification on how that fits with the critical path

			=Development spreadsheet=
			*Seed one for every project
			*Understand when it's appropriate to set up a new development spreadsheet and to do so as needed

Marcin: Created page with "=Intro= There are many areas of process Management in the OSE development process. The development team can help perform these tasks and therefore make Process Management a s..."

2017-06-13T16:14:30Z

Created page with "=Intro= There are many areas of process Management in the OSE development process. The development team can help perform these tasks and therefore make Process Management a s..."

New page

=Intro=

There are many areas of process Management in the OSE development process. The development team can help perform these tasks and therefore make Process Management a scalable process in itself. Key is clarity on organizational functioning.

These are broken into the following areas.

=