Articles

Scrum and Architecture

| |

I am currently trying to find my way as an architect on a Scrum team, and I am finding it pretty difficult. I feel that, Scrum by itself largely focusses on 'what' needs to be build, expecting the 'how' to somehow magically happen by itself. Worse, software customers tend to focus on concrete, visible functionality, often expecting quality (performance, robustness, modifiability, etc.) to be implicitly handled by a ‘good’ development team. If these quality aspects are not part of the process somehow, it becomes a challenge giving them sufficient attention. Unfortunately, there are always lots of ways some functionality can be realised, but only a few that all stakeholders will be happy with in the long run. 


Syndicate content