Team Leads/Experts

Anju Kurup
Fasiullah(Drivers Pay)

Shraddha Agrawal PQL

Shreya Joshi
Rishi Khandelwal CAST/CART advocate

Ruchita Bhatane
Naveen
Gaurav Gawade

Phanidranath Orruganti

Swetank Rupesh Kumar

Debabrata Pal

Gaurav Agarwal
Falguni/Arun (Love Shares)
Neha Patil

Rajani Nelluri

Kalpana Timmapuram
Sradhanjali Khadanga

A, Kaarthik
John Kenady Madda
Aarti Parab
 Shreya Joshi Phanidranath Orruganti

Fasiullah Naveen

Rupesh Kumar Falguni Dedhia

Phanidranath Orruganti Debabrata Pal

 Guidelines
• Team leads :
– REVIEWS (TSD/TUT/DEG) & Code (CDR)
– Testing
– Resolve Bottle Necks
– Issue log – review/upload & send me the link.
• Aarti & John to test the scenarios & provide data. (Objects
have to be evenly distributed)
• After confirmation from each level the code will be
delivered to Onsite.
• Swetank reviews/test after confirmation from Aarti/John &
Team leads.
• Code should be checked for ATC, SLIN, CI, & CART
• Code should follow naming conventions
 Guidelines…
• TUT scenarios should be verified against FSD
• Swetank or Sarah should be involved in meetings with
Onsite functional team
• Any issue or bottlenecks should be first addressed to
team leads/experts.
• Any delays in object deliveries should have a valid &
strong justifications.
• Follow-up on issue logs should be promptly done by
developers.
• Request for test data should be done in advance & not
when you start testing.
 Guidelines…
• No assumptions should be made during
development, clarify everything & follow FSD.
• FSD reviews with functional team member
should be conducted before development
starts.
• During these FSD reviews, test case scenarios
should be discussed and added to the SSD for
cases when the SSD does not have detailed
test case scenarios.
 Guidelines…
• FUT or defects raised by onsite has to follow process (will
be explained)
• Incorporate only valid fixes & minor changes.
• Any functionality change should be immediately
communicated to Swetank and Sarah (for change request)
• Any change which can take more then 2-3 hours should be
immediately communicated to Swetank and Sarah
• Retest SHOULD be done for all scenarios after FUT fixes.
• TUT document should be updated during retests.
• TUT document should reflect the most recent testing
results