If you mean no scrum, simple, no card wall, tasks are epics, trust people to know what to do and let them do it. Help people when needed.
The board is far from only agile practice and nit obligatory either. Even Epic sounds like an agile term.
Even modified waterfall seems to be described as agile.
As a sole developer of a software product, I haven't figured out how the agile principles even apply to me.
"Individuals and interactions over processes and tools" doesn't work when there's only one person.
"Working software over comprehensive documentation" Does that mean ship code but don't provide comprehensive documentation to my users? No, it means internal process documentation. Which isn't applicable since it's just me.
"Customer collaboration over contract negotiation". That only applies for contract software development. I sell a software product.
"Responding to change over following a plan". I don't have much of a plan, so I guess I do this one. But I do have a long-term vision, since that's essential to figuring out what groundwork to have.
Personally, I learned RAD (rapid application development) when I was a young programmer back in the 1990s, and that's what I still use.
The software vendor sells a software product, not the developer.
Assuming your definition makes sense, what are the "interactions ... processes and tools" between me-the-vendor and me-the-developer?
What is the comprehensive documentation that I'm supposed to avoid?
What is the contract negotiation?
Since it's clear to you, perhaps you can clarify how the Agile Manifesto applies to software product sales when there's a single developer and once-per-year product cycles?
But if "a process" is all that's needed to be Agile then waterfall is Agile.
Why not once a year? Does Agile require a higher delivery frequency than that?
That is, how is your question relevant to the topic?
Yeah, that's what Agile seems to mean to most people. Courtiers to the Emperor, praising the new clothes none can see.
Scrum reminds me of the old adage about measuring a beach, you can measure it by sight, or by using a yardstick, or by counting grains of sand in a row. Scrum sits too close to counting sand, I prefer to be at the yardstick level.
There is an idiocy to scrum that involves/wastes the whole team on simple planning tasks that could be more effectively done by a single person. This is compounded with practices like mobbing… It removes craft from software and just makes it lowest common denominator.
Agile manifesto is still great and relevant. But that’s not what people mean when they say Agile