March 09, 2007

Agile development comes to Photoshop

The Register hosts a Q&A with Photoshop co-architect Russell Williams about how the team changed its ways in the CS3 development cycle, making product quality paramount, improving the team’s work/life balance (i.e. fewer "Photoshop widows/-ers" who never see their loved one), and yet still delivering a rich set of features.  In brief: rather than building all the features up front, then spending the rest of the cycle fixing them, the team moved to a more incremental development model, insisting that bugs be fixed as we went along (not allowing them to build into a late-stage "bugalanche").  The article is a good read if you work in product development, or if you just want some inside geekery on how this stuff gets done.

Russell addressed the engineering side, so I thought I’d add some product management perspective.  Overall I’m pleased with how things have gone, but no approach is perfect, and it’s worth noting some of the challenges we faced. [Continued in this post’s extended entry]


3:21 PM | Permalink | Comments [9]

"416 megapixels ought to be enough for anybody…"

I wonder if that statement will sound laughably outdated someday.  Until then, the new 416MP scanning back from Better Light is mighty impressive. According to CNET, each 2-minute exposure generates a 794MB file that can provide 300 pixel-per-inch resolution for a poster measuring 34" x 45"–all for a cool 23 grand.  Put that in your Flickr account and smoke it. [See also 160 megapixels or bust.]

9:36 AM | Permalink | Comments [6]
Copyright © 2020 Adobe Systems Incorporated. All rights reserved.
Terms of Use | Privacy Policy and Cookies (Updated)