Startup Lessons Learned

MARCH 29, 2010

These are the big questions Ive heard over and over again as Ive traveled presenting the lean startup methodology: "Sure, sounds great for a five-person team, but how can such a fast-paced development process scale? Doesnt the communication overhead of a large team lead to chaos of overlapping experiments and continuously-deployed bugs?" "If

San Francisco 120

San Francisco Lean Continuous Deployment DC 120

Startup Lessons Learned

JUNE 8, 2009

So the product development team was busy creating lots of split-tests for lots of hypotheses. That’s causing the Product Owner and team to spend more time with each other reviewing the results of experiments, which is allowing them to learn and iterate much faster. Case Study: Continuous deployment makes releases n.

San Francisco 84

San Francisco Lean Continuous Deployment DC 84

Startup Lessons Learned

FEBRUARY 22, 2009

We also learned that law is code , and that leadership was needed to build thriving communities in a digital age. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Expo (and a call for he.

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

JANUARY 19, 2009

You are doing the startup community a great service by sharing your insights via your blog. Particularly the Continuous Deployment and Split testing posts. Case Study: Continuous deployment makes releases n. Labels: hiring , lean startup 4comments: Tamar said. This post has been removed by the author.

Lean 140

Lean Hiring San Francisco Continuous Deployment 140

Startup Lessons Learned

JANUARY 12, 2009

The number one reason I keep coming back to PHP is that it has overwhelming community support. Ive written elsewhere that success in creating a platform is "becoming a function not of the size and resources of the company that builds it, but of the size of the community that supports it." Lets start with some circular reasoning.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

MAY 14, 2009

Im open to being the coffee and snack technician :-) On another note, I live in Atlanta and believe that we have a strong enough start-up community that would greatly benefit from your lessons learned. I have contacts within the university and entrepreneurial communities and would be happy to help you set up something if interested.

Lean 60

Lean San Francisco Continuous Deployment Software Review 60

Startup Lessons Learned

SEPTEMBER 8, 2009

So heres my simple question: What do folks in Washington need to know about the global community of entrepreneurs? I'll add two ideas: The modern structure of university patent licensing and technology transfer works really well in the life sciences and other fields with expensive product development processes.

DC 90

DC Washington San Francisco SBIR 90

Startup Lessons Learned

DECEMBER 14, 2009

And passionate players are often the backbone of game communities – especially online. A great product enables customers, developers, partners, and even competitors to exchange their unique currencies in combinations that lead to financial success for the company that organizes them.

Customer 156

Customer San Francisco Viral Lean 156

Startup Lessons Learned

MARCH 3, 2009

You can still see these early manifestos thanks to the wayback machine: [link] [link] We did that not just out of principle but because it served a very specific purpose: giving early adopters in our community a reason to invest in our success and give us strong feedback. Case Study: Continuous deployment makes releases n.

Employee 146

Employee San Francisco Lean Software Review 146

Startup Lessons Learned

AUGUST 24, 2009

When I reviewed a recent product development book, it immediately shot up to Amazon sales rank 300. Make it easy to “pilot&# new work with a test community of actively engaged readers, and provide a mechanism for measuring the impact of these pilots. Case Study: Continuous deployment makes releases n.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

NOVEMBER 5, 2008

We were building a community, open to anyone who shared its values, and that mission inspired volunteers and staff to try and reach out to as many people as possible. Case Study: Continuous deployment makes releases n. It would have been pretty easy for the volunteers and supporters to slow down, confident in victory.

Campaign 84

Campaign San Francisco Lean Agile 84

Startup Lessons Learned

OCTOBER 11, 2008

These decisions cause problems that will challenge you for years, if you are lucky enough to be successful with your product. As the size of your community and economy grows, youll be able to solve them as they arise, as long as you know what to look for. Case Study: Continuous deployment makes releases n.

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Startup Lessons Learned

SEPTEMBER 15, 2009

Lessons Learned by Eric Ries Tuesday, September 15, 2009 Testing the new Disqus comment system The recent and overwhelming influx of comments on The cardinal sin of community management. Testing the new Disqus comment system The recent and overwhelming influx of comments on The cardinal sin of community management.

San Francisco 84

San Francisco DC Continuous Deployment Lean 84

Startup Lessons Learned

FEBRUARY 7, 2013

The Embrace infant warmer was developed - by getting out of the country -- and how Rob Emrich learned and scaled his non-profit, Road of Life. BetaBrand building apparel MVPs and testing them quickly with targeted customer communities. A nascent community has blossomed into a full-fledged movement.

Lean 167

Lean Entrepreneur Agile San Francisco 167

Startup Lessons Learned

SEPTEMBER 14, 2009

We'll have IDCEE conf on October 28-29, [link] If you could come any other day we'll organize small event at #kievstartup community. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

San Francisco 84

San Francisco DC Finland Washington 84

Startup Lessons Learned

SEPTEMBER 28, 2009

Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, and more ► January (6) Lo, my 18891 subscribers, who are you?

San Francisco 103

San Francisco Lean DC Continuous Deployment 103

Startup Lessons Learned

SEPTEMBER 3, 2009

Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, and more ► January (6) Lo, my 18891 subscribers, who are you?

San Francisco 104

San Francisco DC Continuous Deployment Lean 104

Startup Lessons Learned

AUGUST 8, 2009

In particular, we would cover customer development, continuous deployment, minimum viable product, and actionable metrics. Thanks for all that you have done to help the startup community! Case Study: Continuous deployment makes releases n. August 9, 2009 10:28 AM Chris said. I love the business model.

Lean 102

Lean Programming San Francisco Continuous Deployment 102

Startup Lessons Learned

SEPTEMBER 9, 2009

Why Continuous Deployment? * Minimum Viable Product: a guide You can see and even install the Top Posts widget yourself if you like (simple install for blogger blogs): [link] Not bad, dude. Case Study: Continuous deployment makes releases n. As for top posts we have: * 10.0 Don't launch * 8.9

San Francisco 84

San Francisco Continuous Deployment Lean DC 84

Startup Lessons Learned

JANUARY 27, 2009

We're keeping ourselves free for the community that has helped us build our product; premium vs basic seems wrong to us. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

San Francisco 148

San Francisco Lean Continuous Deployment DC 148

Startup Lessons Learned

SEPTEMBER 19, 2009

Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, and more ► January (6) Lo, my 18891 subscribers, who are you?

San Francisco 150

San Francisco Founder DC Washington 150

Startup Lessons Learned

SEPTEMBER 15, 2009

Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, and more ► January (6) Lo, my 18891 subscribers, who are you?

San Francisco 92

San Francisco DC Washington Lean 92

Startup Lessons Learned

NOVEMBER 22, 2008

Theres a lot of controversy surrounding NPS in the customer research community, and I dont want to recapitulate it here. Even if you have a very large community, I dont think this number needs to be higher than 100. In other words, we committed the one cardinal sin of community management. Heres how Ive set it up in the past.

.Net 158

.Net Operations San Francisco Lean 158

Startup Lessons Learned

NOVEMBER 19, 2008

I would recommend periodic surveys, along with some kind of forum or other community tool where the most passionate customers can congregate. Im Community Manager at VenCorps, co-host of commandN. Case Study: Continuous deployment makes releases n. Either way, Ive been a happy subscriber ever since.

San Francisco 60

San Francisco Lean Continuous Deployment DC 60