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. Some people refer to scope as effectiveness, Units, availability or quality.

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

Startup Lessons Learned

JUNE 8, 2009

So the product development team was busy creating lots of split-tests for lots of hypotheses. That’s causing the Product Owner and team to spend more time with each other reviewing the results of experiments, which is allowing them to learn and iterate much faster. Case Study: Continuous deployment makes releases n.

San Francisco 84

San Francisco Lean Continuous Deployment DC 84

Startup Lessons Learned

MARCH 29, 2010

These are the big questions Ive heard over and over again as Ive traveled presenting the lean startup methodology: "Sure, sounds great for a five-person team, but how can such a fast-paced development process scale? Doesnt the communication overhead of a large team lead to chaos of overlapping experiments and continuously-deployed bugs?" "If

San Francisco 120

San Francisco Lean Continuous Deployment DC 120

Startup Lessons Learned

APRIL 18, 2010

Lean Startups waste less money, because they use a disciplined approach to testing new products and ideas. Lean, when used in the context of lean startup, refers to a process of building companies and products using lean manufacturing principles applied to innovation. Case Study: Continuous deployment makes releases n.

Lean 167

Lean San Francisco Continuous Deployment Startup 167

Startup Lessons Learned

SEPTEMBER 9, 2009

First OODA reference: Ideas. Why Continuous Deployment? * Minimum Viable Product: a guide You can see and even install the Top Posts widget yourself if you like (simple install for blogger blogs): [link] Not bad, dude. Case Study: Continuous deployment makes releases n. As for top posts we have: * 10.0

San Francisco 84

San Francisco Continuous Deployment Lean DC 84

Startup Lessons Learned

JULY 31, 2009

A common question I get asked is "do you know someone amazing that we can hire?" I do my best to play matchmaker, but as those of you who have ever tried to fill a job in a startup know, the most important and elusive quality for a startup hire is fit. Great startups are always hiring, if the fit is right.

San Francisco 68

San Francisco Lean Startup Continuous Deployment 68

Startup Lessons Learned

AUGUST 3, 2009

I've started a Wikipedia page for the Minimum Viable Product to burn it into my brain. You refer to an anonymous Valley-based MMORPG that consumed years and tens of millions in development, but got little commercial traction. Case Study: Continuous deployment makes releases n. There was only one such company.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

FEBRUARY 22, 2010

To be clear, though, this diversity refers only to diversity of opinion, not necessarily to demographic diversity. After all, if you already have an all-male startup, you’re already at a disadvantage when it comes to hiring the very women that could fix that imbalance. Beyond hiring, our actual work process matters, too.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

Startup Lessons Learned

JULY 2, 2009

Labels: five whys root cause analysis , product development 15comments: Anonymoussaid. It would make article more approachable initially, and easier to scan when I go back to reference it. " paragraph have the heading "Training New Hires", above the "Returning to the meeting itself."

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

DECEMBER 30, 2008

Lessons Learned by Eric Ries Tuesday, December 30, 2008 Assessing fit with the Wisdom of Crowds When I wrote earlier about how to conduct a good technical interview , I had only a few things to say about how to assess if the candidate fits in with the team, including this: This responsibility falls squarely to the hiring manager.

San Francisco 83

San Francisco Lean Continuous Deployment DC 83

Startup Lessons Learned

SEPTEMBER 5, 2008

So, for reference, I am Adam, of [link]. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Thoughts on scientific product development Lo, my 5 subscribers, who are you?

Open Source 107

Open Source San Francisco Continuous Deployment Lean 107

Startup Lessons Learned

MARCH 3, 2009

Now he really thought I was nuts, replying "from the recruiter who hired me, of course!" If youre hiring creative, resourceful and smart people (and you are screening for that , right?) post) is very similar, I think the key is to hire smart people first, though. Are you hiring sysadmins? It was my turn to be dumbfounded.

Employee 146

Employee San Francisco Lean Software Review 146

Startup Lessons Learned

SEPTEMBER 8, 2009

I'll add two ideas: The modern structure of university patent licensing and technology transfer works really well in the life sciences and other fields with expensive product development processes. What were you referring to? Case Study: Continuous deployment makes releases n.

DC 90

DC Washington San Francisco SBIR 90

Startup Lessons Learned

JANUARY 4, 2009

And in MMOs, of course, it was a fiction-derived term for parallel servers which has managed to stick (many people refer to parallel VW servers as "shards" now). Case Study: Continuous deployment makes releases n. A quick Google seems to show it as a term coming from someone who worked at Flickr.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

NOVEMBER 22, 2008

I know you probably can't say exactly which issue you were referring to, but was this issue 'behind the doors' so to speak or was this a public issue that up-to-date IMVU-ers would have been familiar with (and thus actively uneasy about)? Case Study: Continuous deployment makes releases n.

.Net 158

.Net Operations San Francisco Lean 158

Startup Lessons Learned

OCTOBER 19, 2009

Take this fictional example of a Seedcamp attendee (actually a composite), which I will refer to as Hairbrush 2.0. Take this fictional example of a Seedcamp attendee (actually a composite), which I will refer to as Hairbrush 2.0. Case Study: Continuous deployment makes releases n. But only startups combine all three.

San Francisco 111

San Francisco Lean Continuous Deployment DC 111

Startup Lessons Learned

FEBRUARY 12, 2009

It takes advantage of the idea, which I owe to Clayton Christensen , that customers buying a product are really "hiring" it to do a specific "job" for them. An employer is trying to hire someone for a specific job, and they think they know what that job is. There are four: Existing market. This is applying for an open job req.

San Francisco 89

San Francisco Continuous Deployment Ruby Lean 89

Startup Lessons Learned

MARCH 20, 2009

Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, and more ► January (6) Lo, my 18891 subscribers, who are you?

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

SEPTEMBER 11, 2009

In fact, I am convinced that if you could find some of IMVU’s earliest adopters, they would say something like this: “sure, those guys at IMVU HQ were helpful in writing code and stuff, but in the end they were just the hired help. It was really the community who built that product.&# My last real concern is with the new 2.0

Community 158

Community Management Lean Software Review 158