The Agile Developer
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
<< Start < Prev 1 2 3 Next > End >> |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Page 1 of 3 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Kirk is an Analyst at 
Over the past two years, I've written numerous articles as part of 
Design and
code reviews promise to improve software quality, ensure compliance with
standards, and serve as a valuable teaching tool for developers. As with most
practices, there are subtle nuances surrounding how they're performed that can
dramatically affect their value. In some organizations, reviews are a valuable
aspect of the software lifecycle. In others, they are a necessary evil tainted
with political bureaucracy and big egos. Sub-optimal reviews conducted late in
the lifecycle are often misguided due to few objective guidelines that help
guide the review process. When used throughout the development lifecycle, code
and design quality metrics are valuable inputs to the review process.
Last
year, I resolved that in 2007 I'd focus on the essential characteristics of
technology that help maximize the effectiveness of agile practices. Since about
90 percent of folks don't keep their resolutions throughout the year, I've
decided this year not to make any such promises. Instead, I'll let you make
your own resolutions this year, and will offer up a few tips that you might
want to consider seriously if you're interested in increasing your personal or
team's agility.
Agile has grown
and evolved from a very simple developer centric process defined by Extreme
Programming to a complex product brand that enterprises are using to bring more
resiliency to governance programs, enterprise architecture initiatives, and
application portfolio management efforts. But at its roots, there remains a key
fundamental aspect that defines the essence of agility on the software
development project. Continuous Integration is a strategy where software is
integrated and built continuously, or at least as frequently as is feasibly
possible. Many teams have adopted a continuous integration strategy, yet do not
fully realize all the benefits that continuous integration might bring to the
development effort. This article discusses the subtle though significant ways
that continuous integration can be leveraged -from helping to align IT with the
business to enforcing architectural constraints - and shows that this
fundamental aspect of agility is the defining and necessary element of a truly
agile development experience.Agile Marketplace - Announcements and Special Offers
Upcoming Webcasts
Sponsored by Urbancode - On Demand
Mastering Complex Application Deployment
Sponsored by CollabNet - Wednesday, August 24, 2011
Closing the Agile Loop: Continuous Integration, Continuous Information
ScrumWorks Pro – The World’s Best Agile Project Management Tool
Simply put, CollabNet’s ScrumWorks Pro is the best Agile project management solution on the market, bar none. More than 150,000 Agile professionals rely on the power and simplicity of ScrumWorks every day. But don’t take our word for it – try it yourself for free. CollabNet is now providing the first 10 users of ScrumWorks Pro at no charge!
Download ScrumWorks Pro today!
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