Agile Performance Testing

References
[1] Waterfall Model, Wikipedia, retrieved from http://en.wikipedia.org/wiki/Waterfall_model

[2] Pepperdine K. "Proposed Anti-Pattern, Shot in the Dark", Kirk Pepperdine's Blog, 10 July 2006.

[3] Manifesto for Agile Software Development, 2001 http://agilemanifesto.org/

[4] Gunther N. Guerilla Capacity Planning: A Tactical Approach to Planning for Highly Scalable Applications and Services, Springer-Verlag, 2007.

[5] Smith C., Williams L. Performance Solutions, Addison-Wesley, 2002.

[6] Johnson K. "Multi-User Testing", Software Test & Performance, February 2008, 20-23.

[7] Grove A. Only the Paranoid Survive, Doubleday, New York, 1996.

[8] Podelko A. "Multiple Dimensions of Performance Requirements", CMG, 2007.

[9] Podelko A. "Workload Generation: Does One Approach Fit All?",CMG, 2005.

[10] Gunther N. "Benchmarking Blunders and Things That Go Bump in the Night", MeasureIT, June 2006 (Part I), August 2006 (Part II).

http://www.cmg.org/measureit/issues/mit32/m_32_2.html

http://www.cmg.org/measureit/issues/mit34/m_34_1.html

[11] Gimarc R., Spellmann A., Reynolds J. "Moving Beyond Test and Guess. Using Modeling with Load Testing to Improve Web Application Readiness", CMG, 2004.

[12] Agile Software Development, Wikipedia, retrieved from http://en.wikipedia.org/wiki/Agile_software_development

[13] Podelko A. "Load Testing: Points to Ponder", CMG, 2006. 

 

 

 

 


 

 

About the author

Alexander Podelko's picture
Alexander Podelko

For the past fifteen years, Alex Podelko has worked as a performance engineer and architect for several companies. Currently, he is consulting member of technical staff at Oracle, where Alex is responsible for performance testing and optimization of Hyperion products. He blogs at http://alexanderpodelko.com/blog and can be found on Twitter as @apodelko.