Startup Lessons Learned

OCTOBER 5, 2008

Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more. 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.

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. Ken Yagen (@kenyagen) KenAtYagenDotCom January 3, 2010 1:38 PM Paramendra Bhagat said. My first time at your blog. You are a great blogger.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

APRIL 26, 2009

Lessons Learned by Eric Ries Sunday, April 26, 2009 Product development leverage Leverage has once again become a dirty word in the world of finance, and rightly so. But I want to talk about a different kind of leverage, the kind that you can get in product development. Its a key lean startup concept. Great post!

Product Development 88

Product Development Developer San Francisco Product 88

Startup Lessons Learned

SEPTEMBER 30, 2008

If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? Labels: product development 15comments: mukund said. March 23, 2010 2:05 PM Anonymoussaid. But along the way, something strange happened. And what about if deployment takes forever?

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. Joel said it: "Top notch development teams dont torture their programmers."

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

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?) . Expo SF (May.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

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. Expo SF (May.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

JULY 29, 2009

I hope to show why lean and agile techniques actually reduce the negative impacts of technical debt and increase our ability to take advantage of its positive effects. Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

APRIL 25, 2011

If you somehow missed SLLCONF 2010 , you can get caught up with a complete video recording here.) It may be hard to remember that there was a time when people in the agile software development community thought Lean Startup was incompatible with agile practices. Wealthfront CTO Pascal-Louis Perez will show you how.

San Francisco 146

San Francisco Silicon Valley Lean Agile 146

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. Sounds very similar to agile development which is the way. Interesting post. February 21, 2009 7:39 AM Rocky1138 said.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

NOVEMBER 13, 2008

Wed never heard of five whys, and we had plenty of "agile skeptics" on the team. Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? Expo SF (May.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

SEPTEMBER 2, 2008

We wanted an agile approach that would allow us to build our software architecture as we needed it, without downtime, but also without large amounts of up-front cost. After all, the worst kind of waste in software development is code to support a use case that never materializes. Expo SF (May.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

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

DECEMBER 16, 2009

For those whove heard it, it contains a length discourse on the subject of agile software development and extreme programming, including its weaknesses when applied to startups. As Im pontificating about agile, I see the name Kent Beck in my peripheral vision. Now, this webcast was packed, hundreds of people were logged in.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

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

MARCH 25, 2009

Lessons Learned by Eric Ries Wednesday, March 25, 2009 The Lean Startup at Agile Vancouver April 21st A surprising number of respondents in the latest Lessons Learned survey hail from one of the flourishing startup hubs in Canada. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Thank you so much!) Expo SF (May.

Agile 60

Agile Lean San Francisco Continuous Deployment 60

Startup Lessons Learned

NOVEMBER 4, 2008

Boyd emphasized the importance of agility in combat: "the key to victory is to be able to create situations wherein one can make appropriate decisions more quickly than ones opponent." Agile software development. Agile allows companies to build higher quality software faster. Hopefully others will find it useful as well.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

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

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. Labels: agile , listening to customers 3comments: hauteroute said. Expo SF (May.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

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 146

Technology Silicon Valley Fractional VPE Part-Time VPE 146

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

JUNE 15, 2009

The agile software movement has made numerous contributions: continuous integration, which helps accelerate feedback about defects; story cards and kanban that reduce batch size; a daily stand-up that increases tempo. Glad you don't develop software for space shuttles. January 29, 2010 11:18 AM Eric said. > Expo SF (May.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

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. Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down?

SEM 164

SEM San Francisco Lean Continuous Deployment 164

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 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. Expo SF (May.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

Startup Lessons Learned

FEBRUARY 28, 2009

This builds on a lot of great thinking that has come before, like the agile movements insistence that only the creation of working code counts as progress for a software development team. 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.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

JULY 2, 2009

Labels: five whys root cause analysis , product development 15comments: Anonymoussaid. Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? Expo SF (May.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

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

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

APRIL 9, 2009

Thats the essence of so many of the lean startup techniques Ive evangelized: customer development , the Ideas/Code/Data feedback loop , and the adaptation of agile development to the startup experience. Creating a company-wide feedback loop that incorporates both customer development and agile development is a challenge.

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

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, Expo SF (May.

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136

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. Expo SF (May.

San Francisco 128

San Francisco Lean Continuous Deployment Agile 128

Startup Lessons Learned

NOVEMBER 17, 2008

Strategy - startups first encounter this when they have the beginnings of a product, and theyve achieved some amount of product/market fit. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Stevey's Blog Rants: Good Agile, Bad Agile Learning from Obama: maneuver warfare on the campa.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

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

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

MARCH 3, 2009

March 17, 2009 7:48 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?) April 23, 2010 in San Francisco.

Employee 146

Employee San Francisco Lean Software Review 146

Startup Lessons Learned

JULY 5, 2010

In the meantime, go buy a copy of The Entrepreneur´s Guide to Customer Development right now. Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? Expo SF (May.

Customer Development 166

Customer Development Developer San Francisco Customer 166

Startup Lessons Learned

SEPTEMBER 10, 2008

Lessons Learned by Eric Ries Wednesday, September 10, 2008 Smarticus — 10 things you could be doing to your code right now Smarticus — 10 things you could be doing to your code right now A great checklist of techniques and tools for making your development more agile, written from a Rail perspective. Expo SF (May.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68