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. Managing timelines instead of queues.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

NOVEMBER 29, 2008

Finding great engineers is hard; figuring out whos good is even harder. Balancing competing objectives is a recurring theme on this blog - its the central challenge of all management decisions. The six key attributes spell ABCDEF: Agility. If done right, a programming interview serves two purposes simultaneously. Communication.

San Francisco 146

San Francisco Lean Agile Java 146

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. The last thing you need is a manager telling you how to do your job. When they see a problem with the teams process, why dont they just fix it?

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

NOVEMBER 17, 2008

Id like to talk about a technique Ive used to help manage this growth without slowing down. This technique rests on three things: identifying the kinds of work that need to get done, creating the right type of teams for each kind, and steering the company by allocating resources among them. Expo SF (May.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

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

SoCal CTO

FEBRUARY 13, 2013

Examples might be a recommendation engine, search engine, matching engine or something with a complex interface. Even with these, you will have paper-tested your MVP, but the reality is that customers will not be able to assess the value to them until they actually use it. Review the code being built.

Technical Cofounder 338

Technical Cofounder Technical Review CTO Hire Fractional CTO 338

mashable.com

MAY 9, 2011

Not only do they need to have a high level of diversified technical prowess and proficiency, but they also need to possess strong leadership and project management capabilities. However, it’s more important that the CTO have exceptional interpersonal skills and be able to manage a team effectively.

CTO Hire 73

CTO Hire Fractional CTO CTO Technical Review 73

Startup Lessons Learned

JUNE 8, 2009

You constantly assess the situation, looking for hazards and timing your movements carefully to get across safely. So the product development team was busy creating lots of split-tests for lots of hypotheses. Each day, the analytics team would share a report with them that had the details of how each test was doing.

San Francisco 84

San Francisco Lean Continuous Deployment DC 84

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

Startup Lessons Learned

APRIL 26, 2009

The idea of leverage is simple: for every ounce of effort your product development team puts into your product, find ways to magnify that effort by getting many other people to invest along with you. That engine of creativity has led to a catalog of something like 2 million virtual goods authored by a hundred thousand developers.

Product Development 88

Product Development Developer San Francisco Product 88

www.readwriteweb.com

OCTOBER 7, 2007

These serve to ensure that everyone who ends up on the development team knows what the system is for. More than one person can review it, but only one person can author. Theres an engineer currently looking at it, hopefully it (along with the email mock-up) should be back online within the hour.

Web 40

Web AJAX Software Review Development Team Review 40

blog.expensify.com

APRIL 24, 2012

And.NET’s languages (C#, IronPython, managed C++, etc.) How about reviewing some of the incredible work being done by the likes of Mark Rendle, Ben Vanderveen, Alex Robson, Jon Skeet, Chris Patterson, Glen Block, Rob Eisenberg or Steve Sanderson? are also reasonable and flexible. The rest of us have some fine dining to enjoy.

Java 107

Java PHP Software Review Coder 107