Comments on: Product Management Posts http://securitybuddha.com/2007/04/02/product-management-posts/ Security Enlightenment - Mark Curphey Sun, 06 Jul 2008 06:31:47 +0000 http://wordpress.org/?v=MU By: Adam Bullied http://securitybuddha.com/2007/04/02/product-management-posts/#comment-8152 Adam Bullied Thu, 18 Oct 2007 17:25:29 +0000 http://securitybuddha.com/2007/04/02/product-management-posts/#comment-8152 Mark -- sorry for being so late to the party; just caught this post now. I run all software development in agile currently, and really wouldn't want to do it any other way. I agree with all elements of the agile manifesto; however getting people to believe in them as well (either explicitly or implicitly) is not always an easy feat. Waterfall is, like you say, cut out for old school software development. While it may have its place, it's not my cup of tea, that's for sure. Thanks for the link, and the compliments! I'm enjoying your archive / current posts... Mark — sorry for being so late to the party; just caught this post now.

I run all software development in agile currently, and really wouldn’t want to do it any other way. I agree with all elements of the agile manifesto; however getting people to believe in them as well (either explicitly or implicitly) is not always an easy feat.

Waterfall is, like you say, cut out for old school software development. While it may have its place, it’s not my cup of tea, that’s for sure.

Thanks for the link, and the compliments! I’m enjoying your archive / current posts…

]]> By: The Productologist » Blog Archive » Fighting, er, Working with Engineering http://securitybuddha.com/2007/04/02/product-management-posts/#comment-1053 The Productologist » Blog Archive » Fighting, er, Working with Engineering Tue, 24 Apr 2007 22:18:01 +0000 http://securitybuddha.com/2007/04/02/product-management-posts/#comment-1053 [...] an interesting thread going on across several blogs about the Agile development method (Agile, here and across other posts, is being used as a [...] [...] an interesting thread going on across several blogs about the Agile development method (Agile, here and across other posts, is being used as a [...]

]]> By: The Productologist » Blog Archive » Fast Release Cycles http://securitybuddha.com/2007/04/02/product-management-posts/#comment-701 The Productologist » Blog Archive » Fast Release Cycles Tue, 10 Apr 2007 17:17:16 +0000 http://securitybuddha.com/2007/04/02/product-management-posts/#comment-701 [...] wrote a comment the other day on another blog, Security Buddha, in response to a post about how Product Managers (at least not the ones who write blogs) are not [...] [...] wrote a comment the other day on another blog, Security Buddha, in response to a post about how Product Managers (at least not the ones who write blogs) are not [...]

]]> By: Embedded Components and Tools Blog Center http://securitybuddha.com/2007/04/02/product-management-posts/#comment-682 Embedded Components and Tools Blog Center Tue, 10 Apr 2007 00:50:40 +0000 http://securitybuddha.com/2007/04/02/product-management-posts/#comment-682 <strong>Community Software Development for Embedded Devices</strong> Photo by Ron Fredericks using Canon EOS-10D 34mm fluorite lens, circular polarizer, 1.5s & f/22 @ ISO 100, on tripod, from ECI’s HP lab collection. Ron Fredericks writes: I envision the day when community software engineering projects are c... Community Software Development for Embedded Devices

Photo by Ron Fredericks using Canon EOS-10D 34mm fluorite lens, circular polarizer, 1.5s & f/22 @ ISO 100, on tripod, from ECI’s HP lab collection.
Ron Fredericks writes: I envision the day when community software engineering projects are c…

]]> By: Ivan Chalif http://securitybuddha.com/2007/04/02/product-management-posts/#comment-596 Ivan Chalif Wed, 04 Apr 2007 01:48:12 +0000 http://securitybuddha.com/2007/04/02/product-management-posts/#comment-596 Mark, I have to disagree with your statement that PM gurus (not sure that I would label myself with that moniker, but I appreciate the complement) are better suited to old-school development. It can be very easy (and comfortable) to rest on long cycles, but it really depends on what your product does and who your audience is. I'd like my releases to be faster and more frequent, but my products are for enterprise-level customers and they frequently have to go through rigorous testing (the products, not the customers) before they can be put into production at the customer site. I could have a new release/update every two weeks, but in reality, our customers would wait until there was a significant amount of new/fixed features before they would upgrade and start the testing process on their end. Of the principles listed on the Agile Manifesto, I like to believe that I use the following ones regularly-- + Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. + Continuous attention to technical excellence and good design enhances agility. + Simplicity--the art of maximizing the amount of work not done--is essential. Mark, I have to disagree with your statement that PM gurus (not sure that I would label myself with that moniker, but I appreciate the complement) are better suited to old-school development. It can be very easy (and comfortable) to rest on long cycles, but it really depends on what your product does and who your audience is.

I’d like my releases to be faster and more frequent, but my products are for enterprise-level customers and they frequently have to go through rigorous testing (the products, not the customers) before they can be put into production at the customer site. I could have a new release/update every two weeks, but in reality, our customers would wait until there was a significant amount of new/fixed features before they would upgrade and start the testing process on their end.

Of the principles listed on the Agile Manifesto, I like to believe that I use the following ones regularly–

+ Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.

+ Continuous attention to technical excellence and good design enhances agility.

+ Simplicity–the art of maximizing the amount of work not done–is essential.

]]>