(OLD VERSION) Intro to Agile Scrum in Under 10 Minutes

What people said

Recommends Justin Standard · 2008-12 · Stack Overflow · on “Agile Development 101 Video”

Aggregating the answers here as a single answer: Video Links Introduction to Agile for Traditional Project Managers [LINK] Autumn of Agile [LINK] Scrum Et Al: Google Tech Talk [LINK] [LINK] Scrum in less than 10 minutes [this video] (Hamid Shojaee) Resource Links Ken Schwaber Videos & Links [LINK] Scrum Alliance [LINK] Introductory Podcast Re Scrum (audio only) [LINK]

Recommends philant · 2009-01 · Stack Overflow · on “Agile Development 101 Video”

Hamid Shojaee [LINK] produced a ten minutes video on Scrum [LINK] (also available in High Definition [this video] ). It's very rhythmical and amusing. Could be a great start for a discussion for your Lunch'n Learn.

Recommends Ólafur Waage · 2009-03 · Stack Overflow · on “How to avoid the 80/20 rule in software development”

It always takes longer than you expect, even when you take Hofstadter's Law into account But i digress. The best practice is sadly experience. SCRUM methods [LINK] have been very helpful for some types of software development since they constantly update the release date to a more accurate date. (quick video about scrum) [this video]

Recommends Esko Luontola · 2009-03 · Stack Overflow · on “How to avoid the 80/20 rule in software development”

How do you estimate the amount of work? You say that "the pesky 20% of work remaining seems to take 4 times as long as the previous 80%", but how did you get to the estimate that "20%" of the work is remaining and that "80%" is done? Obviously the estimates are wrong - in reality only 20% of the work is done and 80% is remaining. In software development it's very hard to give accurate estimates long time in advance. The only way is to split the work into small manageable pieces (maybe less than 10 hours each). You can estimate accurately only the immediate next steps. Some practices which help in estimating progress can be found in Scrum. The scope of what work will be done during the next s

Recommends Brad Bruce · 2009-07 · Stack Overflow · on “how to manage an agile project with a third party”

This is where some of the concepts of SCRUM pay off. The business leader MUST be involved with every step of the process. Picking which stories make a particular sprint MUST be done with the business leader. Don't do anything in a sprint that is not scheduled for that sprint without adding it to the sprint backlog chart for that sprint. It's good to show things that were added to a sprint in a different color. That way you can see the original plan (hopefully on schedule) and the additions (what causes the delay). Produce something that "could go to production" in each sprint. The business will see that it's getting something for their money. They can also adjust future sprints based on what

Recommends InvertedAcceleration · 2009-10 · Stack Overflow · on “How to convince a client that all next projects/enhancements should be done via TDD (with some agile practices)?”

I spent the time since asking this question looking for the best videos I could and I've come across a number that are very close to what I need. I will post them here so that others will find them if they are in a similar position to me. I realise that I asked more about TDD - but these videos capture a good portion of the message I'm trying to drive home... especially 'Why does Agile Software Development Pay' and 'Scrum in under 10 minutes'... it is the process of being responsive to change, producing higher quality code, having fewer defects and faster development cycles. Agile vs waterfall: A Tale of Two Teams (8:20) [LINK] Why does Agile Software Development Pay? (5:03) [LINK] Scrum Bas