Please enable JavaScript.
Coggle requires JavaScript to display documents.
the concept of user acceptance and its testing methods (Siteimprove…
the concept of user acceptance
and its testing methods
user acceptance in different software methodologies
spiral/incremental: verification in increments, absolute in itself but learning phases on following increments
agile: build-measure-learn in small batches; requirements and solutions evolve in collaboration; can be extended on both ends of development (design sprints, adding UAT to sprint) >> customer centricity
waterfall/v-model: complete and absolute verification at once
test/feedback/behavior-driven development: actual developement starts with testing and measurement; acceptance is not determined/fixed!
SaaS industry
development and operations get closer together (DevOps)
different contract relationship: continious development due to changing requirements (easier to provide and push products)
combination of formative (throughout development) and summative (after development) evaluations
co-creation
user-driven design: in a firm-hosted context this would be technical/social arrangements for users to independently provide ideas and solutions (openAPI) (doesnt know user acceptance)
design thinking (user-centered): get inspired and invent future, generate and test ideas, implement and launch (knows user acceptance)
participatory design: synchronous/collaborative (users as design partners help determine product needs) or asynchronous/co-creative (designers provide solutions, users build on them as they take them into use) (temporary)
Siteimprove interviewees
CX (TESTER)
RELEASE MGMT (2)
DEV
PRODUCT OPS
SALES (TESTER)
PARTNER MGMT (TESTER)
UX
PRODUCT OWNER (2)
PARTNER OR CUSTOMER ?!?!
current status
implications on theory (so far)
the outcome changes the foundation of requirements = new reality (begriff? performativity?)
question of software ecosystems?
acceptance tests are a (hybrid between usability tests) and a legal sign off
future (developement) is not nowhere, but from somewhere
acceptance is only a temporary closure
analysis of data (so far)
goal: no more code complete nor done
doing the splits when designing for and/or with customers
forms of inclusion (testers are building ideas around or within solutions depending on if they are involved in alpha or beta phase)
silos between dev and ops
the question of desiring a happy customer
doing the splits between deflecting and opening up to release "troubles"
cultural issues in engagement of testers (what's in for them?)
method < > results
literature < > discussion
introduction < > conclusio