Startup Lessons Learned

OCTOBER 16, 2013

As Shutterstock has grown, there are a few key elements to our continued development speed: Small, autonomous teams: The more a team can do on their own, the faster they can go. Continuous deployment: A key component of speed is to keep pushing out work. But that doesn’t mean that we don’t take these ideas seriously.

Lean 167

Lean Startup Software Engineering Agile 167

Startup Lessons Learned

MAY 9, 2012

Brant and Patrick have set out to write and design a book that not only describes practical steps for implementing Lean Startup principles in your innovative endeavors – but to inspire your creativity as well by sharing diverse examples of what works, and more importantly, what often doesn’t work. It will be published by Wiley this fall.

Entrepreneur 167

Entrepreneur Lean Southern California San Diego 167

Startup Lessons Learned

JUNE 15, 2009

Lessons Learned by Eric Ries Monday, June 15, 2009 Why Continuous Deployment? Of all the tactics I have advocated as part of the lean startup , none has provoked as many extreme reactions as continuous deployment , a process that allows companies to release software in minutes instead of days, weeks, or months.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

APRIL 29, 2013

Eric has talked often about recognizing a startup as an organization designed to create a new product or service under conditions of extreme uncertainty. So if you’ve got advice to share on implementing a continuous deployment framework, for example, we’re all eyes. 5) Do I have to follow the directions on the application form

Lean 165

Lean Technical Review Startup Software Review 165

Startup Lessons Learned

JANUARY 18, 2010

Lessons Learned by Eric Ries Monday, January 18, 2010 Case Study: Continuous deployment makes releases non-events The following is a case study of one entrepreneurs transition from a traditional development cycle to continuous deployment. Continuous Deployment is Continuous Flow applied to software.

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

Startup Lessons Learned

DECEMBER 28, 2009

Lessons Learned by Eric Ries Monday, December 28, 2009 Continuous deployment for mission-critical applications Having evangelized the concept of continuous deployment for the past few years, Ive come into contact with almost every conceivable question, objection, or concern that people have about it.

Continuous Deployment 122

Continuous Deployment San Francisco Lean Metrics 122

Startup Lessons Learned

FEBRUARY 10, 2009

Lessons Learned by Eric Ries Tuesday, February 10, 2009 Continuous deployment and continuous learning At long last, some of the actual implementers of the advanced systems we built at IMVU for rapid deployment and rapid response are starting to write about it. Continuous learning -> Continuous feedback!

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

www.subelsky.com

FEBRUARY 25, 2010

His descriptions of lean startup techniques and philosophies have had a big influence on the way I design and build software. Because it has an RSS feed, one could also use "Unresolved Hoptoad Errors" as a metric influencing the continuous deployment system. I'm a lighting audio and video designer.

Lean 41

Lean Baltimore Ruby Maryland 41

usersknow.blogspot.com

APRIL 30, 2010

A good answer to this question should really include all of the following: I have both development and design time scheduled for quick follow up work on the feature over the next few sprints. Visual Design is Important, But Maybe Not Just Yet. ▼ April (5) 7 Ways Design Can Speed Up Your Product Developmen.

Software Review 40

Software Review Agile San Francisco Metrics 40

Startup Lessons Learned

FEBRUARY 16, 2009

Lessons Learned by Eric Ries Monday, February 16, 2009 Continuous deployment with downloads One of my goals in writing posts about topics like continuous deployment is the hope that people will take those ideas and apply them to new situations - and then share what they learn with the rest of us. Thanks for the comments.

Continuous Deployment 68

Continuous Deployment San Francisco Software Review Lean 68

Startup Lessons Learned

FEBRUARY 7, 2013

Struggling to explain the successes and failures of those companies, I discussed principles like continuous deployment, customer development, and a hyper-accelerated form of agile. Therefore, we needed a new management toolkit designed explicitly for iteration, scientific learning, and rapid experimentation.

Lean 167

Lean Entrepreneur San Francisco Agile 167

YoungUpstarts

APRIL 25, 2019

Adding the right tools and automation, teams can design, test, build, and deploy software more agilely. An integrated workflow supports rapid deployment and flexible workflows. Kubernetes is an open source software solution to automate deployment, scaling, and management of containerized applications. Automation.

Java 127

Java XML Open Source Continuous Deployment 127

Startup Lessons Learned

NOVEMBER 5, 2013

The conference is still designed to help entrepreneurs learn from each other. Mariya Yao has thoroughly practical advice for rapidly iterating mobile designs. John Goulah will show you how Etsy gets engineers on board with continuous deployment, an important technical environment that many resist.

Lean 166

Lean Early Stage San Francisco Cofounder 166

Startup Lessons Learned

JULY 29, 2009

Like a financial debt, the technical debt incurs interest payments, which come in the form of the extra effort that we have to do in future development because of the quick and dirty design choice. We can choose to continue paying the interest, or we can pay down the principal by refactoring the quick and dirty design into the better design.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

FEBRUARY 20, 2009

Lessons Learned by Eric Ries Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. I dont think so.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

MAY 7, 2009

I spent some time with his company before the conference and discussed ways to get started with continuous deployment , including my experience introducing it at IMVU. Moreover, approaching the problem from the direction that I had intuitively is a recipe for never reaching a point where continuous deployment is feasible.

San Francisco 131

San Francisco Continuous Deployment Software Review Lean 131

Startup Lessons Learned

