Software Organization

Software Organization

1. Component 1; Marketers: Try to find opportunities to provide value.

2. Component 2; Product managers: What value will the product provide.

3. Component 3: Designers: How the software will provide value.

4. Component 4; Software Engineers

5. Component 5; Sales

6. Component 6; Support

7. Each of those components or roles can be overlapped on the same person or each of them can have a designated person.

   • If they each have their own person or department, they need a proper way to communicate so that all potential value is utilized.

8. Risk: There's always risk associated with uncertain processes.

9. Communication

   • Conway's Law: Any designed system will reflect the communication structure it's builders utilized.
   • Communication models should have "Conceptual Integrity"
   • Communication to avoid: "Fight Fires", Abusive, Biased, etc.
   • Utilizing knowledge sharing tools to be effective.
   • The software development team should be able to communicate intersectionally