In This Issue

• The Secret to Organizational Agility -Mike Cottmeyer
• Prioritizing Your Product Backlog - Mike Cohn @ Agile 2008
• Code Cast 17-David Laribee on Lean/Kanban - Elegant Code
• Group Coherence for Project Teams - A Search for Hyper-Productivity - Joanna Zweig and Cesar Idrovo for Agile Journal

---

The Secret to Organizational Agility - Mike Cottmeyer for AgileChronicles.com

Are you ready... here it is... to be agile you must... break dependencies at all costs! A great article/blog post from VersionOne product specialist, Mike Cottmeyer.

Read the blog post here.
(http://www.agilechronicles.com/blog/2008/12/the-secret-to-organizational-agility.html)

---

Prioritizing Your Product Backlog- Mike Cohn at Agile 2008 (video)

Choosing the right features can make the difference between the success and failure of a software product. Mike Cohn presented 'Prioritizing your Project Backlog' at Agile 2008 on how a project backlog should be organized and prioritized and non-financial techniques for prioritization such as kano analysis, theme screening/scoring, relative weighting and analytic hierarchy process.

View the presentation here.
(http://www.infoq.com/presentations/prioritizing-your-product-backlog-mike-cohn)

---

Code Cast 17-David Laribee on Lean/Kanban - Elegant Code (podcast)

Introduction by David Starr of Elegant Code:

The esteemed Mr. Laribee was good enough to join Jarod Ferguson and me on this episode of the Elegant Code Cast where we discussed Lean and Kanban. This is a great conversation and a must listen for folks looking to take their high-functioning Agile team to the next level.

Available as MP3, iTunes, RSSPodcast here.
(http://elegantcode.com/2008/12/12/code-cast-17-david-laribee-on-lean-kanban/)

---

Group Coherence for Project Teams - A Search for Hyper-Productivity- Joanna Zweig and Cesar Idrovo for Agile Journal

Group characteristics and group dynamics are invisible to most of us. We are not trained to detect them, let alone manage them. Our work is influenced by much more than what we see. This can make project success (and failure) sometimes appear to be random.

Read the article here.
(http://www.agilejournal.com/content/view/891/33/)