Startup Lessons Learned

SEPTEMBER 30, 2008

Own the development methodology - in a traditional product development setup, the VP Engineering or some other full-time manager would be responsible for making sure the engineers wrote adequate specs, interfaced well with QA, and also run the scheduling "trains" for releases. Labels: product development 15comments: mukund said.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

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

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

San Francisco 158

San Francisco Management Software Review Product 158

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

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. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, April 23, 2010 in San Francisco. Interesting post.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

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. Thank you, Jerry Sheridan Reply Amazing Posts « Shashank ND , on February 11, 2010 at 5:48 am Said: [.]

Technology 145

Technology Silicon Valley Fractional VPE Part-Time VPE 145

Startup Lessons Learned

NOVEMBER 8, 2008

Customer development is a parallel process to product development, which means that you dont have to give up on your dream. Our goal in product development is to find the minimum feature set required to get early customers. January 6, 2010 12:49 AM Anonymoussaid. April 23, 2010 in San Francisco.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

SEPTEMBER 15, 2008

This gets me into trouble, because it conjures up for some the idea that product development is simply a rote mechanical exercise of linear optimization. You just constantly test little micro-changes and follow a hill-climbing algorithm to build your product. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

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

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

Startup Lessons Learned

APRIL 25, 2011

If you somehow missed SLLCONF 2010 , you can get caught up with a complete video recording here.) And this year, we’re going to talk not just about business and product development, but we’ll be exploring one of the Lean Starutp movements next big frontiers: the role of design.

San Francisco 146

San Francisco Silicon Valley Lean Agile 146

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.

Vertical 167

Vertical Silicon Valley Marketing Customer 167

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 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

JULY 2, 2009

Labels: five whys root cause analysis , product development 15comments: Anonymoussaid. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, April 23, 2010 in San Francisco. Facebook Fans Recent & Upcoming Events 2010 I am experimenting with using Plancast to track my 2010 event schedule.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

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

Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, April 23, 2010 in San Francisco. Facebook Fans Recent & Upcoming Events 2010 I am experimenting with using Plancast to track my 2010 event schedule. [link] June 20, 2009 2:52 PM Anonymoussaid. Case Study: Continuous deployment makes releases n.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

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

SEPTEMBER 13, 2008

There is much work that I need to do (the only developer so far) before we have something customers can use. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Thoughts on scientific product development Lo, my 5 subscribers, who are you? April 23, 2010 in San Francisco. Bring your questions.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Steve Blank

MAY 7, 2009

My two cents is that a business plan is the single place to collect your thinking about about your: business model, distribution channel, demand creation plan, financial assumptions, and customer and product development plan. If you’re text averse like i am, try to diagram these key items and then write-up the diagrams.

Business Plan 160

Business Plan Silicon Valley RSS Venture Capital 160

Steve Blank

FEBRUARY 23, 2009

Home Books for Startups Secret History-Bibliography Steve Blank Startup Resources Steve Blank Entries RSS | Comments RSS Categories Air Force (9) Ardent (9) Big Companies versus Startups: Durant versus Sloan (29) California Coastal Commission (3) Conservation (2) Convergent Technologies (1) Customer Development (98) Customer Development Manifesto (..)

Silicon Valley 133

Silicon Valley RSS Venture Capital Customer Development 133

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 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. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, April 23, 2010 in San Francisco. kaChing has been very active in the Lean Startup movement.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

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. > Bring your questions.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

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

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Both Sides of the Table

APRIL 28, 2010

11.2mm in Series A, rumored pre-money of $35mm; $1.6mm angel raised in Jan 2010. In late April 2010, VentureBeat published that Blippy credit card numbers were published on Google search: [link] followed by Blippy’s response. The investment will be used for product development initiatives. Read more: TechCrunch.

Venture Capital 270

Venture Capital Cofounder Spain San Diego 270

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

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136

Startup Lessons Learned

FEBRUARY 22, 2009

January 14, 2010 12:43 AM wesley chun said. speaking of Python, over a decade ago, the creator of Python wrote an essay called Computer Programming for Everybody (CP4E) which turned into a DARPA grant describing how programming should be taught like reading, writing, and arithmetic: [link] January 14, 2010 1:25 AM drhowarddrfine said.

Programming 143

Programming San Francisco Lean Continuous Deployment 143

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

Steve Blank

JULY 30, 2009

Look for some “ skunk works &# project where the product developers are actively seeking alternatives to their own engineering organization. These companies will look at innovative startups to help them gain market share from the incumbent.

Silicon Valley 146

Silicon Valley RSS California Customer Development 146

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

Steve Blank

FEBRUARY 23, 2009

This product development diagram had become part of the DNA of Silicon Valley. That’s in stark contrast to the traditional Product Development Model where it’s expected a customer is already there and waiting and it’s simply a matter of [.] familiar with Customer Development you should be.

Product Development 163

Product Development Developer Silicon Valley Product 163

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

APRIL 7, 2010

Lessons Learned by Eric Ries Wednesday, April 7, 2010 Learning is better than optimization (the local maximum problem) Lean startups don’t optimize. In fact, the curse of product development is that sometimes small things make a huge difference and sometimes huge things make no difference. Get me a new one&# was closer.

San Francisco 154

San Francisco Lean Metrics Design 154

Startup Lessons Learned

JULY 5, 2010

In the meantime, go buy a copy of The Entrepreneur´s Guide to Customer Development right now. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, April 23, 2010 in San Francisco. Facebook Fans Recent & Upcoming Events 2010 I am experimenting with using Plancast to track my 2010 event schedule.

Customer Development 166

Customer Development Developer San Francisco Customer 166

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

OCTOBER 6, 2008

Lessons Learned by Eric Ries Monday, October 6, 2008 When NOT to listen to your users; when NOT to rely on split-tests There are three legs to the lean startup concept: agile product development , low-cost (fast to market) platforms , and rapid-iteration customer development. I think Drucker said it best.

San Francisco 128

San Francisco Lean Continuous Deployment Agile 128