Startup Lessons Learned

APRIL 29, 2013

For example, if your publishing company is thinking of putting out a coffee table book in the U.S. You know you can produce such a volume; the processes you already use for publishing lavish books on baking cakes nearly all apply here.) One way to find out if anybody will buy the book is to go ahead and publish it.

Lean 165

Lean Technical Review Startup Software Review 165

Startup Lessons Learned

NOVEMBER 7, 2008

Labels: customer development , search engine marketing 13comments: Jim Lindstrom said. Its my understanding that at one point (if not currently) Time-Life books did essentially this for their book series. Case Study: Continuous deployment makes releases n. Eric -- This is a pretty interesting idea.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

NOVEMBER 8, 2008

You can learn about customer development, and quite a bit more, in Steves book The Four Steps to the Epiphany. I highly recommend this book for all entrepreneurs, in startups as well as in big companies. This is a self-published book, originally designed as a companion to Steves class at Berkeleys Haas school of business.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

MARCH 16, 2009

In a startup, rather than think of ourselves as having a marketing department and an engineering department, I now believe its better to think of ourselves as focusing our energies on unknown problems and unknown solutions. Following XP puts you in a good place to start doing continuous improvement.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

JANUARY 12, 2010

Last, Ive tried to keep this blog updated with events , slides , audio , video and books that are helpful as well. Most of all, thank you for your continuing support. Last, Ive tried to keep this blog updated with events , slides , audio , video and books that are helpful as well. Have a favorite who I overlooked?

Lean 146

Lean San Francisco Wiki Startup 146

Startup Lessons Learned

NOVEMBER 4, 2008

The best resources there are his book Extreme Programming Explained: Embrace Change and the gentle introduction at extremeprogramming.org. For customer development, start with Steves book The Four Steps to the Epiphany or take a look at his recent Entrepreneurial Thought Leader Lecture.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

FEBRUARY 22, 2009

I'd be interested to hear your opinion of a book we published earlier this year: "Hello World! " The book teaches kids programming with examples written in Python, and is illustrated with fun kid-friendly characters. Case Study: Continuous deployment makes releases n. Can I send you a review copy?

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

JUNE 5, 2009

I think this idea is particularly appealing to those of us from an engineering background. Imagine a general manager that has read The Innovator’s Dilemma and related books, and is therefore trying hard to help her organization make a transition to a new product category via disruptive innovation.

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

MAY 31, 2010

In the meantime his two books, The Monk and the Riddle and Getting to Plan B are both a must-read. In the meantime his two books, The Monk and the Riddle and Getting to Plan B are both a must-read. Case Study: Continuous deployment makes releases n. There are so many more people to thank: Sarah Milstein and the Web 2.0

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

AUGUST 24, 2009

I place them roughly in this order: Movies > Television > Books > Music > Magazines > Radio > Newspapers Each industry is watching the one in front of it sink into the quicksand. When I reviewed a recent product development book, it immediately shot up to Amazon sales rank 300. My blog has over 14000 subscribers, for example.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

JANUARY 19, 2009

One, which is described in great detail in the Mythical Man-Month (in finding that link, I discovered that today is coincidentally the exact 11th anniversary of my first purchasing that book: Jan 19, 1998), is that as you add people to a team or project, there is an increase in communications overhead that makes everyone slightly less productive.

Lean 140

Lean Hiring San Francisco Continuous Deployment 140

Startup Lessons Learned

JUNE 9, 2009

Yet its one of those features thats only ever requested by investors and engineers - never by customers. Books like Crossing the Chasm are excellent, but they can be misleading. Case Study: Continuous deployment makes releases n. Pivot, don't jump to a new vision Why Continuous Deployment?

Lean 60

Lean San Francisco Japan Continuous Deployment 60

Startup Lessons Learned

APRIL 14, 2009

This is an incredible skill, one that most engineers overlook. So heres the question that I pose to you - our startup helps software companies develop a scalable revenue engine in the form of software-specific hardware devices. Case Study: Continuous deployment makes releases n. involved before we go into production.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

