Startup Lessons Learned

MARCH 24, 2009

Lessons Learned by Eric Ries Tuesday, March 24, 2009 The metrics and levers of engagement, presentation on Engagement Loops for Facebook Developer Garage SF Ill be presenting a talk at the Facebook Developer Garage SF Wednesday evening. Unfortunately, its easy to lose track of positioning effects when optimizing for a single metric.

Metrics 88

Metrics San Francisco Lean Viral 88

Startup Lessons Learned

AUGUST 3, 2009

In a lot of cases, this requires a lot of energy invested in talking to customers or metrics and analytics. Refreshing to finally see lean and agile thinking emerge in product/business-floors and not only in technology. In fact, MVP is quite annoying, because it imposes extra overhead. Thank you. August 13, 2009 3:43 AM Robert said.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

JUNE 2, 2010

As start-ups scale, this agility will be lost unless the founders maintain a consistent investment in that discipline. Two Ways to Hold Entrepreneurs Accountable Beware of Vanity Metrics For Startups, How Much Process Is Too Much? Start-ups supposedly dont have time for detailed processes and procedures. Speed up or slow down?

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

SEPTEMBER 7, 2008

In addition to presenting the IMVU case, we tried for the first time to do an overview of a software engineering methodology that integrates practices from agile software development with Steves method of Customer Development. Still, I thought Id share this email that happened to arrive during class. Sure, Id be delighted to.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

SEPTEMBER 22, 2008

