Startup Lessons Learned

SEPTEMBER 15, 2008

I would add -- think of your development and running your business like a PM/Developer uses Agile or Scrum in software development. ► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Startup Lessons Learned

SEPTEMBER 10, 2008

But if you want to practice rapid deployment, you need to be able to deploy that build in one step as well. If you want to do continuous deployment, youd better be able to certify that build too, which brings us to. For more on continuous deployment, see Just-in-time Scalability. Can you make a build in one step?

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

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. Case Study: Continuous deployment makes releases n. Seth Godin: How often should you publish?

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68

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. He’s right.

Technical Review 168

Technical Review Software Review San Francisco Lean 168