• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Junilu Lacar
  • Jeanne Boyarsky
  • Bear Bibeault
Sheriffs:
  • Knute Snortum
  • Tim Cooke
  • Devaka Cooray
Saloon Keepers:
  • Ron McLeod
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Piet Souris
  • Frits Walraven
  • Ganesh Patekar

Agile Testing: New to Agile Methodologies

 
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Lisa and Janet,
I am a programming student interested in agile methodologies. Is there any way to implement agile concepts in single person projects?
Would the content provided in your book be suitable/learnable for someone such as myself who is new in the agile field?

Cheers,
Joe
 
author
Posts: 14112
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Take a look at http://c2.com/cgi/wiki?ExtremeProgrammingForOne
 
Ranch Hand
Posts: 43
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Joe Deluca wrote:Lisa and Janet,
I am a programming student interested in agile methodologies. Is there any way to implement agile concepts in single person projects?
Would the content provided in your book be suitable/learnable for someone such as myself who is new in the agile field?

Cheers,
Joe


Hi Joe,
IMO, Agile is mainly about values and principles. If you're committed to delivering high-quality software and the best possible business value, and you're always trying to improve the way you work, that's agile in my book. Being "agile" would mean working closely with your customer, and using good practices to produce what the customer needs. The smallest agile project I worked on had two programmers, a tester and a customer, and it was a success.

Our book assumes some readers won't be very familiar with agile development, so we give a lot of context and explanations, but oriented towards testing in an agile project. You shouldn't have any problems following it even if you're brand new to agile. If you want a more general introduction to agile development, there are a lot of good books. The Art of Agile Development by James Shore is a good intro for newbies and also contains a lot of good information about testing. Bob Martin's Agile Software Development is also good, although it's several years old now, I don't think it's dated. You could also find some good information on the Agile Alliance site, www.agilealliance.org.
-- Lisa
 
Ilja Preuss
author
Posts: 14112
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Lisa Crispin wrote:
IMO, Agile is mainly about values and principles. If you're committed to delivering high-quality software and the best possible business value, and you're always trying to improve the way you work, that's agile in my book. Being "agile" would mean working closely with your customer, and using good practices to produce what the customer needs.



Uh, while I agree that Agile is defined by values and principles, I'd also say that it's a bit more specific than "just" what you indicate above. I think it's very well defined by the Agile Manifesto. William Petri has a very good blog post on this topic: http://agilefocus.com/2009/02/agile-versus-agile/ (well, at least I like it... ;)
 
Lisa Crispin
Ranch Hand
Posts: 43
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Ilja Preuss wrote:

Lisa Crispin wrote:
IMO, Agile is mainly about values and principles. If you're committed to delivering high-quality software and the best possible business value, and you're always trying to improve the way you work, that's agile in my book. Being "agile" would mean working closely with your customer, and using good practices to produce what the customer needs.



Uh, while I agree that Agile is defined by values and principles, I'd also say that it's a bit more specific than "just" what you indicate above. I think it's very well defined by the Agile Manifesto. William Petri has a very good blog post on this topic: http://agilefocus.com/2009/02/agile-versus-agile/ (well, at least I like it... ;)



Oh, I do like William's post.

I don't think I'm communicating my viewpoint very well. My wish is that someday we don't give it a special name, it's just the accepted good way to develop software. And of course, there are variations in practices from team to team, but the principles and values are the same.
-- Lisa
 
Ilja Preuss
author
Posts: 14112
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Lisa Crispin wrote:My wish is that someday we don't give it a special name, it's just the accepted good way to develop software.



Oh, you are a dreamer!
 
All of life is a contant education - Eleanor Roosevelt. Tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!