SEPTEMBER 18, 2008

Examples, theory, practical advice, links to books, counter-intuitive thinking. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. 4) I would like to see more of what I've seen.

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

Startup Lessons Learned

FEBRUARY 7, 2013

Last May, I shared the news that long-time Lean Startup advocates Brant Cooper and Patrick Vlaskovits were working on a new book called The Lean Entrepreneur featuring illustrations by FAKEGRIMLOCK. That new book is about to hit bookstores everywhere. You can pre-order on their site until February 10 th 2013, and after that on Amazon.

Lean 167

Lean Entrepreneur Agile San Francisco 167

Startup Lessons Learned

OCTOBER 5, 2010

We did our best to package as much content (including almsot a dozen books and ebooks) as well as tools and apps, into one low-priced magic offer. But I am even more excited to report that it will include a hardcover copy of my new Lean Startup book. But thats not all! And theres so much more.

Lean 153

Lean San Francisco Startup Continuous Deployment 153

Startup Lessons Learned

MAY 20, 2010

Heres an excerpt: Philosophy Helps Start-Ups Move Faster - WSJ.com Silicon Valley entrepreneurs and venture capitalists often churn out how-to business books and fancy themselves as management gurus, but few see their methodologies adopted. Case Study: Continuous deployment makes releases n.

Lean 153

Lean San Francisco Arlington Continuous Deployment 153

Startup Lessons Learned

MARCH 4, 2009

In particular, Ive focused on the two channels of communication that were most commonly suggested in the first survey: conferences and books. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Startup Lessons Learned

MAY 3, 2009

This also gives me a chance to clarify that I am no relation to the author of the classic book on positioning , Al Ries ) Next up, heres the video from my talk with Steve Blank at startup2startup. Case Study: Continuous deployment makes releases n. Ive embedded the slides below the video feed.

Video 104

Video San Francisco Continuous Deployment DC 104

Startup Lessons Learned

JULY 13, 2009

Reinertsen is the book for you. Its quite simply the most advanced product development book you can buy. For those who hunger for a rigorous approach to managing product development, Donald Reinertsens book is epic. The book is structured as a series of principles, logically laid out and briefly discussed - 175 in all.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

SEPTEMBER 9, 2009

Or, for something more substantive, how about the top five-most-read posts: Why PHP won Dont launch Five Whys Work in small batches The engineering managers lament But wait, theres more! If all that archive-browsing leaves you hungry for more, you will soon be able to get Startup Lessons Learned in book form. Let me summarize.

San Francisco 84

San Francisco Continuous Deployment Lean DC 84

Startup Lessons Learned

NOVEMBER 13, 2008

His book Toyota Production System: Beyond Large-Scale Production is a fascinating read, even though its decidedly non-practical. Yet there is one specific technique that I learned most clearly from this book: asking why five times. Its why, at my previous job, we were able to get a new engineer completely productive on their first day.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

AUGUST 8, 2009

In particular, we would cover customer development, continuous deployment, minimum viable product, and actionable metrics. How many workshops, books, webinars, blog posts, etc have you read, said "that's awesome", and then never did anything beyond that. Case Study: Continuous deployment makes releases n.

Lean 102

Lean Programming San Francisco Continuous Deployment 102

Startup Lessons Learned

JULY 2, 2009

We started with a simple wiki page with a few bullet points of things that new engineers had tripped over recently. In response to Five Whys that noticed that not all new engineers were reading the list, we expanded it into a new engineer curriculum. We never set out to build a world-class engineering-training process.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

SEPTEMBER 15, 2009

On to what seems to have stuck: kwooleyy : #g2s Showed startup OODA loop developed by USAF pilot John Boyd I included two Boyd-inspired books in the recommended reading list on the right-hand side of this blog: Certain to Wi n and Boyd: The Fighter Pilot Who Changed the Art of War. Case Study: Continuous deployment makes releases n.

