InfoQ Homepage Change Content on InfoQ
-
InfoQ Article: Why Would a .NET Programmer Learn Ruby on Rails?
.NET developer Stephen Chu gives us some insight into his transition to Ruby on Rails programming. Quote: "By being loyal to one technology stack, I am bound to unconsciously make biased decisions, which will ultimately hinder my ability to deliver business value."
-
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.
-
Tech Stories Need to Include People and Technology
Brian Marick, reflecting on conversations heard at Agile2006, blogged about his concern that some of us are telling stories from the purely human or social viewpoint, while other are telling technology-only stories, noting that that XP isn't a story you can tell well without talking about both of these. Marick encourages us to include both when we communicate in and about projects.
-
O'Reilly: Ruby Book Sales Surpass Perl
Tim O'Reilly reports that Ruby book sales have surpassed those of Perl for the first time this quarter.
-
InfoQ Article: From Java to Ruby...
The Ruby on Rails revolution has been led by developers. Convincing management takes another kind of persuasion. A manager needs to understand the risks of adopting Ruby, the risks of snubbing mainstream languages like Java--even for one project--and the overall technical landscape of Ruby's capabilities.
-
Increase Your Personal Resilience to Change
"Highly resilient people are best suited for a world of constant change. They don't fight against disruptive change... they adjust to new situations quickly." Sounds useful for members of Agile teams which want to "embrace change", even more so for those experiencing the drastic change from traditional to Agile methods. Bob Weinstein's article lists some ways to increase your own resiliency.
-
TOC More Powerful than Six-Sigma, Lean
A manufacturing study has shown that TOC is twenty times as effective as Six Sigma, and nearly ten times more effective than lean at causing cost savings. This is the only scientific double-blind study of its kind performed "in the wild", i.e. in actual business plants. These ideas are frequently discussed in Agile circles and integrated into Agile methodologies.
-
A More Holistic View of Organizational Change
Change in the workplace affects more than just our nine-to-five lives. We sometimes feel it at a very deep level, and it's a good bet we'll take that stress home. On the Future Of Work blog, Charlie Grantham has proposed that we lose valuable opportunities to facilitate change when we ignore the deeply personal, or spiritual, aspects of workplace change.
-
Sowing Organic Change
Kevin Rutherford blogged recently on fostering change, rather than imposing it, this latter strategy being more likely to backfire. He's provided three tools useful to get the ball rolling and keep it moving.
-
Dangling the Right "Carrot" in Changing Times
For organizations heavily dependent on software development, the shift to Agile affects core aspects of the business. Eventually there will be ripples felt in the HR domain of incentives, performance and remuneration. Wharton University brings us an article on Employee Incentive Systems: Why, and When, They Are So Hard to Change. Examples are cited from Kodak, Accenture, Microsoft.
-
Where Did All the Positions Go?
How can existing, experienced IT professionals fit into an Agile project? By being flexible, open minded, and willing to change.
-
Clemens Vasters on Services and Business/IT Alignment
Clemens Vasters writes about the value of service-orientation (or lack thereof) for aligning business and IT.
-
Converting a project from a waterfall to an iterative approach
Software developers who firmly believe in an iterative approach must work for clients who, for various reasons, are rooted in a traditional methodology. This article discusses ways to help such organizations make a transition.
-
Agile Rollout - a Considered Approach
What's the best way to introduce Agile into the enterprise? Start at the bottom, with individual practices? Start at the top, obtaining upper management's buy-in? There's no one recipe for success, but there's likely to be less dissonance if the stages of adoption are understood and addressed. Kane Mar outlined steps to help an entire organization become Agile in stages in his 4-part blog series.
-
Article: Being Agile Without Going Overboard
Author Venkat Subramaniam speaks from experience in this exclusive InfoQ article, on how to incrementally introduce agility into a project which is in trouble and not currently agile.