Review: Difference between revisions

From Open Source Ecology
Jump to navigation Jump to search
Line 26: Line 26:


==Technical Review==
==Technical Review==
Send to forums, publish on blog, Facebook, and send to Subject Matter Experts, etc.
To perform a technical review: state your question clearly and send this form to forums, publish on blog, Facebook, and send to Subject Matter Experts, etc.


Post the results on a wiki page and link to it in the [[Development Board]] for the respective project.
Post the results on a wiki page and link to it in the [[Development Board]] for the respective project.

Revision as of 23:07, 24 January 2015

If you have suggestions, use our Review Form

Results

Introduction

Review is desired within an open organization - on anything that can lead to organizational learning. The goals are:

  1. Providing general feedback
  2. Providing mid-course corrections as necessary
  3. Identifying key missing resources that prevent goals from being met
  4. Assessing proper allocation of resources and shifting resources around if necessary

Key Elements of a Review Submission

  1. Clear presentation of results - allow review to happen rapidly. Brevity and clarity are key, without which it is impossible to go through all of a person's materials.
  2. Verifiable - results are easily verifiable, increasing the likelihood that

Organizational Review

Key questions:]

  1. Clarity - What is the mission of the company and what is its unique approach? How is that approach implemented? For OSE, it's the Developing an ethical, open source economy.
  2. Strategy - does the core work of the company adhere to its core mission?
  3. Coherence - is every piece of the company aligned with the core mission? What could be better?
  4. Resource allocation - are people matched to their skill set?
  5. Projects - are the projects priorities chosen in a way that helps the company grow, while considering constraints and opportinities?
  6. Learning - what mechanisms are built in so that the company is a learning organization?

Technical Review

To perform a technical review: state your question clearly and send this form to forums, publish on blog, Facebook, and send to Subject Matter Experts, etc.

Post the results on a wiki page and link to it in the Development Board for the respective project.

Implementation

Currently, OSE uses the following review process:

Organizational/Technical

  1. Core contributors maintain a daily Work Log showing all results and progress.
  2. Staff maintains a Project Review framework consisting of a Critical Path Diagram and a spreadsheet of all supporting tasks
  3. Core staff writes a monthly planning and review in their work log - 1. summary of accomplishments, 2. What worked. 3. What didn't. 4. Plan for next month.
  4. Staff meet with ED once a month for the Project Review