Startup Lessons Learned

FEBRUARY 28, 2009

This builds on a lot of great thinking that has come before, like the agile movements insistence that only the creation of working code counts as progress for a software development team. I used to think that investments in metrics were a form of waste. that justify decisions already made. March 2, 2009 1:58 PM programiTV said.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

SEPTEMBER 2, 2008

Lessons Learned by Eric Ries Tuesday, September 2, 2008 On deployment My favorite question to ask a software development team is "how do you do a release." And the same is true in reverse - a lone brilliant coder can build a great widget, but it takes a system of people working well together to produce consistently great results.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

JUNE 15, 2009

So developers stuck in this world tend to think the other developers on their team are either, deep in their souls, plodding pedants or sloppy coders. Part of putting this into action is requiring your team to have a very deep understanding of their customers. Why do software developers think this is acceptable?

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

maplebutter.com

JANUARY 8, 2013

Written By Dan Martell on February 2nd, 2012 | Category: Hiring LeanStartup Marketing Metrics Startup Life | 6 Comments. Building Metrics / Usage Reports / KPI 3. Product/Metrics (70%/30% time) * Get your product activation (sign-up + meaningful action) to 60% * then, Get your product retention to 20% weekly. 10) Metrics.

Technical Review 44

Technical Review Startup Cofounder Software Review 44