InfoQ Homepage Agile Content on InfoQ
-
Meeting the Challenge of Collective Code Ownership
The challenge: find the balance between pure practice and local compromise. Martin Fowler has brought us a story of a team in trouble, which took a step back to improve coding discipline and brush up on the basic practices that support collective ownership. In addition to the short-term gains of increased velocity and improved morale, the overall quality of the team's output improved as well.
-
Discussion: "Decide as Late as Possible"
Lean Software Development says "decide as late as possible", but this goes against the grain for new Agile managers and team leads, who used to be responsible for careful up-front planning. Can this possibly be right? A group of ScrumMasters recently discussed the topic.
-
Sign up for the APLN Leadership Summit at Agile 2006
The APLN Leadership Summit will be held at the Agile 2006 conference in Minneapolis on July 26 this year.
-
Thirty Days to Better Software
J.T. King describes the idea that you can slowly improve the way that you work over time by trying something for 30 days, giving it a fair chance, then assessing how well it worked for you.
-
Agile vs. Formal Methods
Should you adopt an agile method or a more formal one? Which is right for you? Perhaps you should mix and match?
-
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.
-
Software Manager Basics Explained
Most software managers began their careers as software developers. They either had some ambition, some skill recognized as good management material, or were in the right/wrong place at the right/wrong time. If you find yourself in a management position, or in a team lead position, how do you succeed?
-
Is the Feedback Loop Worth the Time?
John Brothers, on Indefinite Articles, blogged an interesting conversation last week between Mary Poppendieck and Robert Bogue. Drawn from the Agile Project Management newsgroup, it pointed out two different stances on the relative cost and value of "frequent feedback", a key component of Agile methodologies.
-
Article: What is Agility, and Why Should You Care?
Business is moving faster than ever, there's no time for fads. But Agile has been around for decades, enabling businesses to be ever more responsive in these times of rapid change. This short article tells how it has helped two teams excel.
-
Agile Unified Process v1.1 Released
The latest version of the Agile Unified Process (AUP) is available for download. This free, HTML-based product describes an agile instantiation of the Unified Process (UP).
-
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.
-
Improving Processes in Small Settings
The Software Engineering Institute is forming the IPSS Working Group, a three-year project to collaboratively explore the unique challenges of improving processes in small settings.
-
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.
-
The Art of Performance Feedback
The Agile approach, with its emphasis on "people over process" and "face-to-face communication", requires that managers pay attention to developing their communication skills. This is particularly important when helping employees improve their performance at work. Paul B. Brown has reviewed three recent books on the subject.
-
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.