Swarming Strategies: Difference between revisions

Revision as of 23:51, 23 June 2020

Swarming Strategies should be developed for all major phases of product, assuming parallel development within swarms and between swarms.

Website Swarming Strategy - how to handle dozens of people collaborating realtime on the website
Design Swarming - how to handle dozens or hundreds of people in technical design
Prototyping Swarming - how to produce prototypes within minutes or hours of design completion
Documentation Swarming - how to document substance within hours of all content being available.
Testing Swarming - how to swarm on product tests so a result is obtained within an hour of obtaining substance for testing.
Legal Swarming - how to write up all the legal contracts, terms, licenses involved in the product
Distribution Swarming - how to swarm efforts on developing distribution channels
Marketing Swarming - how to develop a detailed, executable ste-by-step plan for doing marketing
Business Plan Swarming - how to produce a detailed and executable business plan in hours.
Process Swarming - How to swarm on developing the development process by the scrum masters/managers on the team. Includes how to keep track of all iterations so that versions aren't mixed up when a Tech Tree of Choices is being evaluated.

@@ Line 10: / Line 10: @@
 #[[Marketing Swarming]] - how to develop a detailed, executable ste-by-step plan for doing marketing
 #[[Business Plan Swarming]] - how to produce a detailed and executable business plan in hours.
-#[[Iteration Swarming]] - how to keep track of all iterations so that versions aren't mixed up when a [[Tech Tree of Choices]] is being evaluated.
+#[[Process Swarming]] - How to swarm on developing the development process by the scrum masters/managers on the team. Includes how to keep track of all iterations so that versions aren't mixed up when a [[Tech Tree of Choices]] is being evaluated.