Software By Rob

NOVEMBER 16, 2009

Join nearly 6,000 startup entrepreneurs by subscribing to my RSS feed. The conference was the second reminder in just over a month that I need to get out of the house more often and meet other developers and entrepreneurs. photos by [link] November 16th, 2009 | Cool News, Links & Reviews Building your startup?

Software Review 47

Software Review Software San Francisco RSS 47

Steve Blank

FEBRUARY 23, 2009

This product development diagram had become part of the DNA of Silicon Valley. Reply A real time story start-up | Failed Screenwriter , on April 8, 2009 at 6:33 pm Said: [.] Reply Best books for the lean product managers — Justin Gibbs , on April 28, 2009 at 2:44 pm Said: [.]

Product Development 143

Product Development Developer Silicon Valley Product 143

Steve Blank

MAY 18, 2009

Next, you have to deal with the daily crisis of product development and acquiring early customers. And here’s where life gets really interesting, as the reality of product development and customer input collide, the facts change so rapidly that the original well-thought-out business plan becomes irrelevant.

Founder 297

Founder Silicon Valley RSS China 297

Startup Lessons Learned

JULY 5, 2010

Brant and Patrick undertook a difficult challenge: to provide a generally accessible introduction to Customer Development, without diluting its impact or dumbing-down its principles. The Entrepreneur’s Guide is an easy read. Many “airport business books&# urge entrepreneurs to never give in. I think theyve succeeded.

Customer Development 166

Customer Development Developer San Francisco Customer 166

Steve Blank

SEPTEMBER 24, 2009

Pattern Recognition One of the great things about being an entrepreneur is that you are constantly running a pattern recognition algorithm against a continual collection of customer and market data. But at times it’s why entrepreneurs can sink their own companies. Other times it’s just plain dumb. More on this in later posts.)

Customer 195

Customer Silicon Valley RSS California 195

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.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Steve Blank

NOVEMBER 13, 2012

By then, I had become a venture capitalist at Mitsui Sumitomo Insurance and found myself talking to a lot of entrepreneurs who were proclaiming their great technology yet were struggling with little revenue, and claiming they were “crossing the chasm”. Evangelizing Customer Development in Japan.

Japan 292

Japan Customer Development Developer Customer 292

Steve Blank

JUNE 25, 2009

Twenty eight years ago I was the bright, young, eager product marketing manager called out to the field to support sales by explaining the technical details of Convergent Technologies products to potential customers. They couldn’t keep up with the fast product development times that were enabled by using standard microprocessors.

Technology 138

Technology Silicon Valley Fractional VPE Part-Time VPE 138

Startup Lessons Learned

JANUARY 15, 2010

Lessons Learned by Eric Ries Friday, January 15, 2010 Two Ways to Hold Entrepreneurs Accountable (for Harvard Business Review) The next part in the series I am writing for Harvard Business Review is online. This time, Im discussing the challenge for corporate CFOs and VCs alike in holding entrepreneurs accountable. Read the rest here.

Hockey Stick 105

Hockey Stick San Francisco Entrepreneur Lean 105

Startup Lessons Learned

SEPTEMBER 15, 2008

So far, I have found "lean startup" works better with the entrepreneurs Ive talked to than "agile startup" or even "extreme startup.") The application of agile development methodologies which dramatically reduce waste and unlock creativity in product development. April 27, 2009 8:59 AM Anonymoussaid.

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. Luckily, I now have the benefit of a forthcoming book, The Principles of Product Development Flow. February 21, 2009 12:10 AM Harold Fowler said. Interesting post.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

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

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. Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage. Remember Hamlet?

Technical Review 168

Technical Review Software Review San Francisco Lean 168

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.

Silicon Valley 125

Silicon Valley RSS Venture Capital Customer Development 125

Startup Lessons Learned

MARCH 16, 2009

Lessons Learned by Eric Ries Monday, March 16, 2009 Combining agile development with customer development Today I read an excellent blog post that I just had to share. In most agile development systems, there is a notion of the "product backlog" a prioritized list of what software is most valuable to be developed next.

Agile 111

Agile Customer Development Developer San Francisco 111

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? This may sound crazy, coming as it does from an advocate of c harging customers for your product from day one. And what of the product development team?

Customer 167

Customer San Francisco Lean Hockey Stick 167

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

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 144

Vertical Silicon Valley Marketing Customer 144

