Are you worried that Agile won't work because you want to move your project fast? Are you afraid that it'll slow you down? Are you curious what scrum is like from a developers perspective? Or do you simply want to see a bunch of developers bitch about their PMs?

Scrum and Agile are buzzwords that you seemingly can't get away from. As a developer, if you haven't run into them one way or another, you will. After working on 2 large scrum projects -- SDG&E's new website and The Economist -- I saw the good, the great, the bad, and the ugly. In this panel members of both teams will discuss their experiences and review what they loved, and what they hated. We'll attempt to separate the fact from the sales pitch, the process from the ritual, and give you a view from the trenches.

I was introduced to scrum 6 short months ago. Since then, I have had the opportunity to see it work in two very different projects. One was a fast paced project that had a short timeline: a small team and in which everyone was new to the process. The other is an example of an organization that has lots of experience with the process: a large number of teams working in concert. By examining these divergent projects, we'll hear how the process worked in a variety of situations and get down-and-dirty opinions from real developers on what they loved and what they hated about it.