NOVEMBER 13, 2008

It seems your cluster architecture is one of the key architectural constraints making continuous deployment possible. If you cant deploy to 5% of the nodes and check the results, then how would you accomplish continuous deployment? Case Study: Continuous deployment makes releases n.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

SEPTEMBER 27, 2010

This is precisely the dilemma that the doctrine of minimum viable product is designed to solve. When people start using quality, reliability, or design as an excuse to delay, it used to make me nervous, even when these suggestions were well intentioned. Rules of thumb can be infuriatingly unhelpful. And it’s really hard.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

AUGUST 8, 2009

Lessons Learned by Eric Ries Saturday, August 8, 2009 Revisiting the Software Design Manifesto (and whats changed since then) My recent article on technical debt and its positive uses generated a fair bit of controversy. The argument itself got me thinking a lot about design and its role in building products.

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

FEBRUARY 22, 2010

I have personally taught many “non-technical&# people to program – graphic designers, QA folks, even artists and animators. Instead of focusing on programs designed to specifically benefit any one group, I think our focus should be on making our companies as meritocratic as possible.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

Startup Lessons Learned

SEPTEMBER 10, 2008

But if you want to practice rapid deployment, you need to be able to deploy that build in one step as well. If you want to do continuous deployment, youd better be able to certify that build too, which brings us to. For more on continuous deployment, see Just-in-time Scalability. Can you make a build in one step?

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

SEPTEMBER 15, 2008

The new design improved on the old one in several ways, but these improvements didnt translate all the way through the funnel. Usually, I think that means youve lost some good aspect of the old design. The designers might be telling you that the new design looks much better than the old one, and thats probably true.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

OCTOBER 20, 2008

Most of the other processs changes - mandatory design reviews (prelimninary, critical, etc), - documenting all our procedures, and so on - were to support those two factors. It might be more precise to categorize them of two kinds of flaws: flaws in implementation, and flaws in design. Im keen on the two-kinds-of-bugs thing.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

AUGUST 1, 2009

My guess is they have lots of people constantly working on interesting new tools for their designers to play with. Discover whats in customers heads, and tackle problems where design is a differentiator. Case Study: Continuous deployment makes releases n. Revisiting the Software Design Manifesto (and what.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

SEPTEMBER 30, 2008

If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? Platform selection and technical design - if your business strategy is to create a low-burn, highly iterative lean startup, youd better be using foundational tools that make that easy rather than hard.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

OCTOBER 5, 2009

In the past, we invested in brilliant architecture, code reuse, refactoring, modular design, etc. If we’re practicing continuous deployment, we can be confident that we’ll be able to rush an emergency fix into production without risking introducing further problems.

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

Startup Lessons Learned

OCTOBER 5, 2008

These specs are handed to a designer, who builds layouts and mockups of all the salient points. Then the designs are handed to a team of programmers with various specialties. The programmers keep asking for more say in the designs and direction that they work on. First, he writes it nice and clear.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

JULY 28, 2010

If you havent seen it, Pascals recent presentation on continuous deployment is a must-see; slides are here. If you havent seen it, Pascals recent presentation on continuous deployment is a must-see; slides are here. Case Study: Continuous deployment makes releases n.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

Startup Lessons Learned

JULY 13, 2009

Product development deals in designs, which are fundamentally intangible. Team New Zealand designed the yacht that won the Americas Cup. When they tested improvements in keel designs, they used two virtually identical boats. The unimproved boat would sail against the improved boat to determine the effect of a design change.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

APRIL 7, 2010

Some designers also hate optimizing (which is why the “41 shades of blue&# test is so famous – a famous designer claims to have quit over it ). After you’ve spent months on a painstaking new design, who wants to be told what color blue to use? It takes some getting used to for most designers, though.

San Francisco 154

San Francisco Lean Metrics Design 154

SVPG

JULY 31, 2013

While I am currently a passionate advocate of methodologies like Agile, Lean, Design Thinking, Customer Development and more, I try very hard not to get too attached to, or to be too closely associated with, any particular school of thought or technique. Then of the people and teams I work with. I could go on.

SCRUM 60

SCRUM Continuous Deployment Agile Lean 60

Startup Lessons Learned

JUNE 17, 2010

The artists on the team had called in the big guns, and VP-level folks were there to explain the importance of certain aspects of the visual design that threatened to be cut. Case Study: Continuous deployment makes releases n. I was invited to a feature decision meeting, where the team was closing in on a detailed spec.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

JULY 2, 2009

Five Whys is designed to avoid these nebulous arguments. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. In fact, even the investigation itself is considered too much work.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

AUGUST 3, 2009

Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Revisiting the Software Design Manifesto (and what. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

DECEMBER 16, 2009

Those who are interested in work-in-process might want to take a look at Work in small batches and Continuous deployment - Eric) Some specific TPS practices appear in Lean Startups. A/B testing is set-based design. A/B testing is set-based design. Case Study: Continuous deployment makes releases n.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

Startup Lessons Learned

JUNE 22, 2009

Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Pivot, don't jump to a new vision Why Continuous Deployment? Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

DECEMBER 14, 2009

I had a lot of use for this concept back when I worked on game design and virtual worlds. In order to maintain game play balance, game designers have to take into account the needs of customers who have an excess of four different assets: time , money , skill , and passion. Having a balanced ecosystem is what game designers strive for.

Customer 156

Customer San Francisco Viral Lean 156