Startup Lessons Learned

SEPTEMBER 22, 2008

is an elegant way to model any service-oriented business: Acquisition Activation Retention Referral Revenue We used a very similar scheme at IMVU, although we werent lucky enough to have started with this framework, and so had to derive a lot of it ourselves via trial and error. Case Study: Continuous deployment makes releases n.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

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

MARCH 13, 2009

Start with a five-dollar-a-day SEM campaign. You create an entire framework of understanding and action based on your product/idea that sets it in motion in a self-sustaining way. the most sensible SEM advice Ive read - discussed in the context of a real situation. Case Study: Continuous deployment makes releases n.

San Francisco 168

San Francisco PR Lean Early Stage 168

Startup Lessons Learned

SEPTEMBER 22, 2008

It also has the nice side-effect of driving down the batch size of work, but thats for another post) This framework for making progress evident applies to more than just scheduling, of course. Case Study: Continuous deployment makes releases n. If the task is not complete, you force people to surface the issue quickly. (It

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68