Startup Lessons Learned

APRIL 18, 2013

. * As you''re refining your talk idea, bear in mind this IMPORTANT point: when we refer to "the Lean Startup," we mean specifically the set of ideas that Eric and others have articulated for testing, validating, and learning quickly. and we are NOT looking for talks about how to bootstrap or run a business on the cheap. *

Lean 167

Lean San Francisco Startup Continuous Deployment 167

Startup Lessons Learned

APRIL 29, 2013

Now, “lean” is often used to refer to a company’s financial situation, so it might make you think of a bootstrapped or under-funded organization. But when we talk about “lean,” we’re referring to the processes a company can use, when developing a new product or service, to learn quickly about the questions it has.

Lean 165

Lean Technical Review Startup Software Review 165

Startup Lessons Learned

MARCH 29, 2010

These case studies range in size and scope: from pre-product/market fit to already exited, bootstrapped to venture-backed, solo practitioner to large organization. Doesnt the communication overhead of a large team lead to chaos of overlapping experiments and continuously-deployed bugs?" "If Were in pursuit of the truth, not orthodoxy.

San Francisco 120

San Francisco Lean Continuous Deployment DC 120

Startup Lessons Learned

APRIL 14, 2009

extraneous SHIMMER reference spotted; you are dating yourself eric. People talk about funding funding funding, bootstrapping, etc., Transitioning from founder sold bootstrapped revenue to a functioning sales team is certainly possible. Case Study: Continuous deployment makes releases n. Great Post on Start Ups.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

APRIL 18, 2010

Lean, when used in the context of lean startup, refers to a process of building companies and products using lean manufacturing principles applied to innovation. And they can benefit from the speed and discipline of starting with a minimum viable product and then learning and iterating continuously.

Lean 167

Lean San Francisco Continuous Deployment Startup 167

www.subelsky.com

FEBRUARY 25, 2010

This tool adds a lot of context to bug discussions, because nonprogrammers can reference the exact Hoptoad URL containing all of the information a programmer needs to fix a bug (including backtraces). Because it has an RSS feed, one could also use "Unresolved Hoptoad Errors" as a metric influencing the continuous deployment system.

Lean 41

Lean Baltimore Ruby Maryland 41