The global skills and competency framework for the digital world

User acceptance testing BPTS

Validating systems, products, business processes or services to determine whether the acceptance criteria have been satisfied.

Revision notes

Updates for SFIA 9

  • Theme(s) influencing the updates for this skill: Making SFIA easier to consume (enhance readability/guidance/descriptions), Making SFIA easier to consume (updates to skill name/skill description).
  • Skill renamed to aid understanding of the scope of this skill
  • Content and/or readability changes have been made to levels 5 and 6.
  • You can move to SFIA 9 when you are ready - SFIA 8 skill descriptions will still be available to use.
  • Previous SFIA assessments or skills mapping are not impacted by this change.

Guidance notes

Activities include, but are not limited to:

  • setting and applying standards for user acceptance testing (UAT)
  • planning, identifying, designing, managing, executing and reporting on the outcomes of acceptance tests
  • collaborating with a range of relevant stakeholders
  • defining clear entry and exit criteria for UAT
  • requesting and enabling formal acceptance of systems, products or services
  • creating measurable acceptance criteria related to functional and non-functional requirements, features, business processes, user stories and business rules
  • devising test cases and scenarios from acceptance criteria
  • enabling exploratory testing to discover unexpected behaviours
  • deploying model office testing to simulate real-world usage
  • ensuring appropriate training for users involved in UAT
  • providing input on UAT resource requirements, including necessary skills and availability.

The acceptance testing approach will be based on the context of the work and may be selected from predictive (plan-driven) or adaptive (iterative/agile) approaches.

Understanding the responsibility levels of this skill

Where lower levels are not defined...
  • Specific tasks and responsibilities are not defined because the skill requires a higher level of autonomy, influence, and complexity in decision-making than is typically expected at these levels. You can use the essence statements to understand the generic responsibilities associated with these levels.
Where higher levels are not defined...
  • Responsibilities and accountabilities are not defined because these higher levels involve strategic leadership and broader organisational influence that goes beyond the scope of this specific skill. See the essence statements.

Developing skills and demonstrating responsibilities related to this skill

The defined levels show the incremental progression in skills and responsibilities.

Where lower levels are not defined...

You can develop your knowledge and support others who do have responsibility in this area by:

  • Learning key concepts and principles related to this skill and its impact on your role
  • Performing related skills (see the related SFIA skills)
  • Supporting others who are performing higher level tasks and activities
Where higher levels are not defined...
  • You can progress by developing related skills which are better suited to higher levels of organisational leadership.

Show/hide extra descriptions and levels.

Levels of responsibility for this skill

2 3 4 5 6

User acceptance testing: Level 2

Level 2 - Assist: Essence of the level: Provides assistance to others, works under routine supervision, and uses their discretion to address routine problems. Actively learns through training and on-the-job experiences.

Assists in planning and preparing acceptance tests for systems, products, business processes or services.

Assists in collecting feedback from acceptance testing.

User acceptance testing: Level 3

Level 3 - Apply: Essence of the level: Performs varied tasks, sometimes complex and non-routine, using standard methods and procedures. Works under general direction, exercises discretion, and manages own work within deadlines. Proactively enhances skills and impact in the workplace.

Follows agreed standards and techniques to devise test cases and scenarios based on pre-defined acceptance criteria.

Analyses and reports on test activities, results, issues and risks.

User acceptance testing: Level 4

Level 4 - Enable: Essence of the level: Performs diverse complex activities, supports and guides others, delegates tasks when appropriate, works autonomously under general direction, and contributes expertise to deliver team objectives.

Develops acceptance criteria related to functional and non-functional requirements, business processes, features, user stories and business rules.

Designs and specifies test cases and scenarios to test that systems, products and services fulfil the acceptance criteria and deliver the predicted business benefits.

Collaborates with project colleagues and stakeholders involved in the analysis, development and operation of products, systems or services to ensure accuracy and comprehensive test coverage.

Analyses and reports on test activities, results, issues and risks including the work of others.

User acceptance testing: Level 5

Level 5 - Ensure, advise: Essence of the level: Provides authoritative guidance in their field and works under broad direction. Accountable for delivering significant work outcomes, from analysis through execution to evaluation.

Plans and manages user acceptance testing activity.

Specifies the testing environment. Manages the creation of test cases and scenarios, ensuring they reflect realistic operational conditions and coverage needs.

Ensures entry and exit criteria are set and met before user acceptance testing starts or ends. Specifies required user resources. Ensures users receive appropriate training and support.

Ensures tests and results are documented, analysed and reported, highlighting issues and risks to stakeholders. Provides authoritative advice on acceptance testing planning and execution.

User acceptance testing: Level 6

Level 6 - Initiate, influence: Essence of the level: Has significant organisational influence, makes high-level decisions, shapes policies, demonstrates leadership, promotes organisational collaboration, and accepts accountability in key areas.

Leads the organisation's approach to user acceptance testing.

Engages senior stakeholders to secure organisational commitment and resources for effective acceptance testing.

Integrates entry and exit criteria into user acceptance testing planning and execution. Provides input on required resources, including skills and availability, for user acceptance testing activities. Reports on any significant risks and issues, recommending actions as needed.

Develops organisational policies, standards and guidelines for acceptance testing. Develops acceptance testing capabilities and methods for the organisation.

Keywords
Small change Re-named