My work with
the NADA team.

Checking the conversation order

During app testing, I noticed that the conversation list placed older conversations above recently active ones. The expected behavior was for the most recently active conversation to appear first.

1. 01

   Document the issue

   I recorded the actual and expected results in our shared QA sheet, added screenshots, and notified my supervisor.

2. 02

   Check other accounts

   We repeated the check using different accounts and confirmed the behavior affected more than mine.

3. 03

   Review with developers

   I arranged a meeting so we could demonstrate the issue and clarify what needed correcting.

4. 04

   Retest the fix

   After developers reported a fix, we checked the app again, confirmed the ordering was correct, and updated the QA record.

Result: Retesting confirmed that the reported ordering issue was resolved.

The developers implemented the code change. My contribution was testing, documentation, coordination, and verification.

Keeping Jira current

During and after meetings, I worked with the senior product manager to create tasks, assign the responsible team members, and add deadlines.

When a task was delayed, I followed up under his direction to clarify what the task owner needed. Sometimes work was waiting for a new app update. I reported the information back and updated Jira; the senior product manager sometimes made the record updates himself.

Organizing documents and checking the handoff

I organized project files in designated Google Drive folders, restricted access to myself and my supervisor, and shared documents with others when he authorized it.

For the external development team’s handoff, my supervisor supplied a checklist. I attended the handoff meeting, collected source code, access information, and technical documents, checked receipt against the list, and confirmed with him.

I checked that the requested materials had been received and confirmed that with my supervisor.