Neil Killick discusses his background in Agile and his thoughts on estimation in Agile software projects, in particular the discussion around #noestimates.
Gojko Adzic talks about the need to iterate and learn about business value before jumping into solutions. Impact Mapping helps visualize and learn which behavior changes impact business results. Those changes might not even require any kind of software delivery.
Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Does success at the team level always result in success at the organization level? Sanjiv Augustine and Arlen Bankston discuss the Seven Deadly Sins that organizations repeatedly make so you can steer clear of them and benefit from a successful Enterprise Agile Adoption.
In this interview, Jeff Patton discusses the Product Owner role and points out that Agile has never been very focused on the customer. While Agile development excels at “delivery”, it struggles to support “discovery” (i.e. defining what the customer really needs). Also discussed are techniques such as Lean Startup and story maps and the importance of defining business value in an Agile context.
Nathaniel Talbott discusses the concept of Experiment Driven Design.
Pragmatic Programmer Dave Thomas, author of the 'pickaxe book' Programming Ruby, and co-author of Agile Web Development with Rails and The Pragmatic Programmer, found some time to talk with InfoQ about Ruby, Rails and the importance of choosing the right tool for the job.
Lean software gurus Mary and Tom Poppendieck share their years of practical experience, as they speak on the history of Lean thinking, the value of fast delivery and deferred committment, their use of Value Stream Mapping to identify and reduce waste, the importance of identifying and dealing well with cross-organizational and inter-organizational boundaries, and how Lean relates to RUP and Scrum.
Ron Jeffries' upcoming book looks at how tracking "Running Tested Features" is the essential element of Agility, from which all other practices and activities necessarily follow. Deborah Hartmann interviews Ron who takes to the whiteboard to explain how, when supported by XP's "simple design" practice, RTF helps teams deliver consistently without building up costly technical debt.
InfoQ editor Obie Fernandez asks David some hard-hitting questions about the future of Rails in the enterprise, profiting from his success and whether a vendor will fork Rails someday. Contains lots of good information for technologists staking their future on the Rails platform, including David's opinions on Rails adoption, service-oriented architecture and scaling Rails applications.