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. Ive attempted to embed the relevant slides below. What about a hardware business with some long-lead-time components?

Customer Development 131

Customer Development Engineer San Francisco Developer 131

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 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. ► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th.

Lean 68

Lean San Francisco Continuous Deployment DC 68

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

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. Phases of product & company growth.

Customer Development 168

Customer Development Developer San Francisco Customer 168

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. ► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th.

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

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. I owe it originally to lean manufacturing books like Lean Thinking and Toyota Production System. Im a huge fan of small batches as well.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

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

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. Check if the currently logged-in user is part of this experiment already.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

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

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

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. ► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th.

Lean 140

Lean Hiring San Francisco Continuous Deployment 140

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. I also think you're spot-on with the solution - viewing spreadsheets as big holes to fill in with early learnings. Expo SF (May.

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Gregg Fraley, Author of Jack's Notebook

AUGUST 28, 2018

It includes an overview of key frameworks ( Design Thinking, Agile, Lean, TRIZ, Synectics, Stage-Gate, CPS ) and their essential tools. The Instructor: Gregg Fraley is a master trainer and facilitator who has worked with: Sanofi, Abbvie, Coca-Cola, P&G, US Cellular, YUM, Georgia Pacific, and the University of Chicago, to name a few.

Chicago 25

Chicago Georgia Agile Framework 25

Steve Blank

JUNE 22, 2009

It was still a year away from its IPO. The original Hewlett Packard which made test and measurement products was spun-out and renamed Agilent. The remaining company kept the Hewlett Packard name and focussed on computers. Agilent is a $5.8 But first some background.) Its latest product was an oscilloscope, the HP 150a.

Silicon Valley 169

Silicon Valley RSS California Agile 169

Startup Lessons Learned

AUGUST 3, 2009

MVP, despite the name, is not about creating minimal products. Alan mentions above what I believe is the critical learning element your team needs to gain insight into via the Minimum Viable Product, Compelling Product Offering or other named approach. Some caveats right off the bat. There is a distinction between product and offering.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

FEBRUARY 7, 2010

If youre a startup investor, and you support the goals of the Startup Visa proposal, wed like you lend your name to our efforts. If youre a startup investor, and you support the goals of the Startup Visa proposal, wed like you lend your name to our efforts. You can read about the latest iteration of the proposal at StartupVisa.com.

San Francisco 118

San Francisco DC Startup Lean 118

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

Steve Blank

JUNE 8, 2009

Waterfall, Agile, Lean? M&A, IPO? Building a Chart We realized that if we wrote the names of the vertical markets across the top of the board, and then the startup functions on the left of the board, we could make a chart that could visually compare what differs across the vertical markets. Liquidity – How?

Vertical 123

Vertical Silicon Valley RSS Marketing 123

Agile VC

JULY 11, 2012

The names of these once great, now defunct firms may not be terribly familiar today but here are just a few examples: American Research & Development [Boston] –> Founded by George Doriot and depending how you count it, either the first or second formal VC firm in the US.

Silicon Valley 240

Silicon Valley Carried Interest Cofounder Boston 240

Startup Lessons Learned

JULY 13, 2009

Lessons Learned by Eric Ries Monday, July 13, 2009 The Principles of Product Development Flow If youve ever wondered why agile or lean development techniques work, The Principles of Product Development Flow: Second Generation Lean Product Development by Donald G. Reinertsen is the book for you. This is not for the faint of heart.

Product Development 153

Product Development Developer San Francisco Product 153

The Next Web

JANUARY 24, 2014

Let me drop a few names and you will get the picture: Adyen, Booking.com (acquired by Priceline), Distimo, Mendix, Shapeways, Spilgames, Takeaway.com, TravelBird, WeTransfer and Qandidate. Bringing macro back down to micro – there are Dutch techies and executives ‘ kicking ass and taking names ‘ around the globe.

Netherlands 143

Netherlands Technical Review Stock Silicon Valley 143

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 am very happy while reading your blog.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

JULY 9, 2009

All the good domain names were taken, all the good ideas were being implemented. If Id bought just a handful of the "best of the rest" domain names that were available at the time (for a whopping $70 each), I probably could have just retired right then. Almost all of them got scooped up by pre-IPO Google this time. Expo SF (May.

San Francisco 94

San Francisco Lean Continuous Deployment DC 94

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. But, unfortunately, startups cant afford to adopt that standard.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

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

FEBRUARY 11, 2009

The same is true of brand-name products in almost every category (and it can be measured ). ► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Expo SF (May. Expo (and a call for he.

San Francisco 102

San Francisco Continuous Deployment Lean DC 102

Startup Lessons Learned

OCTOBER 7, 2008

If necessary, consider doing this under a different brand name than the one you are wedded to using. ► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Its like knowing the future.

San Francisco 68

San Francisco Lean Retention SEM 68

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. See if their answer is about tactics or strategy. Founders push for it. In some ways, founders are even worse.

San Francisco 168

San Francisco PR Lean Early Stage 168

Startup Lessons Learned

JULY 31, 2009

lets you post a description of a job without having to reveal the name of the company who is offering it, or the contact information of the hiring manager. Its incredibly simple, and its called joblink.tw. Think of it as a bit.ly Using it to recruit takes less than a minute. Who wants that stuff posted on the internet? Expo SF (May.

San Francisco 68

San Francisco Lean Startup Continuous Deployment 68

Startup Lessons Learned

MARCH 24, 2009

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Combining agile development with customer developm. No departments The Five Whys for Startups (for Harvard Business R. Expo SF (May.

Metrics 88

Metrics San Francisco Lean Viral 88

Startup Lessons Learned

JULY 2, 2009

Pay attention to whether people are comfortable “naming names&# in the meeting. ► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. There’s no easy fix to this problem.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

SEPTEMBER 18, 2008

All I see is a name, an icon, a price, the developers name, and a review star-rating. ► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. And what distinguishes a good app?

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74

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. There are some good anecdotes about Chief Engineers in the Toyota Product Development Book.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166