Startup Lessons Learned

SEPTEMBER 22, 2008

Lessons Learned by Eric Ries Monday, September 22, 2008 Thoughts on scientific product development I enjoyed reading a post today from Laserlike (Mike Speiser), on Scientific product development. I agree with the less is more product development approach, but for a different reason. Now that is fun.

Product Development 68

Product Development Developer San Francisco Product 68

Startup Lessons Learned

MARCH 25, 2009

Lessons Learned by Eric Ries Wednesday, March 25, 2009 The Lean Startup at Agile Vancouver April 21st A surprising number of respondents in the latest Lessons Learned survey hail from one of the flourishing startup hubs in Canada. This workshop brings together leading thinkers from Lean Production and Lean software. Thank you so much!)

Agile 60

Agile Lean San Francisco Continuous Deployment 60

Steve Blank

NOVEMBER 24, 2010

the wave of semiconductor startups in the 1960’s/70’s, the emergence of venture capital as a professional industry, the personal computer revolution in 1980’s, the rise of the Internet in the 1990’s and finally. the wave of internet commerce applications in the first decade of the 21 st century. Consumer Internet Driving Innovation.

Silicon Valley 335

Silicon Valley United States Venture Capital Software Review 335

Startup Lessons Learned

JANUARY 18, 2010

