Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in the manual

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

How did dissolving the QA team enable the DevOps culture at Prezi?

Atuomated Testing Meetup, SF, 2014 May
by Gábor Török on 27 May 2014

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of How did dissolving the QA team enable the DevOps culture at Prezi?

QUALITY ASSURANCE
QUALITY ACTIONS
acceptance test framework
track bugs
level 2 support
acceptance tests for all features
track all issues
rewrite the whole
acceptance test suite
owner of jenkins
qa writes code
exploratory testing
speed-up tests
engineers
ux
pm
qa writes acceptance tests
bake quality into processes
empowerment & ownership
need for automated tests
form a team
avoid interrupting developers
faster release
raise awareness
of product quality
qa is no role but mindset
paas
why
why not
prezi engineering in numbers
why dissolving then?
s.w.a.t. team
framework and processes
best practices
you can be very agile in a small team
reflects to problems in processes
transfer knowledge
full stack engineers
quality is important for the team
establish culture and provide tool chain
Getting rid of QA team to enable DevOps culture
learnings
everyone is qa
+
go to persons
code review
coding dojos
qa roles
push back
level 2 support
issue tracking
test automation
jenkins
{
=
+
+
what is the system that allows no qa
run all tests on each code changes
feature flags
being oncall
kanban
weekly meetings
daily stand-ups
engineering friday
qa does not scale
monitoring, alerts
former qa roles
bootcamp
paas
run all tests for each commits
no blaming culture
whobrokethetests.prezi.com
who broke the tests?
it was janos
get ready: security team
spotify would call it a chapter
http://engineering.prezi.com/blog/2013/07/16/short-lived-functional-teams/
product team
startup-like teams
micro services, micro components
tech talks
Gabor Torok, @processpirate
See the full transcript