Extreme Enterprise Event Design: Difference between revisions
Jump to navigation
Jump to search
David Lemmer (talk | contribs) |
|||
Line 10: | Line 10: | ||
=Pre-Preparation= | =Pre-Preparation= | ||
*Initial Requirement - one page doc, can be pulled in from existing wiki assets and [[OSE Specifications]] | *Initial Requirement - one page doc, can be pulled in from existing wiki assets and [[OSE Specifications]] | ||
*High level functional requirements determined by SMEs | |||
*Functional units determined through modular decomposition [Modular decomposition strategies to be added soon] | |||
*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 | |||
* '''Goal:''' Producing documentation that describes requirements and constrain critical interfaces for each module to be developed in the XE event. Describe technical skill-sets necessary for dev-team success for each module. Fully Describe how modules will interface e.g. inputs/outputs, Connectors, Signal/language type, and all known spatial constraints. | |||
*Define [[Swarming Strategies]] for all elements of event - ie, how a swarm can divide roles and solve a task rapidly. | *Define [[Swarming Strategies]] for all elements of event - ie, how a swarm can divide roles and solve a task rapidly. | ||
*Internet search through [[Open Source Hardware Journals]] for contributors | *Internet search through [[Open Source Hardware Journals]] for contributors |
Revision as of 01:52, 6 July 2020
Internet Infrastructure
- Wiki - master Dev Template for Extreme Enterprise is synthesized from Template:Dev and Template:Enterprise plus many others of Extreme Enterprise Task Breakdown. Make this palatable on the wiki by using a well-formatted template.
- Self-managed lightweight Scrum Board for task allocation on wiki (Scrumy used to be available, now we may want to try Google Presentation as at OSE_Kanban_Board#Idea_3.2C_editable_google_drawing
Role Architecture
Pre-Preparation
- Initial Requirement - one page doc, can be pulled in from existing wiki assets and OSE Specifications
- High level functional requirements determined by SMEs
- Functional units determined through modular decomposition [Modular decomposition strategies to be added soon]
- 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
- Goal: Producing documentation that describes requirements and constrain critical interfaces for each module to be developed in the XE event. Describe technical skill-sets necessary for dev-team success for each module. Fully Describe how modules will interface e.g. inputs/outputs, Connectors, Signal/language type, and all known spatial constraints.
- Define Swarming Strategies for all elements of event - ie, how a swarm can divide roles and solve a task rapidly.
- Internet search through Open Source Hardware Journals for contributors
- Internet search for all open source interests around universities worldwide. Look for professors running projects, such as RPI autonomous tractor - that for example have software and we could add hardware. Look for specific related topics.
- Internet search through all likely venues to identify event candidates. Social media, forums, email lists, platforms (such as ArchDaily and searching for open source. EV, Electronics, Power Electronics, ESC, Hacker channels. Electric Vehicle Forums. Electronics Forums. Electronics YouTube Channels - for publicity and collaboration. Maker and DIY YouTube Channels. Hacker Forums. Hacker Platforms. Arduino Forums. 3D Printing Forums. Maker and DIY Forums. Electrical Engineering Forums. 2000 Fab Labs. 2000 Hackerspaces and Makerspaces. OSE-Related Podcasts - has an example of evaluation points on the 5-Legged Dog. OSE Related Facebook Groups. OSE-Related Reddit Groups. OSE-Related Linked-In Groups. OSE-Related Youtube Channels. OSE-Related Email Lists. Social Enterprise Channels. The above should be done across OSE Keywords.
- Create a list of crowd development sites. Hackaday, Crowd Supply, Seeed Studio, Kickstarter, Indiegogo, Tindie, SZOIL, GOSH, Open Electonics, GrabCad, HeroX, etc.
- Contact all crowd development sites/
Before
- Reach out to candidates with a short, inspiring intro email. See if they are 'interested'.
- Prepare a Media Kit on OSE, and specifically on Extreme Enterprise - to include FMI. Build upon existing Media Kits
- 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.
During
- Do a Kickstarter campaign to focus enterprise assets, and do other campaigns depending on the time allotted.
- Do video, such as Kickstarter and other promos
- Crowdfund
- Have a 24-7 access video room.
- Have ancillary lessons on content from SMEs.
- Publish website for MOOC on the content
...
After
Governance
- All assets generated on design and enterprise are open source
- Anything can be edited mercilessly by anyone, with due respect.
- Some assets belong to OSE.
- 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.
- Whoever creates something can start a business, but they must publish all assets.
- ALL assets are published on the wiki