In the context of Agile Project Management when developing the Prioritised Requirements List during Feasibility, the two statements that align with Agile principles are:
B; The re-laying of the driveway and a landscaping solution should be listed as Must Have requirements.
E: Regulatory obligations associated with the redevelopment of Hoy Hall should be recorded as Must Have requirements.
Here's the rationale:
*B: In Agile, requirements are often categorized by priority such as "Must Have", "Should Have", "Could Have", and "Won't Have for now" (the MoSCoW method). The re-laying of the driveway and a landscaping solution are essential for the project's success and thus should be classified as "Must Have".
*E: Regulatory requirements are non-negotiable constraints that the project must adhere to. These should always be prioritized in the requirements list to ensure compliance and to avoid legal issues, making them
"Must Have" items as well.