It's hard to answer such question concretely without knowing your specific context. The first thing you should start with is asking yourself what you would like to do. I mean, if it happens that the next role on the ladder is something you're going to hate would you really pursue the promotion?
Think about your strengths, which you may exploit, and weaknesses, which would make the transition harder. Think about your potential to grow, which means you can become good in a new role.
As you've already worn different hats (you mention developer and BA) you know what kind of different roles you can think of - which of them suit you fine?
Then, there is also a context of your organization. However, in this case you shouldn't limit yourself to your organization only. Actually focusing on hierarchy of your organization only would be a mistake, as there are different companies pursuing different values out there.
Start with considering what kind of organization you'd like to be a part of. If you like your current employer, that's perfect. But be aware that different firms bring different cultures, different responsibilities and different roles. I personally know people who switched from senior management position to software engineering and their main driver was organizational culture.
Once you know what you would like to do and what kind of organization you'd like to work for you may try to think about specific roles. Unfortunately, at this point it is so heavily dependent on a specific context that it is hard to come up with details as they may differ vastly.
Remember though that the same role, say project management, in different companies can mean very different jobs.
Definitely on a list of roles you may want to consider, there are:
- Project management. You mention this one. Actually I would say that this is one of pretty common paths in big, formalized organizations.
- Product management/product ownership. Focus on product which, with your experience as a BA, you should have pretty good background for.
- People management. Leading a software development team or one of teams supporting software development process might be another idea.
- Sales. Actually best salespeople I know in software industry have roots in technical departments. Their biggest advantage: they know how things they're selling are built.
Remember that most of these roles look differently at vendor's side and at client's side and this is also an important variable in this equation.
And one more thing: sometimes an answer to a second question (where would you like to work at?) will make above definitions irrelevant. If you decide to run a startup you will be fulfilling a number of different roles simultaneously.