InfoQ Homepage Agile in the Enterprise Content on InfoQ
-
Planning 101 for Agile Teams
Detractors have propagated the myth that "Agile teams don't plan", which couldn't be farther from the truth. Planning is essential to Agile, because of its empirical nature: plan, execute, inspect, adapt... plan again. Stacia Heimgartner outlines the five levels of planning required to set good expectations with all levels of the organization.
-
Should Architects Code? Agile Ones Do!
One of the "religous" issues within the architecture community is whether or not architects should code, at least this is still being debated within the traditional community. For agilists, the answer is a resounding YES.
-
Database Regression Testing: Isn't It Time to Bring Quality to Data Management?
Mission-critical business functionality is often implemented in stored procedures within your databases, and data is an important corporate asset. This article overviews a strategy for effective DB regression testing.
-
Are Traditional Project Managers De-Agilizing Projects?
David Nicolette fears that it is all too common to see agile teams have a traditional manager thrust upon them who doesn't understand agile and thereby harms the project through over control.
-
Using Agile Processes and Modeling To Build Enterprise Applications
The traditional approach of doing big requirements up front (BRUF) or big design up front (BDUF) results in significant wastage which can cause many software developments projects to be challenged and/or fail entirely. The article shows how to apply Agile Modeling (AM) practices when building enterprise Java applications.
-
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.
-
Feature Driven Development : Still Relevant?
First described in 1999, FDD was dismissed by some as "waterfallish". But it has developed into a complete methodology and is still in use. Is it truly Agile? Brad Appleton's recent article in CM Crossroads described it as different from other approaches, but still Agile and suitable for large projects and companies, especially those striving for CMM/CMMI certification.