Remove 2008 Remove Metrics Remove Programming Remove SCRUM
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. Consider the classic project that was essential to the creation of extreme programming , the Chrysler Comprehensive Compensation System. Just a thought.

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. I also owe a great debt to Kent Beck, whose Extreme Programming Explained: Embrace Change was my first introduction to this kind of thinking. (So

Lean 168
Insiders

Sign Up for our Newsletter

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

Trending Sources

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. Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more. Nice write-up.

article thumbnail

Social, Agile, and Transformation: Strategic Agile Thinking: Balancing Value, Innovation and Research

ctotodevelopers.blogspot.com

decide on success metrics, measure, and then decide if additional investment is warranted. If the innovation is successful, then the metrics should help drive the enhancement into the top/right "agile happy place" quadrant. Shifting to a Market, Program, and Platform Organization. Kill Projects and Develop Agile Programs.

Agile 40
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. There are several ways to make progress evident - the Scrum team model is my current favorite. Please leave feedback!) Do you have a spec?

article thumbnail

Lessons Learned: ScienceDaily: Corporate culture is most important.

Startup Lessons Learned

At IMVU , we called this person a Producer (revealing our games background); in Scrum , they are called the Product Owner. Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down?

article thumbnail

Embrace technical debt

Startup Lessons Learned

The Extreme Programming folks call those "spikes", and generally don't check them in.) Darn good - I have struggled in relevant conversations with our in house move to scrum/agile. From a product perspective, it can also be very useful to try something quick out to see what the response is before investing more deeply.