This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
And this year, we’re going to talk not just about business and productdevelopment, but we’ll be exploring one of the Lean Starutp movements next big frontiers: the role of design. For readers of this blog, Steve needs no introduction. Yes, you really can use continuousdeployment – even in an SEC regulated environment.
Or you could work with the writer to create a blog, see if it can attract a readership, and then test whether those readers will pre-order a book—which you can do before you’ve put ten seconds of effort into creating a print volume. You can give advice about applying Lean Startup ideas to business areas other than productdevelopment.
As Shutterstock has grown, there are a few key elements to our continueddevelopment speed: Small, autonomous teams: The more a team can do on their own, the faster they can go. Continuousdeployment: A key component of speed is to keep pushing out work.
Lessons Learned by Eric Ries Monday, June 15, 2009 Why ContinuousDeployment? Of all the tactics I have advocated as part of the lean startup , none has provoked as many extreme reactions as continuousdeployment , a process that allows companies to release software in minutes instead of days, weeks, or months.
Lessons Learned by Eric Ries Monday, January 18, 2010 Case Study: Continuousdeployment makes releases non-events The following is a case study of one entrepreneurs transition from a traditional development cycle to continuousdeployment. ContinuousDeployment is Continuous Flow applied to software.
Lessons Learned by Eric Ries Monday, December 28, 2009 Continuousdeployment for mission-critical applications Having evangelized the concept of continuousdeployment for the past few years, Ive come into contact with almost every conceivable question, objection, or concern that people have about it.
Lessons Learned by Eric Ries Monday, July 13, 2009 The Principles of ProductDevelopment Flow If youve ever wondered why agile or lean development techniques work, The Principles of ProductDevelopment Flow: Second Generation Lean ProductDevelopment by Donald G. Reinertsen is the book for you.
Lessons Learned by Eric Ries Tuesday, February 10, 2009 Continuousdeployment and continuous learning At long last, some of the actual implementers of the advanced systems we built at IMVU for rapid deployment and rapid response are starting to write about it. At IMVU it’s a core part of our culture to ship.
As we head into 2013, it's a good time to reflect on how far the Lean Startup movement has come: When I first started blogging in August of 2008, I had no idea what to expect. Startup blogging was hardly "cool" back then. Lastly, I wanted to share with you the foreword I wrote for The Lean Entrepreneur.
Lessons Learned by Eric Ries Monday, February 16, 2009 Continuousdeployment with downloads One of my goals in writing posts about topics like continuousdeployment is the hope that people will take those ideas and apply them to new situations - and then share what they learn with the rest of us. Thanks for the comments.
Startups especially can benefit by using technical debt to experiment, invest in process, and increase their productdevelopment leverage. The biggest source of waste in new productdevelopment is building something that nobody wants. Leverage productdevelopment with open source and third parties.
Its had tremendous impact in many areas: continuousdeployment , just-in-time scalability , and even search engine marketing , to name a few. I owe it originally to lean manufacturing books like Lean Thinking and Toyota Production System. Labels: five whys root cause analysis , productdevelopment 11comments: Peter Severin said.
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 productdevelopment process. Good luck, engineering manager. It was painful for a lot of people.
It seems your cluster architecture is one of the key architectural constraints making continuousdeployment possible. If you cant deploy to 5% of the nodes and check the results, then how would you accomplish continuousdeployment? Case Study: Continuousdeployment makes releases n.
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 productdevelopment team. For more on continuousdeployment, see Just-in-time Scalability.
One of the sayings I hear from talented managers in productdevelopment is, “good enough never is.&# And, most importantly, it helps team members develop the courage to stand up for these values in stressful situations. Case Study: Continuousdeployment makes releases n. Good enough never is (or is it?)
To illustrate this point, I want to excerpt a large part of a recent blog post by Owen Rogers, who organized my recent trip to Vancouver. I spent some time with his company before the conference and discussed ways to get started with continuousdeployment , including my experience introducing it at IMVU.
Lessons Learned by Eric Ries Wednesday, July 28, 2010 Case Study: kaChing, Anatomy of a Pivot (The following guest post is a new experiment for this blog. If you havent seen it, Pascals recent presentation on continuousdeployment is a must-see; slides are here. Case Study: Continuousdeployment makes releases n.
Lessons Learned by Eric Ries Saturday, August 1, 2009 The Steve Jobs method Image via CrunchBase Its been a long time since I did a post that was primarily a link to another blog with commentary, but I came across something today that I really want to share. Case Study: Continuousdeployment makes releases n. Great post Eric.
Own the development methodology - in a traditional productdevelopment 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: productdevelopment 15comments: mukund said.
Lessons Learned by Eric Ries Sunday, April 26, 2009 Productdevelopment leverage Leverage has once again become a dirty word in the world of finance, and rightly so. But I want to talk about a different kind of leverage, the kind that you can get in productdevelopment. Its a key lean startup concept.
This gets me into trouble, because it conjures up for some the idea that productdevelopment 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. Case Study: Continuousdeployment makes releases n.
Labels: five whys root cause analysis , productdevelopment 15comments: Anonymoussaid. Case Study: Continuousdeployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuousdeployment for mission-critical applica. Leave your thoughts in a comment.
The application of agile development methodologies which dramatically reduce waste and unlock creativity in productdevelopment. 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.
Balancing competing objectives is a recurring theme on this blog - its the central challenge of all management decisions. The technical interview is at the heart of these challenges when building a productdevelopment team, and so I thought it deserved an entire post on its own. Thats OK, were not trying to hire a therapist.
Lessons Learned by Eric Ries Saturday, October 4, 2008 About the author ( Update January, 2010: This post originally dates from October, 2008 back when I first started writing this blog. I hope you take something of value from this blog. Eric, love the blog. Thanks for your professional blog. So thats me, your author.
Customer development is a parallel process to productdevelopment, which means that you dont have to give up on your dream. Our goal in productdevelopment is to find the minimum feature set required to get early customers. A book I am looking forward to read after reading you blog. This is a common mistake.
But first I think we need to save the product manager from that special form of torture only a waterfall productdevelopment team can create. Once the different parts of the team can trust each other again, well have the basis we need to start a true continuous improvement feedback loop.
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 ProductDevelopment/Management - a common misinterpretation of the Toyota Production System.
This is one of the blog we posted about how some company is doing SEO to promote the website. To help find the right keywords, Ive written an article on my blog Web Startup Help that details How to Do Keyword Research for startups. This post has been removed by a blog administrator. link] November 8, 2008 7:13 PM Jason said.
If we’re practicing continuousdeployment, we can be confident that we’ll be able to rush an emergency fix into production without risking introducing further problems. Regular readers of this blog will know the specific methodology I recommend, called Five Whys. To a lot of smart engineers, that sounds crazy.
thanks for the post, i just discovered this blog recently from one of Steven Blank's post. I am very happy while reading your blog. Case Study: Continuousdeployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuousdeployment for mission-critical applica.
blog comments powered by Disqus Newer Post Older Post Home Subscribe via email Blog Archive ▼ 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Case Study: Continuousdeployment makes releases n.
Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. Their productdevelopment 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.
blog comments powered by Disqus Newer Post Older Post Home Subscribe via email Blog Archive ▼ 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Case Study: Continuousdeployment makes releases n.
Sometimes we have the attitude that the ProductDevelopment 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).
In fact, the curse of productdevelopment is that sometimes small things make a huge difference and sometimes huge things make no difference. When we’re optimizing, productdevelopment teams encounter similar situations. I mean, here we are, paying them to be there, and they won’t use the product!
If you find it worthwhile, we'd appreciate a post on the blog to help us spread the word. Case Study: Continuousdeployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuousdeployment for mission-critical applica. Can I send you a review copy?
In a startup, both the problem and solution are unknown, and the key to success is building an integrated team that includes productdevelopment in the feedback loop with customers. 2008 09 06 Eric Ries Haas Columbia Customer Development Engineering View SlideShare presentation or Upload your own.
I had a background in lean manufacturing (book knowledge, anyway) and lean software development (hands on) before encountering Lean Startups. When I read Erics blog I immediately felt at home: the principles were the same even though some of the practices were different. Case Study: Continuousdeployment makes releases n.
Utopian theoretics make great blogs but not great managers. I absolutely love your blog and have a high degree of respect for your ideals. Most of the entries on your blog are very practical with obvious real life examples on how they have worked for you or others. Case Study: Continuousdeployment makes releases n.
Lessons Learned by Eric Ries Monday, March 16, 2009 Combining agile development with customer development Today I read an excellent blog post that I just had to share. In most agile development systems, there is a notion of the "product backlog" a prioritized list of what software is most valuable to be developed next.
By doing a "soft" product launch first, we were able to quickly identify any remaining bugs before they upset too many users. Great blog BTW, adding this to my favourites. OH>>> they can, since i have an ezine and blog, too. I recently came accross your blog and have been reading along. Nice blog.
Lessons Learned by Eric Ries Monday, September 22, 2008 Thoughts on scientific productdevelopment I enjoyed reading a post today from Laserlike (Mike Speiser), on Scientific productdevelopment. I agree with the less is more productdevelopment approach, but for a different reason. Now that is fun.
We organize all of the trending information in your field so you don't have to. Join 5,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content