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

Hearpreneur

OCTOBER 10, 2023

By presenting your plans in an organized manner to potential investors and lenders, you increase the chances of them taking action and providing the resources necessary for you to get started or expand. #4- 14- No, as I relied on customer feedback Photo Credit: Michael Mastin I relied on agility and adaptability.

Business Plan 143

Business Plan Jordan Entrepreneur Florida 143

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. But it lacked a framework for testing all commercialization hypotheses outside of the building.

Lean 120

Lean Agile Business Model Customer Development 120

The Startup Magazine

SEPTEMBER 20, 2019

However, there is no better source than the actual customer using the product in the present. Today’s world presents us with other options that were not available in the past, one of which is the Net Promoter Score. Agility, Adaptiveness, and Responsiveness. Let’s dive deeper. To Round It Up.

Software Review 100

Software Review Management Early Stage Startup 100

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. Second, we’re presenting something unusual for an entrepreneurship conference: the CEO of a Fortune 1000 company. Design + Lean Startup = Lean UX.

San Francisco 146

San Francisco Silicon Valley Lean Agile 146

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. Steve Blank was very impressed by this presentation and mentioned it when he spoke at TiE on Wed-Sep-19.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Steve Blank

NOVEMBER 5, 2009

This post describes how companies using the Customer Development model can increase their credibility, valuation and probability of getting a first round of funding by presenting their results in a “Lesson Learned&# venture pitch. Tons of advice is available on how to pitch , present and market your company.

Customer Development 270

Customer Development Developer Customer Silicon Valley 270

YoungUpstarts

APRIL 14, 2014

As companies strive to stay agile and innovative, they’ve discovered that units of 8 to 12 people work best as the natural size of high-performance teams. This is the magic number for leadership teams, product teams, research teams, design teams, and more. An engineer will get her hands dirty to ensure the product is perfect at launch.

Agile 196

Agile Leadership Architecture Product Development 196

Steve Blank

MARCH 3, 2015

See the presentation here.). 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. It taught lean theory ( business model design , customer development and agile engineering) and practice.

Business Plan 120

Business Plan Silicon Valley Saudi Arabia Lean 120

Hearpreneur

SEPTEMBER 22, 2021

Tesla has always put a huge emphasis on product development and technological advancement. For me, it's a live example of agile and sustainable business. maybe not a mainstream pick, the lessons I have learned from them in communication, presentation, and overall effectiveness is invaluable. Photo Credit: Jeremy Goldman.

Technical Review 138

Technical Review Entrepreneur Software Review SEO 138

Steve Blank

OCTOBER 25, 2022

How do they become present on new social media and communications channels? All 15 topic had team leads presenting poster sessions, there were presenters from the field sales and partners emphasizing the urgency and specificity of the problems, and there were breakout sessions where the topic area teams brainstormed with each other.

Framework 401

Framework Distribution Channel Leadership 401

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. Thoughts on scientific product development Lo, my 5 subscribers, who are you?

Lean 168

Lean San Francisco Startup Continuous Deployment 168

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

AUGUST 3, 2009

Without further ado, the video: Slides are below: Minimum Viable Product View more presentations from Eric Ries. Labels: minimum viable product , slides , video 13comments: Alan Pinstein said. I do this as a core part of the Product Management process I use at all startups. August 13, 2009 3:43 AM Robert said.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Steve Blank

SEPTEMBER 7, 2009

Finally, I’ll write about how Eric Ries and the Lean Startup concept provided the equivalent model for product development activities inside the building and neatly integrates customer and agile development. Each starts inventing and testing their own alternatives about how to sell and position the product.

Customer Development 233

Customer Development Developer Customer Silicon Valley 233

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

Master of 500 Hats: Startup Metrics for Pirates (SeedCamp 2008, London) This presentation should be required reading for anyone creating a startup with an online service component. I break the answer to that question down into three engines: Viral - this is the business model identified in the presentation as "Get Users." Choose one.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

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. You need to strike a balance between process and problem-solving.

Lean 167

Lean Startup Software Engineering Agile 167

ConversionXL

APRIL 3, 2018

Corporate Agility. Transparency correlates to agility (Does your CEO know how many tests you ran last month?). gyalif great presentation about AI #CXLLive pic.twitter.com/L4b7pqIl6o. Great presentation from @els_aerts today at #cxllive "Without research there is nothing" true story! Culture of Innovation.

Retention 106

Retention Artificial Inteligence Channel Email 106

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

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. When talking about their past experience, candidates with agility will know why they did what they did in a given situation.

San Francisco 146

San Francisco Lean Agile Java 146

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.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

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 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. Even worse, agile wasnt really helping me ship higher quality software.

Software Review 164

Software Review Engineer Management Technical Review 164

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

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 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

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

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

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

FEBRUARY 10, 2009

That leads to a seemingly-obvious question: what is progress in software development? Heck, thats what it says right there in the agile manifesto. This development philosophy created a culture around rapid prototyping of features, followed by testing them against large numbers of actual customers. If it didnt, wed trash it.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

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

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 27, 2010

One of the sayings I hear from talented managers in product development is, “good enough never is.&# And, most importantly, it helps team members develop the courage to stand up for these values in stressful situations. Lessons Learned by Eric Ries Monday, September 27, 2010 Good enough never is (or is it?) Expo SF (May.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

JULY 30, 2009

During the same period (1987 – 1990) and I did some work at MIT under Eric von Hippel on “user driven innovation with regard to software development&# which today would probably fall under the heading of “open source software development approaches.&# Expo SF (May. Conference streaming, sponsors, discounted tickets.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

NOVEMBER 7, 2008

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? Stevey's Blog Rants: Good Agile, Bad Agile Learning from Obama: maneuver warfare on the campa. Expo SF (May.

Demand 167

Demand San Francisco Lean Continuous Deployment 167