Startup Lessons Learned

DECEMBER 14, 2017

Editor’s Note: We wrapped up the 2017 Lean Startup Week in San Francisco just a few weeks ago, and we’re excited to share with you some of the best lessons learned in entrepreneurship and corporate innovation. To support the three Cs, ING has also developed their own iterative practice named PACE.

Lean 245

Lean Startup CTO Hire Cofounder 245

Hearpreneur

DECEMBER 16, 2020

We’ve recently opened 2 new locations in San Francisco and New York so our # 1 goal in 2021 is to make similar partnerships in new services areas and assist the underserved families in these 2 new cities. 4- Remain agile as a brand. My goal is to develop a name for myself and establish a personal brand in my industry.

Entrepreneur 147

Entrepreneur Agile Artificial Inteligence San Francisco 147

YoungUpstarts

JULY 30, 2015

Back in early 2003, a Dane named Janus Friis and a Swede named Niklas Zennström had an idea for a software application, and founded a business with the help of three Estonian software developers. They set about registering an internet domain name and preparing for the release of a Beta version of their app later that year.

Dominican Republic 100

Dominican Republic Global San Francisco Arizona 100

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. April 23, 2010 in San Francisco. Thank you for your nice posting.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

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. April 23, 2010 in San Francisco. He previously co-founded and served as Chief Technology Officer of IMVU. Expo SF (May. Bring your questions.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

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

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. Labels: agile , continuous deployment , lean startup , product development , Test-driven development 4comments: Nivi said. April 23, 2010 in San Francisco. But it worked.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

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. Sounds very similar to agile development which is the way. April 23, 2010 in San Francisco. No doubt about it, small batches are the way to go RT www.anonymity.eu.tc Expo SF (May.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

AUGUST 26, 2009

As a result, for a lot of these companies, Boulder is just a gateway to San Francisco. 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. Expo SF (May.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

SEPTEMBER 27, 2010

Lean manufacturing , agile software development , and Theory of Constraints are all examples of this idea in action. In fact, we know so much that we already know what they will care enough about (namely, the product’s quality – as opposed to, say, missing features). However, a commitment to quality alone is not enough.

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. The book takes its name from Steves theory of the four stages of growth any startup goes through. April 23, 2010 in San Francisco.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Steve Blank

MAY 9, 2017

I lived through the time when working in my first job in Ann Arbor Michigan we had to get out a map to find out that San Jose was not only in Puerto Rico but there was a city with that same name in California. And that’s where my plane ticket ought to take me to install some computer equipment.

Restful 222

Restful Silicon Valley Puerto Rico San Jose 222

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. April 23, 2010 in San Francisco. 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. Expo SF (May.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

MARCH 22, 2010

Many of these companies are started by entrepreneurs, and are now household names: Google, Yahoo, eBay and Intel. Many of these companies are started by entrepreneurs, and are now household names: Google, Yahoo, eBay and Intel. April 23, 2010 in San Francisco. Startups are the lifeblood of our economy. Expo SF (May.

San Francisco 121

San Francisco Indiana Lean Startup 121

Steve Blank

APRIL 20, 2009

When I read the funny names of these microwaves devices… Backward wave oscillators, TWT’s, Magnetrons…long silent memories came back. Poulsen Wireless was later bought by Federal Telegraph of San Francisco. The HP and Agilent credit union is called “Addison Avenue&#. to do that.

Silicon Valley 270

Silicon Valley RSS San Francisco Technical Review 270

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. April 23, 2010 in San Francisco. Expo SF (May.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 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 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. April 23, 2010 in San Francisco. It strokes your ego. Expo SF (May. Conference streaming, sponsors, discounted tickets. Learning is better than optimization (the local ma. Bring your questions.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

OCTOBER 20, 2008

When I first encountered agile software techniques, in the form of extreme programming , I thought I had found the answer. I explained it to people this way: agile lets you make the trade-offs visible to whole company, so that they can make informed choices. Even worse, agile wasnt really helping me ship higher quality software.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

AUGUST 1, 2009

In talking with Mary Poppendieck about it, she said that the Chief Engineer role at 3M was called a "Product Champion" The name is less important than understanding the depth of competence that this person has, and what it takes to build it. April 23, 2010 in San Francisco. Expo SF (May. Bring your questions.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

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. Yet other agile principles suggest the opposite, as in YAGNI and DoTheSimplestThingThatCouldPossiblyWork. Reconciling these principles requires a little humility.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

APRIL 14, 2009

Now, in some situations, this over-selling would lead to a secondary problem, namely, that customers would realize they had been duped and refuse to re-subscribe. Go on an agile diet quickly. With a product development team that is not shipping, any agile methodology will surface major problems quickly. Great post! Expo SF (May.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

JULY 2, 2009

Pay attention to whether people are comfortable “naming names&# in the meeting. 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? Expo SF (May.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

OCTOBER 26, 2009

In previous posts, I’ve mentioned quite a few of these, including these most important ones: having engineers post on the forums in their own name when they make a change routinely split-testing new changes routinely conducting in-person usability tests and interviews Net Promoter Score Each of these techniques is fundamentally bottoms-up.

Advisory Board 151

Advisory Board Customer San Francisco Lean 151

Startup Lessons Learned

OCTOBER 11, 2009

Ironically, meetings like this had given data and experimentation a bad name inside this company. This team had been working for many months in a standard agile configuration: a disciplined engineering team taking direction from a product owner who would prioritize the features they should work on. What a waste. And who can blame them?

San Francisco 133

San Francisco Lean Metrics Continuous Deployment 133

Startup Lessons Learned

JANUARY 12, 2009

Some of them are probably still cursing my name, because - lets face it - PHP can be pretty painful. Almost every PHP-based website is burdened with ugly URLs that contain the name of the file that implements each page. The IMVU downloadable client, just to name one example, is written primarily in python.

PHP 166

PHP Software Review Ruby San Francisco 166

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. April 23, 2010 in San Francisco. This can be especially challenging for HR professionals who measure their success based on the number of jobs they fill. Expo SF (May.

Lean 140

Lean Hiring San Francisco Continuous Deployment 140

Startup Lessons Learned

MARCH 13, 2009

Who doesnt want to see their name in print? 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. April 23, 2010 in San Francisco. See if their answer is about tactics or strategy. Founders push for it.

San Francisco 168

San Francisco PR Lean Early Stage 168

Startup Lessons Learned

SEPTEMBER 18, 2008

All I see is a name, an icon, a price, the developers name, and a review star-rating. 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? I cant really tell.

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74

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

Startup Lessons Learned

JANUARY 18, 2010

Ive previously named his post Achieving Flow in a Lean Startup as one of my favorite blog posts of 2009. My transition to Continuous Deployment Prior to adopting continuous deployment, I used to release software on a weekly schedule (come rain or shine) which I viewed as pretty agile, disciplined, and aggressive. Expo SF (May.

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

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

Startup Lessons Learned

JUNE 5, 2009

We're starting our new business, fanminder.com, to help small merchants instantly communicate with their customers, and I'm increasingly hearing your name and reading your keen insights. April 23, 2010 in San Francisco. Keep them coming, they're a help.Maybe one day we'll meet up. Expo SF (May.

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

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. April 23, 2010 in San Francisco. Expo SF (May.

Metrics 88

Metrics San Francisco Lean Viral 88

Startup Lessons Learned

SEPTEMBER 22, 2008

We had all the tools in place but we didn’t actually practice agile development. No fancy tools needed here — it’s about the mentality, attention to detail, and the actions that foster agile development, not the tools & systems you set up in place to facilitate this. April 23, 2010 in San Francisco.

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68

Startup Lessons Learned

DECEMBER 14, 2009

This attention is valuable to yet another set of people: namely, the traditional businesses (see above) who are using marketing to grow, and are looking to advertise to new prospects. April 23, 2010 in San Francisco. Those other consumers pay for this content sometimes with money, but more often with their attention.

Customer 156

Customer San Francisco Viral Lean 156

Startup Lessons Learned

APRIL 7, 2010

I’m sure other disciplines have their own names for it; even protozoans exhibit this behavior (its called taxis ). I’m sure other disciplines have their own names for it; even protozoans exhibit this behavior (its called taxis ). April 23, 2010 in San Francisco. Expo SF (May. Bring your questions.

San Francisco 154

San Francisco Lean Metrics Design 154