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. No departments The Five Whys for Startups (for Harvard Business R.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Startup Lessons Learned

NOVEMBER 6, 2008

Lessons Learned by Eric Ries Thursday, November 6, 2008 Steveys Blog Rants: Good Agile, Bad Agile I thought Id share an interesting post from someone with a decidedly anti-agile point of view. Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

Startup Lessons Learned

OCTOBER 16, 2013

Guest post by Lisa Regan, writer for The Lean Startup Conference. As Lean Startup methods have been used now for a number of years, we’ve become increasingly interested in how companies use them to sustain growth. One good example is the way in which we''ve adjusted the length of different phases of our agile sprints.

Lean 167

Lean Startup Software Engineering Agile 167

Startup Lessons Learned

SEPTEMBER 30, 2008

Lessons Learned by Eric Ries Tuesday, September 30, 2008 What does a startup CTO actually do? When Ive asked mentors of mine who have worked in big companies about the role of the CTO, they usually talk about the importance of being the external face of the companys technology platform; an evangelist to developers, customers, and employees.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

YoungUpstarts

APRIL 21, 2013

Creators of new products in environments of extreme uncertainty, startups face enormous risks. As a startup owner, what can you do to improve your chances? Through rapid experimentation, short product development cycles, and rigorous measurements of the right metrics, they can ascertain what customers really want.

Lean 193

Lean Technical Review North America Startup 193

Startup Lessons Learned

DECEMBER 16, 2009

Lessons Learned by Eric Ries Wednesday, December 16, 2009 What is Lean about the Lean Startup? That foundational idea, so clearly articulated in books like Lean Thinking, is what originally led me to start using the term lean startup. The following is a guest post for Startup Lessons Learned by the legendary Kent Beck.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

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.

Product Development 88

Product Development Developer San Francisco Product 88

Both Sides of the Table

NOVEMBER 1, 2009

This is part of my ongoing posts on Startup Advice. I know that this all seems obvious now with the movements started by Steven Blank ( Four Steps of Epiphany ) with the whole Customer Development processes / Lean Startup movements also popularized by people like Eric Ries. Turn Your Organization Inside Out. It was humbling.

Customer 280

Customer Technical Review Software Review Mexico 280

Both Sides of the Table

MAY 27, 2013

But the thing I am most proud of about Rob is that he has taken a company with a uniquely talented founder & CTO – Nick Halstead – and managed to build a very tight working relationship with Nick where we drive world-class product development without having the usual founder / CEO conflicts. The Agile Board.

Advisory Board 365

Advisory Board CTO Hire Fractional CTO Los Angeles 365

Startup Lessons Learned

SEPTEMBER 7, 2008

In addition to presenting the IMVU case, we tried for the first time to do an overview of a software engineering methodology that integrates practices from agile software development with Steves method of Customer Development. Can this methodology be used for startups that are not exclusively about software?

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

APRIL 25, 2011

It’s been just over a year since the inaugural Startup Lessons Learned conference , and it’s time to do it again. The Lean Startup movement has made tremendous progress in the past year. Kent Beck himself helped us explain that “quality work” means something different when we’re facing the extreme uncertainty of a startup.

San Francisco 146

San Francisco Silicon Valley Lean Agile 146

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. I was delighted to be asked to give a brief talk about the MVP at the inaugural meetup of the lean startup circle here in San Francisco. Thanks Eric.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

OCTOBER 5, 2008

Lessons Learned by Eric Ries Sunday, October 5, 2008 The product managers lament Life is not easy when youre working in an old-fashioned waterfall development process, no matter what role you play. Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more. Nice write-up.

San Francisco 158

San Francisco Management Software Review Product 158

The Startup Magazine

FEBRUARY 16, 2022

DataRails , the financial analysis and reporting software startup, has announced the hiring of David Rosenberg as the company’s new VP of customer success. The promotion signals the importance of product development for the company’s growth roadmap. CEO Perspective. Investor Sees Opportunity. DataRails has already raised $53.5

Hiring 172

Hiring Software Review Customer Israel 172

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

NOVEMBER 4, 2008

Lessons Learned by Eric Ries Tuesday, November 4, 2008 Principles of Lean Startups, presentation for Maples Investments Image via Wikipedia Steve Blank and I had the opportunity to create a presentation about lean startups for Maples Investments. Agile software development. you get the idea.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

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

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. This workshop brings together leading thinkers from Lean Production and Lean software.

Agile 60

Agile Lean San Francisco Continuous Deployment 60

Steve Blank

MAY 9, 2017

I’ve spent my life in innovation, eight startups in 21 years, and the last 15 years in academia teaching it. the wave of semiconductor startups in the 1960’s/70’s, the emergence of Venture Capital as a professional industry, the personal computer revolution in 1980’s, the rise of the Internet in the 1990’s and finally.

Restful 249

Restful Silicon Valley San Jose Puerto Rico 249

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.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

NOVEMBER 7, 2008

It was one of those brilliant startup brainstorms that comes to the team in a flash, with a giant thunderclap. We spent weeks working on this new product, racing the clock so it would be done in time for the real presidential debates. Eric, Excellent article about an essential technique for startups. Expo SF (May. .

Demand 167

Demand San Francisco Lean Continuous Deployment 167

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. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

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

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. It was a great experience to see a relatively new startup hub in action - and thriving. Their model looks like a key ingredient in the startup brew there.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

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. Five Whys has its origins in the Toyota Production System.

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

JANUARY 12, 2010

Lessons Learned by Eric Ries Tuesday, January 12, 2010 Amazing lean startup resources A year ago, there was no lean startup movement. I continue to believe that the explosion of interest in the lean startup has very little to do with me. If you are attempting to apply lean startup ideas in your own business - you are not alone.

Lean 146

Lean San Francisco Wiki Startup 146

Startup Lessons Learned

NOVEMBER 13, 2008

Wed never heard of five whys, and we had plenty of "agile skeptics" on the team. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May. .

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Steve Blank

MAY 6, 2015

It’s time to update Build, Measure, Learn to what we now know is the best way to build Lean startups. Build a product, get it into the real world, measure customers’ reactions and behaviors, learn from this, and use what you’ve learned to build something better. Waterfall Development. Here’s how.

Lean 120

Lean Agile Business Model Customer Development 120

Startup Lessons Learned

SEPTEMBER 15, 2008

Lessons Learned by Eric Ries Monday, September 15, 2008 The one line split-test, or how to A/B all the time Split-testing is a core lean startup discipline, and its one of those rare topics that comes up just as often in a technical context as in a business-oriented one when Im talking to startups. First of all, why split-test?

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

The Startup Magazine

SEPTEMBER 20, 2019

Startup companies often face numerous obstacles that stand in the way of their desired level of success—from lack of planning to inability to scale up or poor management to neglecting marketing. Among these obstacles exists the idea of product viability and adaptability. Agility, Adaptiveness, and Responsiveness.

Software Review 122

Software Review Management Early Stage Startup 122

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. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

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? In an early-stage startup especially, revenue is not an important goal in and of itself. Let’s start with a simple question: why do early-stage startups want revenue?

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

OCTOBER 4, 2008

(Maybe youd like to start with The lean startup , How to listen to customers , or What does a startup CTO actually do? ) He serves on the advisory board of a number of technology startups, and has worked as a consultant to a number of startups, companies, and venture capital firms.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

The Next Web

MARCH 6, 2014

Successful collaboration between a company’s business development and product development requires mutual understanding and purpose. Practice Agile Development. Entrepreneur Insider Analysis and Opinion Entrepreneurship startup YEC yec.co Matt Ehrlichman , Porch. Consider Using a Liaison.

Technical Review 129

Technical Review Development Team Review Developer Agile 129

The Startup Magazine

APRIL 12, 2017

From marketing to product development, to new software tools and communications, the list is almost endless as to the digital transformations taking place. For startups looking to embrace digital disruption, this an introductory app builder and monitor is good way to get off the ground before scaling.

Technical Review 89

Technical Review Agile Software Review Algorithm 89

YoungUpstarts

JULY 30, 2019

This solution is a philosophy, and this philosophy is AGILE. Agile is a manifesto that has been put forth by a bunch of people and to implement it. As its official website suggests, it is a better way of building products. Moreover, scrum and agile aren’t the same thing. Startups and SCRUM. We use SCRUM.

SCRUM 113

SCRUM Software Review Hiring Agile 113

The Startup Magazine

APRIL 11, 2019

All of us know in software companies that scrum is the most significant agile methodology for handling software projects. In spite of its well-known advantages (flexibility, quick feedbacks, adaptability and better communication), we might be uncertain whether to use this framework or follow a traditional way for the development.

SCRUM 120

SCRUM Software Review Technical Review Framework 120