Guy Nirpaz

JUNE 12, 2010

Guy Nirpaz Blog Thoughts from my startup journey Cloud load testing As a company which operates in the cloud space, we’re experimenting with building a product development company without any servers.

Cloud 45

Cloud EC2 Java RSS 45

Spencer Fry

FEBRUARY 13, 2023

When considering our product development process and track record, however, I simply don’t see the value in the work that they would bring to our team that a developer, designer, or head of product can’t drive themselves. Below you’ll find a copy of the Champion position as outlined in our internal wiki.

Product 72

Product Wiki Developer Hiring 72

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. Good luck, engineering manager. It was painful for a lot of people.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

JULY 29, 2009

Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage. The biggest source of waste in new product development is building something that nobody wants. Leverage product development with open source and third parties.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

JULY 2, 2009

We started with a simple wiki page with a few bullet points of things that new engineers had tripped over recently. Labels: five whys root cause analysis , product development 15comments: Anonymoussaid. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Leave your thoughts in a comment.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

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. Lean Startup Wiki - including a complete list of local meetups and meetup organizers.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

SEPTEMBER 22, 2008

Lessons Learned by Eric Ries Monday, September 22, 2008 Thoughts on scientific product development I enjoyed reading a post today from Laserlike (Mike Speiser), on Scientific product development. I agree with the less is more product development approach, but for a different reason. Now that is fun.

Product Development 68

Product Development Developer San Francisco Product 68

Startup Lessons Learned

JANUARY 18, 2010

If youre interested in contributing a case study for publication here, consider getting started by adding it to the Lean Startup Wiki case study section. I try and follow a formalized Five Whys process (using our internal wiki) for every error. I try and follow a formalized Five Whys process (using our internal wiki) for every error.

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

Startup Lessons Learned

SEPTEMBER 10, 2008

I am convinced one of Joel Spolskys lasting contributions to the field of managing software teams will turn out to be the Joel Test , a checklist of 12 essential practices that you could use to rate the effectiveness of a software product development team. Thoughts on scientific product development Lo, my 5 subscribers, who are you?

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

SEPTEMBER 30, 2008

Own the development methodology - in a traditional product development setup, the VP Engineering or some other full-time manager would be responsible for making sure the engineers wrote adequate specs, interfaced well with QA, and also run the scheduling "trains" for releases. Labels: product development 15comments: mukund said.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

SEPTEMBER 15, 2008

The application of agile development methodologies which dramatically reduce waste and unlock creativity in product development. See Customer Development Engineering for my first stab at articulating the theory involved) Ferocious customer-centric rapid iteration, as exemplified by the Customer Development process.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Startup Lessons Learned

SEPTEMBER 15, 2008

This gets me into trouble, because it conjures up for some the idea that product development is simply a rote mechanical exercise of linear optimization. You just constantly test little micro-changes and follow a hill-climbing algorithm to build your product. April 23, 2010 in San Francisco. Bring your questions.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

JANUARY 12, 2010

The Lean Startup Wiki (hosted by long-time lean startup pbWorks) contains a number of resources, including links to case studies , meetups, tools , and people who have volunteered to help. Its a wiki, feel free to consume and enhance it. Its a wiki, feel free to consume and enhance it. April 23, 2010 in San Francisco.

Lean 146

Lean San Francisco Wiki Startup 146

Startup Lessons Learned

APRIL 7, 2010

In fact, the curse of product development is that sometimes small things make a huge difference and sometimes huge things make no difference. When we’re optimizing, product development teams encounter similar situations. I mean, here we are, paying them to be there, and they won’t use the product!

San Francisco 154

San Francisco Lean Metrics Design 154

Startup Lessons Learned

FEBRUARY 20, 2009

Luckily, I now have the benefit of a forthcoming book, The Principles of Product Development Flow. Labels: five whys root cause analysis , product development 11comments: Peter Severin said. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Interesting post. Bring your questions.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

AUGUST 1, 2009

Also SJ's obsession with better taste (positively) contributes to the overall product development process. There are some good anecdotes about Chief Engineers in the Toyota Product Development Book. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Great post Eric.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

OCTOBER 5, 2008

But first I think we need to save the product manager from that special form of torture only a waterfall product development team can create. Labels: product development 8comments: Vincent van Wylick said. Lean Startup Wiki - including a complete list of local meetups and meetup organizers.

San Francisco 158

San Francisco Management Software Review Product 158

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

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. Still, a startup product development team is a service organization. Labels: hiring , product development 5comments: TedHoward said.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

