Timeframe: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 12: | Line 12: | ||
*2021 management structure in place, team structures tested | *2021 management structure in place, team structures tested | ||
*2020 mirrorswarm.com registered, planning starts. | *2020 mirrorswarm.com registered, planning starts. | ||
== Strategy == | |||
*An emergent team structure driven by the progressive analysis of the requirement. | *An emergent team structure driven by the progressive analysis of the requirement. | ||
*A long-term management structure aimed at retaining command control of the swarm to oversee compliance with the constraints. | *A long-term management structure aimed at retaining command control of the swarm to oversee compliance with the constraints. | ||
*Get it working on paper before anyone takes out a screwdriver. | *Get it working on paper before anyone takes out a screwdriver. | ||
Revision as of 23:51, 2 January 2020
Kurzgesagt says the exponential phase of mirror deployment can be accomplished over a ten year period, so. Let's work backwards.
- 2040 deployment complete, mirror swarm online and sending at full power.
- 2030 deployment started, deployment test phase begins.
- 2029 sponsored launch.
- 2027 plans finalized, sponsors in place, product assembly begins.
- 2026
- 2025 unit testing started
- 2024
- 2023
- 2022
- 2021 management structure in place, team structures tested
- 2020 mirrorswarm.com registered, planning starts.
Strategy
- An emergent team structure driven by the progressive analysis of the requirement.
- A long-term management structure aimed at retaining command control of the swarm to oversee compliance with the constraints.
- Get it working on paper before anyone takes out a screwdriver.