Startup Lessons Learned

SEPTEMBER 22, 2008

Master of 500 Hats: Startup Metrics for Pirates (SeedCamp 2008, London) This presentation should be required reading for anyone creating a startup with an online service component. He also has a discussion of how your choice of business model determines which of these metric areas you want to focus on. Choose one. Expo SF (May.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Startup Lessons Learned

OCTOBER 4, 2008

Lessons Learned by Eric Ries Saturday, October 4, 2008 About the author ( Update January, 2010: This post originally dates from October, 2008 back when I first started writing this blog. Ken Yagen (@kenyagen) KenAtYagenDotCom January 3, 2010 1:38 PM Paramendra Bhagat said. My first time at your blog. You are a great blogger.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

NOVEMBER 7, 2008

February 17, 2010 1:09 AM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) . Expo SF (May.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

NOVEMBER 13, 2008

Because five whys kept turning up a few key metrics that were hard to set static thresholds for, we even had a dynamic prediction algorithm that would make forecasts based on past data, and fire alerts if the metric ever went out of its normal bounds. Wed never heard of five whys, and we had plenty of "agile skeptics" on the team.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

SEPTEMBER 7, 2008

In addition to presenting the IMVU case, we tried for the first time to do an overview of a software engineering methodology that integrates practices from agile software development with Steves method of Customer Development. Ive attempted to embed the relevant slides below. What about a hardware business with some long-lead-time components?

Customer Development 131

Customer Development Engineer San Francisco Developer 131

A Smart Bear: Startups and Marketing for Geeks

JULY 19, 2010

On the surface, it's yet another "marketing metrics" company. Even "cool, agile" companies like 37signals are trapped. Office 2010 will be the end of Zoho, if we stop innovating, stop being nimble and flexible in our business model. Then again, if we stop all that, Zoho will die anyway , no Office 2010 needed to do the job.

Software Review 325

Software Review Technical Review Development Team Review Bolivia 325

Startup Lessons Learned

JUNE 22, 2009

Each has its own iterative process: customer development and agile development respectively. Leading up to a pivot, each cycle, despite our best efforts, the metrics werent good enough. Ajay January 24, 2010 6:15 AM Matthew Ogston said. February 9, 2010 3:16 PM Anonymoussaid. April 12, 2010 7:45 AM @hankzy said.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

OCTOBER 5, 2008

Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more. I went through some of this in bringing agile methodologies to my current firm - except that I am the product manager in question at this case. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

JULY 13, 2009

Lessons Learned by Eric Ries Monday, July 13, 2009 The Principles of Product Development Flow If youve ever wondered why agile or lean development techniques work, The Principles of Product Development Flow: Second Generation Lean Product Development by Donald G. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

Product Development 153

Product Development Developer San Francisco Product 153

Steve Blank

APRIL 9, 2009

But what I wanted was an agile marketing team capable of operating independently without day-to-day direction. And the results weren’t the traditional PR metrics of number of articles or inches of ink. We were constantly creating metrics to see the effects of different PR messages, channels and audiences on end-user purchases.

Silicon Valley 271

Silicon Valley Technical Review RSS PR 271

Startup Lessons Learned

SEPTEMBER 30, 2008

If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? March 23, 2010 2:05 PM Anonymoussaid. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, But along the way, something strange happened. And what about if deployment takes forever?

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

APRIL 25, 2011

If you somehow missed SLLCONF 2010 , you can get caught up with a complete video recording here.) It may be hard to remember that there was a time when people in the agile software development community thought Lean Startup was incompatible with agile practices. No BS, no vanity metrics, no launches, no PR.

San Francisco 146

San Francisco Silicon Valley Lean Agile 146

Startup Lessons Learned

SEPTEMBER 15, 2008

Focus on the output metrics of that part of the product, and you make the problem a lot more clear. To promote this metrics discipline, we would present the full funnel to our board (and advisers) at the end of every development cycle. Max Levchin of Slide and Paypal has noted that 10% of Slides headcount is devoted to metrics only.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

NOVEMBER 8, 2008

This theory has become so influential that I have called it one of the three pillars of the lean startup - every bit as important as the changes in technology or the advent of agile development. January 6, 2010 12:49 AM Anonymoussaid. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Expo SF (May.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

FEBRUARY 20, 2009

Sounds very similar to agile development which is the way. 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? February 21, 2009 7:39 AM Rocky1138 said. Expo SF (May.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

SEPTEMBER 10, 2008

I know plenty of people who prefer more advanced source control system, but my belief is that many agile practices diminish the importance of advanced features like branching. Its not that the idea behind them is wrong, but I think agile team-building practices make scheduling per se much less important. Youd better. Expo SF (May.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

DECEMBER 16, 2009

For those whove heard it, it contains a length discourse on the subject of agile software development and extreme programming, including its weaknesses when applied to startups. As Im pontificating about agile, I see the name Kent Beck in my peripheral vision. Now, this webcast was packed, hundreds of people were logged in.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

Startup Lessons Learned

SEPTEMBER 2, 2008

We wanted an agile approach that would allow us to build our software architecture as we needed it, without downtime, but also without large amounts of up-front cost. You can also download our presentation, " Just-In-Time Scalability: Agile Methods to Support Massive Growth." Expo SF (May.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

NOVEMBER 29, 2008

The six key attributes spell ABCDEF: Agility. When talking about their past experience, candidates with agility will know why they did what they did in a given situation. To probe for agility, you have to ask the candidate questions involving something that they know little about. Expo SF (May.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

MARCH 25, 2009

Lessons Learned by Eric Ries Wednesday, March 25, 2009 The Lean Startup at Agile Vancouver April 21st A surprising number of respondents in the latest Lessons Learned survey hail from one of the flourishing startup hubs in Canada. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Thank you so much!) Expo SF (May.

Agile 60

Agile Lean San Francisco Continuous Deployment 60

Startup Lessons Learned

JUNE 2, 2010

Lessons Learned by Eric Ries Wednesday, June 2, 2010 The Five Whys for Startups (for Harvard Business Review) I continue my series for Harvard Business Review with the Lean Startup technique called Five Whys. As start-ups scale, this agility will be lost unless the founders maintain a consistent investment in that discipline.

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

SEPTEMBER 27, 2010

Lessons Learned by Eric Ries Monday, September 27, 2010 Good enough never is (or is it?) Lean manufacturing , agile software development , and Theory of Constraints are all examples of this idea in action. No vanity metrics should be looked at. No vanity metrics should be looked at. No press should be allowed.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

OCTOBER 20, 2008

When I first encountered agile software techniques, in the form of extreme programming , I thought I had found the answer. I explained it to people this way: agile lets you make the trade-offs visible to whole company, so that they can make informed choices. Even worse, agile wasnt really helping me ship higher quality software.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

MARCH 24, 2009

Lessons Learned by Eric Ries Tuesday, March 24, 2009 The metrics and levers of engagement, presentation on Engagement Loops for Facebook Developer Garage SF Ill be presenting a talk at the Facebook Developer Garage SF Wednesday evening. Unfortunately, its easy to lose track of positioning effects when optimizing for a single metric.

Metrics 88

Metrics San Francisco Lean Viral 88

David Teten

NOVEMBER 26, 2019

Instead of budget approvals, monitor key metrics and give managers more flexibility. So here’s the solution I have recommended to some of my portfolio companies: “ agile budgeting ”, i.e., monitoring a few key variables while giving managers significant flexibility. This agile approach is not restricted to small startups.

Agile 60

Agile Management Forecast Silicon Valley 60

Startup Lessons Learned

AUGUST 2, 2008

0comments: Post a Comment Newer Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) April 23, 2010 in San Francisco. Expo SF (May.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

APRIL 9, 2009

Thats the essence of so many of the lean startup techniques Ive evangelized: customer development , the Ideas/Code/Data feedback loop , and the adaptation of agile development to the startup experience. Creating a company-wide feedback loop that incorporates both customer development and agile development is a challenge.

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

Startup Lessons Learned

JULY 29, 2009

I hope to show why lean and agile techniques actually reduce the negative impacts of technical debt and increase our ability to take advantage of its positive effects. Yet other agile principles suggest the opposite, as in YAGNI and DoTheSimplestThingThatCouldPossiblyWork. Reconciling these principles requires a little humility.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

FEBRUARY 10, 2009

Heck, thats what it says right there in the agile manifesto. Labels: agile , continuous deployment , lean startup , product development , Test-driven development 4comments: Nivi said. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, It seems like it should be the amount of correctly-working code weve written.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

NOVEMBER 4, 2008

Boyd emphasized the importance of agility in combat: "the key to victory is to be able to create situations wherein one can make appropriate decisions more quickly than ones opponent." Agile software development. Agile allows companies to build higher quality software faster. This speeds up the Ideas-Code-Data feedback loop.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

MARCH 3, 2009

In order to give people the data they need to apply the strategy, we were very open with our company metrics, making all reports generally available and easy to run. When you think a certain feature will give a 50% boost to a given metric, and it only eeks out a 5% boost, you cant spin that as failure. March 9, 2009 8:35 AM Eric said.

Employee 146

Employee San Francisco Lean Software Review 146

Startup Lessons Learned

JUNE 15, 2009

The agile software movement has made numerous contributions: continuous integration, which helps accelerate feedback about defects; story cards and kanban that reduce batch size; a daily stand-up that increases tempo. January 29, 2010 11:18 AM Eric said. > January 29, 2010 12:55 PM Gareth Evans said. Expo SF (May.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

MARCH 25, 2010

Lessons Learned by Eric Ries Thursday, March 25, 2010 Speed up or slow down? Two Ways to Hold Entrepreneurs Accountable Beware of Vanity Metrics For Startups, How Much Process Is Too Much? Two Ways to Hold Entrepreneurs Accountable Beware of Vanity Metrics For Startups, How Much Process Is Too Much? Expo SF (May.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

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. I used to think that investments in metrics were a form of waste.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

JULY 28, 2010

Lessons Learned by Eric Ries Wednesday, July 28, 2010 Case Study: kaChing, Anatomy of a Pivot (The following guest post is a new experiment for this blog. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

Startup Lessons Learned

AUGUST 1, 2009

So I don't think the Apple experience should be used to discount lean, agile, or customer development-type approaches. 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?

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

APRIL 14, 2009

Every board meeting, the metrics of success change. Go on an agile diet quickly. With a product development team that is not shipping, any agile methodology will surface major problems quickly. Time-to-complete-a-sale is not a bad metric for validated learning at this stage. And yet, their investors are frustrated.

Customer 167

Customer San Francisco Lean Hockey Stick 167