The Scrum Guide makes it very clear that Scrum is a process framework to manage product development, but it is not a process or technique for buildingproducts. The comments below elaborate on some outside-of-Scrum aspects that can be necessary for a successful system delivery and implementation, with some references to where these are addressed in Macroscope.
The vision of the Scrum Developer is of a flexible, highly collaborative person who is keenly interested in seeing all aspects of the product. He/she is multi-disciplinary and interested in expanding their knowledge of new disciplines.
I fully appreciate that language is always evolving, and as we make up new words and definitions they become added to the dictionary.
When systems people talk about “waterfall” approaches, they mean something like the picture above.
For those who have worked with the Results Chain™ technique found in Macroscope, the most powerful justification for an investment is how it will contribute toward important business outcomes. Here’s how I’d want to use it to approach this question next time. This is a first draft of a model I could use to stimulate deeper understanding and facilitate decisions.
There are some further lines of reasoning, but this gives the main picture.