Steve Blank

AUGUST 24, 2009

Reply Michael Alan Miller » Crash , on August 24, 2009 at 8:47 am Said: [.] | Posted by Chill on 24 Aug 2009 at 11:47 am | Shattered. [.] If you’re a startup raising money or just want to see your name online, there’s not a better blog on the web. I’m not buying it… literally. Reply Michael F.

Silicon Valley 184

Silicon Valley PR Technical Review RSS 184

Startup Lessons Learned

MARCH 25, 2010

This is the first post that moves into making specific process recommendations for product development. Two Ways to Hold Entrepreneurs Accountable Beware of Vanity Metrics For Startups, How Much Process Is Too Much? Labels: product development Speed up or slow down?

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

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. February 14, 2009 11:12 PM Eric said. May 15, 2009 1:17 AM neocoder said.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

JANUARY 30, 2009

Lessons Learned by Eric Ries Friday, January 30, 2009 Achieving a failure We spend a lot of time planning. Without conscious process design, product development teams turn lines of code written into momentum in a certain direction. This is why agility is such a prized quality in product development. Great post!

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

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. I will come back for more.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

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. Labels: five whys root cause analysis , product development 15comments: Anonymoussaid. July 3, 2009 7:49 AM Eric said.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

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. Sure, Id be delighted to.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

APRIL 4, 2010

The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Two Ways to Hold Entrepreneurs Accountable (for Ha. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Case Study: Continuous deployment makes releases n.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

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

Steve Blank

MAY 7, 2009

In exchange, these VCs/companies get early looks at new deal flow and offer aspiring entrepreneurs feedback and advice on their business plan. Martin , on May 7, 2009 at 9:36 am Said: The caveat would be for undergrads at a school like Stanford or Berkeley. I hate business plan competitions.

Business Plan 140

Business Plan Silicon Valley RSS Venture Capital 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. It would be hard to argue against this product development strategy, in general.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

JANUARY 12, 2009

Lessons Learned by Eric Ries Monday, January 12, 2009 Why PHP won When I first learned to program on the web, Perl + CGI was the dominant platform. Since then, PHP (as part of the LAMP stack ) has really been the dominant development platform, at least in the free software and startup worlds. January 16, 2009 2:54 AM DROCKsaid.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

OCTOBER 20, 2008

Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their product development process. krasicki April 3, 2009 7:19 AM control valves said.

Software Review 164

Software Review Engineer Management Technical Review 164

Steve Blank

JULY 30, 2009

Look for some “ skunk works &# project where the product developers are actively seeking alternatives to their own engineering organization. Reply Terence Pua , on July 30, 2009 at 9:27 am Said: Steve, I’ve read and re-read that section in Chapter 2 re: market types and I still don’t fully comprehend.

Silicon Valley 131

Silicon Valley RSS California Customer Development 131

Startup Lessons Learned

AUGUST 26, 2009

Lessons Learned by Eric Ries Wednesday, August 26, 2009 Building a new startup hub Last week, I had a unique opportunity to spend some time in Boulder at the behest of TechStars. But theres no denying the level of support for entrepreneurs that we enjoy. And do your customer development.

San Francisco 113

San Francisco Silicon Valley Startup Continuous Deployment 113

Startup Lessons Learned

JULY 6, 2009

Lessons Learned by Eric Ries Monday, July 6, 2009 Lean Startup fbFund slides and video As a follow-up to my previous post on my talk for fbFund at Facebook , there was enough interest in watching video of the talk that I have finally uploaded it using Apples MobileMe. July 6, 2009 4:21 PM Anonymoussaid. July 6, 2009 8:43 PM Eric said.

Lean 115

Lean Video San Francisco Continuous Deployment 115

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. September 3, 2009 12:25 PM Omar Ead said. Great points Eric.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Steve Blank

FEBRUARY 18, 2010

So bowing to popular demand the 2009 blog posts are now available on Amazon on a portable device which provides instant and random access to any post and does not require power or an internet connection. As a pun on my last company as an entrepreneur, E.piphany, I called the book The Four Steps to the Epiphany. Startup Culture.

Silicon Valley 202

Silicon Valley Customer Development IP Developer 202

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. You can learn about customer development, and quite a bit more, in Steves book The Four Steps to the Epiphany. Heres the catch. Great post.

Customer Development 168

Customer Development Developer San Francisco Customer 168