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. And this was a huge product, which took years to develop.

Software Review 164

Software Review Engineer Management Technical Review 164

SVPG

NOVEMBER 22, 2013

But one of the real advantages from a product point of view is that there’s no legacy to drag along, there’s no revenue to preserve, and there’s no reputation to safeguard. However, once your product develops to the point that it can sustain a viable business (congratulations!), Protect Employees and Customers.

Product 67

Product NDA Continuous Deployment Reputation 67

Startup Lessons Learned

SEPTEMBER 30, 2008

When Ive asked mentors of mine who have worked in big companies about the role of the CTO, they usually talk about the importance of being the external face of the companys technology platform; an evangelist to developers, customers, and employees. Labels: product development 15comments: mukund said.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

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

Startup Lessons Learned

OCTOBER 4, 2008

Although Catalyst folded with the dot-com crash, Ries continued his entrepreneurial career as a Senior Software Engineer at There.com, leading efforts in agile software development and user-generated content. That institution will touch many people in its life: customers, investors, employees, and everyone they touch as well.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

JULY 3, 2009

The same has been true of an unfortunate number of startups, they manage to generate a lot of hype, raise a lot of money, and sometimes make some of their investors, employees, or founders rich. ericries #leanstartup Another new idea in the section on continuous deployment and the cluster immune system. Danger, Will Robinson.

Lean 60

Lean San Francisco Continuous Deployment Cofounder 60

Startup Lessons Learned

MARCH 25, 2009

Agile Vancouver : Lean Development for Lean Times On Tuesday April 21st, we are hosting an afternoon event on the application of Lean Principles to software development. This workshop brings together leading thinkers from Lean Production and Lean software. Case Study: Continuous deployment makes releases n.

Agile 60

Agile Lean San Francisco Continuous Deployment 60

Startup Lessons Learned

OCTOBER 26, 2009

Anyone who has worked in a real-world product development team can tell you how utopian that sounds. Every two months, the company would have a big end-of-milestone meeting, with our Board of Directors, Business Advisory Board, and all employees present. Let me give one small example. Let me give one small example.

Advisory Board 151

Advisory Board Customer San Francisco Lean 151

Startup Lessons Learned

MARCH 17, 2009

Although Im not a developer, I am captivated by the lean and agile start-up model that you write about. I plan to apply these models to my own ventures, especially within new contexts separate from software and web development. Hello Eric, Great talk at the fb developer garage. Case Study: Continuous deployment makes releases n.

Lean 76

Lean San Francisco Web Continuous Deployment 76

Startup Lessons Learned

OCTOBER 28, 2008

We pitch to potential partners, vendors, publishers, conferences, employees, and even lawyers. Its different from selling a product, because it is not part of our regular business practice, is not something that relates to our core competence, and tends not to happen in a repeatable and scalable way. 2comments: King of the Herd said.

San Francisco 128

San Francisco Lean Continuous Deployment DC 128

Startup Lessons Learned

JUNE 17, 2010

Not to be outdone, the technologists on the team had also brought their big guns, and the meeting was packed with employees of every level – from VP’s all the way down to me. They either had to hire a developer onto the art team itself (unthinkable) or learn those development skills themselves (which was, to be fair, really hard).

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

MARCH 4, 2009

The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Combining agile development with customer developm.

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Startup Lessons Learned

MAY 7, 2009

I spent some time with his company before the conference and discussed ways to get started with continuous deployment , including my experience introducing it at IMVU. They were deploying to production with every commit before they had an automated build server or extensive automated test coverage in place.

Continuous Deployment 131

Continuous Deployment San Francisco Software Review Lean 131

Startup Lessons Learned

OCTOBER 19, 2009

Unfortunately, after months or even years of development, many companies discover that customers arent willing to buy their new wares. Thats why some entrepreneurs are trying another approach to product launches: marketing a product online before spending much on research and development or inventory. Read the rest.

San Francisco 137

San Francisco Product Lean Continuous Deployment 137

Startup Lessons Learned

MARCH 23, 2009

Solving the chicken-and-egg platform problem Developers don’t want to develop unless there are customers who are there to buy their products, and customers don’t want to come on the platform unless developers are there selling them something useful. Case Study: Continuous deployment makes releases n.

San Francisco 167

San Francisco Lean Continuous Deployment Audio 167

Startup Lessons Learned

OCTOBER 30, 2008

Over-communicate with employees, investors, customers. Ive also used the voluntary salary reduction tool - its particularly useful as a way to get passionate employees who dont have a lot of personal expenses to buy into the mission of the company at a deep level. Case Study: Continuous deployment makes releases n.

Lean 121

Lean San Francisco Continuous Deployment DC 121

Startup Lessons Learned

FEBRUARY 7, 2010

Whether youre a US citizen or an immigrant, entrepreneur or investor, founder or employee, theres something you can do. Whether youre a US citizen or an immigrant, entrepreneur or investor, founder or employee, theres something you can do. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 118

San Francisco DC Startup Lean 118

Startup Lessons Learned

JUNE 23, 2009

Priority will be given to employees of companies participating in the fbFund REV program, but I am confident that there will be room for members of the general public who want to attend. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Case Study: Continuous deployment makes releases n.

Lean 74

Lean San Francisco Continuous Deployment DC 74

Startup Lessons Learned

MARCH 3, 2009

Lessons Learned by Eric Ries Tuesday, March 3, 2009 Employees should be masters of their own time Every startup should have a culture of learning. The rule is simple: every employee is 100% responsible for how they spend their time. If it sounds simplistic, let me try and make the case that it is actually quite radical. I asked why.

Employee 146

Employee San Francisco Lean Software Review 146

Startup Lessons Learned

JULY 2, 2009

It allows teams to diagnose sources of waste in their development process and continuously improve, reversing the usual trend of teams getting slower over time. These problems can be anything: development mistakes, site outages, marketing program failures, or even internal missed schedules. But Five Whys gives us an alternative.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

SEPTEMBER 19, 2009

In fact theyd cause there to be more jobs for Americans, because the companies they started would hire more employees as they grew. In fact theyd cause there to be more jobs for Americans, because the companies they started would hire more employees as they grew. Case Study: Continuous deployment makes releases n.

San Francisco 150

San Francisco Founder DC Washington 150

Startup Lessons Learned

OCTOBER 16, 2013

We work in prototypically four-week iterations, with quality engineers and software developers working in close collaboration. During this period, the Palantir Gotham team grew from five developers to around 35. But we couldn''t have identified this without having clear metrics (that high bug count) to assess our development process.

Lean 167

Lean Startup Software Engineering Agile 167

Startup Lessons Learned

MARCH 31, 2009

My overwhelming takeaway from the most recent Lessons Learned survey is that there is tremendous hunger out there for in-depth opportunities for entrepreneurs of all stripes to develop their lean startup skills. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

JUNE 21, 2010

Yet, the real stories of successful startups are full of activities that can rightly be called institution-building: hiring creative employees, coordinating their activities, and creating a company culture that delivers results. The Entrepreneur’s Guide to Customer Development ▼ June (3) What is a startup?

San Francisco 168

San Francisco Startup Lean Continuous Deployment 168

Startup Lessons Learned

SEPTEMBER 27, 2010

One of the sayings I hear from talented managers in product development is, “good enough never is.&# And, most importantly, it helps team members develop the courage to stand up for these values in stressful situations. Lessons Learned by Eric Ries Monday, September 27, 2010 Good enough never is (or is it?)

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

NOVEMBER 29, 2008

On the one hand, it gives you insight into what kind of employee the candidate might be. 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. Still, a startup product development team is a service organization.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

AUGUST 20, 2009

Because this radical notion of progress is located firmly in the heads of its employees, and not in any artifacts they produce, the lean startup is employee-centric and knowledge-obsessed. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? It is a truly fun place to work.

Lean 68

Lean San Francisco Startup Continuous Deployment 68

Startup Lessons Learned

OCTOBER 6, 2008

Lessons Learned by Eric Ries Monday, October 6, 2008 When NOT to listen to your users; when NOT to rely on split-tests There are three legs to the lean startup concept: agile product development , low-cost (fast to market) platforms , and rapid-iteration customer development. I think Drucker said it best.

San Francisco 128

San Francisco Lean Continuous Deployment Agile 128

Startup Lessons Learned

MAY 1, 2009

A: have them deploy code to production on their first day as an employee. Related articles by Zemanta Continuous deployment in 5 easy steps (4cloudcomputing.blogspot.com) The Lean Startup workshop coming soon (startuplessonslearned.blogspot.com) The Lean Startup Talk From Web 2.0 made a big impression. What else?"

Lean 60

Lean San Francisco Startup Continuous Deployment 60

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. Instead, five whys kept leading to problems caused by an improperly trained new employee, and wed make a small adjustment. why did that code get written?

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

JULY 9, 2009

Then I wouldnt have the chance to work with the incredible employees and mentors from whom I learned so much. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Case Study: Continuous deployment makes releases n. And yet, missing out on these trends wasnt the end of the world.

San Francisco 94

San Francisco Lean Continuous Deployment DC 94

Startup Lessons Learned

AUGUST 1, 2009

These two principles combine to free up tremendous resources for raw R&D and innovation, because so few people are stuck working on "death march" internal projects or maintaining low-success released products. For one, capacity development. There are some good anecdotes about Chief Engineers in the Toyota Product Development Book.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

FEBRUARY 11, 2009

Heres the short version: hire people from the online communities that develop free software. Its one of the easiest ways to get leverage in your development process, amplifying the power of your team by letting you take advantage of code written by thousands of others. Case Study: Continuous deployment makes releases n.

Software Review 68

Software Review Software Hiring San Francisco 68

Startup Lessons Learned

MARCH 27, 2009

Customer Development : a disciplined approach to finding out if there is a market for your product before its too late. Customer Development Engineering : techniques for accelerating your product development. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 117

San Francisco Lean Continuous Deployment DC 117

Startup Lessons Learned

MARCH 13, 2009

Do some Customer Development instead. They spend so much of their time trying to convince everyone around them that their idea is great and the company is doing well: employees, investors, partners, friends, family, significant others - its a long list. Case Study: Continuous deployment makes releases n.

San Francisco 168

San Francisco PR Lean Early Stage 168

Startup Lessons Learned

DECEMBER 7, 2008

Sometimes, a great hacker has the potential to grow into the CTO of a company, and in those cases all you need is an outside mentor who can work with them to develop those skills. At the end of the day, the product development team of a startup (large or small) is a service organization. Does this sound familiar? Guess what?

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

MARCH 24, 2009

Lessons Learned by Eric Ries Tuesday, March 24, 2009 The metrics and levers of engagement, presentation on Engagement Loops for Facebook Developer Garage SF Ill be presenting a talk at the Facebook Developer Garage SF Wednesday evening. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Metrics 88

Metrics San Francisco Lean Viral 88