FiscalSystems-RETL (ERP) Project Weekly Status Call
Action Items
Contact James about adding additional QA resource to project
Talk to James and send email about adding a second QA resource to assist with testing workload, as the current single QA resource is overwhelmed with multiple concurrent module releases.
Create Excel sheet for tracking QA feedback across releases
Create an Excel spreadsheet with separate tabs for each QA release (QA1, QA2, QA3, etc.) to track and organize feedback points, including summaries where possible to avoid losing information in emails.
Address feedback communication process with UI/UX team
Prioritize discussion with UI/UX team about improving communication back to Lawrence and Manisha regarding their feedback on development calls, ensuring they receive responses about what changes will or won't be implemented.
Provide workflows for all completed modules
Share process flows and workflows for all completed modules by next week to help Lawrence and Manisha understand module functionality, including where processes start, end, and how pages connect.
Update project plan with current status
Update and share the project plan by next week showing what has been completed, what is currently in progress, and what is pending for phase one completion by October trade show.

Overview

    Lawrence agreed to request an additional QA resource from James to support the overwhelmed single QA person currently handling 4-5 modules concurrently
    Chetu committed to provide process workflows and updated project status by August 22nd, 2025 to clarify what's completing in phase one by the October trade show deadline
    Manisha highlighted major UI usability issues where editing requires 5-6 minutes for 2-3 fields due to page closing after each update
    Shankar agreed to fix UI/UX feedback communication gaps where suggestions aren't being addressed or communicated back to Fiscal Systems

Additional QA resource request

    Shankar explained their single QA resource is overwhelmed with 4-5 modules releasing concurrently as phase one nears completion
    Lawrence agreed to email James immediately to request a second QA person, expecting response by August 22nd, 2025
    Chetu plans to split QA work with one person focused on regression testing and another on new feature testing
    Lawrence noted the current setup leaves no coverage for sick days or breaks

Process workflow documentation needs

    Manisha requested process flows for each module showing start-to-end functionality and page connections
    Fiscal Systems currently tests based on assumptions without knowing module workflows or interdependencies
    Shankar committed to provide workflows for all completed modules and updated project status by August 22nd, 2025
    Manisha needs this information to update internal teams and James on phase one completion scope

User interface usability concerns

    Manisha identified editing issues requiring 5-6 minutes to update 2-3 fields because pages close after each individual field update
    Current process requires reopening pages and clicking edit for each field modification
    Manisha noted concern about scalability when master data contains thousands of entries
    No import options currently available for master data pages
    Manisha agreed to create an Excel sheet with tabs for each QA release to track feedback systematically

UI/UX feedback communication gaps

    Manisha and Lawrence provide suggestions during development calls but see no changes implemented in subsequent releases
    Shankar explained Ravi typically verifies feedback against UI/UX documentation and communicates with the UI/UX team
    Shankar committed to address the UI/UX team's lack of follow-up communication on feedback decisions
    Agreement that UI/UX team should discuss feedback responses during calls rather than leaving Fiscal Systems uninformed

Testing coordination improvements

    Shankar committed to provide clearer release documentation including interdependencies and specific testing scope
    Lawrence clarified Fiscal Systems will continue comprehensive UAT testing since they're the customer contact point
    Agreement to hold meetings after each QA release cycle for better feedback communication
    Manisha prefers meetings over email for complex UI/UX feedback explanations
Private notes
Add your own private notes…