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

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. They are gaining valuable customer data.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Steve Blank

NOVEMBER 12, 2019

Within a decade, the rise of venture capital in Silicon Valley enabled startups to find commercial customers rather than military ones. It’s not that these companies are smarter than Defense Department employees, but they operate with different philosophies, different product development methodologies, and with different constraints.

Government 316

Government Artificial Inteligence Silicon Valley North Korea 316

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

But by taking advantage of open source, agile software, and iterative development, lean startups can operate with much less waste. I am heavily indebted to earlier theorists, and highly recommend the books Lean Thinking and Lean Software Development. Labels: customer development , lean startup 8comments: Amy said.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

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

Startup Lessons Learned

JULY 5, 2010

I believe it is the best introduction to Customer Development you can buy. As all of you know, Steve Blank is the progenitor of Customer Development and author of The Four Steps to the Epiphany. You can imagine how well that worked. On the plus side, that means its a great deal. I think theyve succeeded.

Customer Development 166

Customer Development Developer San Francisco Customer 166

Startup Lessons Learned

AUGUST 3, 2009

First, a definition: the minimum viable product is that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort. MVP, despite the name, is not about creating minimal products. There is a distinction between product and offering.

San Francisco 168

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

Steve Blank

NOVEMBER 2, 2009

For those of you who have been following the discussion, a Lean Startup is Eric Ries ’s description of the intersection of Customer Development , Agile Development and if available, open platforms and open source. And most startup code and features end up on the floor as customers never really wanted them.

Lean 263

Lean Silicon Valley Startup RSS 263

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

Steve Blank

MAY 9, 2017

The second thing that’s changed is that we’re now Compressing the Product Development Cycle. In the 20 th century startups I was part of, the time to build a first product release was measured in years as we turned out the founder’s vision of what customers wanted. Founders Need to Run the Company Longer. The founders.

Restful 249

Restful Silicon Valley San Jose Puerto Rico 249

Startup Lessons Learned

SEPTEMBER 14, 2008

Lessons Learned by Eric Ries Sunday, September 14, 2008 How to listen to customers, and not just the loud people Frequency is more important than talking to the "right" customers, especially early on. Youll know when the person youre talking to is not a potential customer - they just wont understand what youre saying.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

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

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. Keep split-testing, but keep this iron rule: if it doesnt change customer behavior, its not a feature. Now that is fun.

Product Development 68

Product Development Developer San Francisco Product 68

Steve Blank

MAY 6, 2015

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. Repeat, learning whether to iterate, pivot or restart until you have something that customers love. Waterfall Development. Microsoft Windows 3.0).

Lean 120

Lean Agile Business Model Customer Development 120

Startup Lessons Learned

NOVEMBER 7, 2008

Thats the conclusion Ive come to after watching tons of online products fail for a complete lack of customers. Our goal is to find out whether customers are interested in your product by offering to give (or even sell) it to them, and then failing to deliver on that promise. We finally settled on a $1.99

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

SEPTEMBER 30, 2008

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. Labels: product development 15comments: mukund said.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

YoungUpstarts

APRIL 21, 2013

Through rapid experimentation, short product development cycles, and rigorous measurements of the right metrics, they can ascertain what customers really want. Such direct experiences allows one to test critical “leap-of-faith” assumptions about what customers like and dislike.

Lean 193

Lean Technical Review North America Startup 193

Startup Lessons Learned

OCTOBER 16, 2013

One good example is the way in which we''ve adjusted the length of different phases of our agile sprints. We don''t follow a set agile methodology, but rather follow a more home-grown, minimal version of various approaches. Create a steady stream of customer input that anyone can dip into. It wasn’t always this way.

Lean 167

Lean Startup Software Engineering Agile 167

YoungUpstarts

MARCH 12, 2020

Also known as a system on module, SOM offers companies a unique strategy when it comes to developing products while keeping customizability fully possible. Using SOM is perfect for system designers who’re interested in having customization of the interface, form factor, and other electronic components.

SCRUM 147

SCRUM Software Review Technical Review Differentiation 147

Startup Lessons Learned

DECEMBER 14, 2009

Lessons Learned by Eric Ries Monday, December 14, 2009 Business ecology and the four customer currencies Lately, I’ve been rethinking the concept of “business model&# for startups, in favor of something I call “business ecology.&# Let’s begin with the four customer currencies. And this is true outside of games.

Customer 156

Customer San Francisco Viral Lean 156

A Smart Bear: Startups and Marketing for Geeks

AUGUST 30, 2010

On this day we stopped looking at the hosted version as a new product line, and started looking at it as a market test; to see if we could build enough of a customer base to warrant a major investment in the hosted invoicing market space. Agile Development, meet Agile Business. After your product launch.

Software Review 284

Software Review Startup Technical Review Hosting 284

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 121

SCRUM Software Review Technical Review Framework 121

A Smart Bear: Startups and Marketing for Geeks

APRIL 5, 2010

When we demand overwhelming customer outcry before committing to the slightest product change, we're in danger of losing the value of creating a cool feature that takes too much effort but people just love. Now sure, there are many of aspects of business and product development where it's best to stop obsessing and just cut corners.

Software Review 226

Software Review Metrics Lean Agile 226

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

Agile 60

Agile Lean San Francisco Continuous Deployment 60

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. How to listen to customers, and not just the loud.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

The Next Web

MARCH 6, 2014

The business development team needs to see the customer feedback they deliver make it back into the product, and the tech team needs to see reasonable requests to develop new features without a constant stream of changing direction. Practice Agile Development. Phil Chen , Givit. Build Trust.

Technical Review 129

Technical Review Development Team Review Developer Agile 129

Duct Tape Marketing

OCTOBER 29, 2019

Bringing Marketing and Product Development Together written by John Jantsch read more at Duct Tape Marketing. On this episode of the Duct Tape Marketing Podcast, I visit with author and product and marketing executive Jill Soley. Why it’s important to start customer segmentation early on in your process.

Product Development 62

Product Development Developer Product Marketing 62

Startup Lessons Learned

SEPTEMBER 15, 2008

In my experience, the majority of changes we made to products have no effect at all on customer behavior. The report is set up to show you what happened to customers who registered in that period (a so-called cohort analysis ). This report is set up to tell you about new customers specifically. One last note on reporting.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

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

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

The Startup Magazine

JUNE 4, 2024

Examples of Goals Increase Market Share: By expanding your product line, aim to capture 10% more of the market within two years. Customer Satisfaction: Improve customer satisfaction scores by 15% in the next year through enhanced support and product improvements. Positive cash flow is essential for business expansion.

Technical Review 146

Technical Review Agile Audience Employee 146

ReadWriteStart

MAY 26, 2022

You also should figure out what your customers’ specific needs are and which of those needs aren’t being met that align with your organization’s core expertise. In software, those avenues are your customers, industry, employees, and the broader trends associated with current events. Make the Future Part of Your Mission Statement.

Software 171

Software Japan Agile Employee 171

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? What is customer development? Stevey's Blog Rants: Good Agile, Bad Agile Learning from Obama: maneuver warfare on the campa.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 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? ) Although Catalyst folded with the dot-com crash, Ries continued his entrepreneurial career as a Senior Software Engineer at There.com, leading efforts in agile software development and user-generated content.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

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. Customer development.

Lean 102

Lean San Francisco Agile Continuous Deployment 102