Remove Continuous Deployment Remove Engineer Remove Lean Remove SCRUM
article thumbnail

Lessons Learned: The lean startup

Startup Lessons Learned

Lessons Learned by Eric Ries Monday, September 8, 2008 The lean startup Ive been thinking for some time about a term that could encapsulate trends that are changing the startup landscape. After some trial and error, Ive settled on the Lean Startup. I like the term because of two connotations: Lean in the sense of low-burn.

Lean 168
article thumbnail

Lessons Learned: Combining agile development with customer development

Startup Lessons Learned

XP and Scrum don’t have much to say - they punt. If you look at the origins of most agile systems, including Scrum and XP , they come out of experiences in big companies. Notice that the unit of progress changes as we move from waterfall to agile to the lean startup. Embedded in that assumption is why startups fail.

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: A new version of the Joel Test (draft)

Startup Lessons Learned

If you want to do continuous deployment, youd better be able to certify that build too, which brings us to. Daily builds are giving way to true continuous integration, in which every checkin to the source control system is automatically run against the full battery of automated tests. Do you make daily builds?

article thumbnail

Lessons Learned: The product manager's lament

Startup Lessons Learned

The VP Engineering spends all of his time trying to make sure the programmers understand and implement the spec. Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more. Great to read posts about introducing lean approaches into more teams. Frustration is mounting. Expo SF (May.

article thumbnail

Embrace technical debt

Startup Lessons Learned

The human tendency to moralize about debt affects engineers, too. 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. Side-effects that reduce agility are the most damaging symptoms of technical debt. One last thought.

article thumbnail

Lessons Learned: ScienceDaily: Corporate culture is most important.

Startup Lessons Learned

Its even more critical in lean startups when they need to manage growth. At IMVU , we called this person a Producer (revealing our games background); in Scrum , they are called the Product Owner. Once an agreement is reached, the Chief Engineer continually watches to make sure that the functions are following through.

article thumbnail

Lessons Learned: Built to learn

Startup Lessons Learned

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. No engineering team. The lean startup focuses on situations where we have both an unknown problem and an unknown solution.