Featured Whitepapers
- Apples, Oranges, and Acorns - All Agile Development Tools Are Not the Same
- One's Enough for Agile Application Development Management
- Requirements Management 101 – 4 Basics Everyone Should Know
- Tips on Requirements Traceability – Learn How to Control Change and Improve Quality
- Scaling Continuous Integration to Large and Distributed Teams
|
| Fact: Agile
processes are appropriate for large-scale and business critical projects.
Certainly software vendors, the most mature users of Agile processes, see Agile
development as the key to increase revenue and quality of their very products.
Why, then, are IT organizations skeptical? In this issue of the Agile Journal,
we look at a range of techniques and best practices that companies have used on
large Agile projects.
Fact: Agile
processes are appropriate for large-scale and business critical projects.
Certainly software vendors, the most mature users of Agile processes, see Agile
development as the key to increase revenue and quality of their very products.
Why, then, are IT organizations skeptical? In this issue of the Agile Journal,
we look at a range of techniques and best practices that companies have used on
large Agile projects. Ross Pettit explores what companies can do to leverage skills and experience, monitor practice adoption, align staff recruiting, and measure results. Linsley Meadows and Sean Hanly share how British Telecom is transforming an organization of 14,000 developers by investing in strong Agile mentors and coaches. And Kirk Knoernschild argues that Agile processes can provide a set of checks and balances to large teams, so that development teams can minimize dependencies among their development artifacts and emphasize integration earlier in the software lifecycle. From an architectural perspective, Scott Ambler looks at the balance between effective up front architectural design and the need for just-in-time refinement and implementation. Israel Gat and Ryan Martens show how BMC Software has not only scaled its use of Agile processes for large teams, but how it is running product development teams across six locations and 11 time zones. And finally, we are fortunate to have just received Alistair Cockburn's second edition of the "Agile Software Development: The Cooperative Game." Cockburn provides a set of core principles that are key to the success of Agile projects, and takes a particular look at how teams can truly become self-adapting. This is an exciting time in the history of Agile development. We know that 2007 will bring even more successful large-scale projects and best practices on which Agile newcomers can draw. Please send us your best practices and suggestions for future articles. If you would like to contribute an article on this or another upcoming topic, go to the "Letters to the Editor" in the forum at AgileJournal.com.
Liz
Barnett
Set as favorite
Bookmark
Email this
Hits: 4354 Trackback(0)Comments (0)
|
| Last Updated on Friday, 12 October 2007 18:14 |
TrackBack URI for this entry
Show/hide comment form
Agile Marketplace - Announcements and Special Offers
The Business Case for ALM Transformation
Are legacy systems holding your company back? Breakthrough these technical constraints with an open and scalable environment that meets your unique business need to transform. There is no reason to be locked into an obsolete platform. The output of a number of recent transitions from legacy systems, this is practical white paper shares lessons learned and illustrates how guidance and enablement can pave the way for change.
Download this Whitepaper