Startup Lessons Learned

NOVEMBER 29, 2008

Lessons Learned by Eric Ries Saturday, November 29, 2008 The ABCDEFs of conducting a technical interview I am incredibly proud of the people I have hired over the course of my career. Finding great engineers is hard; figuring out whos good is even harder. This second objective plays no small part in allowing you to hire the best.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

SEPTEMBER 22, 2008

I break the answer to that question down into three engines: Viral - this is the business model identified in the presentation as "Get Users." Thats why eBay advertises on search engines, and Facebook doesnt. Beware the new hire who has "extensive experience" in startups or big companies - using a different growth driver.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Startup Lessons Learned

SEPTEMBER 15, 2008

The application of agile development methodologies which dramatically reduce waste and unlock creativity in product development. See Customer Development Engineering for my first stab at articulating the theory involved) Ferocious customer-centric rapid iteration, as exemplified by the Customer Development process.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Startup Lessons Learned

JANUARY 12, 2010

The Lean Startup Wiki (hosted by long-time lean startup pbWorks) contains a number of resources, including links to case studies , meetups, tools , and people who have volunteered to help. Its a wiki, feel free to consume and enhance it. Its a wiki, feel free to consume and enhance it. April 23, 2010 in San Francisco.

Lean 146

Lean San Francisco Wiki Startup 146

Startup Lessons Learned

JUNE 17, 2010

The team hired only the best and the brightest. I was an engineer on the engineering team. For one, the engineers consider the artists stupid; the artists consider the engineers arrogant. Meanwhile the drawbacks of functional departments can cause real and lasting harm. The meeting was tense.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

APRIL 4, 2010

Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Startup Lessons Learned season two : Every post from the blogs second year in print form. Startup Lessons Learned for Kindle Startup Lessons Learned - the conference. April 23, 2010 in San Francisco. Bring your questions.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Startup Lessons Learned

SEPTEMBER 30, 2008

So I initially gravitated to the CTO title, and not VP of Engineering. But since I spent a long time in a hybrid CTO/VP Engineering role, I still have this nagging question. I want to add one last idea, even though I recognize it is controversial, bordering on the boundary between the CTO and VP Engineering. Heres my take.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

bizthoughts.mikelee.org

MARCH 8, 2012

BizThoughts Thoughts about business, technology, the web & entrepreneurship About Booklist Contact Nov 15 2011 Finding a Technical Cofounder By Mike Lee Categories: Entrepreneurship , Leadership Since I have a technical background, I get about one offer a month to join some engineering team, or to be a technical cofounder.

Technical Cofounder 40

Technical Cofounder Cofounder Technical Review Software Review 40

Startup Lessons Learned

FEBRUARY 20, 2009

Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. I owe it originally to lean manufacturing books like Lean Thinking and Toyota Production System. The batch size is the unit at which work-products move between stages in a development process.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

JULY 2, 2009

We started with a simple wiki page with a few bullet points of things that new engineers had tripped over recently. In response to Five Whys that noticed that not all new engineers were reading the list, we expanded it into a new engineer curriculum. We never set out to build a world-class engineering-training process.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

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. He wrote it in 2000, and as far as I know has never updated it.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

SEPTEMBER 13, 2008

Lessons Learned by Eric Ries Saturday, September 13, 2008 SEM on five dollars a day How do you build a new product with constant customer feedback while simultaneously staying under the radar? Trying to answer that question at IMVU led me to discover Google AdWords and the world of search engine marketing. SEM is a simple idea.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

JANUARY 30, 2009

Hire the absolute best and the brightest, true experts in their fields, who in turn can hire the smartest people possible to staff their departments. By hiring experts, conducting lots of focus groups, and executing to a detailed plan, the company became deluded that it knew what customers wanted. We can skip the chasm.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

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. April 23, 2010 in San Francisco.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

SEPTEMBER 2, 2008

Thoughts on scientific product development Lo, my 5 subscribers, who are you? Waves of technology platforms The lean startup Customer Development Engineering Greasemonkey compiler Great open source scalability tools from Danga Ideas. Lean Startup Wiki - including a complete list of local meetups and meetup organizers.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

MARCH 16, 2009

Ever since that time, I have struggled to explain how the feedback loop in customer development should interface with the feedback loop in product development. Eric Ries Lean Startup Schematic View Of Agile Development And Customer Development View more presentations from Eric Ries.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

NOVEMBER 6, 2008

Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective. They work hard to keep their house in order at all times, and there are strict rules and guidelines in place that prevent engineers and teams from doing things their own way. Bring your questions.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

Startup Lessons Learned

JANUARY 28, 2009

I was told they werent sure, because all of their engineers were currently busy refactoring. The engineering team has decided its reached a breaking point, and is taking several weeks to bring it up to modern standards, including unit tests, getting started with continuous integration , and a new MVC architecture. Practice five whys.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

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

