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

JUNE 11, 2009

Posted on June 11, 2009 by steveblank When my students ask me about whether they should be a founder or cofounder of a startup I ask them to take a walk around the block and ask themselves: Are you comfortable with: Chaos – startups are disorganized Uncertainty – startups never go per plan Are you: Resilient – at times you will fail – badly.

Cofounder 230

Cofounder Founder Silicon Valley Technical Cofounder 230

Steve Blank

MAY 18, 2009

We agreed that all her founding CEOs seemed to have the same set of personality traits – tenacious, passionate, relentless, resilient, agile, and comfortable operating in chaos. I coach agile teams for a living, and I do most of my work with start-ups. Reply Jonathan Payne , on May 20, 2009 at 8:43 pm Said: fascinating.

Founder 312

Founder Silicon Valley RSS China 312

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.") April 27, 2009 8:59 AM Anonymoussaid.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Steve Blank

SEPTEMBER 7, 2009

Finally, I’ll write about how Eric Ries and the Lean Startup concept provided the equivalent model for product development activities inside the building and neatly integrates customer and agile development. Reply links for 2009-09-07 « Blarney Fellow , on September 7, 2009 at 6:10 pm Said: [.]

Customer Development 233

Customer Development Developer Customer Silicon Valley 233

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. August 3, 2009 10:52 AM Chris Hopf said. August 3, 2009 11:49 AM Jason Brownlee said. August 3, 2009 8:08 PM William Mitchell said. Great post.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Steve Blank

MAY 15, 2009

Reply Andrew Warner , on May 15, 2009 at 9:53 am Said: I had a similar thing happen to me. Reply Michael Pryor , on May 15, 2009 at 10:33 am Said: I won’t dispute your anecdote, but I would like to add that life should be lived not in hopes of a better future. Sorry about the long comment Steve.

Silicon Valley 233

Silicon Valley RSS Lean Agile 233

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. July 13, 2009 7:38 AM George said. Reinertsen is the book for you.

Product Development 153

Product Development Developer San Francisco Product 153

Steve Blank

NOVEMBER 12, 2009

After these slides, these VC’s recognized that this company had dramatically reduced risk and built a startup that was agile, resilient and customer-centric. Reply jordancooper , on November 12, 2009 at 8:08 am Said: Steve, sorry to do this in your comment forum, but I don’t see an email or contact. The rest is just fluff.

Venture Capital 245

Venture Capital Silicon Valley RSS Hockey Stick 245

YoungUpstarts

MAY 30, 2014

After all, Gmail wasn’t taken out of beta until 2009 — five years after it was originally released. Sam Bahreini, a seasoned operations officer and agile entrepreneur, is co-founder and COO of VoloForce , a company that helps enterprise retail brands understand organization implementation through automation and simplification.

Customer 231

Customer Development Team Review Cofounder Agile 231

Startup Lessons Learned

JULY 29, 2009

Lessons Learned by Eric Ries Wednesday, July 29, 2009 Embrace technical debt Financial debt plays an important and positive role in our economy under normal conditions. 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.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

NOVEMBER 7, 2008

February 7, 2009 5:40 AM Major_Grooves said. May 6, 2009 3:03 PM Ivan Acosta-Rubio said. June 22, 2009 6:30 AM Anonymoussaid. June 28, 2009 2:51 PM beorn said. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Great post - I think Ill try this.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

JUNE 22, 2009

Lessons Learned by Eric Ries Monday, June 22, 2009 Pivot, dont jump to a new vision In a lean startup , instead of being organized around traditional functional departments, we use a cross-functional problem team and solution team. Each has its own iterative process: customer development and agile development respectively.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

OCTOBER 4, 2008

In 2007, BusinessWeek named Ries one of the Best Young Entrepreneurs of Tech and in 2009 he was honored with a TechFellow award in the category of Engineering Leadership. January 2, 2009 8:54 AM mancjew said. January 2, 2009 8:57 AM Abbas said. Abbas February 22, 2009 3:33 PM cwillu said. Would love to get in touch.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

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. February 21, 2009 12:10 AM Harold Fowler said. February 21, 2009 7:39 AM Rocky1138 said. February 21, 2009 12:26 PM Anonymoussaid. February 21, 2009 3:08 PM SCC said.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Steve Blank

APRIL 9, 2009

But what I wanted was an agile marketing team capable of operating independently without day-to-day direction. on April 10, 2009 at 6:58 am Said: Amazing blog. Greetings from Crete, Greece Reply Jerry Ji , on April 10, 2009 at 11:09 am Said: Simply _THE BEST_ war story I’ve read in months.

Silicon Valley 271

Silicon Valley Technical Review RSS PR 271

Steve Blank

JUNE 3, 2010

Customer and Agile Development (and the Lean Startup ) may be the emerging methodologies large companies need to build innovative new products. Customer and Agile Development may be the methodologies that large companies need to build innovative new products. More in future posts. Lessons Learned.

Search 251

Search Agile Customer Development Technical Review 251

Startup Lessons Learned

AUGUST 1, 2009

Lessons Learned by Eric Ries Saturday, August 1, 2009 The Steve Jobs method Image via CrunchBase Its been a long time since I did a post that was primarily a link to another blog with commentary, but I came across something today that I really want to share. August 1, 2009 7:39 AM Ravi Mohan said. August 1, 2009 8:11 AM Michael said.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

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? January 18, 2009 8:22 AM Dan Khan said. Cheers, -Dan January 18, 2009 9:04 PM Ivo said. January 20, 2009 1:12 PM Anonymoussaid. April 12, 2009 12:28 AM kenshin said. Great article!

