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

Steve Blank

AUGUST 3, 2012

consisted of product manager, hardware-engineering manager, software-engineering manager, applications analyst, and software designer. That earned us the right to ask questions of fact about their department’s mission, goals, operations, volumes, tools, methods, and success metrics.

San Jose 256

San Jose Technical Review Customer Development Software Review 256

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. Brad Smith is the CEO of Intuit, one of the most successful software companies in Silicon Valley. No BS, no vanity metrics, no launches, no PR.

San Francisco 146

San Francisco Silicon Valley Lean Agile 146

Version One Ventures

APRIL 11, 2019

The first and foremost category of quality for engineers is the mainstream definition of quality: “Did the code work as designed?” Technical design quality. Architectural and software design integrity is very important to us. Technical design is one of the most rewarding parts of code development.

Part-Time VPE 100

Part-Time VPE Software Review Engineer Technical Review 100

crowdSPRING Blog

OCTOBER 20, 2010

These posts and videos are about logo design , web design , startups, entrepreneurship, small business, leadership, social media, marketing, and more! Absolutely Stunning Promotional Poster and Flyer Designs – [link]. Why marketer misuse of metrics may be an addressable cultural issue – [link].

Social Media 91

Social Media Small Business Design Media 91

Gust

APRIL 27, 2014

Software Development Process via Wikipedia. This will include the first version of many critical processes that can be split out later, including market opportunity, requirements, product definition, business model, sales process, and organization. Product development process. Billing and revenue collection.

Startup 187

Startup Institutional Investors Angel Investor Bootstrapping 187

Software By Rob

NOVEMBER 16, 2009

Business of Software is a conference organized by Neil Davidson and Joel Spolsky , and was held this year in San Francisco. The speaking line-up is a who’s who of software bloggers and authors, including Geoffrey Moore, Paul Graham, Dharmesh Shah and Joel Spolsky. There were several great presentations during the conference.

Software Review 47

Software Review Software San Francisco RSS 47

David Teten

APRIL 1, 2021

Nick Kim , Crosscut’s Head of Platform, in his presentation at the 4th Annual VC Platform Summit, shared their Platform development methodology, which he viewed as an exercise in product development. For example, recruiting writ large is useful at all stages of development. Alpaca VC shares their Master Agency List.

Private Equity 78

Private Equity Venture Capital Portfolio Equity 78

ConversionXL

SEPTEMBER 6, 2013

Not because they have a conversion problem but because they never really nail the product or how to market it. So What is Customer Development? Steve Blank, a serial entrepreneur in Silicon Valley, developed a methodology for creating businesses that runs in parallel with the traditional product development process.

Customer Development 126

Customer Development Conversion Developer Customer 126

ConversionXL

APRIL 13, 2017

Jonathan Price wrote on the same Quora thread that he believes growth marketing to differ from regular marketing because it “is technology-centric and it blurs the boundary between marketing and product development.” A growth team, however, is largely overlapped with product, engineering, and design as well.

Analytics 99

Analytics Engineer SEO Channel 99

YoungUpstarts

JUNE 11, 2015

If you know what those numbers (also called metrics) are, how to collect them, and how to evaluate what they mean, you will increase your understanding of what drives your customers. Develop products customers want. Figuring out what customers want and what they will purchase is one of the holy grails of product development.

Analytics 100

Analytics Customer Acquisition Metrics 100

Startup Lessons Learned

FEBRUARY 20, 2009

Lessons Learned by Eric Ries Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. I owe it originally to lean manufacturing books like Lean Thinking and Toyota Production System. 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

Steve Blank

MARCH 3, 2015

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. Seeing Is Believing. The Business Plan is Dead.

Business Plan 120

Business Plan Silicon Valley Saudi Arabia Lean 120

Startup Lessons Learned

APRIL 4, 2010

Kent is a significant figure in the field of software development. Kent is a significant figure in the field of software development. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Startup Lessons Learned

DECEMBER 28, 2009

Or, phrased more hopefully, "I see how you can use continuous deployment to run an online consumer service, but how can it be used for B2B software?" That continuous deployment leads to lower quality software than software built in large batches. Or variations thereof. Implicit in these concerns are two beliefs: 1.

Continuous Deployment 122

Continuous Deployment San Francisco Lean Metrics 122

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. They just assumed it was the way software companies worked. Sound good?

Software Review 164

