InfoQ Homepage Culture & Methods Content on InfoQ
-
Article: Lean and Agile, Marriage Made in Heaven or Oxymoron?
Dave West takes a look at the world views of the Agile and Lean communities and finds them in conflict. If true, then many of us in the community blending Lean and Agile and unaware of the inherent clash in ideals could be making some big mistakes. As an example of a manifestation of this conflict Dave takes the backlog.
-
Presentation: Craftsmanship and Ethics
In this talk Robert C. Martin outlines the practices used by software craftsmen to maintain their professional ethics. He resolves the dilemma of speed vs. quality, and mess vs schedule. He provides a set of principles and simple Dos and Don'ts for teams who want to be counted as professional craftsmen.
-
Article: What Would Alan Cooper Do?
In this article, Naysawn Naderi makes a summary of About Face 3, Alan Cooper’s book, noting some key takeaway points. The User Interface plays an important role in an application, be it a desktop one, a web application or a mobile one, and the guidelines contained by the article help creating better interfaces.
-
Should the Product Owner Be One Person Only?
Is the role of product owner a role that should be satisfied by only one person? There are those who say that there must be one person accountable - a single wringable neck. There are those that say that the expertise needed for a product owner cannot be satisfied by one person. There are many ideas in between about what and who a product owner should be.
-
A Quick Look at Architectural Styles and Patterns
App Arch Guide 2.0 (Microsoft patterns&practices), Chapter 6, talks about architectural styles like Message-Bus, Layered Architecture, SOA. Beside those styles there are numerous architectural patterns like Plug-in, Peer-to-Peer, Publish-Subscribe. Some authors make a difference between architectural styles, patterns and metaphors.
-
Refactoring Not a Substitute for Design
A member of the stack overflow community asked "Is design now a subset of refactoring?" The question highlights a common misunderstanding about the agile approach to emergent design. A common agile mantra is: "Test. Code. Refactor. Repeat!" This approach doesn't replace design; it simply spreads the work out over the life of the project.
-
Apache Ivy 2.0 Final Released
Apache Ivy 2.0, a project dependency manager, has been released. 2.0 is the first release of Ivy as an official Apache project.
-
Presentation: How (7 years of) Eclipse Changed my Views on Software Development
Erich Gamma shares the lessons learnt being deeply involved in the development of the Eclipse platform over the years. From being a platform in closed development, Eclipse turned into an open source one supported by a large and growing community. Erich also talks about Jazz, IBM’s software development platform which incorporates the lessons learnt from Eclipse.
-
Applying SOA Lessons to Web 2.0 Implementations
In their new article, two experienced SOA architects present five SOA best practices that can help to achieve success in adopting Ajax, REST, and other Web 2.0 technologies.
-
Presentation: Convergence: Model-Based Software, Systems And Control Engineering
In this presentation filmed during OOPSLA 2008, Janos Sztipanovits attempts to tackle the complexity of large scale systems integration. Software, systems and control engineering converge in such systems, raising the integration challenges and demanding a new approach to model-based design.
-
Interview: Software Design Helps Being Agile
In this interview made by InfoQ’s Deborah Hartmann during Agile 2008, Rebecca Wirfs-Brock talks about software design, the need for good design and the technical debt that might accumulate slowing down the development process. The conclusion is that agile developers should not disregard design.
-
Adopting The Whole Enchilada
Recently InfoQ reported on Jim Shore's 'The Decline and Fall of Agile', which highlighted a trend for organizations to adopt "Agile" (in name) but fail to adopt what it means to be Agile (in practice). Community leaders such as Joshua Kerievsky, Martin Fowler, and Ron Jeffries have taken Shore's post a few steps further recently, posting their own thoughts on what's going on with this situation.
-
Rebooting Computing Summit 2009: Computing is Not Dead
Rebooting Computing Summit 2009 concluded recently and had over 250 people representing industry, practitioners, and academia convene to discuss how to 'reboot' the computer science field, since reports show that the innovation rate in our field has been declining and that enrollments in our degree programs have dropped 50% since 2001.
-
Presentation: Agile Methods and User Centered Design
In this presentation filmed during ThoughtWorks’ Quarterly Technology Briefing, Dave Robertson and John Johnston explain what the Agile and User Centered Design’s (UCD) common denominators are, common values being the most important one in their opinion.
-
Succession, an Agile Approach to Evolving Architecture
Kent Beck wrote 'First One, Then Many' to explain the application of Succession to software design. Succession is a technique for evolving the architecture of a system from 'just enough for now' to what will eventually be needed. The example given is for a system that only needs to process one transaction today, but will eventually need to process many.