...

Well managed projects are always driven by:
key roles ( sponsors, beneficiaries, users etc ), clear use cases, clear objectives, scope, resourcing, system boundaries, stakeholder management and dependency management across all 3 domains: business, project and technical.

In addtion to the listed PM concepts to manage Agile projects:

It's important to understand all stakeholders views on the current solution and their roles and views on the new solution to manage expectations effectively throughout the project.

Prepare for success following the VCRS method ( Value, Costs, Right, Success ) for all stakeholder groups

The common PM concepts all make sense for to manage Agile projects:

1. to embrace change in a controlled manner in projects
2. increase learning across teams
3. provide good collaboration opportunities
4. use the sprints as improvement opportunities with plan, deliver, review and retrospective steps

prepare for success following VCRSOther considerations to deliver a quality solution:

A few key business solution architecture concepts that apply to the project scope should be reviewed for the key use cases in scope:

1. NFR - what are the key non-functional requirements for the project / solution?
2. RAS - who do you define specific test cases for reliability, service, availability?
3. KPIs - what are the key performance indicators in scope for operations & support of the production solution?
4. tools - does the target production environment provide the right observability, management tools to operate effectively?
5. what is the ongoing change management model for the solution including learning and onboarding new resources?
6. Failure and integration scenarios: ask the right questions on potential failure scenarios and their criticality, frequence using any good data

Potential Value Opportunities

...