Startup Lessons Learned

NOVEMBER 7, 2008

So, if youre interested in helping avoid mistakes like that, here are the steps: Get a domain name. It doesnt have to be the worlds catchiest name, just pick something reasonably descriptive. If youre concerned about sullying your eventual brand name, dont use your "really good" name, pick a code name.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

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. Eric Names matter. There is a dark side to naming.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

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

A Smart Bear: Startups and Marketing for Geeks

JULY 19, 2010

During a lull in her practice she got a serendipitous opportunity to shift gears completely and ended up leading software product development teams. Some examples of a feature being a company's primary advantage are: Apple compromises everything in the name of design. Even "cool, agile" companies like 37signals are trapped.

Software Review 325

Software Review Technical Review Development Team Review Bolivia 325

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. Naturally, we already know the standard of quality that they will use to judge our product.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

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 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. The batch size is the unit at which work-products move between stages in a development process.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

SEPTEMBER 15, 2008

If she is, return the name of the hypothesis she was exposed to before. Return the name of the hypothesis chosen or assigned. From the point of view of the caller of the function, they just pass in the name of the experiment and its various hypotheses. Thoughts on scientific product development Lo, my 5 subscribers, who are you?

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

JUNE 22, 2009

Each has its own iterative process: customer development and agile development respectively. Pivotal Labs doesn't carry "Pivot" in its name by accident. I'm glad there's a 'name' for this part of the process Eric. Thank you for your nice posting. I like this term. great metaphor.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

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

A Smart Bear: Startups and Marketing for Geeks

AUGUST 30, 2010

Ideally, by the time I code it up, we'll have many customers using the platform which means I'll be working on a product I know is viable, and that's paying for the time I'm spending to automate it. Agile Development, meet Agile Business. After your product launch. Point #1: Developing a Proof of Concept.

Software Review 284

Software Review Startup Technical Review Hosting 284

Startup Lessons Learned

FEBRUARY 10, 2009

