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. Kent is a significant figure in the field of software development.

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

Steve Blank

MAY 6, 2015

Waterfall Development. While it sounds simple , the Build Measure Learn approach to product development is a radical improvement over the traditional Waterfall model used throughout the 20 th century to build and ship products. Waterfall Development was all about execution of the requirements document.

Lean 120

Lean Agile Business Model Customer Development 120

Startup Lessons Learned

SEPTEMBER 7, 2008

Lessons Learned by Eric Ries Sunday, September 7, 2008 Customer Development Engineering Yesterday, I had the opportunity to guest lecture again in Steve Blank s entrepreneurship class at the Berkeley-Columbia executive MBA program. Ive attempted to embed the relevant slides below. Talk about waste.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

NOVEMBER 8, 2008

Lessons Learned by Eric Ries Saturday, November 8, 2008 What is customer development? When we build products, we use a methodology. Steve Blank has devoted many years now to trying to answer that question, with a theory he calls Customer Development. a roadmap for how to get to Product/Market Fit." Theory of market types.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Hearpreneur

OCTOBER 10, 2023

5- Yes, to adapt to market changes Photo Credit: Sammi Jaeger It's helped our three Founders stay on the same page, project our roadmap of growth, and provide clarity on our goals, strategies, and financial projections, making it easier to communicate our vision to all of our stakeholders and clients. Thanks to Jordan Adair, Shirt Max ! #14-

Business Plan 130

Business Plan Jordan Entrepreneur Florida 130

View from Seed

NOVEMBER 6, 2014

Isaac Cambron is co-founder and CTO of Zensight.co , whose pre-launch product enables sales reps to find and use their best content to close more deals. Below, he answers questions about developing products from scratch, as well as the difficult technology choices and tradeoffs CTOs must make.

Technology 334

Technology Ruby Startup Engineer 334

Steve Blank

SEPTEMBER 1, 2021

Do they have better sales, marketing, or product development groups? What the winners start with is the realization that in a world of continuous disruption, they have only a few years to develop new capabilities or be pushed over the brink. Is it that some CEOs are better than others? Are their people smarter?

Incubator 402

Incubator Lean Agile Business Model 402

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. I have personally sold many copies of his book, and continue to recommend it as one of the most important books a startup founder can read.

Customer Development 166

Customer Development Developer San Francisco Customer 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. This workshop brings together leading thinkers from Lean Production and Lean software. Thank you so much!)

Agile 60

Agile Lean San Francisco Continuous Deployment 60

YoungUpstarts

APRIL 21, 2013

Enter “ The Lean Startup: How Today’s Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses “, a New York Times bestseller by founder of IMVU (creator of 3D avatars) Eric Ries. This reduces guesswork, time, money and effort. Key ideas from the book include the following: 1.

Lean 193

Lean Technical Review North America Startup 193

Startup Lessons Learned

APRIL 25, 2011

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. But along with Intuit founder Scott Cook, Brad is a leader that recognizes that entrepreneurship is critical to his company’s success.

San Francisco 146

San Francisco Silicon Valley Lean Agile 146

Startup Lessons Learned

JULY 13, 2009

Lessons Learned by Eric Ries Monday, July 13, 2009 The Principles of Product Development Flow If youve ever wondered why agile or lean development techniques work, The Principles of Product Development Flow: Second Generation Lean Product Development by Donald G. Reinertsen is the book for you.

Product Development 153

Product Development Developer San Francisco Product 153

Steve Blank

AUGUST 27, 2012

It was great to watch him embrace the spirit and practice of customer development. What I saw reminded me of some of the best and worst things I did as a founder. We’re building the wrong product!” Some of the engineers figuring if the founder was declaring they were toast in 90 days were updating their resumes.

Founder 316

Founder Cofounder Advisory Board Burn Rate 316

Startup Professionals Musings

MAY 4, 2020

In my experience as an advisor to startups, the difference is almost always related to the founder and their execution strategy , more so than to the solution quality or the market. Initially, you may be able to do everything in your startup, including product development, marketing, and shipping orders.

Advisory Board 308

Advisory Board Agile Social Media Metrics 308

Startup Lessons Learned

JULY 9, 2010

Lessons Learned by Eric Ries Friday, July 9, 2010 Founder personalities and the “first-class man&# theory of management At any given time, something like four percent of the US population is engaged in some form of new-company-creation. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 161

San Francisco Management Founder Lean 161

YoungUpstarts

MARCH 4, 2015

In order to grow, startups need a much more focused, realistic and agile approach to goal setting that builds momentum and establishes a pattern of success. For startups, agility is a must. As Dan Dodge, developer advocate at Google once said, “At Google, a year is like a decade. How OKRs Can Help. Here’s how: 1.

Agile 100

Agile Startup Cofounder Metrics 100

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.

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

SEPTEMBER 1, 2008

Lessons Learned by Eric Ries Monday, September 1, 2008 Test-Driven Development as andon cord You cannot control what you cannot see, and the hardest part of managing software projects is that the final product is so intangible. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 68

San Francisco Developer Continuous Deployment DC 68

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. And this was a huge product, which took years to develop.

Software Review 164

Software Review Engineer Management Technical Review 164

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

APRIL 14, 2009

It should be even more important to the founders themselves, because it demonstrates that their business hypothesis is grounded in reality. Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. In fact, this company hasn’t shipped any new products in months.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Steve Blank

SEPTEMBER 17, 2009

This post describes a solution – the Customer Development Model. In future posts I’ll describe how Eric Ries and the Lean Startup concept provide the equivalent model for product development activities inside the building and neatly integrates customer and agile development.

Customer Development 242

Customer Development Developer Customer Silicon Valley 242

Steve Blank

AUGUST 18, 2010

Here’s his story of when Customer Development failed. We were lucky to learn about Customer Development early on in the life of our startup. More importantly, we’d witnessed Customer Development’s massive success at another local startup. So how did Customer Development fail us? The founders do.

Customer Development 230

Customer Development Developer Customer California 230

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

Startup Lessons Learned

JULY 29, 2009

Like a financial debt, the technical debt incurs interest payments, which come in the form of the extra effort that we have to do in future development because of the quick and dirty design choice. 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

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

Startup Lessons Learned

JUNE 2, 2010

And yet the key to startup speed is to maintain a disciplined approach to testing and evaluating new products, features, and ideas. As start-ups scale, this agility will be lost unless the founders maintain a consistent investment in that discipline. No departments The Five Whys for Startups (for Harvard Business R.

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

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

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

Startup Lessons Learned

MARCH 25, 2010

This is the first post that moves into making specific process recommendations for product development. Labels: product development Speed up or slow down? This is the first post that moves into making specific process recommendations for product development. Expo SF (May. Want to learn more about me?

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

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. So what does CTO mean, besides just "technical founder who really cant manage anyone?"

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

FEBRUARY 20, 2009

The batch size is the unit at which work-products move between stages in a development process. Similar results apply in product management, design, testing, and even operations. Take the example of a design team prepping mock-ups for their development team. For software, the easiest batch to see is code. I dont think so.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

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

Startup Lessons Learned

AUGUST 2, 2008

Its to everyones advantage to let the world think the founders thought of everything. I say this as a founder: the contribution of founders is always overestimated. The danger here is that new founders, looking at existing founders, will think that theyre supermen that one couldnt possibly equal oneself.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

SEPTEMBER 22, 2008

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

San Francisco CPA SEM CTO Hire 167