We already have all what is needed for Agile, but ProjeQtOr will not force you into a way to do (and won't "help" you to select one).

In projeqtor, a sprint can be
1) an activity, that will contain acitvities (defining parent activity) : then sprint can be fully planned, in detail
2) an activity that will contain tickets (defining planning actiovity on tickets) : then spint is only globally planned through the activity, and you can control on activity that total planned work for tickets fits the planned work on activity
3) a milestone that will "contain" tickets (defining target milestone on the tickets) : then sprint is not "planned" except for a target date
4) a milstone that will "contain" requirements (defining target milestone on the tickets) : then sprint is not "planned" except for a target date
5) a product version that will "contain" either tickets and/or activities and/or requirements

So in projeqtor, a print can be an activity or a milstone or a product version, and a user story can be a ticket or an activity or a requirement
All solutions are possible and will lead to different ways to plan / manage you project.

We also propose extra plugins to ease agile management :
- Kanban boards : you can manage kanbans of activities, tickets, actions or requirements, with columns based on status or product version or planning acitvity (this plugin may includ ecommunity version next year)
- Live meeting : fitting scrum meetings with quick minutes, time recording for each speaker, ...