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

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 408

Incubator Lean Agile Business Model 408

ctotodevelopers.blogspot.com

JULY 11, 2012

Social, Agile, and Transformation. I cover several topics including agile software development, software startups, web 2.0, Strategic Agile Thinking: Balancing Value, Innovation and Research. 2) The agile "happy place". Agile teams sprint when value is known, implementation is low risk. More to come.

Agile 40

Agile Architecture Offshore Software Developers 40

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

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

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. Where is it going? We now understand that’s wrong.

Restful 227

Restful Silicon Valley Puerto Rico San Jose 227

Steve Blank

AUGUST 31, 2009

After 20 years of working in startups, I decided to take a step back and look at the product development model I had been following and see why it usually failed to provide useful guidance in activities outside the building – sales, marketing and business development. So what’s wrong the product development model?

Customer Development 241

Customer Development Developer Customer Silicon Valley 241

Steve Blank

NOVEMBER 24, 2010

Wave after wave of hardware, software, biotech and cleantech products have emerged from what has become “ground zero” of entrepreneurial and startup culture. Compressing the Product Development Cycle. While companies execute business models, startups search for a business model. (Or Starting now.

Silicon Valley 335

Silicon Valley United States Venture Capital Software Review 335

Steve Blank

MARCH 3, 2015

During the Cold War with the Soviet Union, science and engineering at both Stanford and U.C. Berkeley were heavily funded to develop Cold War weapon systems. The disadvantage is that its methodology was based on the old waterfall model of product development and not the agile and lean methods that startups use today.

Business Plan 120

Business Plan Silicon Valley Saudi Arabia Lean 120

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. Combining agile development with customer developm. And when did there get to be 3000 of you?

Agile 60

Agile Lean San Francisco Continuous Deployment 60

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. I like the term because of two connotations: Lean in the sense of low-burn.

Lean 168

Lean San Francisco Startup Continuous Deployment 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. The Customer Development process (and the Lean Startup) is one way to do that.

Lean 250

Lean Silicon Valley Startup RSS 250

Occam's Razor

APRIL 23, 2012

And no, she was not able to complete her task after 6.3802146 frustrating minutes because neither your navigation nor your internal site search engine got her to the right page. of Search Traffic vs. Share of Global Search Volume. That shows you that 45% of your traffic is from Search. She is fine young woman. :).

Metrics 152

Metrics Analytics Search Channel 152

Startup Lessons Learned

NOVEMBER 29, 2008

Finding great engineers is hard; figuring out whos good is even harder. The technical interview is at the heart of these challenges when building a product development team, and so I thought it deserved an entire post on its own. The six key attributes spell ABCDEF: Agility. I have found this quite rare in engineers.

San Francisco 146

San Francisco Lean Agile Java 146

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

Both Sides of the Table

NOVEMBER 1, 2009

Yet he still personally travels in his customers’ neighborhoods in search of deeper customer insights. Getting Customers Involved in Product Priorities – Around the time that Salesforce.com acquired my company we also acquired a company called CrispyNews. Who in the family sends cash, how much, how frequently, etc.

Customer 280

Customer Technical Review Software Review Mexico 280

Startup Lessons Learned

SEPTEMBER 22, 2008

I break the answer to that question down into three engines: Viral - this is the business model identified in the presentation as "Get Users." Thats why eBay advertises on search engines, and Facebook doesnt. Labels: search engine marketing 0comments: New comments are not allowed. Expo SF (May.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Startup Lessons Learned

SEPTEMBER 13, 2008

Lessons Learned by Eric Ries Saturday, September 13, 2008 SEM on five dollars a day How do you build a new product with constant customer feedback while simultaneously staying under the radar? Trying to answer that question at IMVU led me to discover Google AdWords and the world of search engine marketing. SEM is a simple idea.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

JULY 29, 2009

The human tendency to moralize about debt affects engineers, too. 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. The biggest source of waste in new product development is building something that nobody wants.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Hearpreneur

SEPTEMBER 22, 2021

Tesla has always put a huge emphasis on product development and technological advancement. Google wasn't the first search engine around. For me, it's a live example of agile and sustainable business. It has whole teams dedicated to R&D and invests regularly to ensure it's at the top of the food chain.

Technical Review 124

Technical Review Entrepreneur Software Review SEO 124

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

So I initially gravitated to the CTO title, and not VP of Engineering. If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? But since I spent a long time in a hybrid CTO/VP Engineering role, I still have this nagging question. They might do anything !

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

FEBRUARY 20, 2009

Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. I owe it originally to lean manufacturing books like Lean Thinking and Toyota Production System. Every time an engineer checks in code, they are batching up a certain amount of work.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

JANUARY 30, 2009

Even though some aspects of the product were eventually vindicated as good ones, the underlying architecture suffered from hard-to-change assumptions. After years of engineering effort, changing these assumptions was incredibly hard. 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

MARCH 25, 2010

This is the first post that moves into making specific process recommendations for product development. Pretty soon, a soul-searching meeting ensues. Labels: product development Speed up or slow down? This is the first post that moves into making specific process recommendations for product development.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

OCTOBER 5, 2008

For some reason, though, despite the increased buy-in, the final product often doesnt look anything like the original spec. The VP Engineering spends all of his time trying to make sure the programmers understand and implement the spec. Labels: product development 8comments: Vincent van Wylick said. Nice write-up.

San Francisco 158

San Francisco Management Software Review Product 158

ConversionXL

MAY 1, 2017

Past Product: Lackluster Marketing Causes Growth Stalls, Too. These pitfalls are not limited to product development. Often, erosion of customer loyalty has been going on for years but the company has failed to perceive it—until it’s too late. Swimming with Sharks. Growth teams are like those sharks.

Technical Review 127

Technical Review Algorithm Channel Analytics 127

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. Eric, I landed upon your blog when I was searching for the path to CTO a couple of months back and I have been a frequent to the site since then. Blew my mind.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

AUGUST 3, 2009

Refreshing to finally see lean and agile thinking emerge in product/business-floors and not only in technology. Critical also, as the lean company/start-up can not be lean by just using lean principles in IT and not in Product Development/Management - a common misinterpretation of the Toyota Production System.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

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

NOVEMBER 7, 2008

And if you dont know who your customer is, perhaps some customer development is in order? Labels: customer development , search engine marketing 13comments: Jim Lindstrom said. Seems like a fairly low-cost method of gauging customer interest for a would-be product. Eric -- This is a pretty interesting idea.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

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. No engineering team. April 21 - Agile Vancouver is sold-out (thank you all so much!). Those are only symptoms.

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

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

NOVEMBER 13, 2008

Our bias as technologists is to over-focus on the product part of the problem, and five whys tends to counteract that tendency. Its why, at my previous job, we were able to get a new engineer completely productive on their first day. Most engineers would ship code to production on their first day.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

JUNE 22, 2009

Each has its own iterative process: customer development and agile development respectively. The more work youve sunk into a product or vision, the harder it is to let it go. As the CTO/VP Engineering, I was the worst offender. Thats why its so essential to have a co-equal problem team. Context matters.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

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. Start-ups supposedly dont have time for detailed processes and procedures.

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

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