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
But if you want to practice rapid deployment, you need to be able to deploy that build in one step as well. If you want to do continuousdeployment, youd better be able to certify that build too, which brings us to. For more on continuousdeployment, see Just-in-time Scalability. Can you make a build in one step?
But by taking advantage of opensource, agile software, and iterative development, lean startups can operate with much less waste. One that is powered by three drivers, each of which is a part of a major trend: The use of platforms enabled by opensource and free software. What are the characteristics of a lean startup?
Leverage product development with opensource and third parties. For example, early on at IMVU, we incorporated in tons of opensource projects. Darn good - I have struggled in relevant conversations with our in house move to scrum/agile. Case Study: Continuousdeployment makes releases n.
Heres something I can relate to: We used assembla for subversion, scrums, milestones, wikis, and for general organizational purposes. Scrum reports would come in once a month, nobody was actually responsible for anything. 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