Startup Lessons Learned

OCTOBER 5, 2008

But I have a special sympathy for the "product manager" in a startup that is bringing a new product to a new market, and doing their work in large batches. Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more. No departments The Five Whys for Startups (for Harvard Business R.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

JULY 29, 2009

I hope to show why lean and agile techniques actually reduce the negative impacts of technical debt and increase our ability to take advantage of its positive effects. 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

DECEMBER 14, 2017

Guest Post by Misti Yang, Writer for Lean Startup Co. Editor’s Note: We wrapped up the 2017 Lean Startup Week in San Francisco just a few weeks ago, and we’re excited to share with you some of the best lessons learned in entrepreneurship and corporate innovation. Because these Lean Startup people, they do crazy stuff,” Alex joked. “So

Lean 245

Lean Startup CTO Hire Cofounder 245

Startup Lessons Learned

NOVEMBER 18, 2008

Its even more critical in lean startups when they need to manage growth. At IMVU , we called this person a Producer (revealing our games background); in Scrum , they are called the Product Owner. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Expo SF (May. . Expo SF (May.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

MAY 25, 2020

13:58) Advice for companies who think it's too late to start looking for new ways to operate, including some examples from Austin, Texas. (15:55) So now I'm home-based in Austin, Texas and I'm spending a lot of time with a lot of startups and a lot of CEOs that are trying to scale their companies. Let's go."

Technical Review 148

Technical Review Balance Sheet Texas Austin 148

Startup Lessons Learned

APRIL 9, 2009

MarkH : Key takeaways from Erics great talk #w2e #leanstartup 1) "building a culture to learn " @ericries Marks point is the one that seems to have had the biggest impact from the talk as a whole: that startups should be built to learn. The lean startup focuses on situations where we have both an unknown problem and an unknown solution.

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

Startup Lessons Learned

DECEMBER 6, 2008

Lessons Learned by Eric Ries Saturday, December 6, 2008 The four kinds of work, and how to get them done: part three Those startups that manage to build a product people want have to deal with the consequences of that success. And still being a startup means continuing to innovate as well as keep the lights on.

San Francisco 74

San Francisco SCRUM Lean Continuous Deployment 74

SVPG

JUNE 5, 2015

This is usually where Agile finally enters the picture. Anyway, the engineers will typically break up the work into a set of iterations - called “sprints” in the Scrum process. In fairness to the engineers, they’re typically doing about as much Agile as they can given the broader Waterfall context.

Product 60

Product Agile Engineer SCRUM 60

www.vccafe.com

MARCH 11, 2013

Startup Resources (Updated Mar 2013). Venture Capital Cafe > Startup Resources (Updated Mar 2013). VC & Startup Resources. Seed Startups. VC Cafe covers early stage Israeli and European tech & mobile startups. Hundreds of startups featured since 2005, will yours be next? About VC Cafe.

Software Review 53

Software Review Technical Review Startup 53