Startup Lessons Learned

OCTOBER 7, 2016

Guest post by Jennifer Maerz, contributing editor of Lean Startup Co. It’s been exciting to watch the Lean Startup movement grow from a practice utilized in the tech world to one implemented in a wide variety of sectors ranging from enterprise to education, religious organizations, nonprofits, and government groups.

Government 165

Government Lean Startup San Francisco 165

YoungUpstarts

MAY 29, 2017

The Lean Startup.”. Agile Methodology.”. Combine this with the fact that third-party code or library integration is almost unavoidable these days. It should be noted that writing good code is an art unto itself and we will not delving deeply into that for this article. Fail Fast, Pivot.”. Testing and Verification.

Security 206

Security Software Review Technical Review Agile 206

Startup Lessons Learned

DECEMBER 8, 2008

Integration risk is the term I use to describe the costs of having code sitting on some, but not all, developers machines. It happens whenever youre writing code on your own machine, or you have a team working on a branch. It also happens whenever you have code that is checked-in, but not yet deployed anywhere.

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136

Startup Lessons Learned

OCTOBER 5, 2008

Each specialist takes up his part of the spec (UI, middleware, backend) and cranks out code. So the product manager winds up actually having to use the software, by hand, updating the spec and helping create a new test plan. In exchange, the team agrees to show each piece of working code to the product manager for his approval.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

JUNE 15, 2009

Of all the tactics I have advocated as part of the lean startup , none has provoked as many extreme reactions as continuous deployment , a process that allows companies to release software in minutes instead of days, weeks, or months. When a developer wants to check-in code, this is a very scary moment.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

FEBRUARY 20, 2009

Lessons Learned by Eric Ries Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. I owe it originally to lean manufacturing books like Lean Thinking and Toyota Production System. For software, the easiest batch to see is code.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

NOVEMBER 6, 2008

Lessons Learned by Eric Ries Thursday, November 6, 2008 Steveys Blog Rants: Good Agile, Bad Agile I thought Id share an interesting post from someone with a decidedly anti-agile point of view. Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

Steve Blank

FEBRUARY 25, 2010

In my book, “ The Four Steps to the Epiphany ” I use enterprise software as the business model example. His two key slides are at the end of this post but the details on his blog are worth reviewing. Agile Development is the way startups quickly iterate their product as they learn. I think his process models are pretty good.

Customer Development 274

Customer Development Web Developer Customer 274

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. But there is more to technical debt than just the interest payments that come due. The failure of the feature had nothing to do with the quality of the code.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

AUGUST 3, 2009

Lessons Learned by Eric Ries Monday, August 3, 2009 Minimum Viable Product: a guide One of the most important lean startup techniques is called the minimum viable product. I was delighted to be asked to give a brief talk about the MVP at the inaugural meetup of the lean startup circle here in San Francisco. Thanks Eric.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Up and Running

DECEMBER 6, 2012

Today, I want to introduce you to a new concept for starting and growing successful companies: Lean Planning™. Before I dive too deeply into the Lean Planning methodology, it makes sense to talk about its history and where it comes from. Lean Planning is born. Flesh out the specifics with more detailed planning (as necessary).

Lean 147

Lean Silicon Valley Forecast Technical Review 147

Startup Lessons Learned

MARCH 25, 2010

for Harvard Business Review) Over at Harvard Business Review, Ive been building up a series designed to introduce the Lean Startup methodology to a business-focused audience. Defective prototype code was as often thrown out (because customers didnt want it) as it was fixed (when customers did).

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Both Sides of the Table

NOVEMBER 1, 2009

I know that this all seems obvious now with the movements started by Steven Blank ( Four Steps of Epiphany ) with the whole Customer Development processes / Lean Startup movements also popularized by people like Eric Ries. I know that their are independent software companies now focused on this like UserVoice and Get Satisfaction.

Customer 280

Customer Technical Review Software Review Mexico 280

Startup Lessons Learned

AUGUST 30, 2008

