InfoQ Homepage Methodologies Content on InfoQ
-
Starfish Brings Google-Style Distributed Processing to Ruby
An implementation of MapReduce, a process invented by Google to easily split up tasks to be performed by hundreds of machines, is brought to Ruby in a library called Starfish.
-
Five Habits of Highly Effective Software Developers
What are some of the code-level practices of highly effective developers? Robert Miller wrote a detailed article on Java.NET covering 5 practices which could apply to any language, including minimalist constructors, methods with clear focus and intent, minimizing logic in mutating methods, and minimizing dependendies between behaviour methods.
-
Opinion: Inability to Adopt Agile May Signal Bigger Problems
Peter Coffee, IT industry veteran, blogged on the recent Digital Focus survey of the state of Agile practice, noting that obstacles to Agile adoption are also general danger signs of development dysfunction.
-
Survey: The State of Agile in Practice
In March Scott Ambler surveyed over 4,200 people to discover the actual rate of Agile process adoption and effectiveness. His conclusion: Agile is not only growing in popularity, it's working so well that adopting an Agile approach appears to be an incredibly low-risk choice. Ambler recently published not only his conclusions but also the raw data he collected.
-
InfoQ Article: Simplifying Enterprise Apps with Spring 2 and AspectJ
Adrian Colyer, AspectJ lead and Chief Scientist at Interface21 has contributed an excellent article which shows how to use Spring 2's new AspectJ integration features followed by a roadmap for the adoption of Aspect Oriented Programming on an enterprise project, with lots of specific examples of how and where to apply Aspects.
-
Naked Agile and Naked Skydiving
Prompted by recent discussions on the ScrumDevelopment list, Alistair Cockburn and Jeff Patton sound a call to focus on the basics: "Listening, Designing, Coding, Testing. That's all there is to software. Anyone who tells you different is selling something."
-
Agile, Orthodoxy and a Message From God
A long and complex thread on the ScrumDevelopment list, set off by the phrase "Agile 2.0," has been exploring the past and future of Agile methodologies (for good or ill) including so-called "next generations" approaches like AUP, MSF Agile, and AMDD. Ron Jeffries, Ken Schwaber and Scott Ambler are just a few of the serious agilists who participated in this lively conversation.
-
Hanselminutes Podcast on Scrum Project Management
Scott Hanselman, a Certified Scrum Master at Corillian, has posted a podcast on the Scrum project management methodology. He uses Scrum in his own projects and feels that Scrum makes Agile approachable and easy to grasp. He goes over just-in-time task-level estimation, velocity, how burndown charts help forecast delivery dates, and the concept of when a feature can be considered really "done".
-
Is there room for both Ruby on Rails and J2EE?
Aaron Rustad takes a look at the differences between Rails and J2EE in an article published by IBM developerWorks, and ultimately suggests J2EE won't be dying any time soon.
-
SOA Integration and Methodologies
Miko Matsumura interviews John Harby, an independent consultant, OASIS Techican Committee member and SOA practitioner on popular SOA implementation methodologies.
-
Refactoring your Rails application to be RESTful
Scott Raymond writes about how his life became easier when he refactored the application behind IconBuffet.com to using RESTful URLs.
-
Online Discussion on Scrum Requirements Basics
The ScrumDevelopment list has seen lively discussion lately on Requirements issues frequently faced by new teams: "Can the ScrumMaster be the Product Owner too?", "How do we prioritize our Product Backlog?" and "QA's role in a SCRUM process". New teams quickly discover that a poor-quality Product Backlog can frustrate and undermine a team that is otherwise raring to start delivering value.
-
Patterns for Daily Stand-up Meetings Published
Jason Yip has published "It's not just standing up", Patterns for Daily Standups on Martin Fowler's Bliki. In the article he discusses the benefits and consequences of common practices for daily stand-ups. The patterns are intended to help direct the experimentation and adjustment of new practitioners as well as provide points of reflection to experienced practitioners.
-
Agile Work Cheatsheets Posted
It's been said before: Agile may be simple, but it's not so easy. Mishkin Berteig contributes some one-page quick-references to jog our memories and keep us focused on delivering value.
-
Statistics on Agile Practices Problematic
Keith Ray questions the value of statistics for software processes, including Agile processes.