• 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • Ron McLeod
  • paul wheaton
  • Jeanne Boyarsky
Sheriffs:
  • Paul Clapham
  • Devaka Cooray
Saloon Keepers:
  • Tim Holloway
  • Roland Mueller
  • Himai Minh
Bartenders:

The Art of Agile Development:-Any Comparative Studies covered in the Book

 
Ranch Hand
Posts: 111
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello Autors,

My question is if there is any comparative stuides covered in the book? I think it will help us to understand the benefits of Agile Development Process.

My Another question is
Is the agile development process explained in the book is only for Software Development or can it be applied to the development of any thing for example electronic hardwares?

Regards
Padma
 
author
Posts: 16
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Padma Asrani:
My question is if there is any comparative stuides covered in the book? I think it will help us to understand the benefits of Agile Development Process.

My Another question is
Is the agile development process explained in the book is only for Software Development or can it be applied to the development of any thing for example electronic hardwares?



Hi Padma,

We cite a few studies about various software development practices, but to my knowledge there are no particular studies pitting development methods against each other. (I'm not sure how you'd create a double-blind study of that sort anyway; you'd need teams of comparable skill working on the same project in such a way that you could identify and measure any differences.)

The best we can do is explain the experiences we've had and studied and suggest what we've seen work and what we think will work for you if you perform it with discipline and mindfulness and start to adapt it for your own circumstances.

We do spend a fair amount of time comparing agile practices to comparable practices. We recognize that it's not possible to adopt XP completely from the start of every project, and that you may have to adapt what you do to fit your team and organization.

As for applying agile principles to non-software projects, I'm sure a lot of the book applies... but we concentrated solely on software, so you'll have to do more work to fit the process to a new domain.
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic