Startup Lessons Learned

AUGUST 8, 2009

Lessons Learned by Eric Ries Saturday, August 8, 2009 Revisiting the Software Design Manifesto (and whats changed since then) My recent article on technical debt and its positive uses generated a fair bit of controversy. The argument itself got me thinking a lot about design and its role in building products.

Software Review 87

Software Review Design Software San Francisco 87

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

Hearpreneur

DECEMBER 29, 2021

Thanks to Wes Marlan, Lighthouse Web Design, Inc ! #2- 7- Providing employee engagement software. My #1 goal for 2022 is to help my company become the number one provider of employee engagement software. It's important to keep business agile. One of the key metrics of success in Real Estate is having a large market share.

Entrepreneur 138

Entrepreneur Social Media Employee Los Angeles 138

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

Steve Blank

MARCH 31, 2014

Today’s workforce has radically different expectations, brands are losing their power, physical channels are being destroyed by virtual ones, market share is less important than market creation, and software is eating world. To manage these employees companies create metrics to control, measure and reward execution. Act Like a Startup.

Private Equity 325

Private Equity Metrics China Intellectual Property 325

ConversionXL

JANUARY 18, 2022

In this article, you’ll learn how to design a successful brand marketing campaign that expresses your brand’s core values, create content your customers crave, and ensure your entire brand ecosystem is designed to support customer loyalty. Marketers must adjust their expectations and metrics with expanded brand tracking.

Marketing 128

Marketing Campaign Software Review Tulsa 128

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

ConversionXL

OCTOBER 14, 2021

In this article, we’ll share key brand tracking metrics and methods for how to measure and optimize your success. Key brand tracking metrics. Supplement brand loyalty metrics with qualitative measures such as brand associations and perceived quality, as these can give you insight into why customers intend to repurchase.

Metrics 157

Metrics Marketing Campaign Audience 157

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

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

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. For software, the easiest batch to see is code. Similar results apply in product management, design, testing, and even operations. I dont think so.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

andrewchenblog.com

MARCH 10, 2010

However, there’s the other side of the coin, which is the product design. After you’ve added a ton of new features and stuck them all on the homepage, you create Product Design debt. Arguably, MySpace is a company that never paid down their product design debt, and their traffic has been impacted as a result.

Technical Review 47

Technical Review Design Las Vegas Product 47

Startup Lessons Learned

SEPTEMBER 7, 2008

In addition to presenting the IMVU case, we tried for the first time to do an overview of a software engineering methodology that integrates practices from agile software development with Steves method of Customer Development. Can this methodology be used for startups that are not exclusively about software? Expo SF (May.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

NOVEMBER 27, 2013

Kent, a veteran programmer, a founder of the Agile method and the creator of Extreme Programming, came armed with anecdotes and lessons from his own experience, as well as a few questions for Eric. So I get to see this hothouse of software design. As a reflex, I always think that. Would that really be a disaster?’

Lean 165

Lean San Francisco Cofounder Programming 165

Startup Lessons Learned

OCTOBER 7, 2016

series that also includes the Future of Work , the Future of Corporate Agility, Skill-Sharing, and more in the weeks leading up to Lean Startup Week. I’ve always been intrigued by the concepts of design thinking and customer empathy and how those concepts might intersect with local government. This interview is part of a “Future of….”

Government 165

Government Lean Startup San Francisco 165

Startup Lessons Learned

OCTOBER 20, 2008

They just assumed it was the way software companies worked. Unfortunately, threats work a lot better at incentivizing people to CYA than getting them to write quality software. When I first encountered agile software techniques, in the form of extreme programming , I thought I had found the answer. Sound good?

Software Review 164

Software Review Engineer Management Technical Review 164

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

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. We can choose to continue paying the interest, or we can pay down the principal by refactoring the quick and dirty design into the better design.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

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!) Can you make a build in one step? Youd better.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

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. November 5, 2008 10:13 AM spanky said.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

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 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. Expo SF (May.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

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. February 9, 2009 7:45 PM Joseph Flahiff said.

Lean 68

Lean San Francisco Web Advisory Board 68

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). Read the rest.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

AUGUST 26, 2009

Inspiring ideas: real-time biz metrics; safe continuous deployment; A/B split testing. Thank you @ericries for drastically altering my perception of agile startup Thank you all so much for your kind words. That meant getting designers, programmers, and QA folks to cross-train and work together as peers. Expo SF (May.

San Francisco 113

San Francisco Silicon Valley Startup Continuous Deployment 113

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?

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 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. Go on an agile diet quickly. And yet, their investors are frustrated. Great post!

Customer 167

Customer San Francisco Lean Hockey Stick 167

ConversionXL

FEBRUARY 28, 2017

There, a smoke test is the process of running test cases involving the “important functionality of a component or system, to ascertain if crucial functions of the software work correctly” Using this definition, smoke tests address questions like… Does the program run? This type of agile thinking is what matters.

Product 48

Product Audience Stock Conversion 48

Startup Lessons Learned

MAY 31, 2010

Kent Beck is deservedly famous for his many contributions in the software industry. Kent Beck is deservedly famous for his many contributions in the software industry. His characteristic humility and clear thinking were on display as he casually demolished one sacred cow after another. Of course ideas have to evolve and change.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

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

Software Review 74

Software Review Software Delaware Forecast 74

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. All customers will see the new software as soon as it’s deployed.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

MARCH 17, 2009

Eric- I am an industrial design student at Virginia Tech. Although Im not a developer, I am captivated by the lean and agile start-up model that you write about. I plan to apply these models to my own ventures, especially within new contexts separate from software and web development. March 19, 2009 9:34 PM Chris Morgan said.

Lean 76

Lean San Francisco Web Continuous Deployment 76

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. Were a software company, so what we do everyday is turn ideas into code. Labels: agile , listening to customers 3comments: hauteroute said. Great points Eric.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

NOVEMBER 8, 2008

For software, we have many - you can enjoy a nice long list on Wikipedia. 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. When we build products, we use a methodology. Heres the catch.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

JANUARY 18, 2010

This case presents a further complication: desktop software. Without being able transparently modify the software in situ, is it still possible to deploy on a continuous basis? Continuous Deployment is a process by which software is released several times throughout the day – in minutes versus days, weeks, or months.

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

ConversionXL

MAY 22, 2017

A Brief History of Marketing Technology Software. launched a contact management software. That was designed to allow information storage and manage customer contact information. Siebel took off the most important features from the Database Marketing Systems and combined them with contact management solutions software.

Customer 92

Customer Marketing Artificial Inteligence Clickthrough 92

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. In almost all Agile Development systems, thousands of automated tests are run against every change to the software.

San Francisco 68

San Francisco Developer Continuous Deployment DC 68