I think it is wrong to look for "true agile", as it's not a set of checkboxes to fill. I agree with other comments that sprints, backlogs, etc. are just tools to pick from based on the problems you're facing. You see them proposed time and again because many organizations face the same, boring problems as everyone.
To me, the only one true principle of Agile is to:
- Always take time to reflect on the way you and your team work
- Discuss openly if it's appropriate or not
- Be ready to accept ANY solution that is discussed, be it organizational, technical, or self-improvement.
I would even go as far as calling it a basic principle of engineering. It is very simple to state, but very hard to implement due to our human nature (ego and feelings get in the way of open discussion and self-change) and budgets (taking time to discuss and implement change feels like a cost to most management, not added value).
There were examples of this principle and mindset in many organizations long before Agile was codified, and it can actually cause valuable results in organizations that look nothing like the stereotype of Agile !
For example, the NASA software department was famous for stopping all developments any time their QA detected any bug, and taking the time needed to ensure this kind of bug can never be committed again in the future. This kind of behavior is extremely Agile to me : continually improving your process to match your requirements. It is very slow and expensive for them, but it matches the stakes (potential loss of lives).
It doesn't capture every keystroke in the system, those sent to an elevated window are not sent to the low-level hook: https://stackoverflow.com/q/52696285
This fits with the security model of Windows, and PCs in general. Processes from the same user can see and interact with each other, but not with those of another user. Users are expected not to run any process from shady vendors.
This might seem lightweight security in the age of too much internet where everyone runs anything, but it is what enables some kind of openness and control on those platforms, vs. the very controlled interfaces of smartphones.
For all its complexity, it's actually pretty much relaxing and autopilot once you've crossed a few hundred hours.