I'm new to Agile as a methodology, although I believe a have a basic grasp on its principles.
My team is currently building a framework that will support our client's application in the future. As an input, we have a bunch of requirements and even a suggestion of how the application should be implemented, at a VERY high level.
As an approach, we decided to use some sprints to understand the requirements before actually build the system. Our output is more documents describing the system to be build.
After the first sprint I started to question whether this isn't violating Agile principles, since our output (documents) aren't testable or a goal of the project in itself, only intermediary byproducts.