Wiki source code of OSI-EDU-WG: Months 1 & 2 Project Completion Report (March-April 2014)
Last modified by Administrator on 2023/02/17 01:52
Hide last authors
author | version | line-number | content |
---|---|---|---|
1.2 | 1 | = Timeline = | |
2 | |||
3 | * Initial OSI-EDU-WG project proposal sent to OSI by Joseph Potvin, Nov. 7, 2013. | ||
4 | * Preliminary work performed between Nov 2013 and Jan 2014. | ||
5 | * Work performed under sponsor contract from February through April 2014. | ||
6 | |||
2.4 | 7 | = Regular Participants to Date = | |
8 | |||
9 | **Joseph Potvin**, Chair, OSI-EDU-WG | ||
10 | Operations Manager, The Opman Company, http://www.opman.ca | ||
11 | |||
12 | **Amanda Brock** | ||
13 | Director/ Solicitor, Origin, International Technology Law | ||
14 | http://www.origin.co.uk | ||
15 | |||
16 | **Ken Udas** | ||
17 | Deputy Vice Chancellor & CIO, University of Southern Queensland | ||
18 | http://www.evolllution.com | ||
19 | |||
20 | **Wayne Macintosh** | ||
21 | Coordinator, OERu | ||
22 | Open Educational Resources University | ||
23 | http://www.oeru.org | ||
24 | |||
1.1 | 25 | = Summary = | |
26 | |||
1.2 | 27 | * The FLOW Syllabus v1.x has been successfully hosted by OSI and its content has been advanced. | |
1.1 | 28 | * The scope, emphasis and boundaries have been [[clarified and documented>>url:http://osi.xwiki.com/bin/Projects/draft-flow-syllabus#HAbouttheFLOWSyllabus||title="clarified and documented"]]. | |
1.2 | 29 | * The v2.0 launch is being planned for mid-June. | |
1.1 | 30 | * The Working Group structure for the coming year is described. | |
31 | |||
32 | == General Outcome == | ||
33 | |||
1.2 | 34 | * Meeting with OSI Board in Boston, 29 April 2014. Positive review. | |
2.5 | 35 | * The FLOW Syllabus now stands on it's own as a competed project, and as a re-usable resource. | |
1.2 | 36 | * Plans underway for mid-June launch. | |
37 | * Board requests: | ||
38 | ** Review the original charter to draft a new Working Group Charter with a 1-year time horizon. | ||
39 | ** Brief hand-off report regarding this first stage now being "completed". | ||
1.1 | 40 | ||
1.2 | 41 | == Review of Original OSI-EDU-WG Workplan Items and Outcomes == | |
1.1 | 42 | ||
43 | === Months 1 & 2 (March-April 2014) === | ||
44 | |||
45 | Refine initial syllabus based on initial review and preferences | ||
46 | |||
47 | * Shorten the course to 2 or 3 days only | ||
2.1 | 48 | ** **Outcome**: Structure is now fully modular to support course development of any scope and length | |
1.1 | 49 | * More specific targeting to developers' decisions | |
2.1 | 50 | ** **Outcome:** Increased reference material for developers, but also project managers | |
1.1 | 51 | * More gradual and structured entry to each topic | |
2.1 | 52 | ** **Outcome:** Learning objectives added, overall structure improved | |
1.1 | 53 | * Follow the expert-discussions with group discussion of highlights | |
2.1 | 54 | ** **Outcome:** This will be for course designers to manage | |
1.1 | 55 | * More situational examples for discussion | |
2.1 | 56 | ** **Outcome:** Additional pragmatic sources | |
1.1 | 57 | * When actual legal documents are used, provide more specific pointers for discussion | |
2.1 | 58 | ** **Outcome:** Interpretive references added | |
1.1 | 59 | * Update the content (esp. current major court case references) | |
2.1 | 60 | ** **Outcome:** Several updates, but also the role of legal principles versus legal cases are distinguished | |
1.1 | 61 | * Produce a course delivery guide (“train the trainer”) | |
2.1 | 62 | ** **Outcome:** Section: About the FLOW Syllabus | |
1.1 | 63 | * Expand content on financial, benefit/cost & accounting to support ROI analysis | |
2.1 | 64 | ** **Outcome:** Expansion of references under the title: "Good Values + Good Value" | |
1.1 | 65 | * Create a short evocative name for this syllabus | |
2.1 | 66 | ** **Outcome:** Free/Libre/Open Works (FLOW) Syllabus | |
1.1 | 67 | * Design and begin train-the-trainer workshops based on existing materials and prior contractor experience | |
2.1 | 68 | ** **Outcome:** To be pursued in relation to launch of v2.0 | |
1.1 | 69 | * Complete podcasts based on existing materials | |
2.1 | 70 | ** **Outcome:** Some audio segments will be used in instructional videos | |
1.1 | 71 | ||
72 | === Months 3 & 4 (May-June 2014) === | ||
73 | |||
74 | * Priority syllabus additions identified, researched and integrated | ||
2.1 | 75 | ** **Outcome:** In effect, this was completed in the March-April 2014 period. The main additions now focus on providing simpler more accessible means of communicating key complex topics. | |
2.2 | 76 | * Instead, the May-June period is being used to document status, and to plan/undertake an official launch of v2.0 | |
1.1 | 77 | ||
1.5 | 78 | == Resourcing Requirements Going Forward == | |
1.2 | 79 | ||
1.5 | 80 | There are three different types of ongoing activity each with separate resourcing models: | |
81 | |||
82 | * __Development and marketing of commercial/academic training based on the syllabus.__ This work can proceed as financially self-sustained ad hoc offerings to the clients by each training/consulting services company/organization. Use of the syllabus creates a natural incentive for routine updates, improvements and extensions to the syllabus. | ||
83 | * __Development of specific educational modules to advance the scope, quality and utility of the syllabus, beyond routine updates, improvements and extensions.__ Such work can sometimes be contributed by suppliers of commercial/academic training. Modules can also be individually resourced by particular companies, foundations or other organizations that wish to advance the coverage of a certain topic within the framework of The FLOW Syllabus. | ||
84 | * __Coordination, administration, strategic direction and marketing of the Working Group and its four teams: Educational; Management; Legal; Technological.__ The FLOW Syllabus combines contributions from all four of these teams. To ensure continuity this coordination work requires a moderate amount of regular core funding from one or more organizations that benefit from its overall availability and evolution. Business co-sponsors are required. (WG Chair: At least 1/2 day per week at this time; Each Team Chair: At least 1/2 day per week at this time.) | ||
85 | |||
86 | == OSI Board Assistance Requirements Going Forward == | ||
87 | |||
88 | * OSI Staff and Board | ||
2.1 | 89 | ** **Needs:** Pro-active communication and engagement by GM and at least one Board Member | |
1.5 | 90 | * OSI infrastructure needs | |
2.1 | 91 | ** **Needs:** Current BBB support should continue | |
1.5 | 92 | * Ongoing participant community | |
2.1 | 93 | ** **Needs:** This needs to expand through the June launch | |
1.5 | 94 | * Ongoing budgeting/revenue | |
2.1 | 95 | ** **Needs:** OSI Board assistance will be valuable towards arranging core funding through networking and referral for resourcing. | |
1.5 | 96 | ||
97 | == Work Items Not Yet Addressed == | ||
98 | |||
1.1 | 99 | === Months 5 & 6 === | |
100 | |||
101 | * Hold workshop based on syllabus with Project Management Professionals/Educators | ||
2.1 | 102 | ** **Plan**: TBD | |
1.1 | 103 | ||
104 | === Months 7 & 8 === | ||
105 | |||
106 | * Scope, research and integrate any new changes resulting from workshop held in previous milestone | ||
2.1 | 107 | ** **Plan**: TBD | |
1.1 | 108 | ||
109 | === Months 9 & 10 === | ||
110 | |||
111 | * Special free/libre/open issue of a PM journal | ||
2.1 | 112 | ** **Plan**: TBD |