Best practice to ensure user stories are "ready" for development to start work. Each story has the correct acceptance criteria. Gathering, management and prioritization of the product backlog. Close collaboration with development teams.

Best practice to elicit (research and discover) requirements. Development of functional requirements and ensure the requirements are fully understood and communicated with the stakeholders.

Best practice of processes, methods, skills, knowledge and experience to archive project objectives according to acceptance criteria. All in line with finite timeline and budget.

Best practice of implementing mechanisms in the construction of software to help it remain functional (or resistant) to attacks. Covering infrastructure as well as security testing practices.

Best practice to expose the structure of a system while hiding implementation details. It focusses on how the elements and components within a system interact with each other.

Best practice to oversee all activities and tasks that must be accomplished to maintain a desired level of excellence. Covering manual and automated testing processes.