Startup Lessons Learned

MAY 19, 2011

Jeff has been promoting the use of Lean UX as an effective method to spur greater innovation, quality and productivity in startups as well as within teams in larger organizations. Lean Startups need to make snap decisions, iterate quickly and pivot when needed. Levels of Agile adoption span the full spectrum across our 6 Scrum teams.

Lean 165

Lean Software Review SCRUM Non-Compete 165

Steve Blank

OCTOBER 30, 2012

The Lean LaunchPad Class. You may have read my previous posts about the Lean LaunchPad entrepreneurship class. The class teaches founders how to dramatically reduce their failure rate through the combination of business model design, customer development and agile development using the Startup Owners Manual. How it Works.

Startup 335

Startup Lean Incubator Business Model 335

Startup Lessons Learned

APRIL 4, 2010

Lessons Learned by Eric Ries Sunday, April 4, 2010 Kent Beck keynote, "To Agility, and Beyond" Kent Beck will give the opening keynote at the Startup Lessons Learned conference on April 23. Kent is a significant figure in the field of software development. To his credit are Extreme Programming , jUnit, patterns, TDD , the list goes on.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Startup Lessons Learned

SEPTEMBER 30, 2008

It became harder and harder to separate how the software is built from how the software is structured. If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? If not, whos going to insist we switch to free and open source software?

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

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

Steve Blank

APRIL 20, 2009

Most of the ability to create a radio industry in the 1920s was due to the accident of ionospheric radio propagation. Intercontinental radio was CW only (morse code) and all used spark gaps, alternators and arc converters through out the 1920s. The HP and Agilent credit union is called “Addison Avenue&#. to do that.

Silicon Valley 302

Silicon Valley RSS San Francisco Technical Review 302

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

Startup Lessons Learned

FEBRUARY 10, 2009

Our code pushes take another six minutes. Since these two steps are pipelined that means at peak we’re pushing a new revision of the code to the website every nine minutes. On average we deploy new code fifty times a day. Code reviews and pairing Great practices. Throwing out a lot of code.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

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

Steve Blank

OCTOBER 15, 2019

This article previously appeared in the Harvard Business Review. These processes reduce risk to an overall organization, but each layer of process reduces the ability to be agile and lean and – most importantly – responsive to new opportunities and threats. Process Versus Product.

Government 322

Government Technical Review Acquisition Metrics 322

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 Algorithm 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

AUGUST 2, 2008

Your natural tendency when an investor says yes will be to relax and go back to writing code. The Lean Startup Intensive is tomorrow at Web 2.0. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

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

SEPTEMBER 27, 2010

Over time, such teams either explode due to irreconcilable differences or dramatically slow down. As I found out to my dismay, this is a dangerous game: in many cases, you’re asking trained professionals to violate their own code of best practices, for the good of the company. Any excesses are likely to be moderated by others.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

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

OCTOBER 5, 2009

Due to an interaction effect between your hardware, solar flares, and quantum flux, this virus will crash your computer and erase your hard drive sometime soon. In the past, we invested in brilliant architecture, code reuse, refactoring, modular design, etc. In other words, a principled way to combine agility with stability.

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

The Startup Magazine

DECEMBER 26, 2021

Customer experience (CX) approaches in particular have had to develop and evolve rapidly over the last year – something which has benefitted startups and small enterprises who are able to move with agility to shift and flex to changing customer attitudes and expectations.

Startup 167

Startup Analytics Agile Software Review 167

SoCal CTO

DECEMBER 1, 2010

The United States is now a debtor nation to China and that the bill is about to come due. Five Reasons You Haven’t Launched - Software By Rob , November 10, 2010 Photo by stevendepolo. These are probably the two sites where I've posted the most reviews. This Thanksgiving it might seem that there’s a lot less to be thankful for.

Technical Review 175

Technical Review Technology Product CTO Hire 175

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