Ask HN: How should we prepare for an external review of our dev practices

We're a ruby/rails agency that uses TDD, Agile, version control via Git, unit tests and Pivotal Tracker for managing stories.<p>Our client has just received a big funding grant and an external Information Management PHD consultant has been engaged to 'review our development processes'.<p>Following our initial meeting where they asked for copies of our GANTT charts and we mentioned Kanban and they said 'What's a Kanban?'. We're really nervous that we will be assessed against some archaic project management principals and that all our agile and modern development best practices won't be appreciated or reflected in the review mainly due to naivety by the reviewer.<p>What should we do?<p>Do you have or know of any resources/facts/stats which could help us make the case for our agile and modern ruby/rails development practices?

[edit: Edited the title to be more of a question.]