blog.nahurst.com

JULY 19, 2010

The graphic below balances the risks cofounders take with their relative contributions to help answer this question. This covers one of the most common situations I encounter: For a pre-funding web startup whose team includes only a non-technical cofounder, how much equity should an incoming technical cofounder get?

Technical Cofounder 43

Technical Cofounder Cofounder Equity Salary 43

Startup Lessons Learned

OCTOBER 5, 2008

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. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

SEPTEMBER 15, 2008

I had the opportunity to pioneer this approach to funnel analysis at IMVU, where it became a core part of our customer development process. To promote this metrics discipline, we would present the full funnel to our board (and advisers) at the end of every development cycle. Case Study: Continuous deployment makes releases n.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

SEPTEMBER 7, 2008

In a startup, both the problem and solution are unknown, and the key to success is building an integrated team that includes product development in the feedback loop with customers. 2008 09 06 Eric Ries Haas Columbia Customer Development Engineering View SlideShare presentation or Upload your own.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

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

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. May 30, 2010 1:34 AM Poker Workout said. Its incredibly hard to do.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

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. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? April 23, 2010 in San Francisco.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

NOVEMBER 7, 2008

February 17, 2010 1:09 AM 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?) Bring your questions.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Steve Blank

JUNE 25, 2009

They couldn’t keep up with the fast product development times that were enabled by using standard microprocessors. So their management teams were insisting that they OEM (buy from someone else) these products. Customer Development and Selling Strategy If you’ve just started your company you are in customer discovery.

Technology 145

Technology Silicon Valley Fractional VPE Part-Time VPE 145

viniciusvacanti.com

SEPTEMBER 7, 2010

Home About Contact Me How To Make It as a First-Time Entrepreneur Vinicius Vacanti Guide to Finding a Technical Co-Founder September 7, 2010 | View Comments Steve Job's Technical Co-Founder “I’ve got this HUGE idea. I just need to find a technical co-founder.&# Have Experience.

Cofounder 43

Cofounder Technical Cofounder Founder Ruby 43

Startup Lessons Learned

APRIL 14, 2009

It should be even more important to the founders themselves, because it demonstrates that their business hypothesis is grounded in reality. Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. In fact, this company hasn’t shipped any new products in months.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

JULY 28, 2010

Lessons Learned by Eric Ries Wednesday, July 28, 2010 Case Study: kaChing, Anatomy of a Pivot (The following guest post is a new experiment for this blog. Andy Mathieson, a founder and managing member at Fairview Capital , was particularly supportive. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

Startup Lessons Learned

JULY 29, 2009

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. Leverage product development with open source and third parties.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

MARCH 25, 2010

Lessons Learned by Eric Ries Thursday, March 25, 2010 Speed up or slow down? This is the first post that moves into making specific process recommendations for product development. Labels: product development Speed up or slow down? Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

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

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 13, 2008

There is much work that I need to do (the only developer so far) before we have something customers can use. ► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Bring your questions.

SEM 164

SEM San Francisco Lean Continuous Deployment 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. 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

NOVEMBER 13, 2008

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? April 23, 2010 in San Francisco.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

SEPTEMBER 2, 2008

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? April 23, 2010 in San Francisco.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

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

JULY 2, 2009

Labels: five whys root cause analysis , product development 15comments: Anonymoussaid. ► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Leave your thoughts in a comment.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

FEBRUARY 22, 2009

Then you set up a web app to co-ordinate volunteers who can wipe a hard drive and install Ubuntu. You can find out more at: manning.com/sande Many thanks in advance, Todd -- Todd Green Manning Publications Co. January 14, 2010 12:43 AM wesley chun said. January 14, 2010 12:43 AM wesley chun said. Good Post.

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

JULY 5, 2010

As all of you know, Steve Blank is the progenitor of Customer Development and author of The Four Steps to the Epiphany. I have personally sold many copies of his book, and continue to recommend it as one of the most important books a startup founder can read. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

Customer Development 166

Customer Development Developer San Francisco Customer 166

Startup Lessons Learned

FEBRUARY 22, 2010

Lessons Learned by Eric Ries Monday, February 22, 2010 Why diversity matters (the meritocracy business) Diversity is the canary in the coal mine for meritocracy. One last suggestion, which is a technique I learned from my IMVU co-founder Will Harvey. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

The Next Web

DECEMBER 2, 2013

Founder Kevin Systrom launched Instagram with 25,000 beta users on October 6, 2010; two years later, the app continues to see massive growth, recently reporting 150 million active users. If you asked me to build Facebook.com for you, I would quote you $500,000 and nine months of development and design time,” says Schippers.

Cost 168

Cost San Francisco New York City Ruby 168

Startup Lessons Learned

DECEMBER 8, 2008

March 26, 2010 8:42 AM ankur aggarwal said. Theoretically, i can visualize the Continuous Integration as RAD ( Rapid action development) along with iterative method, which we used to study in Software Engineering's Process model. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136

Startup Lessons Learned

JULY 9, 2010

Lessons Learned by Eric Ries Friday, July 9, 2010 Founder personalities and the “first-class man&# theory of management At any given time, something like four percent of the US population is engaged in some form of new-company-creation. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 161

San Francisco Management Founder Lean 161

Startup Lessons Learned

JUNE 15, 2009

I can appreciate the benefits of a fast develop-build-test cycle improving quality, improving team satisfaction and improving productivity, but automated deployment will take some getting used to. Glad you don't develop software for space shuttles. January 29, 2010 11:18 AM Eric said. >

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

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. Luckily for me, my co-founders eventually prevailed and we went on to build a product that customers actually wanted. Labels: product development 4comments: Doug said.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

APRIL 9, 2009

sachinrekhi : "Visionary customers are as smart if not smarter then the founders" #leanstartup Theres no skipping the chasm. At IMVU, I remember spending an incredible amount of time iterating on the model that would power our third-party developer economy. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

Startup Lessons Learned

MAY 31, 2010

Lessons Learned by Eric Ries Monday, May 31, 2010 Thank you The past month has been an incredible roller coaster: #sllconf was a trending topic (briefly topping Justin Bieber before the wifi in the hotel gave out), the Web 2.0 The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

SEPTEMBER 14, 2008

Most of the people building our product werent themselves target customers. So there was simply no substitute for seeing actual customers with the product, live. Today, when I talk to startup founders, the most common answer I get to the question "do you talk to your customers?"

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

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

Startup Lessons Learned

JUNE 17, 2010

Lessons Learned by Eric Ries Thursday, June 17, 2010 No departments Big companies have departments. They are leaders, visionaries, founders and managers having tremendous success. They are leaders, visionaries, founders and managers having tremendous success. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

NOVEMBER 4, 2008

Eric, Any thoughts on how forum feedback fits into customer development and agile product development? Youve probably addressed this in the past, but I continue to be blown away by how fast Blizzard reacts to noise in their forums and rapidly makes fixes to the product. April 23, 2010 in San Francisco.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

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. So far, 2010 is shaping up to be an even more amazing year; read on to find out why.

San Francisco 122

San Francisco Lean Continuous Deployment DC 122