Lessons Learned by Eric Ries Monday, January 18, 2010 Case Study: Continuous deployment makes releases non-events The following is a case study of one entrepreneurs transition from a traditional development cycle to continuous deployment. I also identified a set of events that would indicate something terribly going wrong (e.g.

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

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. I am heavily indebted to earlier theorists, and highly recommend the books Lean Thinking and Lean Software Development. I like the term because of two connotations: Lean in the sense of low-burn.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

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. Ive attempted to embed the relevant slides below. Expo SF (May.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

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. After all, the worst kind of waste in software development is code to support a use case that never materializes. Expo SF (May.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

AUGUST 3, 2009

Refreshing to finally see lean and agile thinking emerge in product/business-floors and not only in technology. Critical also, as the lean company/start-up can not be lean by just using lean principles in IT and not in Product Development/Management - a common misinterpretation of the Toyota Production System.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

JANUARY 30, 2009

Without conscious process design, product development teams turn lines of code written into momentum in a certain direction. This is why agility is such a prized quality in product development. As far as I know, there are no products that are immune from the technology life cycle adoption curve.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

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. Hopefully others will find it useful as well.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

MARCH 25, 2010

This is the first post that moves into making specific process recommendations for product development. Labels: product development Speed up or slow down? This is the first post that moves into making specific process recommendations for product development. Expo SF (May.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

JUNE 2, 2010

And yet the key to startup speed is to maintain a disciplined approach to testing and evaluating new products, features, and ideas. As start-ups scale, this agility will be lost unless the founders maintain a consistent investment in that discipline. Start-ups supposedly dont have time for detailed processes and procedures.

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

OCTOBER 5, 2008

Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more. But first I think we need to save the product manager from that special form of torture only a waterfall product development team can create. Labels: product development 8comments: Vincent van Wylick said.

San Francisco 158

San Francisco Management Software Review Product 158

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

APRIL 9, 2009

Thank you all so much for making the event an overwhelming success (way beyond my wildest expectations) and a special thanks to all of you who have reached out to share your feedback, comments, and questions since then. 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

JULY 30, 2009

Lessons Learned by Eric Ries Thursday, July 30, 2009 Techstars brings The Lean Startup to Boulder Im very excited to announce a pair of events that will kick off a very busy fall speaking tour. The event will include a talk from Eric on The Lean Startup over dinner, followed by moderated table discussion and then final Q&A with Eric.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

SEPTEMBER 10, 2008

I am convinced one of Joel Spolskys lasting contributions to the field of managing software teams will turn out to be the Joel Test , a checklist of 12 essential practices that you could use to rate the effectiveness of a software product development team. Joel said it: "Top notch development teams dont torture their programmers."

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

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

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. None of it would have happened if we had plenty of cash, or were content to count our progress by traffic or product development milestones.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

NOVEMBER 29, 2008

The technical interview is at the heart of these challenges when building a product development team, and so I thought it deserved an entire post on its own. The six key attributes spell ABCDEF: Agility. When talking about their past experience, candidates with agility will know why they did what they did in a given situation.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

SEPTEMBER 22, 2008

Sometimes we have the attitude that the Product Development team is the one responsible for Activation and Retention (hey, a great product would do that naturally) or that the Marketing team is responsible for Revenue and Referral (hey, go get me some money or free customers already). . Expo SF (May.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Startup Lessons Learned

FEBRUARY 10, 2009

That leads to a seemingly-obvious question: what is progress in software development? Heck, thats what it says right there in the agile manifesto. This development philosophy created a culture around rapid prototyping of features, followed by testing them against large numbers of actual customers. If it didnt, wed trash it.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

OCTOBER 20, 2008

Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their product development process. Even worse, agile wasnt really helping me ship higher quality software.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

SEPTEMBER 2, 2008

Its inspired by the classic OODA Loop and is really just a simplified version of that concept, applied specifically to creating a software product development team. There are three stages: We start with ideas about what our product could be. Labels: agile , listening to customers 3comments: hauteroute said. Expo SF (May.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

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

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. I got my start programming on an old IBM XT; it was thanks to MUDs that I first discovered the internet. Expo SF (May.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

NOVEMBER 8, 2008

This theory has become so influential that I have called it one of the three pillars of the lean startup - every bit as important as the changes in technology or the advent of agile development. You can learn about customer development, and quite a bit more, in Steves book The Four Steps to the Epiphany. Expo SF (May.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

FEBRUARY 20, 2009

Luckily, I now have the benefit of a forthcoming book, The Principles of Product Development Flow. Labels: five whys root cause analysis , product development 11comments: Peter Severin said. Sounds very similar to agile development which is the way. Interesting post. February 21, 2009 7:39 AM Rocky1138 said.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

SEPTEMBER 27, 2010

One of the sayings I hear from talented managers in product development is, “good enough never is.&# And, most importantly, it helps team members develop the courage to stand up for these values in stressful situations. Lessons Learned by Eric Ries Monday, September 27, 2010 Good enough never is (or is it?) Expo SF (May.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

NOVEMBER 7, 2008

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? Stevey's Blog Rants: Good Agile, Bad Agile Learning from Obama: maneuver warfare on the campa. Expo SF (May.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

SEPTEMBER 30, 2008

If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? Labels: product development 15comments: mukund said. Thoughts on scientific product development Lo, my 5 subscribers, who are you? But along the way, something strange happened.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

APRIL 14, 2009

Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. Their product development team is hard at work on a next-generation product platform, which is designed to offer a new suite of products – but this effort is months behind schedule.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

JANUARY 2, 2010

Lessons Learned by Eric Ries Saturday, January 2, 2010 Towards a new entrepreneurship When I started writing about the lean startup , my aspiration was to do more than just share a handful of tips and tricks that work for consumer internet startups. The result is a profound democratization of the digital means of production.

San Francisco 122

San Francisco Lean Continuous Deployment DC 122

Startup Lessons Learned

AUGUST 2, 2008

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? Facebook Fans Recent & Upcoming Events 2010 I am experimenting with using Plancast to track my 2010 event schedule.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

NOVEMBER 17, 2008

Strategy - startups first encounter this when they have the beginnings of a product, and theyve achieved some amount of product/market fit. Stevey's Blog Rants: Good Agile, Bad Agile Learning from Obama: maneuver warfare on the campa. Expo SF (May. Conference streaming, sponsors, discounted tickets.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

JUNE 22, 2009

Each has its own iterative process: customer development and agile development respectively. 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?

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

MAY 31, 2010

I am grateful to everyone who helped make this event a success, especially my co-organizers Charles Hudson and David Sachs. I am grateful to everyone who helped make this event a success, especially my co-organizers Charles Hudson and David Sachs. All video from the conference is available for free at Justin.tv Expo SF (May.

San Francisco 133

San Francisco Lean Technical Review Software Review 133