Agile Continuous Deployment SCRUM 
Startup Lessons Learned
MARCH 16, 2009
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. Jim Murphy is a long-time agile practitioner in startups. But startups sometimes have trouble applying agile successfully.
Startup Lessons Learned
SEPTEMBER 15, 2008
But by taking advantage of open source, agile software, and iterative development, lean startups can operate with much less waste. So far, I have found "lean startup" works better with the entrepreneurs Ive talked to than "agile startup" or even "extreme startup.") Case Study: Continuous deployment makes releases n.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
SEPTEMBER 10, 2008
I know plenty of people who prefer more advanced source control system, but my belief is that many agile practices diminish the importance of advanced features like branching. But if you want to practice rapid deployment, you need to be able to deploy that build in one step as well. Can you make a build in one step? Youd better.
Startup Lessons Learned
OCTOBER 5, 2008
Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more. I went through some of this in bringing agile methodologies to my current firm - except that I am the product manager in question at this case. Case Study: Continuous deployment makes releases n.
Startup Lessons Learned
APRIL 9, 2009
Thats the essence of so many of the lean startup techniques Ive evangelized: customer development , the Ideas/Code/Data feedback loop , and the adaptation of agile development to the startup experience. Creating a company-wide feedback loop that incorporates both customer development and agile development is a challenge.
Startup Lessons Learned
JULY 29, 2009
I hope to show why lean and agile techniques actually reduce the negative impacts of technical debt and increase our ability to take advantage of its positive effects. Yet other agile principles suggest the opposite, as in YAGNI and DoTheSimplestThingThatCouldPossiblyWork. Reconciling these principles requires a little humility.
Startup Lessons Learned
DECEMBER 6, 2008
The advantages of cross-functional teams are well documented, and for a thorough treatment I recommend the theory in the second half of Agile Software Development with Scrum. Scrum recommends 30 days; I have worked in one or two-week cycles up to about three months. Case Study: Continuous deployment makes releases n.
Expert insights. Personalized for you.
111 
Let's personalize your content