Remove Agile Remove Continuous Deployment Remove Employee
article thumbnail

Lean Startup at Scale

Startup Lessons Learned

One good example is the way in which we''ve adjusted the length of different phases of our agile sprints. We don''t follow a set agile methodology, but rather follow a more home-grown, minimal version of various approaches. Continuous deployment: A key component of speed is to keep pushing out work.

Lean 167
article thumbnail

Lessons Learned: Combining agile development with customer development

Startup Lessons Learned

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. Thats pretty clear.

Agile 111
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Lessons Learned: Employees should be masters of their own time

Startup Lessons Learned

Lessons Learned by Eric Ries Tuesday, March 3, 2009 Employees should be masters of their own time Every startup should have a culture of learning. The rule is simple: every employee is 100% responsible for how they spend their time. The suggestion is that you implement one single company-wide rule. I asked why.

Employee 146
article thumbnail

Lessons Learned: Five Whys

Startup Lessons Learned

Hes a new employee, and he was not properly trained in TDD So far, this isnt much different from the kind of analysis any competent operations team would conduct for a site outage. Instead, five whys kept leading to problems caused by an improperly trained new employee, and wed make a small adjustment. why did that code get written?

article thumbnail

Lessons Learned: The engineering manager's lament

Startup Lessons Learned

When I first encountered agile software techniques, in the form of extreme programming , I thought I had found the answer. I explained it to people this way: agile lets you make the trade-offs visible to whole company, so that they can make informed choices. Even worse, agile wasnt really helping me ship higher quality software.

article thumbnail

Fear is the mind-killer

Startup Lessons Learned

I spent some time with his company before the conference and discussed ways to get started with continuous deployment , including my experience introducing it at IMVU. Moreover, approaching the problem from the direction that I had intuitively is a recipe for never reaching a point where continuous deployment is feasible.

article thumbnail

Lessons Learned: A new version of the Joel Test (draft)

Startup Lessons Learned

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.