San Francisco 92

San Francisco DC Washington Lean 92

Startup Lessons Learned

DECEMBER 16, 2009

That foundational idea, so clearly articulated in books like Lean Thinking, is what originally led me to start using the term lean startup. I had a background in lean manufacturing (book knowledge, anyway) and lean software development (hands on) before encountering Lean Startups. A/B testing is set-based design.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

Startup Lessons Learned

NOVEMBER 5, 2008

Education Guideline Book (1st Edition) Sep 2006 View SlideShare document or Upload your own. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. If not, you might want to take a look.

Advertising 60

Advertising San Francisco Media Continuous Deployment 60

Startup Lessons Learned

APRIL 9, 2009

No engineering team. But where it makes sense, that team may also include engineers building new experiments or prototypes to try with customers. And instead of design, engineering, QA, and operations we have a solution team implementing a startup-centric version of agile development. You need a problem team and a solution team."

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

Startup Lessons Learned

AUGUST 1, 2009

Beyond Apple, we can find examples of the Steve Jobs character at Toyota, in the form of the Chief Engineer. There are some good anecdotes about Chief Engineers in the Toyota Product Development Book. Apple also hired away key engineers from Pixo, who I believe still work there. August 2, 2009 9:50 AM Milton said.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

NOVEMBER 11, 2008

I think the absolute best reading on this subject is a book called Regional Advantage: Culture and Competition in Silicon Valley and Route 128 by AnnaLee Saxenian. The book is really fun to read (how often do you see an academic tome crossed with a real whodunit?). Case Study: Continuous deployment makes releases n.

Silicon Valley 68

Silicon Valley San Francisco Lean Continuous Deployment 68

Startup Lessons Learned

JULY 9, 2009

Reminded me of Randy Komisar's book "The Monk and the Riddle" Concentrating on spotting trends is what Komisar writes of push towards something which ultimately is not sustainable or fulfilling as such. Google was not the first search engine, but it's the one that succeeded. what your experience says about that ?

San Francisco 94

San Francisco Lean Continuous Deployment DC 94

Startup Lessons Learned

OCTOBER 6, 2008

Both are related to a common brain defect we engineers and entrepreneurs seem to be especially prone to. Especially for us introverted engineering types, there is one major drawback to talking to customers: its messy. Engineers just want to build, designers just want to create, product managers just want to spec, etc.

San Francisco 128

San Francisco Lean Continuous Deployment Agile 128

Startup Lessons Learned

DECEMBER 30, 2008

I have found James Surowiecki s book The Wisdom of Crowds particularly helpful in thinking through these issues. This book is Tipping Point - esque , full of anecdotes and interesting social science citations. Let me briefly summarize the part of the book I find most helpful (leaving a few out, which arent germane to todays topic).

San Francisco 83

San Francisco Lean Continuous Deployment DC 83

Startup Lessons Learned

MARCH 27, 2009

In fact, every single lean transformation documented in books like Lean Thinking took place in the midst of serious external threats. Customer Development Engineering : techniques for accelerating your product development. Case Study: Continuous deployment makes releases n.

San Francisco 117

San Francisco Lean Continuous Deployment DC 117

Startup Lessons Learned

SEPTEMBER 5, 2008

Id also recommend Cal Hendersons (flickr) presentations (and book), e.g. [link] And - of course - going through [link] and reading up on the various different approaches different companies have (successfully) taken towards getting scalability at reasonably low cost. Case Study: Continuous deployment makes releases n.

Open Source 107

Open Source San Francisco Continuous Deployment Lean 107

Startup Lessons Learned

SEPTEMBER 29, 2008

Thanks again and if you have any other suggestions or books that I should read, I would be forever in your debt. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Very exciting.

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Startup Lessons Learned

MARCH 13, 2009

Im converted - ordered Garys book as well. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. March 19, 2009 11:47 PM Chandima Cumaranatunge said. Great article. So, heres a question.

San Francisco 168

San Francisco PR Lean Early Stage 168