AUGUST 3, 2009

Refreshing to finally see lean and agile thinking emerge in product/business-floors and not only in technology. Critical also, as the lean company/start-up can not be lean by just using lean principles in IT and not in Product Development/Management - a common misinterpretation of the Toyota Production System.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

SEPTEMBER 22, 2008

Sometimes we have the attitude that the Product Development team is the one responsible for Activation and Retention (hey, a great product would do that naturally) or that the Marketing team is responsible for Revenue and Referral (hey, go get me some money or free customers already). April 23, 2010 in San Francisco.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

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. Lean Startup Wiki - including a complete list of local meetups and meetup organizers.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

SEPTEMBER 7, 2008

In a startup, both the problem and solution are unknown, and the key to success is building an integrated team that includes product development in the feedback loop with customers. 2008 09 06 Eric Ries Haas Columbia Customer Development Engineering View SlideShare presentation or Upload your own. Bring your questions.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

MARCH 16, 2009

Ever since that time, I have struggled to explain how the feedback loop in customer development should interface with the feedback loop in product development. Eric Ries Lean Startup Schematic View Of Agile Development And Customer Development View more presentations from Eric Ries. April 23, 2010 in San Francisco.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

NOVEMBER 7, 2008

Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Startup Lessons Learned season two : Every post from the blogs second year in print form. Startup Lessons Learned for Kindle Startup Lessons Learned - the conference. April 23, 2010 in San Francisco. Bring your questions.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

FEBRUARY 10, 2009

This development philosophy created a culture around rapid prototyping of features, followed by testing them against large numbers of actual customers. It would be hard to argue against this product development strategy, in general. Lean Startup Wiki - including a complete list of local meetups and meetup organizers.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

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. Bring your questions.

San Francisco 128

San Francisco Lean Continuous Deployment Agile 128

Startup Lessons Learned

NOVEMBER 13, 2008

Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Startup Lessons Learned season two : Every post from the blogs second year in print form. Startup Lessons Learned for Kindle Startup Lessons Learned - the conference. April 23, 2010 in San Francisco. Bring your questions.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

OCTOBER 4, 2008

Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Startup Lessons Learned season two : Every post from the blogs second year in print form. Startup Lessons Learned for Kindle Startup Lessons Learned - the conference. April 23, 2010 in San Francisco. Bring your questions.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

JULY 28, 2010

Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Startup Lessons Learned season two : Every post from the blogs second year in print form. Startup Lessons Learned for Kindle Startup Lessons Learned - the conference. April 23, 2010 in San Francisco. Bring your questions.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

Startup Lessons Learned

JUNE 15, 2009

Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Startup Lessons Learned season two : Every post from the blogs second year in print form. Startup Lessons Learned for Kindle Startup Lessons Learned - the conference. April 23, 2010 in San Francisco. Bring your questions.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

JUNE 22, 2009

Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Startup Lessons Learned season two : Every post from the blogs second year in print form. Startup Lessons Learned for Kindle Startup Lessons Learned - the conference. April 23, 2010 in San Francisco. Bring your questions.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

JUNE 17, 2010

Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Startup Lessons Learned season two : Every post from the blogs second year in print form. Startup Lessons Learned for Kindle Startup Lessons Learned - the conference. April 23, 2010 in San Francisco. Bring your questions.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

AUGUST 8, 2009

The economics of these process trade-offs are discussed in the Principles of Product Development Flow.) Heres an excerpt: In a previous article, we called Toyota’s product development system the “second Toyota paradox.&# Labels: product development 5comments: new york web development company said.

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

FEBRUARY 22, 2010

Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Startup Lessons Learned season two : Every post from the blogs second year in print form. Startup Lessons Learned for Kindle Startup Lessons Learned - the conference. April 23, 2010 in San Francisco. Bring your questions.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

Startup Lessons Learned

OCTOBER 26, 2009

Anyone who has worked in a real-world product development team can tell you how utopian that sounds. Anyone who has worked in a real-world product development team can tell you how utopian that sounds. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Bring your questions.

Advisory Board 151

Advisory Board Customer San Francisco Lean 151

Startup Lessons Learned

SEPTEMBER 13, 2008

Thoughts on scientific product development Lo, my 5 subscribers, who are you? Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Q&A with an actual reader The lean startup comes to Stanford You don't need as many tools as you think The three drivers of growth for your business mode.

SEM 164

SEM San Francisco Lean Continuous Deployment 164