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
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 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.
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 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, 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.
Lessons Learned by Eric Ries Sunday, February 22, 2009 Please teach kids programming, Mr. President Of course, what I really mean is: let them teach themselves. See Paul Grahams Why Nerds are Unpopular to learn more) Take a look at this article on a programming Q&A site: How old are you, and how old were you when you started coding?
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.
I am heavily indebted to earlier theorists, and highly recommend the books Lean Thinking and Lean Software Development. I also owe a great debt to Kent Beck, whose Extreme Programming Explained: Embrace Change was my first introduction to this kind of thinking. (So Case Study: Continuousdeployment makes releases n.
Lessons Learned by Eric Ries Sunday, September 7, 2008 Customer Development Engineering Yesterday, I had the opportunity to guest lecture again in Steve Blank s entrepreneurship class at the Berkeley-Columbia executive MBA program. Unfortunately, positioning our product as an "IM add-on" was a complete mistake.
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.
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.
Its why, at my previous job, we were able to get a new engineer completely productive on their first day. We had a great on-boarding process, complete with a mentoring program and a syllabus of key ideas to be covered. Most engineers would ship code to production on their first day. February 11, 2009 8:05 AM Anonymoussaid.
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.
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). for Harvard Business Revie.
Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more. But first I think we need to save the product manager from that special form of torture only a waterfall productdevelopment team can create. Labels: productdevelopment 8comments: Vincent van Wylick said.
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. Yes, you really can use continuousdeployment – even in an SEC regulated environment. Wealthfront CTO Pascal-Louis Perez will show you how.
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. They were deploying to production with every commit before they had an automated build server or extensive automated test coverage in place.
He is the co-author of several books including The Black Art of Java Game Programming (Waite Group Press, 1996). 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.
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 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.
For those whove heard it, it contains a length discourse on the subject of agile software development and extreme programming, including its weaknesses when applied to startups. I assumed he was there to refute my critique of extreme programming, but nothing could be further from the truth. Was that really the Kent Beck?
If done right, a programming interview serves two purposes simultaneously. 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. Still, a startup productdevelopment team is a service organization.
Kent is a significant figure in the field of software development. To his credit are Extreme Programming , jUnit, patterns, TDD , the list goes on. Kent is a significant figure in the field of software development. To his credit are Extreme Programming , jUnit, patterns, TDD , the list goes on. for Harvard Business Revie.
If you havent seen it, Pascals recent presentation on continuousdeployment is a must-see; slides are here. If you havent seen it, Pascals recent presentation on continuousdeployment is a must-see; slides are here. Case Study: Continuousdeployment makes releases n. for Harvard Business Revie.
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.
Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? Case Study: Continuousdeployment makes releases n. Learning is better than optimization (the local ma.
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. Whats wrong with this picture? I can relate to his experience all too well.
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.
Labels: agile , continuousdeployment 1 comments: timothyfitz said. Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? for Harvard Business Revie.
Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? Case Study: Continuousdeployment makes releases n. Learning is better than optimization (the local ma.
Its inspired by the classic OODA Loop and is really just a simplified version of that concept, applied specifically to creating a software productdevelopment team. There are three stages: We start with ideas about what our product could be. Giving rise to three verbs: Implement (programming!) for Harvard Business Revie.
Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? Case Study: Continuousdeployment makes releases n. Learning is better than optimization (the local ma.
We’ve posted the full program for The Lean Startup Conference , and it includes more than three days of events for Gold pass holders and six days of events for VIP pass holders. We asked him a few questions to learn about continuous delivery, why it’s useful, and what engineers and management need to do to implement it.
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. Case Study: Continuousdeployment makes releases n. This is a common mistake.
This is the first post that moves into making specific process recommendations for productdevelopment. Labels: productdevelopment Speed up or slow down? This is the first post that moves into making specific process recommendations for productdevelopment. for Harvard Business Revie. Amazon PostRank
These problems can be anything: development mistakes, site outages, marketing program failures, or even internal missed schedules. I pick that example on purpose, for two reasons: 1) most of the companies I work with deal with this problem and yet 2) almost none of them have any kind of training program in place for new employees.
Ever since that time, I have struggled to explain how the feedback loop in customer development should interface with the feedback loop in productdevelopment. Consider the classic project that was essential to the creation of extreme programming , the Chrysler Comprehensive Compensation System.
Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? Case Study: Continuousdeployment makes releases n. Learning is better than optimization (the local ma.
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?)
None of it would have happened if we had plenty of cash, or were content to count our progress by traffic or productdevelopment milestones. Labels: productdevelopment 4comments: Doug said. Case Study: Continuousdeployment makes releases n. Thank you Eric. March 2, 2009 1:58 PM programiTV said.
I have personally taught many “non-technical&# people to program – graphic designers, QA folks, even artists and animators. Instead of focusing on programs designed to specifically benefit any one group, I think our focus should be on making our companies as meritocratic as possible.
Also SJ's obsession with better taste (positively) contributes to the overall productdevelopment process. There are some good anecdotes about Chief Engineers in the Toyota ProductDevelopment Book. Case Study: Continuousdeployment makes releases n. Will start to pay attention. Great post Eric.
And, as one entrepreneur put it to me, "we understood that a big part of our responsibility in the program was to make sure the mentors have a good experience, by taking their advice to heart and giving them a feeling of being part of our evolution as a company." Case Study: Continuousdeployment makes releases n.
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