DECEMBER 7, 2008

In a few cases, they are clearly smart people in a bad situation, and Ive written about their pain in The product managers lament and The engineering managers lament. And we cant hire new engineers any faster, because you cant be interviewing and debugging and fixing all at the same time! Hire a CTO or VP Engineering.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

OCTOBER 5, 2008

For some reason, though, despite the increased buy-in, the final product often doesnt look anything like the original spec. The VP Engineering spends all of his time trying to make sure the programmers understand and implement the spec. Labels: product development 8comments: Vincent van Wylick said. Bring your questions.

San Francisco 158

San Francisco Management Software Review Product 158

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. Thoughts on scientific product development Lo, my 5 subscribers, who are you?

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

SEPTEMBER 10, 2008

Thoughts on scientific product development Lo, my 5 subscribers, who are you? Waves of technology platforms The lean startup Customer Development Engineering Greasemonkey compiler Great open source scalability tools from Danga Ideas. Lean Startup Wiki - including a complete list of local meetups and meetup organizers.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

AUGUST 1, 2009

Also SJ's obsession with better taste (positively) contributes to the overall product development process. Beyond Apple, we can find examples of the Steve Jobs character at Toyota, in the form of the Chief Engineer. There are some good anecdotes about Chief Engineers in the Toyota Product Development Book.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

AUGUST 8, 2009

I thought a good place to start was with the origins of the idea that "software design" should be considered a discipline in its own right, on par with computer science, software engineering, and computer programming. Great engineers see it and smile. This is called set-based concurrent engineering (SBCE). [1]

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

SEPTEMBER 12, 2008

Thoughts on scientific product development Lo, my 5 subscribers, who are you? Waves of technology platforms The lean startup Customer Development Engineering Greasemonkey compiler Great open source scalability tools from Danga Ideas. Lean Startup Wiki - including a complete list of local meetups and meetup organizers.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

JULY 29, 2009

The human tendency to moralize about debt affects engineers, too. Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage. The biggest source of waste in new product development is building something that nobody wants.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

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. I help lead the Engineering Leadership SIG at SDForum and wonder if you would be interested in speaking to our group about lean starups. hope to hear from you.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

steveblank.com

JULY 8, 2011

Github - Free public repositories, collaborator management, issue tracking, wikis, downloads, code review, graphs Pivotal Tracker – Agile project management tool that enables real time collaboration. WebSequenceDiagrams - sketch sequence diagrams.

Software Review 110

Software Review Startup Silicon Valley Analytics 110

Startup Lessons Learned

SEPTEMBER 5, 2008

Thoughts on scientific product development Lo, my 5 subscribers, who are you? Waves of technology platforms The lean startup Customer Development Engineering Greasemonkey compiler Great open source scalability tools from Danga Ideas. Lean Startup Wiki - including a complete list of local meetups and meetup organizers.

Open Source 107

Open Source San Francisco Continuous Deployment Lean 107

Startup Lessons Learned

SEPTEMBER 14, 2008

Later, when the company was much larger, we had everyone on our engineering team agree to sit in on one usability test every month. It wasnt a huge time commitment, but it meant that every engineer was getting regular contact with an actual customer, which was invaluable. Seth Godin: How often should you publish? Bring your questions.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Lessons Learned

JUNE 2, 2010

Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Startup Lessons Learned season two : Every post from the blogs second year in print form. Startup Lessons Learned for Kindle Startup Lessons Learned - the conference. April 23, 2010 in San Francisco. Bring your questions.

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

AUGUST 30, 2008

This basic pattern is useful in all aspects of product development. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. 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.&#

Software Review 74

Software Review San Francisco Design Continuous Deployment 74

Startup Lessons Learned

SEPTEMBER 2, 2008

Do the engineers understand what they are building? Thoughts on scientific product development Lo, my 5 subscribers, who are you? Waves of technology platforms The lean startup Customer Development Engineering Greasemonkey compiler Great open source scalability tools from Danga Ideas. Do they measure?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

FEBRUARY 28, 2009

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. Labels: product development 4comments: Doug said. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Thank you Eric. Bring your questions.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

JANUARY 2, 2009

My son is planning a software product that will take the mystery out of wikis and make the technology easier for consumers to use. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. You can read the article to find out why. 3comments: Charles Crawford said. Thank you for this excellent article.

San Francisco 60

San Francisco Tampa Continuous Deployment Lean 60

Startup Lessons Learned

AUGUST 2, 2008

Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Startup Lessons Learned season two : Every post from the blogs second year in print form. Startup Lessons Learned for Kindle Startup Lessons Learned - the conference. April 23, 2010 in San Francisco. Bring your questions.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125