There are a number of mistakes in your interpretation of Agile/Scrum. However, I’ll point out just a couple:
- “Scrum discourages proper design and/or consistency in the code by focusing on getting the work done as fast as possible, not on doing it properly.”
Not true! Regardless of what form of agile (or other software development practice) you are using, proper design must form a part of it. In Scrum, your story breakdown should include design discussion. If at any point the team feels that a feature doesn’t include ‘good’ design then the refactoring of it should be a Technical Debt item on the backlog that is prioritised along with new features.
- “Agile has an obsession with doing things fast.”
Also not true! Agile is just a way of delivering the same products as waterfall — not necessarily any quicker. The strength is in delivering in short increments, so that feedback can be incorporated sooner, rather than later (when the cost of change is much higher).
Having been part of Scrum teams for many years, both as a developer and as a Scrum Master, I don’t feel my creativity has ever been detrimentally impacted. In fact, Scrum (and Agile in general) should give your team more control and more freedom. If you find that isn’t the case then I suggest reaching out to a good Agile Coach to find out where you can improve.