Immersion Program Calendar

OSE Fellows work together remotely, and spend 3 months on site per year. The typical routine is:

1. Daily Standup - at 11 AM CST every day, all of us meet to report on progress and to coordinate, as in the Scrum daily standup meeting - except this meeting is online whenever the Fellows are not on site. This is a 15-30 minute meeting - with longer working meetings set up where we work on projects collaboratively with real-time, cloud, editable documents. Meetings are published online. The daily work schedule may require online research, prototyping with the Fellow's home desktop microfactory, or meetings with stakeholders and collaborators. It is a research and development lifestyle of constant learning. Fellows are also likely to be running their Desktop Microfactory on auto pilot 24-7 making parts, and as an ongoing part of their work - doing prototyping of new products, while recycling failed prints. Fellows log their work in their weekly time log. It is most useful to log tasks on an ongoing basis such that others have immediate access to progress.
2. Weekly Team Meeting - OSE Fellows collaborate with OSE Developers - and all Fellows also act as Developers, logging their time in our collaborative time log. There is a weekly Developer team meeting - in which Fellows coordinate with the greater developer community. Fellows report on their work and coordinate collaboration in this meeting. Participants are encouraged to present a lesson to other developers on their work on a monthly frequency. Meetings are published online.
3. Workshops - This is the core of Fellows' productive/teaching activity - where the typical workshop schedule is biweekly - though Fellows may lead more than two workshops per month if needed. Each Fellow is required to have a minimum of 10 machines built (in XM Workshops) or less if doing Extreme Education workshops. 10 is the bare minimum, 20 is a financially sustainable level that allows OSE to carry out its mission, and more than 20 is a bonus. We review our performance every month and make improvements on an ongoing basis.
4. Monthly Design Jams - These are part of social technology development for democratizing open source product design - and making collaborative product development the norm. This could feed into the Open Source Everything Store. OSE engages in public product development, and encourages the democratization of product development where every person is a designer and builder. To this end - as part of our Extreme Manufacturing and Extreme Education workshops - we teach our constituents to design products that can be built with Open Source Desktop Microfactory and Full Microfactory tools. For example, if we are teaching teachers or librarians how to design products and build productive machines - we are also encouraging them to collaborate with us on Design Jams or Coopetitions. These are cooperative competitions - where we do a day or weekend workshop designing and producing a real product. Incentive prizes can be attached to this, such as Hero X - or we can get sponsors to offer prizes. Fellows are required to collaborate on designing and executing one such Design Jam per month. Here, we have a planning meeting at the beginning of the month to design the challenge and its guidelines/rules - and towards the end of the month - we run the event. The goal is to involve common people to extend their skill set into real product design. The idea is that with the desktop microfactory and common off-the-shelf parts - a wide range of household consumer goods can be produced. Our goal is to create high quality, marketable products that are completely open source and can lead to glocal open source economic development.
5. Monthly team coaching sessions - we have the opportunity to engage in coaching by a professional business coach to improve team performance. To this end - we will engage in a monthly group coaching session, where we learn specific skills that helps us work better as a team by improving specific skill sets.
6. Monthly Skills Publishing- Fellows are required to publish instructional videos to teach one another and the rest of the world about the best practices or insights that they are learning. We learn a lot of things during the development process - and it is useful to produce screen casts and instructionals to help others learn the best practices. This could be a specific skill video such as on FreeCAD, or a short video on the operation of some machine, or other learnings. The key to rapid learning is documentation, wo we encourage frequent publishing on your own channel. Fellows publish on their own channel, and then OSE clones useful videos to the OSE channel.
7. Quarterly Product Release - all Fellows are expected to produce one product release every quarter, marked by 100% burndown of the Simple Development Template towards a marketable product. This could apply at the product or enterprise level. Every quarter, each Fellow reports their product launch to the community via a blog post on the OSE blog, and meets with OSE leadership to discuss performance development. This is also the time when we plan out the next quarter's product release - based on the OSE Roadmap, OSE's available resources, and successful completion of formerly planned milestones. Performance is defined by: (1) producing required parts with the microfactory, inventorying, and preparing for workshops; (2) executing workshops successfully and meeting quotas - including finishing builds successfully in a timely manner, as well as receiving a minimum of 3 of 5 star reviews from workshop participants on the Workshop Review Form; (3) engaging in further R&D effectively towards successful product releases; and (4), engaging in personal development, by spending 5 hours weekly on other reading and learning that helps you do your work better or become a better person - by learning insights and skills and becoming a whole person in a world of psychological disintegration.
8. Quarterly On-Site Visits - there will be many builds and events at OSE headquarters, and Fellows take a regular part in that at least on a quarterly schedule. The first on-site is the Immersion Training - and the second immersion training occurs in the first 6 month period. This is already a total of 2+ months on site. In addition to this, we will hold Summers of Extreme Design Build - where we invite the greater public as well to do prototyping and build work. In another case, Fellows are expected to visit on site for other prototyping and build events. For example, if we have done ample design work and are ready for one or several builds, we may decide to do a focused build event at the OSE headquarters. We are considering 2 such concerted build sessions - with the Summer of Extreme Design Build being one of them. As such, the total on-site time every year is approximately 3 months of the year. We are working to make the OSE headquarters a facility where Fellows and others stay year-round, but at this time we need additional infrastructure to make that happen.
9. 6 Month Review - about 6 months into the program and after the second immersion training - Fellows decide whether to continue their Fellowship beyond the 12 month mark - or to apply for more responsibilities by becoming a Senior Fellow. Fellows may remain as active Fellows for more than one year, and can decide to apply for any future Senior Fellowship. The Senior Fellowship means shadowing OSE leadership and taking other organizational and leadership tasks. See Growing with OSE.
10. Annual Global XM Extreme - Every year we organize a massive event where we build 100 machines or more - or build larger structures such as whole microfactories in a few days with 100+ people - and scale that up to concert-size events. If tens of thousands of people attend rock concerts or sport events - why not create an corresponding culture of productive edutainment?