Steve Blank

JUNE 26, 2014

We’re changing the order in which we teach the business model canvas and customer development to better-fit therapeutics, diagnostics and medical devices. “Customer Development” to test the hypotheses outside the building and. Teams talk to 10-15 customers a week and make a minimum of 100 customer visits.

Intellectual Property 287

Intellectual Property Lean IP Open Source 287

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. It wasn’t always this way. So what was going on? But that doesn’t mean that we don’t take these ideas seriously.

Lean 167

Lean Startup Software Engineering Agile 167

Steve Blank

NOVEMBER 24, 2010

A company developing software would have to buy computers and license software from other companies and hire the staff to run and maintain it. Today open source software has slashed the cost of software development from millions of dollars to thousands. Happy Thanksgiving.

Silicon Valley 335

Silicon Valley United States Venture Capital Software Review 335

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

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 260

Lean Silicon Valley Startup RSS 260

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

Steve Blank

MAY 9, 2017

A company developing software would have to buy computers and license software from other companies and hire the staff to run and maintain it. Today open source software has slashed the cost of software development from millions of dollars to thousands. We now have specific management tools to grow startups.

Restful 243

Restful Silicon Valley Puerto Rico San Jose 243

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. A/B testing is set-based design.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

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

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

andrewchenblog.com

MARCH 10, 2010

Coupled with A/B testing, customer development, and thinking through business problems in a scientific, hypothesis-driven way, you end up with a powerful cocktail of techniques to build a modern startup in the most iterative way possible. However, there’s the other side of the coin, which is the product design.

Technical Review 47

Technical Review Design Las Vegas Product 47

Startup Lessons Learned

JULY 30, 2009

I thought Id share a little bit of that, too: I’ve been interested in different approaches to software development going back to 1987 when – in my first company Feld Technologies – my partner Dave Jilk and I started talking about “semi-custom software development&# (way ahead of its time).

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

SEPTEMBER 27, 2010

This is precisely the dilemma that the doctrine of minimum viable product is designed to solve. When people start using quality, reliability, or design as an excuse to delay, it used to make me nervous, even when these suggestions were well intentioned. Rules of thumb can be infuriatingly unhelpful. And it’s really hard.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

AUGUST 1, 2009

My guess is they have lots of people constantly working on interesting new tools for their designers to play with. Discover whats in customers heads, and tackle problems where design is a differentiator. And in some cases, they disregard the results of customer focus groups if they sense that the results are incongruous.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

FEBRUARY 9, 2009

The Lean Startup: a Disciplined Approach to Imagining, Designing, and Building New Products.: The Lean Startup is a practical approach for creating and managing a new breed of company that excels in low-cost experimentation, rapid iteration, and true customer insight. Expo to explain the lean startup concept to a larger audience.

Lean 68

Lean San Francisco Web Advisory Board 68

Startup Lessons Learned

OCTOBER 4, 2008

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

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

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

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

SEPTEMBER 2, 2008

Lessons Learned by Eric Ries Tuesday, September 2, 2008 On deployment My favorite question to ask a software development team is "how do you do a release." The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? You can tell a lot about a company from their deployment flow. Expo SF (May.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

FEBRUARY 10, 2009

You cant make these global efficiency improvements until you get clear about the goal of your development process. That leads to a seemingly-obvious question: what is progress in software development? Heck, thats what it says right there in the agile manifesto. But it worked. We made it. So can you. Expo SF (May.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

DECEMBER 7, 2008

Even if, in a previous life, you were a world expert in some functional specialty, like in-depth market research or scalable systems design, the compressed timeline of a startup makes it irrelevant. These are two other Extreme Programming practices that are explicitly designed to counteract the problems inherent in this situation.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

FEBRUARY 22, 2010

Even if men have an innate advantage at software development, the gap would have to be massive in order to explain why startup after startup has an all-male team. I have personally taught many “non-technical&# people to program – graphic designers, QA folks, even artists and animators.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

Startup Lessons Learned

JANUARY 28, 2009

Its an essential discipline of good software development, especially in startups. Labels: agile , product development , Test-driven development 11comments: William Pietri said. Back when it first came out, Fowlers book Refactoring was what got me into the Agile world, so it holds a special place in my heart.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

Startup Lessons Learned

MAY 27, 2009

The Lean Startup is a practical approach for creating and managing a new breed of company that excels in low-cost experimentation, rapid iteration, and true customer insight. It uses principles of agile software development, open source and web 2.0, No departments The Five Whys for Startups (for Harvard Business R.

Lean 60

Lean Austin San Francisco Continuous Deployment 60

Startup Lessons Learned

DECEMBER 6, 2008

To begin with, see if you can get designers, programmers, and QA on the same team together. The advantages of cross-functional teams are well documented, and for a thorough treatment I recommend the theory in the second half of Agile Software Development with Scrum. Expo SF (May.

San Francisco 74

San Francisco SCRUM Lean Continuous Deployment 74

Startup Lessons Learned

JUNE 15, 2009

The agile software movement has made numerous contributions: continuous integration, which helps accelerate feedback about defects; story cards and kanban that reduce batch size; a daily stand-up that increases tempo. Part of putting this into action is requiring your team to have a very deep understanding of their customers.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

JULY 2, 2009

Five Whys is designed to avoid these nebulous arguments. Furthermore, I think most of what you are suggesting is applicable in companies/ industries that are not software development. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Expo SF (May.

San Francisco 164

San Francisco Lean Technical Review Software Review 164