Startup Lessons Learned

FEBRUARY 20, 2009

Similar results apply in product management, design, testing, and even operations. When operating with continuous deployment, its almost impossible to have integration conflicts. Luckily, I now have the benefit of a forthcoming book, The Principles of Product Development Flow. Small batches reduce overhead.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

YoungUpstarts

JANUARY 7, 2013

Over the next few decades, this young cohort would comprise a rising proportion of citizens in Asia (31%-40% in Singapore, Korea, Hong Kong and Japan, and more than 51% in Malaysia, Philippines, India and Indonesia). New vistas of opportunities would also be developed as Cloud technologies change the way businesses operate.

Technology 174

Technology Singapore Malaysia Indonesia 174

Startup Lessons Learned

NOVEMBER 4, 2008

It is becoming easier and cheaper for companies to bring products to market, leveraging free and open source software , cloud computing, open social data (Facebook, OpenSocial ), and open distribution (AdWords, SEO). Lean startups have the ability to use this commodity stack to lower costs and, more importantly, reduce time to market.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

NOVEMBER 7, 2008

We spent weeks working on this new product, racing the clock so it would be done in time for the real presidential debates. We had endless arguments internally about what features it should include, how the avatars should look, and how much it should cost. Just load them all in and choose a low cost-per-click. I used to use $.05,

Demand 167

Demand San Francisco Lean Continuous Deployment 167

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. Thats why we need continuous integration and test-driven development.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

APRIL 14, 2009

Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. Their product development team is hard at work on a next-generation product platform, which is designed to offer a new suite of products – but this effort is months behind schedule.

Customer 167

Customer San Francisco Lean Hockey Stick 167

YoungUpstarts

OCTOBER 20, 2016

Thus, having a business environment that is conducive for technological growth is necessary, and it is also the reason why many South Asian countries aside from Japan are hardly mentioned in the big game. In these developing countries, smartphones are acquiring a holy-grail status in the job market, so this is immensely favorable.

Demand 100

Demand Singapore Malaysia Asia 100

Startup Lessons Learned

NOVEMBER 8, 2008

Customer development is a parallel process to product development, which means that you dont have to give up on your dream. Our goal in product development is to find the minimum feature set required to get early customers. This is a common mistake. Lo, my 1032 subscribers, who are you?

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

JUNE 15, 2009

One large source of waste in development is “double-checking.&# For example, imagine a team operating in a traditional waterfall development system, without continuous deployment, test-driven development, or continuous integration. When a developer wants to check-in code, this is a very scary moment.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

MARCH 23, 2009

Pretty soon you’re chasing your own tail a little bit because you’re not operating against a clear, long-term vision of what you’re trying to accomplish. I started writing and teaching about shipping imperfect products a few years ago but this is a far better, practical and more powerful presentation.

San Francisco 167

San Francisco Lean Continuous Deployment Audio 167

Startup Lessons Learned

NOVEMBER 13, 2008

Hes a new employee, and he was not properly trained in TDD So far, this isnt much different from the kind of analysis any competent operations team would conduct for a site outage. This approach is a the heart of breaking down the "time/quality/cost pick two" paradox , because these small investments cause the team to go faster over time.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

NOVEMBER 22, 2008

Lessons Learned by Eric Ries Saturday, November 22, 2008 Net Promoter Score: an operational tool to measure customer satisfaction Ive mentioned Net Promoter Score (NPS) in a few previous posts, but havent had a chance to describe it in detail yet. The whole episode cost us hundreds of thousands of dollars in lost revenue.

.Net 158

.Net Operations San Francisco Lean 158

Startup Lessons Learned

APRIL 9, 2009

So instead of having sales, marketing, and business development, we have a problem team implementing customer development. And instead of design, engineering, QA, and operations we have a solution team implementing a startup-centric version of agile development. Take a look and let me know what you think.

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

Startup Lessons Learned

SEPTEMBER 8, 2009

That is just currently a full personal money sucking process, as you're taxed on income and have no business breaks yet, besides supplies, the majority of costs to start up a business have no tax advantages to creating a start up. Biggest thing for me not on your list is more tax advantages to starting up a company self-funded.

DC 90

DC Washington San Francisco SBIR 90

Startup Lessons Learned

MAY 7, 2009

The idea was that these two people would operate as a unit, with the mentors job performance during this period evaluated by the performance of the new person. The interesting thing about fear is that to reduce it requires two contradictory impulses. First, we can reduce fear by mitigating the consequences of failure.

Continuous Deployment 131

Continuous Deployment San Francisco Software Review Lean 131

Startup Lessons Learned

DECEMBER 8, 2008

Integration risk is the term I use to describe the costs of having code sitting on some, but not all, developers machines. Maybe two different developers made changes to the same underlying subsystem, but in incompatible ways. First, a word about why continuous integration is so important.

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136

Berkonomics

MARCH 17, 2010

Skype provides the infrastructure for cost-free video and audio conferencing and long distance dialing with sound quality often exceeding that of normal communication channels. . 6. A compact all-in-one: When we are at home with our limited space and resources, a great all-in-one printer, scanner, fax is a necessity.

Mobile 59

Mobile Japan Audio Social Network 59

Startup Lessons Learned

JANUARY 4, 2009

This has two major drawbacks: the central directory can become a single point of failure, and there is a performance cost for having to consult the directory ever time you want to access data anywhere in the cluster. Im talking about the actual data-fetching operation. This information is normally maintained by your operations team.

San Francisco 151

San Francisco Architecture Startup Database 151

techcrunch.com

OCTOBER 23, 2010

Tech Gadgets Mobile Enterprise GreenTech CrunchBase TechCrunch TV Disrupt SF More TechCrunch TV Beta Invites Crunchies Elevator Pitches Gillmor Gang Podcasts TechCrunch Europe TechCrunch Trends TechCrunch France TechCrunch Japan Whats Hot: Android Apple Facebook Google Microsoft Twitter Yahoo Zynga Subscribe: From Nothing To Something.

Technical Review 84

Technical Review Cofounder Technical Cofounder Software Review 84

Startup Lessons Learned

FEBRUARY 12, 2009

In the world of startups, this is like trying to sell a product to a very demanding customer who needs to see a lot of features before buying. Resegmented market (low cost variety). Heres a situation where you offer to do the job for 1/10th the cost. They must be thinking "if its costing people their jobs, it must really work.

San Francisco 89

San Francisco Continuous Deployment Ruby Lean 89

Startup Lessons Learned

JANUARY 12, 2009

At the cost of a little extra indirection, you can organize your code around a series of long-lived objects, each of whom communicates with the other objects in simple, easy-to-understand ways. But I think debates about which language, which operating system, even which editor (emacs, vim, Visual Studio) can go on forever. Im curious.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

SEPTEMBER 11, 2009

This single decision wound up costing the company significant revenue and over the course of several months sent its customer growth into decline. In the end, we managed to repair the damage, but only after losing a lot of time and at significant opportunity cost. We were totally unprepared for the magnitude of what happened.

Community 158

Community Management Lean Software Review 158