CTO 168

CTO Fractional CTO CTO Hire Technical Review 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. What about a hardware business with some long-lead-time components?

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

OCTOBER 20, 2008

When I first encountered agile software techniques, in the form of extreme programming , I thought I had found the answer. I explained it to people this way: agile lets you make the trade-offs visible to whole company, so that they can make informed choices. Even worse, agile wasnt really helping me ship higher quality software.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

NOVEMBER 13, 2008

Wed never heard of five whys, and we had plenty of "agile skeptics" on the team. February 11, 2009 8:05 AM Anonymoussaid. June 15, 2009 9:27 PM Mark Graban said. link] June 20, 2009 2:52 PM Anonymoussaid. So let me say for the record: we didnt start with any of this at IMVU. Expo SF (May.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Steve Blank

APRIL 27, 2009

And in hindsight, we seemed a bit more agile and innovative in WWII.) Yet decades later the military lacked the agility to write a spec in two years, let alone get 10′s of thousands of new systems deployed on aircraft as Terman had done. Wall 85: Squint « 365 Wallpapers , on April 27, 2009 at 8:29 am Said: [.]

Silicon Valley 210

Silicon Valley Technical Review Europe Germany 210

Startup Lessons Learned

JUNE 15, 2009

Lessons Learned by Eric Ries Monday, June 15, 2009 Why Continuous Deployment? The agile software movement has made numerous contributions: continuous integration, which helps accelerate feedback about defects; story cards and kanban that reduce batch size; a daily stand-up that increases tempo. June 15, 2009 8:24 AM Stevesaid.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

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. I went through some of this in bringing agile methodologies to my current firm - except that I am the product manager in question at this case. October 6, 2008 12:17 AM r& said. Expo SF (May.

San Francisco 158

San Francisco Management Software Review Product 158

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. March 14, 2009 8:34 AM Can Sar said. April 11, 2009 1:22 AM CeeTee said. December 11, 2009 6:54 PM James Abley said. Great post.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

SEPTEMBER 10, 2008

I know plenty of people who prefer more advanced source control system, but my belief is that many agile practices diminish the importance of advanced features like branching. Its not that the idea behind them is wrong, but I think agile team-building practices make scheduling per se much less important. Youd better.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Steve Blank

APRIL 6, 2009

Forty years before Agile Development methodologies became popular, ESL had analysts from its &# customer&# sitting side-by-side with ESL engineers designing new equipment together. The “Good” Student » 14 Responses Shane Rogers , on April 6, 2009 at 1:37 pm Said: The names of ‘secret’ customers is funny.

Silicon Valley 201

Silicon Valley Stealth RSS California 201

Feld Thoughts

APRIL 14, 2010

If you are an Agile software development shop, or follow ALM, Rally just added Kanban to the mix. This is the second acquisition Rally has made – the other was 6th Sense Analytics which they acquired at the beginning of 2009. Tags: My Investments acquisition agile agilezen kanban rally.

Agile 115

Agile Acquisition Software Development Software Developers 115

Startup Lessons Learned

MARCH 3, 2009

Lessons Learned by Eric Ries Tuesday, March 3, 2009 Employees should be masters of their own time Every startup should have a culture of learning. March 3, 2009 9:54 PM surya said. March 3, 2009 10:02 PM Sean Murphy said. March 3, 2009 11:15 PM kareem said. March 3, 2009 11:28 PM Jon said. Dont even go there.

Employee 146

Employee San Francisco Lean Software Review 146

Steve Blank

JUNE 25, 2009

Reply steveblank , on June 25, 2009 at 9:04 am Said: Prakash, This is at the dawn of time, but I seem to remember when we first started selling the IWS, our first product, there weren’t any. rick , on June 25, 2009 at 8:57 am Said: Great post. rick , on June 25, 2009 at 8:57 am Said: Great post.

Technology 145

Technology Silicon Valley Fractional VPE Part-Time VPE 145

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. "Problems are caused by insufficiently robust symptoms" symptoms => systems July 3, 2009 12:29 AM Daniel Tenner said.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

DECEMBER 16, 2009

Lessons Learned by Eric Ries Wednesday, December 16, 2009 What is Lean about the Lean Startup? 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. Now, this webcast was packed, hundreds of people were logged in.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

Startup Lessons Learned

FEBRUARY 10, 2009

Lessons Learned by Eric Ries Tuesday, February 10, 2009 Continuous deployment and continuous learning At long last, some of the actual implementers of the advanced systems we built at IMVU for rapid deployment and rapid response are starting to write about it. Heck, thats what it says right there in the agile manifesto. But it worked.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

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. Take a look and let me know what you think.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

NOVEMBER 29, 2008

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. To probe for agility, you have to ask the candidate questions involving something that they know little about. Expo SF (May.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

APRIL 14, 2009

Lessons Learned by Eric Ries Tuesday, April 14, 2009 Validated learning about customers Would you rather have $30,000 or $1 million in revenues for your startup? Go on an agile diet quickly. With a product development team that is not shipping, any agile methodology will surface major problems quickly. Great post! Great post!

Customer 167

Customer San Francisco Lean Hockey Stick 167