QA processes in MeriVal Proposal of new service from Luxoft Krakow ODC

1. QA processes in MeriVal Proposal of new service from Luxoft Krakow ODC

Last update 24 Oct 2016
www.luxoft.com

2. Agenda

The highlights of our presentation
“As Is” QA processes overview and ways to
improve.
Proposed best QA practices.
Detailed description of artefacts and “To Be” state
www.luxoft.com

3. “AS IS” QA processes

Why there are still some things to improve in QA Processes in MeriVal
project?
Because of 3 reasons:
Low feedback from Development and BA teams about collaboration with
QA
QA best practices may be recommended
Some defects revealed on a late stage and could bring additional efforts
to project
We believe that the service, we could recommend :
Provide Quality Assurance test coverage
analysis for business-critical tasks.
www.luxoft.com

4. “AS IS” QA processes. Low feedback from Development and BA teams.

Feedback representation in graphic view
BA and Dev team members:
Test coverage
From 81% to
100%
From 61% to
80%
From 41% to
60%
From 21% to
40%
From 0% to 20%
No answer
www.luxoft.com
Satisfaction from test time
delivery
Marks for speed of tests
5- Excellent
4- Good
3 - Satisfied
2 - Not satisfied
1 - Very bad
No answer

5. “AS IS” QA processes. QA best practices may be recommended.

Proposed instruments and techniques
Create workflow diagram to identify possible flows of tested project
Create Traceability matrix for PPs
Apply test design techniques to optimize efforts for detecting
potential defects
Create or Update test cases in accordance with priorities of business
requirements
Krakow BA team ready to provide QA analyst service if they will have
free analysts. They could be a bridge between BA –QA and Dev-QA
teams in same time
www.luxoft.com

6. “AS IS” QA processes. Defects revealed on a late stage.

Will save total efforts spent by the team
AS IS process for defects revealed on late
stages
TO BE
process for defects revealed on late
stages
1. BA Phase (Test Prioritized, test
1. BA Phase (NO priorities, test coverage -?)
2. QA and Dev Phases (Tests are written as much coverage well known)
as possible)
2. QA and Dev Phases (Tests cover all
3. UAT phase (Defects detected and discussed
critical scenarios, new QA approach
with BA/Business)
applied )
4. Planning phase (Fixes estimated)
5. BA Phase (Test coverage is good)
6. QA and Dev Phases (Necessary tests
implemented)
7. UAT phase (Changes verified and applied)
Results: Time between start working over
requirements and correct implementation = 2
Quarters
www.luxoft.com
3. UAT phase (Remarks received and
implemented)
Results: Time between start working
over requirements and correct
implementation = 1 Quarter

7. “AS IS” QA processes. Defects revealed on a late stage.

Example of defects statistics (for 20 Sep 2016) for Q3
By defect Type
Functional
Failure
23%
48%
25%
By defect Severity
1%
3%
13%
Performance
Issue
Critical
High
Medium
By defect Status
13%
2%
Technical
Failure
83%
Around 72% of total defects may be found earlier
www.luxoft.com
Resolved
Deferred
Low
Specification
5%
Closed
85%

8. Proposed QA practices. QA analyst service in Krakow

Benefits if QA Analysts will work in the same location with BA and DEV
team
Save efforts on communication between teams:
­
There are no phones in Indian location, no lync audio in Krakow
­
Same time zone with BA/DEV to conduct a meetings
­
Less efforts working with documentation
No culture difference between QA Analysts and other team
members
Possability to focus BA on detalization of requirements.
Responsibilities of QA analysts and BA are partly the same. Some
QA Analysts could replace BAs.
Easy to control and avoid any bad practicies (copy paste E2E tests,
technical issues)
www.luxoft.com

9. Proposed best QA practice. Our expectations

What could we expect after applying new approach(QA analyst service)?
Increase Krakow QA Analyst Team with
3 Test Analysts for 6 months
Link them to most critical PP
Gather feedback from all(Management,
QA, BA and Dev)
If feedback will be great, leave QA
Analyst team on a permanent basis
www.luxoft.com
It will allow to measure test coverage
and improve estimation of BA and QA
efforts
It will allow on early stages provide test
analysis of req
Feedback should show, that our
process become more predictable and
covers algorithms of critical PP with
better QA tests

10. QA artefacts. Workflow diagram.

Start
Action 1
Create workflow diagram to
identify possible flows of tested
project:
Flow coverage = (Covered
flows/all possible flows)*100%
Action 2
Condition
1
Conditi
on 2
Action 4
Action 3
Condition
3
Action 5
Action 4
Condition 5
Action 6
End
www.luxoft.com

11. QA artefacts. Traceability matrix

It is required to create traceability
matrix that will help to control gaps of
testing coverage on each level.
Create/Update E2E/component tests
regarding to the priorities of tested
requirements.
www.luxoft.com

12. QA artefacts. Internal Jira defect issues.

From Luxoft DM side
www.luxoft.com

13. THANK YOU

www.luxoft.com