>I did not do Sprint planning meeting and ticket estimation (Agile poker cards) because people on my team loved to argue over minutiae's and I strongly suspected half of the team didn't know the details of what the other half is working on; So instead, we had a weekly "flowchart" meeting on a large whiteboard where we brainstormed and added more details to our software project (a big data pipeline lends itself to a flowchart); I found it to be a better visualization of the project than a post-it covered poster.
Principle #5: Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
> The crux of the argument was Agile wasn't well suited for our team; the sprint model of Agile easily lends itself to arbitrary deadlines and building for the "demo" of the story/epic of that sprint and build-up of tech-debt
Principle #7: Working software is the primary measure of progress
>In the end, management relented and we ended our Agile experiment. Project tracking is done in Google Doc's with milestones instead
Principle #12: At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
Presuming that you're delivering more responsively and quickly to the customer than you were before, which you didn't mention, it sounds like you're doing just fine with Agile.