Remove 2008 Remove Continuous Deployment Remove SCRUM Remove Software
article thumbnail

Lessons Learned: Combining agile development with customer development

Startup Lessons Learned

In most agile development systems, there is a notion of the "product backlog" a prioritized list of what software is most valuable to be developed next. The breakthrough idea of agile is that software should be built iteratively, with the pieces that customers value most created first. Hes often felt that there was something missing.

Agile 111
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. But by taking advantage of open source, agile software, and iterative development, lean startups can operate with much less waste. Less is more.

Lean 168
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: The product manager's lament

Startup Lessons Learned

Lessons Learned by Eric Ries Sunday, October 5, 2008 The product managers lament Life is not easy when youre working in an old-fashioned waterfall development process, no matter what role you play. So the product manager winds up actually having to use the software, by hand, updating the spec and helping create a new test plan.

article thumbnail

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

Startup Lessons Learned

Lessons Learned by Eric Ries Wednesday, September 10, 2008 A new version of the Joel Test (draft) (This article is a draft - your comments are especially welcome as I think through these issues. But if you want to practice rapid deployment, you need to be able to deploy that build in one step as well. Please leave feedback!)

article thumbnail

Embrace technical debt

Startup Lessons Learned

To do that, we add specific speed regulators, like integrating source control with our continuous integration server or the more elaborate dance required for continuous deployment. Let's consider cases: Can you have a piece of software with good product design and bad technical design? One last thought.

article thumbnail

Lessons Learned: Built to learn

Startup Lessons Learned

This is true whether youre selling million-dollar software to huge enterprises or selling fifty-cent virtual clothes to teenagers. Well be discussing in greater detail the three techniques I highlighted at the Expo: continuous deployment, split-testing, and five whys. Case Study: Continuous deployment makes releases n.

article thumbnail

The four kinds of work, and how to get them done: part three

Startup Lessons Learned

Lessons Learned by Eric Ries Saturday, December 6, 2008 The four kinds of work, and how to get them done: part three Those startups that manage to build a product people want have to deal with the consequences of that success. And still being a startup means continuing to innovate as well as keep the lights on.