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

JANUARY 15, 2010

Behind this analysis is a spreadsheet model, complete with detailed metrics for a set of customer behaviors that show just how valuable the new product will be. This whole framework breaks down when teams confront entrepreneurial situations in which theyre trying to build something new under conditions of extreme uncertainty.

Hockey Stick 105

Hockey Stick San Francisco Entrepreneur Lean 105

Startup Lessons Learned

JANUARY 12, 2009

Youll notice a pattern: most of the key features that enabled PHPs success are considered among its defects by experts in language design. Ironically, as PHP has grown up, its designers have been busy "fixing" these shortcomings. PHP can do what no other language or framework can (albeit django). and Rails as a web framework.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

OCTOBER 5, 2009

In the past, we invested in brilliant architecture, code reuse, refactoring, modular design, etc. One way to evaluate this fear is to spend time on analysis: how many customers will be affected? How upset will those customers be? In this framework, we’ll tend to either invest in the proposed prevention or do nothing.

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

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. The only efforts a new product team should be expending are those that lead to validated learning about customers. In the meantime, I hope some of you will find the lean startup a helpful framework.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

MARCH 25, 2009

It will probably be the first time Ill be able to take extensive Q&A on some of the new frameworks Ill be debuting at Web 2.0 The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Case Study: Continuous deployment makes releases n. Take a look and let me know what you think.

Agile 60

Agile Lean San Francisco Continuous Deployment 60

Startup Lessons Learned

APRIL 14, 2009

Their product development team is hard at work on a next-generation product platform, which is designed to offer a new suite of products – but this effort is months behind schedule. And yet their numbers continue to grow, month after month. (For Labels: agile , customer development 15comments: Scott Shapiro said.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

OCTOBER 6, 2008

Lessons Learned by Eric Ries Monday, October 6, 2008 When NOT to listen to your users; when NOT to rely on split-tests There are three legs to the lean startup concept: agile product development , low-cost (fast to market) platforms , and rapid-iteration customer development. Thats what business is designed to do.

San Francisco 128

San Francisco Lean Continuous Deployment Agile 128

Startup Lessons Learned

SEPTEMBER 22, 2008

Most engineers are terrible visual designers, but if the designer on their team is struggling, maybe they can help out with an icon or two. And wait until you see a "non-technical" designer writing simple code to try and speed up a release. Case Study: Continuous deployment makes releases n.

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68

Startup Lessons Learned

APRIL 26, 2009

But part was a recognition that we could gain substantial competitive advantage by leveraging a community of like-minded visionary customers to serve a wider (and more mainstream) audience than we could alone. Making UGC work requires good tools, open standards, and proper incentive design. Take a look and let me know what you think.

Product Development 88

Product Development Developer San Francisco Product 88

Startup Lessons Learned

DECEMBER 7, 2008

Even if, in a previous life, you were a world expert in some functional specialty, like in-depth market research or scalable systems design, the compressed timeline of a startup makes it irrelevant. These are two other Extreme Programming practices that are explicitly designed to counteract the problems inherent in this situation.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

MARCH 13, 2009

Do some Customer Development instead. I have wrestled with the way that companies use the "beta" designation to create an ostensible reason for a particular date being their "launch", even though the product has been publicly available for months. Case Study: Continuous deployment makes releases n.

San Francisco 168

San Francisco PR Lean Early Stage 168

Startup Lessons Learned

DECEMBER 7, 2008

Each experiment is like a little mystery, and if you can get into a mindset of open-mindedness about the answer, the answers will continually surprise and amaze you. A few days ago I open-sourced a framework for split-testing, A/B testing or continous optimization. Case Study: Continuous deployment makes releases n.

San Francisco 132

San Francisco Lean Continuous Deployment DC 132

Startup Lessons Learned

FEBRUARY 12, 2009

(a guide for hackers) (This post was inspired by a conversation with Nivi from Venture Hacks , but is otherwise not his fault) There has been a proliferation of frameworks and metaphors lately that are designed to help startups avoid the all-too-common fatal mistake of failing to find a market. Expo (and a call for he.

San Francisco 89

San Francisco Continuous Deployment Ruby Lean 89

Startup Lessons Learned

FEBRUARY 11, 2009

Having had a number of years to try and answer this question at cocktail parties and social gatherings of all kinds, I thought Id try and expand on his framework a little, and then try and use these answers to help make suggestions for those who are trying to get people to buy virtual goods. Case Study: Continuous deployment makes releases n.

San Francisco 102

San Francisco Continuous Deployment Lean DC 102

Startup Lessons Learned

MAY 1, 2009

Heres the working definition Ive started using: A startup is a human institution designed to deliver a new product or service under conditions of extreme uncertainty. Q: Does the Lean Startup framework work efficiently within a company of 2-3 people (think small)?" Case Study: Continuous deployment makes releases n.

Lean 60

Lean San Francisco Startup Continuous Deployment 60

Startup Lessons Learned

DECEMBER 16, 2008

But I think the value in this framework is that it can help make overall business decisions that require thinking about the whole rather than just one of the parts. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Case Study: Continuous deployment makes releases n.

Viral 140

Viral San Francisco Lean Continuous Deployment 140