Extreme Enterprise Event Design

From Open Source Ecology
Jump to: navigation, search

HintLightbulb.png Hint: Early work. See later work 3/2021 at Extreme Enterprise Hackathon Design

Extreme Rules

  • Explainer videos are no more than 1 minute long.
  • Take a task before the event.
  • You don't need to carry everything on your shoulders, Jesus.
  • Play videos at 2x speed to learn if possible.
  • Work Log everything.
  • Break Down everything, modularize, and define interfaces.
  • Break down CAD into Part Libraries
  • Use FreeCAD, KiCad, and other open source tools.
  • Refer to status updates at Part Libraries, Dev template Status, and elsewhere
  • Inspire people to come over to the Light Side

Financial Model

Revenue Projections


Tue August 4, 2020



  • $50k presales, 2000 people. $5k down payment, refundable except for $200 admin fee? All must get product to have deep stakeholdership: you're not going to collaborate without greed? So we know we can pay everyone to organize this. This hedges risk for OSE, and is an inconvenience for people. OR: People simply pay - at least non-refundable down-payment - where we 'expect to succeed?' Maybe the Zero Risk Conditional Presale is less risky *minus small escrow + admin fees. Or we can have Risk-Taking and Risk-Free category - where risk-taker gets the upside of lower cost of the house at the end by say $5000 less if they make it non-refundable?
  • $50k enterprise track, with other presales to outside customers. Involves option of OSE Chapters upon graduation. Better yet - divide into OSE Chapters track, vs Enterprise Only track. This coudl be a great way to preselect for super-cooperators (people who want to contribute to a common pool of design. 5%? Or $5k/year? So we have a $500k R&D budget yearly if 100 people sign up.
  • After training - OSE Chapters, for after the event. Additional people are getting trained.
  • 2000 customers. 200 entrepreneurs. Each entrepreneur does 10 houses, within one year.
  • Extra customers - down payment, non-refundable, outside of non-performance on OSE side. So Zero risk, minus an admin charge to cover costs.


  • Scripts for parsing wiki pages for burndown? Maybe too much overhead. Instead of this, the website is a burndown - simple examination of the website.

Internet Infrastructure

Role Architecture



  • Initial Requirement - one page doc, can be pulled in from existing wiki assets and OSE Specifications
  • High level functional requirements determined by SMEs
  • A “definition of done“ needs to be formulated and agreed to by the SME’s performing the modular decomposition.
  • This will help to focus goals and prevent design creep in this planning phase.
  • The definition of done for this phase should be a general outline that describes the essential goals the SME’s must achieve to build the design template requirements/constraints.
  • The following questions and steps being completed could be the “definition of done”, but this is a flexible item and should be tailored to the needs of the particular design event.

Collect Subject Matter Experts

  • Functional units determined through modular decomposition
    • SMEs will answer generalized and product specific questions. The following questions are a good starting point.
      • Disclaimer: These questions are not law, they are meant to steer design planning/thinking in a coherent direction. When they are insufficient, they should be added to. When they are ill fitting they should not be used. As better questions are identified they should add to or replace the following.
    • What are the sub-units the total product can be broken into such that each maintain a specific and independent function?
      • for a simple example, a hand drill might decompose into the following modules : motor module, power storage/delivery module, driver/chuck and bit module, and a handle module. Each of the above has a function of it's own, however, only when combined together do we see the emergent behavior of a handheld drill.
      • Ex - for PV system, we have an initial design
    • Does OSE GVCS have a design that will interface with this product(or module of the product) in the product ecology map?
      • If yes, what are the interfaces and performance requirements that will maintain product ecology?
      • If no, What are important considerations for how this module will interface with the rest of the system? How much volume can a design occupy? What inputs does it receive? What outputs does it produce? What is the format of these outputs? How well do those outputs generalize across the range of possible recipients?
    • Does a design pattern exist for the product to be developed?
      • If yes, Does the product to be developed replace, modify, or parallel the existing design?
      • If it is to parallel the existing design what are the functional/interface differences that necessitate the redesign?
        • If there are no clear answers to this question consider using the existing pattern instead of redesigning
      • If it is to replace the existing design evaluation should be performed that the new products design requirements fulfill all roles of the design pattern being replaced.
  • Technical team composition will be determined by SME’s for each module proposed based on the skill sets required for development
  • How the functions will interface with other modules shall be constrained in this step to assure product ecology is attainable Product Ecologies
  • Pattern Diagrams/languages developed for Wiki to track and integrate the products developed
  • Metrics also need to be developed and collected once the event goes live to determine how successful the event was.
  • Appropriate metrics can inform on what if anything went wrong. Knowing this enables future XE planning groups to adjust design templates, swarming strategies, and so on to make the events even better!
    • How should we measure collaboration?
    • What is success with respect to XE?
    • How effective were collaborative efforts in group?
    • How well do the designs of different teams swap?e.g. Were the interfacing and design constraints effective at making modules interchangeable?
    • Consider a simple follow up questionnaire for people who signed up but didn't show
  • After the product has been decomposed into module templates consisting of constraints and performance requirements derived from how the module will interface with other product modules the SMEs need to describe the technical backgrounds needed to complete the design. These backgrounds will be the basis for design team make-up during the XE event.
  • The workflow of the design process also needs to be considered such that organizational/management skill sets necessary to keep efforts organized can be baked into the team composition.


  1. Reach out to candidates with a short, inspiring intro email. See if they are 'interested'.
  2. Prepare a Media Kit on OSE, and specifically on Extreme Enterprise - to include FMI. Build upon existing Media Kits
  3. For people that respond positively, send a second email with much deeper intro describing what will be required to pull this off. This determines if they are not only 'interested' in the idea, but can commit to the 24 hours, and the 1 prep meeting beforehand - and one team meeting with entire group prior to event.


  1. Do a Kickstarter campaign to focus enterprise assets, and do other campaigns depending on the time allotted.
  2. Do video, such as Kickstarter and other promos
  3. Crowdfund
  4. Have a 24-7 access video room.
  5. Have ancillary lessons on content from SMEs.
  6. Publish website for MOOC on the content




  1. Team of Stewards oversees ethics, distributive enterprise aspects, feasibility, collaborative and open nature of effort along the OSE Vision.
  2. All assets generated on design and enterprise are open source
  3. Anything can be edited mercilessly by anyone, with due respect.
  4. Some assets belong to OSE.
  5. We do escrow account for funding disbursement - if we don't get enough presales, we simply give it back. In a conditional sale, this is not an issue.
  6. Whoever creates something can start a business, but they must publish all assets.
  7. ALL assets are published on the wiki