Cohort Rationale: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
24 is selected as a good number of a small, platoon-size unit, and double of The 12. It can most favorably be described as 12 pairs, for engaging in 12 parallel tasks in [[Swarm Builds]] that are practiced as part of [[Extreme Manufacturing]] | 24 is selected as a good number of a small, platoon-size unit, and double of The 12. It can most favorably be described as 12 pairs, for engaging in 12 parallel tasks in [[Swarm Builds]] that are practiced as part of [[Extreme Manufacturing]] | ||
Such a team is sufficiently large that they can complete a product development project to a good state of completion (Stage 10) | Such a team is sufficiently large that they can complete a product development project to a good state of completion (Stage 10) according to the [[Stages of Product Release]]. | ||
Revision as of 23:01, 18 April 2022
You may have noticed that the Core Enterprise Module relies on cohorts of 24 people for any build project. Within 4 years - the students can be trained fully as open source design builders - understanding the design to the point that they can design for efficient builds.
24 is selected as a good number of a small, platoon-size unit, and double of The 12. It can most favorably be described as 12 pairs, for engaging in 12 parallel tasks in Swarm Builds that are practiced as part of Extreme Manufacturing
Such a team is sufficiently large that they can complete a product development project to a good state of completion (Stage 10) according to the Stages of Product Release.