--- title: "Adobe uses Agile Development Successfully to build Photoshop CS3 product" url: "https://osherove.com/blog/2007/3/9/adobe-uses-agile-development-successfully-to-build-photoshop.md" canonical: "https://osherove.com/blog/2007/3/9/adobe-uses-agile-development-successfully-to-build-photoshop.html" published: "2007-03-09T09:04:51" updated: "2007-03-09T09:04:51" tags: ["Agile", "Agile Related"] author: "Roy Osherove" description: "What if you read a news story that the new Adobe CS3 product was developed using Agile Development Techniques? Here it is . A notable quote (my highlighting for interesting points): \" Did it change the way you put out…" usage: "Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original page)." license: "https://creativecommons.org/licenses/by/4.0/" --- # Adobe uses Agile Development Successfully to build Photoshop CS3 product By Roy Osherove March 9, 2007 In [Agile](https://osherove.com/blog/category/agile), [Agile Related](https://osherove.com/blog/category/agile-related) **Historical article** · Originally published March 9, 2007; technical details may be outdated. What if you read a news story that the new Adobe CS3 product was developed using Agile Development Techniques? [Here it is](http://www.regdeveloper.co.uk/2007/03/08/adobe_cs3_development/). A notable quote (my highlighting for interesting points): > "**Did it change the way you put out betas?** > > **An automatic process builds the program every night** and runs a set of tests before posting the build on our internal servers for QE to test. We could take **almost any of those daily builds and use them for demos**. > > **The public beta was basically just "whatever build is ready on date X".** There were only a couple of "we really gotta fix _this_ before we send out the public beta" bugs. With past versions, we couldn't have done a public beta at all that far ahead of release - there would have been far too many bugs. > > We weren't swamped with a pile of bugs from the hundreds of thousands of people who downloaded - it really was in the good shape we thought it was. With several hundred thousand downloads, there were fewer than 25 new bugs found. > > **Overall, did you end up with fewer bugs, more bugs, the same number of bugs fixed faster? Did you have to sacrifice features to work this way?** > > **Some people feared this would mean fewer features. That hasn't been the case**. We certainly had **far fewer bugs overall** and fewer during mid-cycle (about a third less in total last time I checked). **Better quality, plenty of features, fewer nights and weekends**: what's not to like?" \[Via [Jeffery](http://codebetter.com/blogs/jeffrey.palermo/archive/2007/03/09/Adobe_2700_s-Photoshop-CS3-developed-using-Agile-_2D00_-level-200.aspx)\] ## More in Agile [All posts in Agile](https://osherove.com/blog/category/agile) - Mar 16, 2007 ### [Remote Pair Programming with collaborative text editors](https://osherove.com/blog/2007/3/16/remote-pair-programming-with-collaborative-text-editors.html) - Mar 13, 2007 ### [Test Reviews Vs. Code Reviews - Some Helpful Tips](https://osherove.com/blog/2007/3/13/test-reviews-vs-code-reviews-some-helpful-tips.html) - Mar 7, 2007 ### [JUnit 4 feels like NUnit with attribute-like syntax](https://osherove.com/blog/2007/3/7/junit-4-feels-like-nunit-with-attribute-like-syntax.html) - Mar 2, 2007 ### [Testable Designs - Round 2: Tooling, Design Smells and Bad Analogies](https://osherove.com/blog/2007/3/2/testable-designs-round-2-tooling-design-smells-and-bad-analo.html) --- ## About the author **Roy Osherove**: Senior Solutions Architect at AWS working on AI for production and AI-driven development; author of The Art of Unit Testing and Elastic Leadership, with about 20 years of consulting and training on unit testing, TDD, team leadership and continuous delivery. ### Sites - [RobotPaper](https://robotpaper.ai/): This blog: AI patterns and anti-patterns, AI and coding agents, and engineering leadership. - [osherove.com](https://osherove.com): Roy's personal site. Author of The Art of Unit Testing and Elastic Leadership; consulting and training on unit testing, TDD, team leadership and continuous delivery, plus about 20 years of blog posts. - [The Art of Unit Testing](https://www.artofunittesting.com): The Art of Unit Testing, 3rd Edition (Manning): readable, maintainable, trustworthy unit tests, plus TDD workshops in C#, JavaScript, Java and Kotlin. - [5whys.com](https://www.5whys.com): Roy's writing on software team leadership: self-organizing teams, surviving chaos, learning mode and the Elastic Leadership model. - [Pipeline Driven](https://pipelinedriven.org): Continuous delivery and DevOps practices: build patterns, pipeline-friendly testing, DevOps metrics and enterprise DevOps. - [Elastic Leadership](https://www.elasticleadership.com): Elastic Leadership, Roy's framework for software team leaders (survival, learning and self-organizing modes). ### Social - X: https://x.com/royosherove - LinkedIn: https://www.linkedin.com/in/osherove/ ### Contact - Contact form: https://forms.gle/jQSx5KoXvrVA1JCK7 ### License Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original page). License: https://creativecommons.org/licenses/by/4.0/