Planning and Review Strategy: Difference between revisions

From Open Source Ecology
Jump to navigation Jump to search
No edit summary
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  

Revision as of 00:20, 23 August 2012

  • People record major milestones (achieved and future) in Gantt Chart
  • Gantt chart links to 6 month work plan for each person


Introduction

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.
    • Logging of tasks done (daily)
    • Vlogging of results (daily)
    • Keeping a Gantt chart of ongoing activities and milestones (weekly), on a 6 month time scale
    • 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)
    • 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
    • Biweekly blogging of progress updatesrequester
    • 6 Month Plan outline

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.