Providing & Addressing Feedback
This article defines procedures for submitting, addressing, and documenting feedback throughout development cycles using spreadsheets or Review 360.
Feedback Submission Methods
Approved Tools
- Review tools (e.g., Review 360)
- Spreadsheets (primary method for Grant Thornton reviewers)
Grant Thornton Process
- Reviewers compile comments into spreadsheets and email them to developers/PMs.
- Direct interaction with ReviewMe (RME) is not required
Roles & Responsibilities
Developer Requirements
- Address all feedback requests
- Implement QA/client edits
- Maintain documentation status
Reviewer Requirements
- Conduct re-reviews after initial QA edits
- Perform full QA review post-alpha edits
Review Process Stages
- Initial QA Edits → Mandatory re-review
- Client Reviews → Alpha/Beta edits implemented
- Final Edits → Re-review decision by Paula (client contact) based on change complexity
Documentation Standards
- In Review 360, check off (resolve) comments as completed
- In client review spreadsheets, clearly mark items as "fixed" or "still outstanding"
- Update statuses in both spreadsheet and review tools
- Maintain version history for audit trails