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. Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

NOVEMBER 14, 2013

Guest post by Lisa Regan, writer for T he Lean Startup Conference. We’ve posted the full program for The Lean Startup Conference , and it includes more than three days of events for Gold pass holders and six days of events for VIP pass holders. On the evening of December 8, Ignite Lean Startup kicks off the conference.

Continuous Deployment 162

Continuous Deployment Norway Lean Analytics 162

Startup Lessons Learned

OCTOBER 20, 2008

Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their product development process. And this was a huge product, which took years to develop.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

JANUARY 30, 2009

Even though some aspects of the product were eventually vindicated as good ones, the underlying architecture suffered from hard-to-change assumptions. Without conscious process design, product development teams turn lines of code written into momentum in a certain direction. Even a great architecture becomes inflexible.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

OCTOBER 5, 2009

It’s important to invest in good architecture so that your website will scale once customers arrive. If you make that investment, and then customers arrive, and the site stays up, most companies will reward the people who built the architecture and, thus, prevented the scaling problems. Why do they harbor that paranoia?

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

Startup Lessons Learned

SEPTEMBER 2, 2008

We wanted an agile approach that would allow us to build our software architecture as we needed it, without downtime, but also without large amounts of up-front cost. After all, the worst kind of waste in software development is code to support a use case that never materializes. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

JUNE 17, 2010

Even more surprisingly, the engineering team was equally vocal about their contention that adding rounded corners would add weeks of development time to the project, which would have pushed it out way past its hard deadline, effectively killing it. The engineering team wasn’t happy either. The engineering team wasn’t happy either.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

YoungUpstarts

APRIL 14, 2014

Not too long ago, German software giant SAP blew up the management framework for its 20,000-person development department and replaced it with “mini-teams” of roughly 10 people. As a result, product development time was cut nearly in half in a three-year period.

Agile 196

Agile Leadership Architecture Product Development 196

Startup Lessons Learned

JANUARY 4, 2009

Lessons Learned by Eric Ries Sunday, January 4, 2009 Sharding for startups The most important aspect of a scalable web architecture is data partitioning. So far, this is just a summary of what all of us who have attempted to build web-scale architectures considers obvious. Support multiple sharding schemes. Easy to understand.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

NOVEMBER 29, 2008

The technical interview is at the heart of these challenges when building a product development team, and so I thought it deserved an entire post on its own. and going into a long diatribe about how insecure the ActiveX architecture was compared to Javas pristine sandbox. what happens if we have a pipelined architecture?

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

JUNE 15, 2009

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. One large source of waste in development is “double-checking.&#

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

AUGUST 8, 2009

And as Kapor himself points out, the core ideas have even older origins: The Roman architecture critic Vitruvius advanced the notion that well-designed buildings were those which exhibited firmness, commodity, and delight. Yet a huge class of modern software projects are being developed in a very different context.

Software Review 87

Software Review Design Software San Francisco 87

Steve Blank

MAY 28, 2009

Market Risk vs. Invention Risk - Click to Enlarge For companies building web-based products, product development may be difficult, but with enough time and iteration engineering will eventually converge on a solution and ship a functional product - i t’s engineering, not invention.

Vertical 144

Vertical Silicon Valley Marketing Customer 144

Startup Lessons Learned

DECEMBER 7, 2008

I know them right away - we can talk high-level architecture all the way down to the bits-and-bytes of his system. When the architecture needs modifying - why do we need a meeting? Building a good application architecture is not just coding. The "just fix it" mentality is counter-productive here. Just change it.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

NOVEMBER 13, 2008

Wanted to add one additional note from the perspective of someone who was intimately involved in developing this system. It seems your cluster architecture is one of the key architectural constraints making continuous deployment possible. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Hearpreneur

APRIL 13, 2022

One of the most important lessons entrepreneurs can learn from Dropbox is to adopt the lean start-up methodology and start. He has been instrumental in the development of artificial intelligence and machine learning, which are key areas of focus for Google. Thanks to Fletcher Wimbush, The Hire Talent ! #2- 2- Dropbox. 17- Improbable.

Artificial Inteligence 78

Artificial Inteligence Entrepreneur Technical Review Software Review 78

Startup Lessons Learned

