Agile & User Acceptance Testing

User Acceptance Testing (UAT) is a crucial part of the software development lifecycle for both inhouse app development and for off-the-shelf applications being integrated into existing applications. Strategic Business Decisions Consulting can bring extensive experience in software user acceptance testing to your development efforts. We bring a wealth of UAT and QA expertise to protect your investment and your reputation. We can provide experienced teams, or individuals, in quality assurance and UAT. We can design and set up quality processes and systems, undertake independent reviews, and provide training, and readiness for Inhouse UAT teams.

User Acceptance Testing (UAT) Stages

Before Testing Starts

  • Review requirements and product plan
  • Identify key engineering and business owners
  • Identify UAT team
  • Ensure that the scope is clear and agreed to
  • Verify that business requirements have been captured
  • Document acceptance criteria
  • Develop UAT test plan and validate with Business and Engineering stakeholders
  • Develop UAT Test cases and validate with Business and Engineering stakeholders
  • Develop and communicate the test plan (start, end, scope, entry and exit criteria)
  • Develop, communicate and validate test cases
  • Ensure environment is ready and there is access to the environment
  • Develop test execution timeline and roles
  • Project kick off and kick off communications

During Testing

  • Kick-off the user acceptance Testing project
  • Define detailed test schedule to achieve achieve test pass results
  • Ensure the test log is kept up to date
  • Identify defects, file bugs, and review in bug triage meeting with Engineering stakeholders
  • Report bugs in a timely manner
  • Attend regular (daily) bug triage with Engineering stakeholders
  • Assign resolution time to bugs and review resolution of the bugs daily
  • Provide daily and weekly status report to all stakeholders
  • Go-No-go for release decision
  • Post Mortem after UAT completion

Go-No-Go Decision

  • Determine status against acceptance criteria
  • Report status to key stakeholders with options for the release

After UAT Completion

  • Conduct post mortem
  • Associate learnings and defects into planning for next phase of testing
  • Prepare readiness documentation

In conclusion, the goal of User Acceptance Testing is to ensure that customers will not have surprises when the product is released to market and the product will not require excessive support calls due to defects.


User stories are complete only after the experiences are tested from end to end and pass all defined acceptance tests. Our approach involves defining, designing and executing acceptance tests, identification of defects, or bugs, bug-tracking, bug triage, bug management, and managing defect backlog to manage release timeline, reduce lead time, manage cycle times, deliver technical features, and support defect resolution.


As companies drive towards a digital business model, they must understand and eliminate pain-points at key moments of truth for the customer and design and deploy delightful customer experiences. Businesses must define requirements to drive customer value from their digital value proposition and enable experiences through digital channels that drive revenue.


Agile brings collaboration and cross-functional team work on evolving requirements, ongoing reviews and rapid delivery of high quality of software. Agile sprint cycles align data integration, requirements and deliverables. An integrated schedule generates awareness of project progress within the PMO and identifies key dependencies between projects in the program. Use of development cycles or sprints maximizes the team’s productive time. It gets priority work done through definition of roles, use of artifacts, and time management. Teams significantly increase productivity and reduce time to results through clear roles, conducting daily Scrum, defining user stories, using Kan Ban prioritization, managing sprint backlog, and use of burn down and burn up charts. Dev Ops brings together the practices of development and operations to create value through people, process, and technology. Teams tend to function in stovepipes if left to their own devices and DevOps brings tools and methodologies to facilitate the collaboration between teams so they can better understand customer needs and experiences and deliver the software with fewer defects and faster time to market.