Skip to main content

Table 5 Change strategies for software organizations

From: Future software organizations – agile goals and roles

Goals Means NEEDS for Software Competences and Resources / Roles
• If you are a big company: How to make your structures lightweight, and increase flow through the system? By fluidity:
• Decouple product architectures and teams.
• Reduce organizational layers and move to flat organization(s).
• Brake new product / service initiatives into smaller chunks (e.g., microservices).
• Develop using smaller batches.
• Flexibility in software systems architecture and organization design
• Feature teams, cross-functional teams
• Unanimous prioritization of work
• If you are a traditional company: Understand the opportunities of cost reduction and innovation By adaptability:
• With the use of software
• With modularity and cross-use of components / systems of systems
• With integration of new software capabilities into existing systems
• Software-based value determination, software as the key enabling technology (KET)
• Enlarging to new software-enabled business opportunities, new markets, new areas / technologies
• Forming new alliances / co-operation (e.g., with software houses
• In ecosystem (digital economy): By flexibility:
• Build and streamline value streams for cost efficiency and new value.
• Create efficient subcontracting and supplier networks.
• Determine the (software) platform strategy (create platforms and/ or use available ones).
• Data systems (e.g., big data, APIs)
• Value co-creation based on software core assets
• Value creations based on wide offering (ecosystem)
• Value creations through better software-based service (customization, predicting service interval, informatics, accumulated data from system or users) with value networks