InfoQ Homepage Culture & Methods Content on InfoQ
-
Application Build and Continuous Integration Patterns
Julian Simpson, Principal Consultant at The Build Doctor, has compiled a set of patterns for maintaining a fast and reliable application build process and avoiding some Continuous Integration (CI) pitfalls. He also presents a number of patterns for deployment automation and testing in production-like environments.
-
Agile and the Crutches of False Confidence
False confidence is often grounded in wishful thinking. It is defined as a state where the projected reality and the actual reality might differ considerably, however for a limited period of time, it does give a feeling of having everything under control. There are many such situations in Agile development which make a team hold onto the false confidence crutch only to fall later.
-
More Reflections on 10 Years Since the Agile Manifesto
In February it was 10 years since the signing of the Agile Manifesto in 2001. InfoQ is running a series of articles commemorating the decade of agility. In this item we report on what a number of commentators and agile luminaries have written recently on the current and future state of Agility.
-
Possible Solutions to the Single Product Owner Problem
A Product Owner arguably, is one of the most demanding roles in Scrum. Product Owner is, single handedly responsible for the success of the project and is expected to lead the development effort by conveying the vision to the team. He is expected to help the team produce maximum business value. Is this expecting a lot from a single role?
-
What is a Cloud?
A new discussion on focus.com “Is Facebook a cloud?” uncovers that there still is no agreement between practitioners on what a cloud really is.
-
Kanban in the Home
Practitioners are finding interesting applications of Kanban concepts in the home, far from the office and factory floor.
-
The H-A Manifesto
The latest of the agile manifestos, in a long line of manifestos, has been launched today, called the H-A Manifesto. Read on to find out if you can apply it in your organisation.
-
Haskell moves to Git
The well-known Haskell implementation GHC is moving from Darcs to a repository on GitHub, citing wider tool support and faster operations.
-
Tasktop 2.0 Supports Task Federation and Cross-Repository Agile Planning
The latest version of Application Lifecycle Management (ALM) collaboration tool Tasktop supports task federation, cross-repository Agile planning, and new connectors to other ALM tools like HP Agile Accelerator and SmartBear CodeCollaborator. Tasktop team last week released version 2.0 of the software which also has integration with Hudson CI tool.
-
Debate: What’s the Reason For MySpace’s Decline?
Some argue that MySpace has lost ground to Facebook because of their technology – Microsoft stack – and due to lack of enough talent in Los Angeles, while others opine that it is management’s fault and the departure of many people when the company was acquired by News Corp. in 2006.
-
The Importance of Agile Feedback Loops
Several members of the Agile community emphasize the importance of feedback loops in the effectiveness of Agile development processes.
-
James Gosling Joins Google
In a brief statement on his blog James Gosling has announced that he has joined Google.
-
Model Driven Development and Domain Specific Language Best Practices
Markus Voelter has published an update to his 2008 "MDD and DSL Best Practices" article. One of his core conclusions today is that "the distinction between modeling and programming goes away almost completely."
-
HTML 5 and CSS 3 Support for Expression Web
Microsoft has released an update to Expression Web 4 to support HTML 5 and CSS 3 development. This update, part of Service Pack 1, is only a partial solution; it offers IntelliSense and error-checking support but with only partial preview support. This update also includes expanded support for PHP IntelliSense.
-
What is a Commitment Anyway?
Commitment is defined as the act of binding yourself to a course of action. In Scrum, commitment has a strong meaning and Scrum practitioners suggest that authentic Scrum is not possible if people are not keeping commitments. In-spite of this, forums have a lot of questions about commitments not being met. Do we understand the real meaning of commitment?