Startup Lessons Learned

MARCH 16, 2009

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. Both Scrum and XP had a role which you could happily call by the modern title "Product Manager". Brilliant insights, advice and information on your blog.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

JULY 29, 2009

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. Darn good - I have struggled in relevant conversations with our in house move to scrum/agile. One last thought.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

APRIL 9, 2009

Well be discussing in greater detail the three techniques I highlighted at the Expo: continuous deployment, split-testing, and five whys. Heres the promo; more information is available on their site. Both informative and inspiring! The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

Startup Lessons Learned

SEPTEMBER 22, 2008

Heres something I can relate to: We used assembla for subversion, scrums, milestones, wikis, and for general organizational purposes. Scrum reports would come in once a month, nobody was actually responsible for anything. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68