Master of 500 Hats: Startup Metrics for Pirates (SeedCamp 2008, London) This presentation should be required reading for anyone creating a startup with an online service component. He also has a discussion of how your choice of business model determines which of these metric areas you want to focus on. Choose one. Expo SF (May.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

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. You can also download our presentation, " Just-In-Time Scalability: Agile Methods to Support Massive Growth." Expo SF (May.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

SEPTEMBER 15, 2008

But by taking advantage of open source, agile software, and iterative development, lean startups can operate with much less waste. So far, I have found "lean startup" works better with the entrepreneurs Ive talked to than "agile startup" or even "extreme startup.") Of course, many startups are capital efficient and generally frugal.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Startup Lessons Learned

APRIL 9, 2009

Thats the essence of so many of the lean startup techniques Ive evangelized: customer development , the Ideas/Code/Data feedback loop , and the adaptation of agile development to the startup experience. Creating a company-wide feedback loop that incorporates both customer development and agile development is a challenge.

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

Startup Lessons Learned

JANUARY 30, 2009

This is why agility is such a prized quality in product development. Departments were built and were even metrics-driven. But there was no feedback loop to help the company find the right metrics to focus on. Labels: agile , customer development 5comments: William Pietri said. Even a great architecture becomes inflexible.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

FEBRUARY 28, 2009

This builds on a lot of great thinking that has come before, like the agile movements insistence that only the creation of working code counts as progress for a software development team. I used to think that investments in metrics were a form of waste. I used to think that investments in metrics were a form of waste.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

MARCH 25, 2010

Two Ways to Hold Entrepreneurs Accountable Beware of Vanity Metrics For Startups, How Much Process Is Too Much? Two Ways to Hold Entrepreneurs Accountable Beware of Vanity Metrics For Startups, How Much Process Is Too Much? Read the rest of The Startups Rules of Speed - The Conversation - Harvard Business Review. Expo SF (May.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

DECEMBER 16, 2009

For those whove heard it, it contains a length discourse on the subject of agile software development and extreme programming, including its weaknesses when applied to startups. As Im pontificating about agile, I see the name Kent Beck in my peripheral vision. Now, this webcast was packed, hundreds of people were logged in.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

Startup Lessons Learned

NOVEMBER 4, 2008

Boyd emphasized the importance of agility in combat: "the key to victory is to be able to create situations wherein one can make appropriate decisions more quickly than ones opponent." Agile software development. Agile allows companies to build higher quality software faster. This speeds up the Ideas-Code-Data feedback loop.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

JULY 13, 2009

Lessons Learned by Eric Ries Monday, July 13, 2009 The Principles of Product Development Flow If youve ever wondered why agile or lean development techniques work, The Principles of Product Development Flow: Second Generation Lean Product Development by Donald G. Reinertsen is the book for you. Thanks for the informative review. Expo SF (May.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

OCTOBER 5, 2008

They exchange countless emails, and hes being constantly interrupted and being asked to clarify exactly what the spec means. The fourth spec exists only in these emails, which are changing the design in an ad-hoc fashion. Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

NOVEMBER 13, 2008

Once that responsibility has been assigned, have that new person email the whole company with the results of the analysis. Each five whys email is a teaching document. Wed never heard of five whys, and we had plenty of "agile skeptics" on the team. This last step is difficult, but I think its very helpful.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Austin Startup

NOVEMBER 28, 2017

I interviewed ten, Austin-based CEOs and top executives about their daily routines in order to glean which habits and rituals have supported their success. It’s easy to get caught up in the barrage of emails, Slack messages, texts and calls, so a couple mornings a week, I start offsite at a coffee shop.

Austin 79

Austin Agile Restful Early Stage 79

Startup Lessons Learned

SEPTEMBER 10, 2008

Lessons Learned by Eric Ries Wednesday, September 10, 2008 Smarticus — 10 things you could be doing to your code right now Smarticus — 10 things you could be doing to your code right now A great checklist of techniques and tools for making your development more agile, written from a Rail perspective. Expo SF (May.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

NOVEMBER 7, 2008

Finally the day came, we unleashed the landing page, emailed our existing customers, and started advertising online. Depending on the type of product, postings on forums, classifieds and emails could give enough information to help gauge potential response. We finally settled on a $1.99 November 8, 2008 8:44 AM OneDish said.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

JUNE 22, 2009

Each has its own iterative process: customer development and agile development respectively. Leading up to a pivot, each cycle, despite our best efforts, the metrics werent good enough. And the two teams are joined together into a company-wide feedback loop that allows the whole company to be built to learn. It was painful.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

FEBRUARY 10, 2009

Heck, thats what it says right there in the agile manifesto. Luckily, Chad Austin has recently weighed in with an excellent piece called 10 Pitfalls of Dirty Code. Labels: agile , continuous deployment , lean startup , product development , Test-driven development 4comments: Nivi said. But it worked. We made it. So can you.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

AUGUST 2, 2008

0comments: Post a Comment Newer Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) . Expo SF (May. Want to learn more about me?

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

JULY 30, 2009

In 2002 I became exposed to the idea of “agile software development&# and subsequently was a first round investor in Rally Software which is now the market leader in Agile application lifecycle management software. July 30, 2009 7:35 AM Hazem Awad said. Expo SF (May. Conference streaming, sponsors, discounted tickets.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

MARCH 17, 2009

Although Im not a developer, I am captivated by the lean and agile start-up model that you write about. Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? Expo SF (May.

Lean 76

Lean San Francisco Web Continuous Deployment 76

Startup Lessons Learned

OCTOBER 4, 2008

Although Catalyst folded with the dot-com crash, Ries continued his entrepreneurial career as a Senior Software Engineer at There.com, leading efforts in agile software development and user-generated content. Please email me if you are interested. While an undergraduate at Yale Unviersity, he co-founded Catalyst Recruiting.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

FEBRUARY 9, 2009

It uses principles of agile software development, open source and web 2.0, If youd like to give feedback, feel free to post comments here, or get in touch on LinkedIn , Facebook , or try to beat the spam filter on email. Hey Someone else who is extending the agile/lean approach beyond just developing software. Expo SF (May.

Lean 68

Lean San Francisco Web Advisory Board 68

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. They are on-schedule and on-budget, but their gross metrics are way off. They are on-schedule and on-budget, but their gross metrics are way off. Read the rest here.

Hockey Stick 105

Hockey Stick San Francisco Entrepreneur Lean 105

Startup Lessons Learned

SEPTEMBER 2, 2008

Labels: agile , listening to customers 3comments: hauteroute said. Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? Split-test experiments that go on forever?

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

FEBRUARY 8, 2010

Lessons Learned by Eric Ries Monday, February 8, 2010 Beware of Vanity Metrics (for Harvard Business Review) The next article in my series on entrepreneurship for Harvard Business Review is live today. Once again, we revisit the topic of Actionable metrics and their nemesis: Vanity metrics. Remember "metrics are people, too."

Metrics 121

Metrics San Francisco Lean Continuous Deployment 121

Startup Lessons Learned

NOVEMBER 17, 2008

Growth - when you have existing customers, the pressure is on to grow your key metrics day-in day-out. Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? Expo SF (May.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

AUGUST 26, 2009

Inspiring ideas: real-time biz metrics; safe continuous deployment; A/B split testing. Thank you @ericries for drastically altering my perception of agile startup Thank you all so much for your kind words. Articulate, inspirational. jdegoes : Great talk from @ericries last night. Learned a lot and enjoyed the discourse. Expo SF (May.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

SEPTEMBER 12, 2008

You might get a bunch of inbound emails from other press and partners, and all of these things can contribute to a feeling that you’re on your way to getting tons of traffic. It’s easy to overestimate the impact of this kind of traffic because it just feels good to have your name and company featured. It strokes your ego.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

JANUARY 12, 2010

For the many entrepreneurs that send me cold emails asking for me to review a business plan or answer a strategic dilemma: Im much more likely to answer if youve already tried getting an answer on the mailing list. Youll probably get a better result, anyway. Youll probably get a better result, anyway. Expo SF (May.

Lean 146

Lean San Francisco Wiki Startup 146

Startup Lessons Learned

JANUARY 7, 2010

blog comments powered by Disqus Newer Post Older Post Home Subscribe via email Blog Archive ▼ 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) . Read the rest at The Conversation - Harvard Business Review.

San Francisco 119

San Francisco Management Continuous Deployment Lean 119

Startup Lessons Learned

OCTOBER 11, 2009

Every experiment has to be evaluated based on a single standard report of 5-10 (no more) key metrics. Any team that creates an experiment must monitor the metrics and customer reactions (support calls, forum threads, etc) while the experiment is in-progress, and abort if something catastrophic happens. It promotes rapid iteration.

San Francisco 133

San Francisco Lean Metrics Continuous Deployment 133

Startup Lessons Learned

MAY 31, 2010

Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? Expo SF (May. Conference streaming, sponsors, discounted tickets. Learning is better than optimization (the local ma.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

JUNE 8, 2009

That’s because many of our reports feed us vanity metrics: numbers that make us look good but don’t really help make decisions. Yet even among those who have access to good actionable metrics, I’ve noticed a phenomenon that prevents taking maximum advantage of data. Too much of this data is non- actionable.

San Francisco 84

San Francisco Lean Continuous Deployment DC 84