Heck, thats what it says right there in the agile manifesto. In a lot of cases, thats just a fancy name for revenue or profit, but not always. This development philosophy created a culture around rapid prototyping of features, followed by testing them against large numbers of actual customers. If a feature worked, wed keep it.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

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. He previously co-founded and served as Chief Technology Officer of IMVU. While an undergraduate at Yale Unviersity, he co-founded Catalyst Recruiting. Expo SF (May.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

AUGUST 1, 2009

Also SJ's obsession with better taste (positively) contributes to the overall product development process. There are some good anecdotes about Chief Engineers in the Toyota Product Development Book. I really enjoyed this article, my first time reading any of your stuff. Will start to pay attention. Great post Eric.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

SEPTEMBER 13, 2008

We would pretty much bid on any phrase that was "[name of competitive product] chat" and variations like that. 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?

SEM 164

SEM San Francisco Lean Continuous Deployment 164

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

JULY 2, 2009

Pay attention to whether people are comfortable “naming names&# in the meeting. Labels: five whys root cause analysis , product development 15comments: Anonymoussaid. Why didn’t our tests/QA/immune system catch and prevent the problem? Why wasn’t it immediately obvious how to fix the problem?

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Steve Blank

JUNE 25, 2009

These companies would take our computers and put their name on them and resell them to their customers. They couldn’t keep up with the fast product development times that were enabled by using standard microprocessors. So their management teams were insisting that they OEM (buy from someone else) these products.

Technology 145

Technology Silicon Valley Fractional VPE Part-Time VPE 145

Startup Lessons Learned

SEPTEMBER 12, 2008

It’s easy to overestimate the impact of this kind of traffic because it just feels good to have your name and company featured. Thoughts on scientific product development Lo, my 5 subscribers, who are you? It strokes your ego. Expo SF (May. Conference streaming, sponsors, discounted tickets.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

AUGUST 26, 2009

Accept that many successful companies are going to want to be backed by big-name firms in other cities. Thank you @ericries for drastically altering my perception of agile startup Thank you all so much for your kind words. Then, create an encouraging environment for early-stage companies. I was really overwhelmed this time.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

APRIL 7, 2010

In fact, the curse of product development is that sometimes small things make a huge difference and sometimes huge things make no difference. I’m sure other disciplines have their own names for it; even protozoans exhibit this behavior (its called taxis ). I understand and respect why optimizers want to do tests like that.

San Francisco 154

San Francisco Lean Metrics Design 154

Startup Lessons Learned

OCTOBER 26, 2009

The key to successful integration of customer feedback is to make each kind of collection part of the regular company discipline of building and releasing products. Anyone who has worked in a real-world product development team can tell you how utopian that sounds. Expo SF (May.

Advisory Board 151

Advisory Board Customer San Francisco Lean 151

Startup Lessons Learned

MARCH 13, 2009

Who doesnt want to see their name in print? gave us two years of a beta product to build up the service and the brand awareness. Now that were beginning our first marketing, the key partners we need have heard our name long enough to trust us. Combining agile development with customer developm. Expo SF (May.

San Francisco 168

San Francisco PR Lean Early Stage 168

Startup Lessons Learned

JULY 30, 2009

I want to thank Techstars for putting this event together and giving me a chance to experience the scene, even if it lacks a name. Traveling to new startup hubs is one of my favorite things about being able to do this full-time. For what its worth, I like Silicon Mountain. Brad Feld also had some thoughts on this event on his blog.

Lean 68

Lean San Francisco Continuous Deployment DC 68

ConversionXL

SEPTEMBER 5, 2019

The first, according to Dr. David Travis at UserFocus , was agile development : Dr. David Travis: “‘Development’ teams morphed into ‘design’ teams. To use the agile terminology, design teams wanted to get a ‘shared understanding’ of their users and they were suspicious of any attempt to set requirements in concrete.”.

Software Review 115

Software Review Design Agile Analytics 115

Startup Lessons Learned

JANUARY 4, 2009

Imagine you want to store data about customers, each of whom has "last name" field in your database. The problem should be familiar to anyone who plays Scrabble: not all letter are equally likely to be used as the first letter of someones name. Give each entity a name. For example, consider this simple scheme.

San Francisco 151

San Francisco Architecture Startup Database 151

Hearpreneur

SEPTEMBER 22, 2021

Tesla has always put a huge emphasis on product development and technological advancement. They dedicate themselves to constant innovation in not only the technology and products that they offer to the public, but as a corporate entity as well. For me, it's a live example of agile and sustainable business.

Technical Review 139

Technical Review Entrepreneur Software Review SEO 139

Startup Lessons Learned

FEBRUARY 22, 2010

Now, whenever I screen resumes, I ask the recruiter to black out any demographic information from the resume itself: name, age, gender, country of origin. Now, whenever I screen resumes, I ask the recruiter to black out any demographic information from the resume itself: name, age, gender, country of origin. “Who is this guy?&#

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

ConversionXL

MARCH 7, 2017

The first, according to Dr. David Travis at UserFocus , was agile development : Dr. David Travis: “‘Development’ teams morphed into ‘design’ teams. To use the agile terminology, design teams wanted to get a ‘shared understanding’ of their users and they were suspicious of any attempt to set requirements in concrete.”.

Software Review 102

Software Review Design Agile Analytics 102

Startup Lessons Learned

JANUARY 18, 2010

Recently, he was bitten by the lean startup bug and has started writing about his experiences attempting to apply lean startup and customer development principles. Ive previously named his post Achieving Flow in a Lean Startup as one of my favorite blog posts of 2009. Expo SF (May. Conference streaming, sponsors, discounted tickets.

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

ConversionXL

APRIL 3, 2018

Corporate Agility. Transparency correlates to agility (Does your CEO know how many tests you ran last month?). Map out each lifecycle stage and variations, and name each. Be agile, move at the speed of business, don’t hold up product development. Culture of Innovation. Continuous Optimization.

Retention 106

Retention Artificial Inteligence Channel Email 106

Startup Lessons Learned

SEPTEMBER 18, 2008

Even with only a few months of development, third parties have crammed every single category in the store full of apps. All I see is a name, an icon, a price, the developers name, and a review star-rating. Thoughts on scientific product development Lo, my 5 subscribers, who are you? I cant really tell.

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74

Startup Lessons Learned

JANUARY 19, 2009

Much of what I have found effective is counter-intuitive, because it requires investing more effort in each hire - all in the name of efficiency. Its one of the hardest things to see while its happening, and its one of the hardest mistakes to undo, because of the human and emotional costs of layoffs. Expo SF (May.

Lean 140

Lean Hiring San Francisco Continuous Deployment 140

Up and Running

SEPTEMBER 28, 2015

Scrum: a flexible way to manage product development. Scrum comes to us from the worlds of product and software development, where creative iteration and collaboration are of the utmost importance. . Development of any kind needs to be able to react to changes in real-time, and to pressure from other teams.

SCRUM 60

SCRUM Japan China Agile 60

Startup Lessons Learned

MARCH 24, 2009

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? Combining agile development with customer developm. Expo SF (May. Join the Lean Startup discussion at Web 2.0

Metrics 88

Metrics San Francisco Lean Viral 88

Up and Running

MAY 23, 2016

Another great way to test your idea is to create a minimum viable product, or MVP. This is the simplest version of your product minus the frills and frosting. It’s a particularly popular strategy in the world of product development and is used to quickly and quantitatively test a product or a product feature.

Software Review 74

Software Review Software Delaware Forecast 74

Transformify

JANUARY 2, 2021

1- Scrum: Scrum is an agile project management methodology with a focus on delivering products as fast as possible. As a more aggressive agile project management methodology, Kanban is all about releasing products faster by focusing only on the tasks that are important. Contrary to Scrum which allocated a fixed time (i.e.

SCRUM 75

SCRUM Management Development Team Review Agile 75