1. 1. Working together
2. Thriving on challenges
3. Speaking up
4. Improving relentlessly
5. Creating a trustworthy environment
Our goal to deliver comprehensive solutions to e-
marketers at hotels, hotel chains and travel websites. We
help our clients to tell compelling visually-driven stories
that reach, engage and convert today’s travel shoppers.
2. We thrive on challenge
In everyday work we face problems head-on, either from
new product design or from customer.
As our product lines grow the regression test workload
in each release cycle becomes heavier tremendously.
Instead of treating it defensively, we take offensive
approach by introducing automation test technology.
It is always a challenge to come up with a test plan that
covers up every possible scenario
It’s always challenge to meet project deadline
3. Real Story:
I was given a scenario and I had to learn how to read and
understand the data and where to get the data from, this was a time
sensitive issue, and had to be ready the same day. To overcome the
challenge, I had to read quite some documentation, I had to
execute small tests and see where the data was recorded in the QA
environment.
I was given a requirement from the client’s perspective, in order
to successfully test the improvement, I had to sit down and think of
every possibility that might happen. The challenge was to make
sure all scenarios are covered, if the scenarios can actually happen.
In order to overcome this challenge, knowing the system, asking
questions, looking at historic test plans and conferring with
colleagues.
4. We work together
• We help each other when needed
• We divide work among the team
• We give each other feedback and ways to improve
• Among QA individuals, ideas and findings are interacted
actively through HipChat communications or in person,
regardless of which scrum team they are in.
• People help each other whenever they have questions or
problems.
• Knowledge transfer is made via formal or informal way.
5. Real Story:
“During 2015.R1.1 regression test session the QA team
worked on weekend as a whole body. We supported each
other. When someone completed their part, they offered
help to others or jumped in directly to an area that were
not finished. We reached the goal altogether.”
6. We are relentless
• When designing test case we pursue full coverage of
requirements
• And we think 100% coverage is not good enough, so we go
beyond it by applying edge case, negative testing and
even error guessing
• We do critical thinking, We think outside the box
• We keep a positive mindset to keep us going when we
have a lot to do
• We don’t stop until we are finished even if it means
working after hours
• We continuously in the learning curve
7. Real Story:
“When I have a lot of tickets sent to me, there are
times when I feel I could not finish them all and more
tickets will keep piling into my queue. But, I gave my
best effort and asked for help when needed. Eventually, I
was able to clear out my queue.”
“When I got a task as part of Vizlly R1.2 release that has
a tight deadline, I worked after hours to keep on
schedule.”
8. We are trustworthy
• The team relies on each individual to finish on time
• We are trusted to do the job with our best effort
• We build long-standing relationships with
customers based on mutual respect and trust
• We are committed to delivering high quality software
• We working in a trustworthy and straightforward
manner
• Paying attention to details – not to let go any possible
vulnerable area
9. Real Story:
“When I was preparing the test suite for Vizlly sanity
testing, I got a task to create a minimum number of test
cases with maximum test coverage. I decided to ask my
colleague for a peer review of my work. The discussion
was really productive for the both of us. We exchanged
our points of view for the Vizlly sanity test suite and
found a way to make it more effective.”
10. We speak up
• We contribute our opinions/suggestions in planning
session
• We present our solutions in design process
• We exchange ideas in daily scrum meetings
• We share experience among the team members
• Raise issues or concerns, instead of keeping it to yourself
• Ask for help when needed
11. Real Story:
“Every Week in UF we have a planning and discuss what
was good and what was bad from last sprint. We cheer
when we have a lot more good stuff. We came up with
some possible solution for the bad things. Which made
the team more productive.”
