Granny's Programming Pearls
"inside of every large program is a small program struggling to get out"
JavaRanch.com/granny.jsp
  • 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
  • Tim Cooke
  • Jeanne Boyarsky
  • Bear Bibeault
Sheriffs:
  • Knute Snortum
  • paul wheaton
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Ron McLeod
  • Piet Souris
  • Ganesh Patekar
Bartenders:
  • Tim Holloway
  • Carey Brown
  • salvin francis

Agile & Product Development

 
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have worked as a director at a small company doing product development. We strived for a repeatable cycle of releases, once per quarter, divided into minor (odd releases - bug fixes, even releases - minor functionality improvements) and major releases - major enhancements and functionality. I had to work hard to get my engineers to accept a more structured way of product development.

In a recent discussion with another senior product manager, he indicated that they were having some success with agile techniques. I expressed surprise, since at first glance (and in my admittedly limited experience), Agile does not seem well suited to time-compressed development.

Does the book talk about product development or just IT Projects? How would you apply Agile techniques to structured product development, where product management defines a set of features that must be implemented?

Thanks, Neil
 
author
Posts: 31
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Neil,

agile techniques works excellent for product development. The book does not specifically talk about IT or product developent, since the practices works for both. As an example, we apply these practices to the development of the product IBM Rational Method Composer (which among others contains Rational Unified Process). I think we have a reasonably complex product, with simultaneous release in 9 languages, etc. And we have had pretty much on time releases for 10 years now (including predecessor products).

Many of these practices are also consistent with how the eclipse platform is developed, and think eclipse is another huge success story....

There are a lot of other success stories with agile development and product development, and I would guess that you actually find product companies being more aggressive with adoption of agile techniques than it shops, but I cannot back that up with facts, it is just my gut feeling.

So, agile developepment and the book works great for product development.

Cheers

/Per
 
author
Posts: 14112
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Originally posted by Neil Johnson:
at first glance (and in my admittedly limited experience), Agile does not seem well suited to time-compressed development.



I'm not sure I'm getting your point here. Why does it look that way to you? Thanks!
 
Yeah. What he said. Totally. Wait. What? Sorry, I was looking at this tiny ad:
professionally read, modify and write PDF files from Java
https://products.aspose.com/pdf/java
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!