Top Menu

Jump to content
Home
    • Projects
    • Work packages
    • News
    • Getting started
    • Introduction video
      Welcome to Government of Rwanda Projects
      Get a quick overview of project management and team collaboration with OpenProject. You can restart this video from the help menu.
    • Help and support
    • Upgrade to Enterprise edition
    • User guides
    • Videos
    • Shortcuts
    • Community forum
    • Professional support
    • Additional resources
    • Data privacy and security policy
    • Digital accessibility (DE)
    • OpenProject website
    • Security alerts / Newsletter
    • OpenProject blog
    • Release notes
    • Report a bug
    • Development roadmap
    • Add and edit translations
    • API documentation
  • Sign in
      Forgot your password?

Side Menu

  • Overview
  • Activity
  • Work packages
  • Boards
  • Project library
    • Table of contents
      • Expanded. Click to collapseCollapsed. Click to showProject library
        • Expanded. Click to collapseCollapsed. Click to show00 Scope
          • Hierarchy leaf00 Project charter (empty)
        • Expanded. Click to collapseCollapsed. Click to show10 Requirements
          • Hierarchy leaf00 Requirements assessment
          • Hierarchy leaf10 Requirements traceability matrix
        • Expanded. Click to collapseCollapsed. Click to show20 Stakeholders & Communication
          • Hierarchy leaf00 Stakeholder analysis (empty)
          • Hierarchy leaf10 Communication plan
        • Hierarchy leaf30 Team & Resources
        • Hierarchy leaf40 Architecture
        • Hierarchy leaf50 Reporting
        • Hierarchy leaf60 Risks (empty)
        • Hierarchy leaf70 Contract Documents
        • Expanded. Click to collapseCollapsed. Click to show80 Deliverables
          • Hierarchy leafSome deliverable
        • Expanded. Click to collapseCollapsed. Click to show90 templates
          • Hierarchy leaf010 project charter
          • Hierarchy leaf020 reporting template
          • Hierarchy leaf030 Default ToR for Government of Rwanda IT projects
        • Expanded. Click to collapseCollapsed. Click to show95 Standards & Processes
          • Expanded. Click to collapseCollapsed. Click to show00 PM methodology at RISA
            • Hierarchy leafMeeting Structure
          • Hierarchy leaf01 Standards for the "Definition of Done" (DoD)
          • Hierarchy leaf04 Severity of Incidents
          • Hierarchy leaf05 Acceptance procedure
          • Hierarchy leaf10 Architecture principles
          • Hierarchy leaf20 Service Digitization Guideline
          • Hierarchy leaf30 Service request process
          • Hierarchy leaf40 Test Management
          • Hierarchy leaf50 Version Managment
          • Hierarchy leaf60 CI/CD
          • Hierarchy leaf70 Contract Management
You are here:
  • Project library
  • 95 Standards & Processes
  • 05 Acceptance procedure

Content

05 Acceptance procedure

  • More
    • Print
    • Table of contents

latest version of this document always under:

https://projectmanagement.risa.rw/projects/risa-template-scrum/wiki/05-acceptance-procedure

All deliverables which are part of a fixed price solution shall be accepted by a formal acceptance procedure aka “user acceptance test”. The set of the tests will be mutually agreed during the project phase. They are mainly a subset of the vendors functional end-to-end-tests but can be extended by RISA with own test cases. All test cases have to be based on the described scenarios and the scenario requirements only. Each iteration finishes with an acceptance of the deliverables of this iteration.

Severity of failed test results

Failing test results will be classified with the following severities:

  • (1) Critical:
    • Failing test critically affects the primary business service, major application or function
    • Characteristics of a Severity 1 case include but are not limited to:
      • Business service or function is not operational
      • Production system crashes
      • Data integrity at risk
      • Production backup and recovery operations fails
  • (2) Major:
    • The business service, major application, function, or system is seriously affected
    • No acceptable workaround is available
    • Documentation not available
  • (3) Medium:
    • The business service, major application, function or system is moderately impacted
    • No data has been lost
    • The business service, application, or system is still functioning
    • Documentation needs explanation
    • The case may be temporarily circumvented using an available workaround
  • (4) Minor:
    • Non-critical cases
    • Minor documentation cases
  • (5) Enhancements:
    • Enhancement requests

Acceptance criteria

Acceptance shall be granted as per the following criteria:

Deliverable Acceptance criteria
Solution as per scenario 1,2,3

User acceptance test with not more than:

  • 0 (zero) critical test fails
  • 0 (zero) major test fails
  • 3 (three) medium test fails
Training as per scenario 1,2,3 Training as per mutually agreed training plan
Licenses Licenses purchased as mutually agreed and proposed
Solution design as per scenario 4 No formal acceptance needed, delivered as service contract
Additional requirements (as per severity 5) No formal acceptance needed, delivered as service contract
Loading...