I knew a few other people who’ve spent years working at banks talking Agile but not doing Agile only to leave and find real Agile elsewhere.

Thanks for your response. Thanks for spotting the error with Ron Jeffries name. I have given them full credit.
I still think that TDD is misunderstood, because even though it should have been written TFD, some organisations and teams do not and will never practice test first. There was life before TFD and for many creative and scientific styles of programming, it does not make sense. For example you can TFD on a Disney/Pixar animation, this is a programming visual media and not really an assertion. Another example, TFD when writing an new algorithm for Quant trading, your Monte Carlo methods are leading to approximations for wider analysis, I think it is difficult to TFD for those types of applications. Certainly, TFD does help in product engineering.

Generally, a good list. Some comments:

1) Uh, who is “Ron Hendries”? I believe you mean Ron Jeffries, Chet Hendrickson and Ann Anderson.

2) Scrum is not an acronym and thus shouldn’t be written all in capitals

3) Spike and Velocity originated with XP, not Scrum

4) A spike is a time-boxed investigation of something when you don’t have enough information to be able to provide a reasonable estimate for some work.

5) “[velocity is] A very basic measurement on the Return-on-Investment”. No it isn’t, and that’s why so many agile practitioners (including those who created the terms story points and velocity) are now advising that you don’t use it. The following sentence is correct, though.

6) Your description of TFD is how TDD was originally described and how I learned it in 2000.

If your CV says I built an app in the App store.. I can download and have a look. If you blog; I can read your blog. etc.

Showcase your talents. A CV is never enough.