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. I owe it originally to lean manufacturing books like Lean Thinking and Toyota Production System. Similar results apply in product management, design, testing, and even operations.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

ConversionXL

JUNE 13, 2017

Agile marketing may not be a phrase you hear often, but it’s becoming increasingly popular and important. Traditionally associated with development and product management, agile is a lightweight and, well, agile framework for software development and bringing features and products to market.

SCRUM 112

SCRUM Agile Marketing Development Team Review 112

Startup Lessons Learned

APRIL 26, 2009

Lessons Learned by Eric Ries Sunday, April 26, 2009 Product development leverage Leverage has once again become a dirty word in the world of finance, and rightly so. But I want to talk about a different kind of leverage, the kind that you can get in product development. We didnt think wed able to compete with that.

Product Development 88

Product Development Developer San Francisco Product 88

Startup Lessons Learned

NOVEMBER 8, 2008

Lessons Learned by Eric Ries Saturday, November 8, 2008 What is customer development? When we build products, we use a methodology. We know some products succeed and others fail, but the reasons are complex and the unpredictable. a roadmap for how to get to Product/Market Fit." Whats wrong with this picture?

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

OCTOBER 20, 2008

Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their product development process. He has a good team, and theyve shipped a working product to many customers.

Software Review 164

Software Review Engineer Management Technical Review 164

mashable.com

MAY 9, 2011

a New York-based sizzle reel production company specializing in promotional videos for PR and marketing professionals, and the Young Entrepreneur Council. When making technical hires, we always reach out to our network of programmer friends and ask them to sit in on interviews and review resumes with us. Have an account?

CTO Hire 73

CTO Hire Fractional CTO CTO Technical Review 73

Startup Lessons Learned

NOVEMBER 17, 2008

If you dont have customers, a product, investors, or a board of directors, you can pretty much stay focused on just one thing at a time. Strategy - startups first encounter this when they have the beginnings of a product, and theyve achieved some amount of product/market fit. What is customer development? Expo SF (May.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

JUNE 8, 2009

Lessons Learned by Eric Ries Monday, June 8, 2009 Datablindness Most of us are swimming in a sea of data about our products, companies, and teams. You constantly assess the situation, looking for hazards and timing your movements carefully to get across safely. Too much of this data is non- actionable. We can learn to see.

San Francisco 84

San Francisco Lean Continuous Deployment DC 84

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.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

OCTOBER 16, 2013

One good example is the way in which we''ve adjusted the length of different phases of our agile sprints. We don''t follow a set agile methodology, but rather follow a more home-grown, minimal version of various approaches. During this period, the Palantir Gotham team grew from five developers to around 35.

Lean 167

Lean Startup Software Engineering Agile 167

Startup Lessons Learned

NOVEMBER 29, 2008

The technical interview is at the heart of these challenges when building a product development team, and so I thought it deserved an entire post on its own. The six key attributes spell ABCDEF: Agility. To probe for agility, you have to ask the candidate questions involving something that they know little about.

San Francisco 146

San Francisco Lean Agile Java 146

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. But now she has the vision and ability to design her own software, capitalizing on modern trends (e.g. At best, they could copy. Our advantage was speed.

Software Review 325

Software Review Technical Review Development Team Review Bolivia 325

Steve Blank

JANUARY 21, 2010

In our previous post we posited that Scalable Startups are designed to become large companies. The good news is this team found a business model, product/market fit and a repeatable sales model. By now, the board has a good sense of the skill set of the CEO and executive team as entrepreneurs. What’s Next.

Agile 120

Agile Development Team Review Leadership Merger 120

Startup Lessons Learned

DECEMBER 7, 2008

In a few cases, they are clearly smart people in a bad situation, and Ive written about their pain in The product managers lament and The engineering managers lament. A good architect should be judged, not by the beauty of the diagram, but by the quality of the work that the team does using it. Every day counts, every minute counts.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

www.readwriteweb.com

OCTOBER 7, 2007

In this post, we show you how to go from idea to specified product. Not only that, but the end product will be better architected, more coherent and easier to maintain. Given this, it might surprise you to learn that the vast majority of out-sourced developments do option 1. Write them as a chronological story.

Web 40

Web AJAX Software Review Development Team Review 40

blog.expensify.com

APRIL 24, 2012

Because.NET is designed to extend, not disrupt. NET is designed to tightly integrate with and seamlessly extend the Microsoft stack in extremely powerful but ultimately incremental ways. Some us have evolved past the visual designers. Again, there’s nothing wrong about that if that’s what you want to do.

Java 107

Java PHP Software Review Coder 107

sivers.org

JUNE 25, 2010

They log in to translate the documents, one at a time, marking each finished when done, which sends the file back to the company for review.” Also important: Only go for providers who have great reviews from many past customers. Decline bids from providers without many great reviews. The translator rejects or approves.

CTO Hire 84

CTO Hire Hiring Software Review Technical Review 84