Table 3 General issues
Old solution | New solution |
|---|---|
Communication and interaction are strongly documentation based also within the development organisation | Rotating staff between SPL platform and release concept planning and between release concept planning and development phases increases willingness to share knowledge and reduces conflicts |
The old ways of working do not support co-learning and distributing best practices | The communicative roles of release manager, ScrumMaster and team architects. The system inspection group and the architecture support group |
Projects do not have chief designer level expertise | The role of team architect |
Project management is based on the conventional specification-planning-execution-control cycle | Project management emphasises adaptation and value generation |
Description of a system product includes all the relevant interfaces and relevant sub-systems | System structure document describes also alternatives, possibilities, limitations and boundary conditions set by SPL platform for ASD |
Important system structure elements are identified as system architecture features for the release backlog | |
Architecture guidelines aim to ensure that projects develop generic solutions, not project-specific or overlapping solutions | Architectural guidelines document includes recommendations for release sprints for forming project teams and for planning content and schedules |
To minimise cross-team and cross-project communication problems, the document defines their roles and identifies interfaces for different software components | |
The guidelines define and recognise independent modules and architectures for releases, utilising either existing or potentially new solutions | |
Documentation is expected to be perfect and changing it is considered as a matter of authority | ASD embraces changing requirements |
Those preparing architectural guidelines do not enforce them. Realisation may differ from guidelines | Project teams consult all team architects when encountering problems while adopting system structure, software architecture descriptions and architectural guidelines |