We face lots of often fierce and confusing debates about architectural work - not only in the agile community. But while all the people endlessly argue about the what, how, when and how much, they forget to ask the most important question: Why?
Why are we doing architectural work in the first place? What is its purpose? Answering this question would render more than 90% of all the debates pointless.
After a short introduction, this slide deck offers three different complementing point of view why we need architectural work, what its purpose is - or at least should be. These points of view can be used to determine if suggested architectural activities really add to the purpose of software architecture or if they are just habits, opinions or beliefs.
As always, the voice track is missing (which can be a bit tricky especially for the third perspective because the accompanying slides consist just of a single quote). Nevertheless, I hope it contains some useful ideas for you.