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, 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. This case presents a further complication: desktop 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 Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. Its had tremendous impact in many areas: continuousdeployment , just-in-time scalability , and even search engine marketing , to name a few. This is easiest to see in deployment.
But by taking advantage of open source, agile software, and iterative development, lean startups can operate with much less waste. I am heavily indebted to earlier theorists, and highly recommend the books Lean Thinking and Lean SoftwareDevelopment. 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 softwareproductdevelopment team. For more on continuousdeployment, see Just-in-time Scalability.
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.
For the last 75 years products (both durable goods and software) were built via Waterfall development. This process forced companies to release and launch products by model years, and market new and “improved” versions. The Old Days – Waterfall ProductDevelopment. Waterfall – The Customer View.
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. My experience is in Enterprise Software - where we are forced to chunk features into formal releases.
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. Can this methodology be used for startups that are not exclusively about software?
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. They just assumed it was the way software companies worked. Sound good?
It may be hard to remember that there was a time when people in the agile softwaredevelopment community thought Lean Startup was incompatible with agile practices. Brad Smith is the CEO of Intuit, one of the most successful software companies in Silicon Valley. Brad doesn’t meet your typical image of a scrappy entrepreneur.
Lessons Learned by Eric Ries Saturday, August 8, 2009 Revisiting the Software Design Manifesto (and whats changed since then) My recent article on technical debt and its positive uses generated a fair bit of controversy. The same might be said of good software. Here we have the beginnings of a theory of design for software.
Best of luck, Your Software." (OK, If a bad change got to production, wed have a built-in set of questions to ask: why didnt the automated tests catch it? I picked up on the 5 whys from Joel on Software earlier this year. Case Study: Continuousdeployment makes releases n. OK, thats not exactly what it said.
It became harder and harder to separate how the software is built from how the software is structured. If not, whos going to insist we switch to free and open source software? Labels: productdevelopment 15comments: mukund said. Case Study: Continuousdeployment makes releases n. I dont think so.
Lessons Learned by Eric Ries Wednesday, February 11, 2009 The free software hiring advantage This is one of those startup tips Im a little reluctant to share, because its been such a powerful source of competitive advantage in the companies Ive worked with. Especially for a startup, not taking maximum advantage of free software is crazy.
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 softwaredevelopment and user-generated content. I know many people who think that software works like magic, but to me it actually was magic.
So the product manager winds up actually having to use the software, by hand, updating the spec and helping create a new test plan. But first I think we need to save the product manager from that special form of torture only a waterfall productdevelopment team can create. This post has been removed by the author.
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 wanted an agile approach that would allow us to build our software architecture as we needed it, without downtime, but also without large amounts of up-front cost. After all, the worst kind of waste in softwaredevelopment is code to support a use case that never materializes.
Kent is a significant figure in the field of softwaredevelopment. Kent is a significant figure in the field of softwaredevelopment. Case Study: Continuousdeployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuousdeployment for mission-critical applica.
We work in prototypically four-week iterations, with quality engineers and softwaredevelopers working in close collaboration. This finally bit us after a four month stint of development blew through its testing schedule by a factor of four: two scheduled weeks turned into two months before the product reached stability.
For those whove heard it, it contains a length discourse on the subject of agile softwaredevelopment and extreme programming, including its weaknesses when applied to startups. I had a background in lean manufacturing (book knowledge, anyway) and lean softwaredevelopment (hands on) before encountering Lean Startups.
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. Apple's first hit product was Apple II, which came after I. Will start to pay attention. Great post Eric.
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.
Lessons Learned by Eric Ries Saturday, November 8, 2008 What is customer development? When we build products, we use a methodology. For software, we have many - you can enjoy a nice long list on Wikipedia. Customer development is a parallel process to productdevelopment, which means that you dont have to give up on your dream.
Jez, who is a principal at ThoughtWorks, co-author of the Jolt Award-winning Continuous Delivery and the forthcoming Lean Enterprise , will address one of the thorniest areas of Lean Startup: how to reduce cycle times by constantly releasing updated software to customers and quickly responding to their feedback.
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. The breakthrough idea of agile is that software should be built iteratively, with the pieces that customers value most created first.
This builds on a lot of great thinking that has come before, like the agile movements insistence that only the creation of working code counts as progress for a softwaredevelopment team. None of it would have happened if we had plenty of cash, or were content to count our progress by traffic or productdevelopment milestones.
Its inspired by the classic OODA Loop and is really just a simplified version of that concept, applied specifically to creating a softwareproductdevelopment team. There are three stages: We start with ideas about what our product could be. Were a software company, so what we do everyday is turn ideas into code.
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?)
Maybe operations has changed the OS configuration in production in a way that is incompatible with some developers change. In many traditional software organizations, branches can be extremely long-lived, and integrations can take weeks or months. I would like the users of my software to test and give their feedback to me.
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.
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. For software engineers, I think this absolutely has to be a programming problem solved on a whiteboard. Still, a startup productdevelopment team is a service organization.
You may have to pay the writer and photographer, and perhaps you’ll spend some money on training the writer to use blogging software and social media tools that help them build a following. Maybe you’ve got technical advice for getting the most out of A/B testing on software projects. Note that this isn’t a free process.
Labels: five whys root cause analysis , productdevelopment 15comments: Anonymoussaid. Furthermore, I think most of what you are suggesting is applicable in companies/ industries that are not softwaredevelopment. It's so old and so buggy that it's a real pain to ship 3D software on it.
It is becoming easier and cheaper for companies to bring products to market, leveraging free and open source software , cloud computing, open social data (Facebook, OpenSocial ), and open distribution (AdWords, SEO). Agile softwaredevelopment. Agile allows companies to build higher quality software faster.
MUDs made the essential truth about software into a powerful metaphor: that code is magic, giving those who wield it the ability to create new forms of value literally out of thin air. Case Study: Continuousdeployment makes releases n. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Expo (and a call for he.
Inspiring ideas: real-time biz metrics; safe continuousdeployment; A/B split testing. More recently it's skewed to software & web. Case Study: Continuousdeployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuousdeployment for mission-critical applica.
Kent Beck is deservedly famous for his many contributions in the software industry. Kent Beck is deservedly famous for his many contributions in the software industry. Case Study: Continuousdeployment makes releases n. Do you know the difference between Durant and Sloan ? If not, youd better watch video of his talk ASAP.
While the customer development framework of Four Steps is universally relevant, The Entrepreneur’s Guide updates its practices for modern startups. Four Steps primarily centers its stories and case studies on B2B hardware and software startups. Case Study: Continuousdeployment makes releases n.
Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective. But its helpful to take a detailed look inside the highly agile process used by Google to ship software. 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