FGL - best project practices and some problems by Roman Shevtsov

Excellence inSoftware Engineering

best project practices and some problems

FGL

Excellence in Software Engineering Confidential

Company Hybris sells enterprise multichannel ecommerce and product content management software.

Used Platforms


CQ5 – CMS system, helps to organize, create and manage assets.

Used Platforms


• Members: 95 people.

• Five teams: alpha, omega, sigma, epsilon, delta.

• Team: project coordinator, 8 developers, 3 QA, BA.

• UAX team provides a design.

• + Architects, QA leads, BA leads.

Team


• Testing is based on SCRUM;

• The testing approach is based on BDD;

• Test automation is a main testing approach;

• Testing process is based on CI practice.

Test Strategy main objectives


Jira Flow

Excellence in Software Engineering Confidential 7

• Component testing

• Integration testing

• System testing

Test levels


BDD approach

BDD scheme:


BDD approach

JBehave story:


BDD approach

JBehave story implementation:


BDD approach

Thucydides reporting:


1. We are implementing a check-list (cross browser testing)

2. Person on duty(QA) is looking after CI and analyzing night auto-tests results

3. Cross functional teams(Front End+Back End CQ+Back End Hybris)

Best practices


1. Huge project, too many members, high level of bureaucracy

2. QA team is focused mainly on automation, plenty of unknown obvious bugs are not found

3. Changes of sprint backlog during the sprint

4. Poor QA coordination from Kyiv

5. Inconvenient and not transparent Jira flow

Problems


6. The sprint backlog is ready for QA review the day before sprint start.

7. BDD story files are different in Jira and test framework

8. Different work load on back-end and front end.

9. Unstable testing process: Git, branches, CI, QA, ST

10. Weak management

11. Poor BA work.

Problems


What did I miss?

Question


THANK YOU