A great way to do story estimation by Steve Bockman.

If you've discovered the value of Scrum agile development while making your game, expert Clinton Keith outlines Lean and Kanban, two ways you can be agile during all phases of the game development process.

The agile methodology known as Scrum is rapidly gaining development credence, and High Moon Studios CTO Clinton Keith (Darkwatch, The Bourne Conspiracy) presents this in-depth Gamasutra article explaining how publishers and developers can benefit through regular, focused iteration.

This page is a work in progress and not meant to be complete.  A chapter in our forthcoming book Lean Software Development: Scaling Agile to the Enterprise will cover this topic to some extent. Note: Many links on this page require you to be registered with the web-site to see them.

This chapter covers several two general sets of beliefs I have encountered which impede learning Scrum effectively. The first involves misunderstandings about Scrum itself: Things that people believe but that are not true about Scrum. The second involves concepts that Scrum does seem to advocate but which are not effective. Errors in understanding always be cast aside before the true intentions can be grasped. Whenever we discover limitations of our thought, or in this case, the thought process we are learning (Scrum), that becomes a place where we can expand our thinking.

How does one go about scaling Agile to the enterprise? Is it better to start out small and scale up or to start at the top and work down? Both approaches have their own set of interesting challenges. After considering what normally happens in each approach, it should become clear that something else is needed. Lean provides the guidance needed to create an Agile enterprise.

This is the wiki for the Lean-Agile-Scrum User group.

Alan Shalloway also puts some of his thoughts on Lean modeling up here.