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
Continuous DeploymentProgrammingSoftware Development
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.
I am heavily indebted to earlier theorists, and highly recommend the books Lean Thinking and Lean SoftwareDevelopment. 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.
Amsterdam-based Rockstart Accelerator , one of the many, many startup accelerators in Europe, is taking the first class of startups who’ve graduated from its six-month program stateside this month. Wercker : a continuousdeployment solution for softwaredevelopers, hosted in the cloud.
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. Case Study: Continuousdeployment makes releases n. for Harvard Business Revie.
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 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?
Kent is a significant figure in the field of softwaredevelopment. To his credit are Extreme Programming , jUnit, patterns, TDD , the list goes on. Kent is a significant figure in the field of softwaredevelopment. To his credit are Extreme Programming , jUnit, patterns, TDD , the list goes on.
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 softwaredevelopment and user-generated content.
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. A few other highlights from this year’s lineup: How Groupon is using Lean Startup ideas to scale their product development team, by VP of Product Development Suneel Gupta.
Even if men have an innate advantage at softwaredevelopment, the gap would have to be massive in order to explain why startup after startup has an all-male team. I have personally taught many “non-technical&# people to program – graphic designers, QA folks, even artists and animators.
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.
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. 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.
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. Case Study: Continuousdeployment makes releases n. I used to think that investments in metrics were a form of waste. Amazon PostRank
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.
Consider the classic project that was essential to the creation of extreme programming , the Chrysler Comprehensive Compensation System. This was to be a new piece of software to run payroll for Chrysler. What causes projects like this to fail in traditional softwaredevelopment is that the solution is unknown.
I thought Id share a little bit of that, too: I’ve been interested in different approaches to softwaredevelopment going back to 1987 when – in my first company Feld Technologies – my partner Dave Jilk and I started talking about “semi-custom softwaredevelopment&# (way ahead of its time).
TDD plus continuous integration works as a natural feedback loop: if the team is working "too fast" to produce quality code reliably, tests fail, which requires the team to slow down and fix them. Use pair programming and collective code ownership. Pair programming is the most radical, but also the most helpful.
It uses principles of agile softwaredevelopment, open source and web 2.0, 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.
Lessons Learned by Eric Ries Tuesday, September 2, 2008 On deployment My favorite question to ask a softwaredevelopment team is "how do you do a release." You can tell a lot about a company from their deployment flow. After an hour with a team talking dirty about deployment, youll know. How fast do they iterate?
Agile Vancouver : Lean Development for Lean Times On Tuesday April 21st, we are hosting an afternoon event on the application of Lean Principles to softwaredevelopment. This workshop brings together leading thinkers from Lean Production and Lean software. Case Study: Continuousdeployment makes releases n.
When youve mastered that, consider adding operations, customer service, marketing, product management, business development - the idea is that when the team needs to get approval or support from another department, they already have an "insider" who can make it happen. Case Study: Continuousdeployment makes releases n.
It uses principles of agile softwaredevelopment, open source and web 2.0, 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.
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.
We might be a ways away from the reality of a Chief Engineer or Product Director role commonly in softwaredevelopment, but ultimately it's going to be a matter of getting the culture right so that people stick around long enough to develop not only the tactical skills, but also the honed instincts and senses.
Lean manufacturing , agile softwaredevelopment , and Theory of Constraints are all examples of this idea in action. Lean manufacturing , agile softwaredevelopment , and Theory of Constraints are all examples of this idea in action. Case Study: Continuousdeployment makes releases n. Amazon PostRank
Design for ContinuousDeployment – [link]. Legal Contracts for SoftwareDevelopers Who Hate Contracts (w/free contract template tco use today) – [link]. Good to see Harvard evolve its MBA program. I hope other programs follow the lead – [link]. Don’t Be A Free User – [link].
Its an essential discipline of good softwaredevelopment, especially in startups. 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.
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