Lessons Learned by Eric Ries Saturday, August 30, 2008 Refactoring for TDD and interaction design In TDD , we follow a rhythm of “test-code-refactor.&# The Lean Startup Intensive is tomorrow at Web 2.0. This basic pattern is useful in all aspects of product development. This process is called refactoring.

Software Review 74

Software Review San Francisco Design Continuous Deployment 74

Startup Lessons Learned

FEBRUARY 11, 2009

Lessons Learned by Eric Ries Wednesday, February 11, 2009 The free software hiring advantage This is one of those startup tips Im a little reluctant to share, because its been such a powerful source of competitive advantage in the companies Ive worked with. Especially for a startup, not taking maximum advantage of free software is crazy.

Software Review 68

Software Review Software Hiring San Francisco 68

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

SEPTEMBER 15, 2008

Lessons Learned by Eric Ries Monday, September 15, 2008 The one line split-test, or how to A/B all the time Split-testing is a core lean startup discipline, and its one of those rare topics that comes up just as often in a technical context as in a business-oriented one when Im talking to startups. October 4, 2008 10:33 AM Amitt Mahajan said.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

A Smart Bear: Startups and Marketing for Geeks

APRIL 5, 2010

We're "lean" but we're not stirring hearts. I'm as excited as everyone else about Lean principles gaining traction, and sure most companies are erring on the side of too little objective feedback rather than too much. Code Historian was my first product. It was always a high point in product reviews. Here's its story.

Software Review 226

Software Review Metrics Lean Agile 226

Startup Lessons Learned

JULY 2, 2009

Lessons Learned by Eric Ries Thursday, July 2, 2009 How to conduct a Five Whys root cause analysis In the lean startup workshops , we’ve spent a lot of time discussing the technique of Five Whys. My intention is to describe a full working process, similar to what I’ve seen at IMVU and other lean startups.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

DECEMBER 7, 2008

When I want to know about some concurrency issues between services in his cluster, he doesnt blink an eye when I suggest we get the source code and take a look. Hes just as comfortable writing code as racking servers, debugging windows drivers, or devising new interview questions. He throws off volumes of code, and it works.

Software Review 94

Software Review Technical Review San Francisco Part-Time VPE 94

Startup Lessons Learned

JUNE 17, 2010

I was the junior guy on a project team; I was called in to do some technical due diligence for reasons that were obscure to me, because the team already had much more senior engineers assigned to it. And like feedback on a simple microphone sound system, this would occasionally boil over into screeching.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

MAY 7, 2009

Getting features and fixes into hands of users was the greatest priority - a test environment would just get in the way and slow down the validation coming from having code running in production. When a new engineer started at IMVU, I had a simple rule: they had to ship code to production on their first day. Heres the key point.

San Francisco 131

San Francisco Continuous Deployment Software Review Lean 131

Startup Lessons Learned

MARCH 3, 2009

At IMVU , these were quite common (after all, were shipping code 50 times a day). They are collected and reviewed after an appropriate interval (e.g. In response to Sean - Intel still runs a very formal process of setting expectations, evaluating employees and reviewing progress on a quarterly basis. love your openness at IMVU.

Employee 146

Employee San Francisco Lean Software Review 146

Startup Lessons Learned

MAY 31, 2010

Expo Intensive rocked, the mainstream media has started writing about the Lean Startup, and - most of all - the movement continues to grow and evolve. I went to the conference thinking that I was well grounded in the basics of the Lean Startup approach and that attendance would hone the edges of that understanding.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

AUGUST 8, 2009

Lessons Learned by Eric Ries Saturday, August 8, 2009 Revisiting the Software Design Manifesto (and whats changed since then) My recent article on technical debt and its positive uses generated a fair bit of controversy. The same might be said of good software. Here we have the beginnings of a theory of design for software.

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

FEBRUARY 22, 2009

See Paul Grahams Why Nerds are Unpopular to learn more) Take a look at this article on a programming Q&A site: How old are you, and how old were you when you started coding? We also learned that law is code , and that leadership was needed to build thriving communities in a digital age. Can I send you a review copy?

Programming 143

Programming San Francisco Lean Continuous Deployment 143

