InfoQ Homepage Culture & Methods Content on InfoQ
-
Opinion: Putting Overtime in Perspective
Agile work, when done in a disciplined, creative way, tends to be very intense, so Agile leaders encourage balanced lives for team members and promote "sustainable pace". Mitch Lacey, a Microsoft Program Manager, recently blogged about his emerging understanding of how to use this XP practice appropriately.
-
Presentation: Agile Project Management Planning and Budgetting
What happens to planning when teams "self organize"? Agile methods are empirical: plan it, do it, evaluate, plan again. David Hussman reviews practices for planning a project, release, iteration.
-
Holacracy - The Self-Organizing Enterprise
The fit between Agile teams and traditional enterprises can be challenging. Agile may highlight or exacerbate pre-existent dysfunctions, in areas a project manager may not be well-placed to address, so those involved in Agile roll-outs are thinking about alternate ways to organize the enterprise. Holacracy, created at Ternary Software, suggests that self-organization can extend outside IT.
-
Opinion: Agile Forgets the Human Factor
Kevin Brady, self-declared Agile critic, has a problem with Agile software development approaches: he feels that while they look great on paper. they fail to work in reality because they forget the human factor. Commenters on his blog entry question whether Agile or poor implementation lie at fault.
-
Sun Officially Backs Ruby, Brings JRuby In-House
Charles Nutter, one of the developers of the JRuby (Ruby on JVM) project, announces JRuby is being brought into the Sun Microsystems fold.
-
Put People First in Agile Distributed Testing
Baiju Joseph's new article on StickyMinds argues that, in order to build an effective testing team for distributed Agile, we need to focus on individuals and interactions over processes and tools. Based on the author's experience in setting up distributed agile testing teams, he lists numerous criteria that must be met in order to reach this goal.
-
24.37% of Web Developers to Try Ruby in Next 12 Months
A recent SitePoint survey of 5000 Web developers show 24.37% are set to try Ruby in the next year.
-
Choosing a Continuous Integration Server
In the first of a series of articles on continuous integration Paul Duvall compares three popular continuous integration servers, Continuum, CruiseControl, and Luntbuild. He considers criteria such as features, longevity, target environment, and ease of use.
-
August Sandcastle CTP is Now Available
Last week Microsoft released another community tech preview for Sandcastle. Sandcastle is the tool Microsoft currently uses to produce the API documentation for Visual Studio 2005. Anand Raman of the Sandcastle team claims that they can compile the documentation for the entire framework API in about 30 minutes.
-
TestNG concluded more suitable for large-scale testing than JUnit 4
Andrew Glover has compared TestNG and JUnit 4, taking a look at some features that TestNG has over JUnit 4. Andrew quickly takes the position that TestNG is better for large scale testing, despite JUnit 4's recent addition of annotations and "dramatically relaxed structural rules for test case authoring."
-
New Forums at AgileSoftwareDevelopment.org
Agile veteran Ron Jeffries is a believer in the value of dialogue. So he's offering the Agile community a new resource, an Agile Forum, hoping it will be a brand-neutral, consultant-neutral place, open to and shared by everyone who is interested in advancing him- or herself in Agile, or in bringing Agile to the world. In XPmag, Ron's made an open invitation to both participants and volunteers.
-
InfoQ Article: When and How to Formalize Business Rules
The terms "Agile software development" and "Business Agility" are confusing: are they orthogonal or complementary? James Taylor says that for even the most complex systems, Agile development can deliver business agility - particularly when supported by the right technology. For business rules he recommends a Rules Engine, and provides guidance in how to distinguish rules from requirements.
-
No Bug Database?
James Shore, a recognized speaker and writer in the Agile space, has had a crazy idea: Get rid of your bug database. He's not advocating that teams ignore problems; but bug databases are often so packed with questions, feature requests, and defects that there's little hope of their all being resolved. Shore and some others in Extreme Programming circles think there's a better way.
-
InfoQ Article: From Java to Ruby - Risk
"Ruby is risky" is a common perception. As Ruby on Rails moves closer to the mainstream, that risk will decrease. In this article, Bruce Tate examines the changing risk profiles for Java and Ruby from a managers perspective, examining Java's initial adoption and also common risk myths about Rails.
-
Opinion: Code Coverage Stats Misleading
John Casey recently spent some time refactoring Maven's assembly plugin, using coverage reporting to mark his progress and make sure he didn't break anything as he went. It didn't exactly go as planned - but at very least it was a learning experience. His conclusion: when you're seeking confidence through testing, perhaps the worst thing you can do is to look at a test coverage report.