JANUARY 28, 2009

Its an essential discipline of good software development, especially in startups. The engineering team has decided its reached a breaking point, and is taking several weeks to bring it up to modern standards, including unit tests, getting started with continuous integration , and a new MVC architecture. Doesnt that sound good?

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

Startup Lessons Learned

AUGUST 14, 2013

Guest post by Lisa Regan, writer for The Lean Startup Conference, who has created content for a number of startups. In our ongoing exploration of how people actually implement Lean Startup methods in their workplaces, we’re asking practitioners to share their techniques. Steph: Segmentation and timing. Steph: For me, it leads.

Lean 167

Lean Conversion Audience Design 167

Startup Lessons Learned

DECEMBER 28, 2009

Thats a perfectly reasonable reaction, given that most releases of most products are bad news. Even worse, the sad state of product development generally means that the new "features" are as likely to be ones that make the product worse, not better. In a successful startup, the development team is also growing.

Continuous Deployment 122

Continuous Deployment San Francisco Lean Metrics 122

Steve Blank

JUNE 25, 2009

They couldn’t keep up with the fast product development times that were enabled by using standard microprocessors. So their management teams were insisting that they OEM (buy from someone else) these products. The answer depends on your answer to two questions: which step in the Customer Development process are you on?

Technology 138

Technology Silicon Valley Fractional VPE Part-Time VPE 138

Startup Lessons Learned

SEPTEMBER 8, 2008

You dont need to invent a new architecture, and you dont need to even build your architecture up-front. You can turn your entire application infrastructure investment into a pay-as-you-go variable cost, and bring new products to market at speeds an order of magnitude faster than just 10 years ago. yeah, its awesome.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

Startup Lessons Learned

FEBRUARY 16, 2009

This is a great example of lean startup thinking. This is one of the most powerful aspects of web architecture, and it often gets lost in other client-server programming paradigms. As you suggest, Thought Experiment Part II is going to involve lots of changes to the classic MMO architecture that makes it more like the web.

Continuous Deployment 68

Continuous Deployment San Francisco Software Review Lean 68

Startup Lessons Learned

SEPTEMBER 8, 2009

Beyond just those who will be hearing about the lean startup for the first time, Im expecting to shake a lot of hands and have a lot of interesting side conversations. Government IT solutions can be iterative, they don't have to be designed down to the last detail by architecture astronauts before implementation. Halling said.

DC 90

DC Washington San Francisco SBIR 90

Up and Running

AUGUST 4, 2016

If your construction tastes lean toward the more aesthetic, check out Contract. This publication puts the spotlight on commercial interior design and architecture, an angle most other sites don’t take. Read the blog, or subscribe to the magazine here. Construction Enquirer.

United States 60

United States Architecture America Lean 60

andrewchenblog.com

MARCH 10, 2010

If you haven’t finished developing your product yet, that’s no excuse! In fact, in many ways talking to your customer and understanding them great detail is often much more powerful before you even go through the product development process. Choice architecture is among the most complex worlds one could study.

Customer 42

Customer Advisory Board RSS Software Review 42

Seeing Both Sides

AUGUST 3, 2012

The Lean Start-Up movement, as exemplified in Eric Ries' book The Lean Start-Up, has appropriately focused a great deal of attention on the hard decisions and techniques required to create a company from nothing. This is the magic of what Akamai and other multi-product companies achieve as they scale. Akamai: The Present.

Distribution 49

Distribution Lean Massachusetts Cofounder 49

techcrunch.com

OCTOBER 23, 2010

Like I said, forget everything else and just get your product out the door. Inevitably, the excuses begin: I need to hire people to build the product. I don’t know any developers. How do you know which designer/developer to choose? I need money for the servers. Looking forward to reading your next post!

Technical Review 84

Technical Review Cofounder Technical Cofounder Software Review 84

ConversionXL

SEPTEMBER 10, 2012

“ There are no facts inside your building, so get outside ,” is one of the mantras of Steve Blank , the father of customer development and author of The Startup Owner’s Manual. In Lean Startup methodology, it’s called a pivot. Talk to people. Here’s a summary of 10 types of pivots.

Audience 122

Audience Analytics B2B eCommerce 122