Yep, Salim, no problem. I see that from time to time.

Quick hint, prior to discussion (if it gathers sufficient interest):
1. Start with a retrospective to know the team and understand the issues that they currently face (e.g. poor communication, visibility, zero policies, limited adaptability).
2. Then ask for permission to help (by presenting the hypothesis that you possibly have a little bit more experience as a process improvement guy in the Agile space and they may be beginners or, at best, advanced novices... - although they are quite possibly experts in their own domain...). Once they agree...
3. Propose a (time limited) experiment with a bunch of your suggestions (e.g. temporary drop/integrate pivotal tracker and use physical index cards in a whiteboard, visualize work in progress, set policies, frequent demos, etc).
4. Put on the wall, beside the scrum/kanban board, the outcome of the retrospective, i.e. a list of improvement taks that you agreed to put forward, ideally with owners (including you).
4. Give them a vision of what the "next level" actually may look like.

That's it! My 2 coins in an uncertain currency.
Claudio

Just a single person's request - I've seen a few projects that went "agile" but really, they just started using Pivotal Tracker and called themselves agile. They dumped their old to-do list into Pivotal, and traded their milestones for "releases," missing a lot of the main benefits of Agile imo. It would be great to learn a few techniques that could be helpful to share when I encounter those teams, to help them get to the next level.