Blog
Categories
- Agile
- Best Practices
- Center of Excellence
- Cloud
- Featured
- Functional Testing and Automation
- Giveaway
- Healthcare IT
- HP
- HP Discover Conference
- HP Software Patches
- Latest News
- LoadRunner
- Methodology
- Mobile
- Northway Navigator Club News
- Operating Systems
- Performance Testing and Automation
- Quality Assurance
- Security
- Service Virtualization
- SiteScope
- Training
- TweakLR
- Uncategorized
- VuGen Code
Archives
- April 2019
- September 2018
- July 2018
- June 2018
- October 2017
- August 2016
- April 2015
- February 2015
- September 2014
- August 2014
- May 2014
- April 2014
- March 2014
- October 2013
- September 2013
- August 2013
- June 2013
- May 2013
- April 2013
- March 2013
- February 2013
- January 2013
- December 2012
- November 2012
- October 2012
- September 2012
- August 2012
- July 2012
- June 2012
- May 2012
- February 2011
- July 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- September 2007
- August 2007
- July 2007
- October 2006
- April 2006
- March 2005
- October 2004
- March 2004
- February 2004
- January 2004
- December 2003
- November 2003
- April 2003
-
Agile vs Fragile: Change … Bring It On!
Posted on February 4, 2013 by Admin
Part 4 in a series of 17. To start at the beginning, first read Agile vs Fragile: A Disciplined Approach or an Excuse for Chaos.
The second Agile principle focuses on being agile (little “a” in this case). The primary concept is that change is seen as a positive way to ensure that what you deliver to the customer has the best chance of being correct. Principle two embraces changes, because it would rather make adjustments to timelines and delivery now rather than continue down the wrong path and have to retrace steps. Read Entire Entry -