The Next Web

DECEMBER 2, 2013

With mobile development agencies and product incubators on the rise and more corporate “labs” spinning out each day, there’s no shortage of talent to help you build the next great Web or mobile app. Werdelin equates building a successful product to building a nightclub. 1) Twitter. 5) Uber.

Cost 168

Cost San Francisco New York City Ruby 168

blog.wepay.com

APRIL 28, 2010

» 6 Things a Non-Engineer Should Know Before Founding a Web Startup By Rich Aberman Despite the obvious look of shock and panic on the faces of my WePay teammates, I recently committed my first lines of production code. Non-engineers are not “designers” by default. The 90/10 rule. Software is never finished.

Engineer 53

Engineer Software Review Web Technical Review 53

Steve Blank

JUNE 25, 2009

Their engineering teams didn’t have the expertise using off-the-shelf microprocessors (back then “real” computer companies designed their own instruction sets and operating systems.) They couldn’t keep up with the fast product development times that were enabled by using standard microprocessors.

Technology 143

Technology Silicon Valley Fractional VPE Part-Time VPE 143

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.&# This basic pattern is useful in all aspects of product development. The same process works in Interaction Design. Case Study: Continuous deployment makes releases n.

Software Review 74

Software Review San Francisco Design Continuous Deployment 74

Startup Lessons Learned

SEPTEMBER 30, 2008

So I initially gravitated to the CTO title, and not VP of Engineering. If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? But since I spent a long time in a hybrid CTO/VP Engineering role, I still have this nagging question. They might do anything !

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

JULY 29, 2009

Like a financial debt, the technical debt incurs interest payments, which come in the form of the extra effort that we have to do in future development because of the quick and dirty design choice. The human tendency to moralize about debt affects engineers, too. Accept that good design sometimes leads to technical debt anyway.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

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

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. Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. 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

OCTOBER 5, 2008

These specs are handed to a designer, who builds layouts and mockups of all the salient points. Then the designs are handed to a team of programmers with various specialties. The programmers keep asking for more say in the designs and direction that they work on. First, he writes it nice and clear.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

OCTOBER 4, 2008

Lessons Learned by Eric Ries Saturday, October 4, 2008 About the author ( Update January, 2010: This post originally dates from October, 2008 back when I first started writing this blog. I help lead the Engineering Leadership SIG at SDForum and wonder if you would be interested in speaking to our group about lean starups. Blew my mind.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

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

MARCH 25, 2010

Lessons Learned by Eric Ries Thursday, March 25, 2010 Speed up or slow down? 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. Labels: product development Speed up or slow down?

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

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." For Neopets, its simply a side-effect of their game-like product design. Thats why eBay advertises on search engines, and Facebook doesnt.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Steve Blank

MAY 28, 2009

Market Risk vs. Invention Risk - Click to Enlarge For companies building web-based products, product development may be difficult, but with enough time and iteration engineering will eventually converge on a solution and ship a functional product - i t’s engineering, not invention. Blog at WordPress.com.

Vertical 162

Vertical Silicon Valley Marketing Customer 162

Startup Lessons Learned

JUNE 17, 2010

Lessons Learned by Eric Ries Thursday, June 17, 2010 No departments Big companies have departments. I was an engineer on the engineering team. For one, the engineers consider the artists stupid; the artists consider the engineers arrogant. Startups are companies. Startups aspire to become big companies.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Steve Blank

FEBRUARY 23, 2009

The same issues arose time and again: big company management styles versus entrepreneurs wanting to shoot from the hip, founders versus professional managers, engineering versus marketing, marketing versus sales, missed schedule issues, sales missing the plan, running out of money, raising new money. Theme: Digg 3 Column by WP Designer.

Silicon Valley 131

Silicon Valley RSS Venture Capital Customer Development 131

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 take things like unit testing, design documents and code reviews more seriously than any other company Ive even heard about. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

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. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

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. Reinertsen is the book for you.

Product Development 153

Product Development Developer San Francisco Product 153

Steve Blank

JULY 30, 2009

We talked about some simple design rules and I remember him thanking me for coming, saying we were the only chip company who cared enough to call on him (little did he know.) Long gone from Zilog I saw the picture of the original Macintosh design team. Theme: Digg 3 Column by WP Designer. Blog at WordPress.com.

Silicon Valley 143

Silicon Valley RSS California Customer Development 143

Steve Blank

MARCH 3, 2015

During the Cold War with the Soviet Union, science and engineering at both Stanford and U.C. Berkeley were heavily funded to develop Cold War weapon systems. Berkeley in 2010 to run the Lester Center for Entrepreneurship in the Haas School of Business we were teaching entrepreneurship the same way as when I was a student back in 1995.

Business Plan 120

Business Plan Silicon Valley Saudi Arabia Lean 120

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

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

SEPTEMBER 15, 2008

This kind of result is typical when you ship a redesign of some part of your product. The new design improved on the old one in several ways, but these improvements didnt translate all the way through the funnel. Usually, I think that means youve lost some good aspect of the old design.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

SEPTEMBER 2, 2008

Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, 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.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

MARCH 9, 2010

Lessons Learned by Eric Ries Tuesday, March 9, 2010 Startup Lessons Learned - the Conference (April 23, 2010 in SF) Today we are opening up registration for the first ever Startup Lessons Learned Conference on April 23, 2010 in San Francisco. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

San Francisco 151

San Francisco Lean Continuous Deployment Startup 151

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. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

AUGUST 26, 2009

You can learn more about that by reading The engineering managers lament.) And one last specific practice that came up at this session: feverishaaron : UI, design and programmers are all in the same department, all have the same title, and all are evaluated the same. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

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

SoCal CTO

DECEMBER 1, 2010

aka: An Open Letter to the Next Big Social Network) - 500 Hats , November 1, 2010 I've held off writing this post for a long time, because I couldn't quite get my head around all the issues. When It’s Darkest Men See the Stars - Steve Blank , November 24, 2010 When It’s Darkest Men See the Stars. but: Something is Still Missing.

Technical Review 175

Technical Review Technology Product CTO Hire 175

Startup Lessons Learned

JUNE 2, 2010

Lessons Learned by Eric Ries Wednesday, June 2, 2010 The Five Whys for Startups (for Harvard Business Review) I continue my series for Harvard Business Review with the Lean Startup technique called Five Whys. Five Whys has its origins in the Toyota Production System. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

SEPTEMBER 10, 2008

Labels: Test-driven development 0comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?)

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

DECEMBER 28, 2009

Thats a perfectly reasonable reaction, given that most releases of most products are bad news. Even worse, the sad state of product development generally means that the new "features" are as likely to be ones that make the product worse, not better. Thats good for QA and for engineers. Faster (and better) feedback.

Continuous Deployment 122

Continuous Deployment San Francisco Lean Metrics 122

Startup Lessons Learned

SEPTEMBER 12, 2008

0comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) April 23, 2010 in San Francisco.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Steve Blank

AUGUST 27, 2009

This series of posts is a brief explanation of how we’ve evolved from Product Development to Customer Development to the Lean Startup. The Product Development Diagram Emerging early in the twentieth century, this product-centric model described a process that evolved in manufacturing industries.

Silicon Valley 269

Silicon Valley Product Startup Product Development 269

Startup Lessons Learned

AUGUST 2, 2008

0comments: Post a Comment Newer Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) April 23, 2010 in San Francisco.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

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. Case Study: Continuous deployment makes releases n.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131