ReadWriteStart

APRIL 8, 2023

In contrast, it left several e-trends: augmented reality, zero coding, the marketplace boom, and product subscriptions are just a few of them. So let’s reveal the e-commerce trends of 2022 and predict the trends for 2023, or, as we may say, crack the Da Vinci code. People love reviews, and everyone reads them before making a purchase.

eCommerce 185

eCommerce Technical Review Software Review Analytics 185

crowdSPRING Blog

APRIL 30, 2019

But, there’s plenty that you can do… if you embrace lean marketing principles. Lean marketing is a philosophy that emphasizes executing campaigns quickly, getting feedback from your audience, analyzing the results, and optimizing the campaign – all in rapid succession. National television campaigns are definitely out.

Lean 91

Lean Small Business Software Review Marketing 91

Up and Running

MAY 23, 2016

Since the term “cloud computing” was coined in 1996—at least as we have come to understand its meaning—the software as a service industry has exploded. Step 1: Start with a lean plan. I started UpKeep after seeing and using traditional enterprise software. Use your knowledge of an industry to solve a problem. “I

Software Review 74

Software Review Software Delaware Forecast 74

Startup Lessons Learned

JULY 5, 2010

When I wrote a review of Four Steps on this blog in November, 2008, I did my best to be candid and warn of a few shortcomings: And Steve is the first to admit that its a "turgid" read, without a great deal of narrative flow. Four Steps primarily centers its stories and case studies on B2B hardware and software startups.

Customer Development 166

Customer Development Developer San Francisco Customer 166

Startup Lessons Learned

MAY 14, 2009

Lessons Learned by Eric Ries Thursday, May 14, 2009 The Lean Startup Workshop - now an OReilly Master Class My rate of posting has been much lower lately, and this is mostly due to preparations for the upcoming Lean Startup Workshop on May 29. We changed our model to B2B and adopted Agile around 2002.

Lean 60

Lean San Francisco Continuous Deployment Software Review 60

Startup Lessons Learned

AUGUST 26, 2009

I did my best to capture video and audio; a YouTube playlist and Slideshare slidecast are below: Slides (with audio): 2009 08 19 The Lean Startup TechStars Edition View more presentations from Eric Ries. Im also excited to share two long-form reviews from actual attendees. More recently it's skewed to software & web.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

AUGUST 24, 2009

When I reviewed a recent product development book, it immediately shot up to Amazon sales rank 300. For example, the best book reviewers only review books published by the best publishers, which only accept manuscripts from the best agents. And how could they possibly review a blog? Is that a lot? Is that good?

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

MARCH 27, 2009

In lean times, it’s most important to focus on cutting costs in ways that speed you up, not slow you down. I believe it is a full, company-wide turn through the OODA loop (for a software business, see especially Ideas-Code-Learn ). And, of course, theres the Lean Startup session at the upcoming Web 2.0

San Francisco 117

San Francisco Lean Continuous Deployment DC 117

Up and Running

AUGUST 8, 2018

But, here at Palo Alto Software, we’ve found one meeting that is simply indispensable. It only takes an hour each month, keeps the management team up to speed on everything that’s going on in the company, and helps us plan and manage in a lean and effective way. This meeting is our monthly plan review meeting. Are we there yet?

Software Review 65

Software Review Business Plan Product Forecast 65

wordsting.com

APRIL 4, 2013

Rigorously simple copywriting for software products. Fat startup: Learn the lessons of my failed Lean Startup. by Word Sting in Lean Startup , Software copywriting , Copywriting for startups. Many software copywriters or developers dream of building their own company. April 1, 2013. My co-founders and I did.

Lean 61

Lean Startup Software Review San Francisco 61

Startup Lessons Learned

DECEMBER 14, 2009

For a consumer internet company in particular, this is often due to a lack of design thinking. These concepts have important implications for any lean startup. In an entrepreneurial situation, this is hard, because artifacts that we are creating (products, code, marketing campaigns, even revenue) are of secondary importance.

Customer 156

Customer San Francisco Viral Lean 156