Software Review Engineer Management Technical Review 164

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. Please leave feedback!) Do you fix bugs before writing code?

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

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

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. Of course, many startups are capital efficient and generally frugal.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Up and Running

MAY 23, 2016

Since the term “cloud computing” was coined in 1996—at least as we have come to understand its meaning—the software as a service industry has exploded. If you use software like LivePlan, you can create this initial “lean plan” in under an hour and then spend your time where it really matters—on validating your idea.

Software Review 74

Software Review Software Delaware Forecast 74

Startup Lessons Learned

APRIL 29, 2013

Eric has talked often about recognizing a startup as an organization designed to create a new product or service under conditions of extreme uncertainty. Most commonly, that’s uncertainty about whether you can build the product at all (what MBAs call “technical risk”) or whether anybody will use or buy it (“market risk”).

Lean 165

Lean Technical Review Startup Software Review 165

Startup Lessons Learned

OCTOBER 5, 2008

These specs are handed to a designer, who builds layouts and mockups of all the salient points. Then the designs are handed to a team of programmers with various specialties. The programmers keep asking for more say in the designs and direction that they work on. First, he writes it nice and clear.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

SEPTEMBER 30, 2008

It became harder and harder to separate how the software is built from how the software is structured. If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? If not, whos going to insist we switch to free and open source software? I dont think so.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

APRIL 14, 2009

Every board meeting, the metrics of success change. Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. And what of the product development team? Time-to-complete-a-sale is not a bad metric for validated learning at this stage.

Customer 167

Customer San Francisco Lean Hockey Stick 167

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. Can this methodology be used for startups that are not exclusively about software?

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

NOVEMBER 6, 2008

Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective. They take things like unit testing, design documents and code reviews more seriously than any other company Ive even heard about. Three concepts I found particularly helpful: Process = discipline.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

Startup Lessons Learned

MARCH 16, 2009

In most agile development systems, there is a notion of the "product backlog" a prioritized list of what software is most valuable to be developed next. The breakthrough idea of agile is that software should be built iteratively, with the pieces that customers value most created first.

Agile 111

Agile Customer Development Developer San Francisco 111

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. Take a look and let me know what you think.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

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

NOVEMBER 14, 2013

Starting on the evening of December 11 and running through December 13—for VIP pass holders only—we’re partnering with UP Global’s Startup Weekend to offer a two-day Lean Startup immersion program , specially designed to teach you how to put Lean Startup theory directly into practice.

Continuous Deployment 162

Continuous Deployment Norway Lean Analytics 162

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. I know many people who think that software works like magic, but to me it actually was magic.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Steve Blank

MAY 14, 2012

———– Whether your venture is a new pizza parlor or the hottest new software product, beware: These nine flawed assumptions are toxic. These founders specify, design, and build a fully featured product using classic product development methods without ever leaving their building.

Balance Sheet 335

Balance Sheet Business Model Customer Development Metrics 335

Up and Running

JULY 26, 2016

Just for reference, Slidebean is a SaaS presentation software where users can add content, and a finished presentation is designed automatically. 1x hacker in charge of product/development. 1x hipster working with both product and growth. Nov-15: Graphic Designer (growth/product).

Revenue 60

Revenue Acquisition Channel Campaign 60

Startup Lessons Learned

FEBRUARY 9, 2009

The Lean Startup: a Disciplined Approach to Imagining, Designing, and Building New Products.: It uses principles of agile software development, open source and web 2.0, Hey Someone else who is extending the agile/lean approach beyond just developing software. Labels: events 2comments: Andrew Meyer said.

Lean 68

Lean San Francisco Web Advisory Board 68

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. Were a software company, so what we do everyday is turn ideas into code.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

AUGUST 26, 2009

Inspiring ideas: real-time biz metrics; safe continuous deployment; A/B split testing. And one last specific practice that came up at this session: feverishaaron : UI, design and programmers are all in the same department, all have the same title, and all are evaluated the same. More recently it's skewed to software & web.

San Francisco 113

San Francisco Silicon Valley Startup Continuous Deployment 113

Startup Lessons Learned

JUNE 15, 2009

Of all the tactics I have advocated as part of the lean startup , none has provoked as many extreme reactions as continuous deployment , a process that allows companies to release software in minutes instead of days, weeks, or months. One is used by engineers to refer to the process of getting code fully integrated into production.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167