Startup Lessons Learned

AUGUST 8, 2009

We owe a lot to this seminal document. The economics of these process trade-offs are discussed in the Principles of Product Development Flow.) Heres an excerpt: In a previous article, we called Toyota’s product development system the “second Toyota paradox.&# it is very helpful for me.

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

JULY 3, 2009

The Lean Startup fbFund Edition View more documents from Eric Ries. The power of A/B testing is so under-exploited in product development, that Im trying new ways to explain its benefits. I had a flip cam with me, and the organizers captured their own video with a tripod and everything. Without further ado. Now for the feedback.

Lean 60

Lean San Francisco Continuous Deployment Cofounder 60

Startup Lessons Learned

JUNE 17, 2010

But according to the theory, this should have been covered by the various specs and documentation we were rigorous about producing. Instead, we spent time making sure the exact behavior of the tools were well documented – by engineers, naturally. This led to some pretty bizarre situations. Expo SF (May.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

FEBRUARY 22, 2009

That data is completely consonant with the people I know who are successful technologists today, and similar patterns are documented in each recent wave of technology innovation. I documented the lesson plans etc on [link] March 4, 2009 5:25 AM Eric said. I offered a programming class at the local school and. only two kids took it up!

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Steve Blank

AUGUST 18, 2010

More importantly, we’d witnessed Customer Development’s massive success at another local startup. We bought Steve’s book , started product development and began reaching out to customers ins search of our first earlyvangelists. It’s the only reliable metric for success. Customer Development is like being Agile.

Customer Development 230

Customer Development Developer Customer California 230

Up and Running

MAY 23, 2016

In this section, you really just want to document how your business will make money. In this section, you really just want to document how your business will make money. Another great way to test your idea is to create a minimum viable product, or MVP. This is the simplest version of your product minus the frills and frosting.

Software Review 74

Software Review Software Delaware Forecast 74

Startup Lessons Learned

AUGUST 16, 2010

Designed for large businesses, the channels let a company share several types of documents, brand the channel with their own design elements, and then include display advertising, contest promotions, blog aggregation, social media integration and metrics reporting. Early this year, SlideShare launched custom channels. Expo SF (May.

San Francisco 167

San Francisco Lean Analytics Continuous Deployment 167

Startup Lessons Learned

OCTOBER 16, 2013

One good example is the way in which we''ve adjusted the length of different phases of our agile sprints. We don''t follow a set agile methodology, but rather follow a more home-grown, minimal version of various approaches. The result was a new process of four-week iterative cycles all about throttling new code.

Lean 167

Lean Startup Software Engineering Agile 167

Startup Lessons Learned

NOVEMBER 5, 2008

You also need to know what each one cares about, which metrics they look at (or studiously ignore). Education Guideline Book (1st Edition) Sep 2006 View SlideShare document or Upload your own. Stevey's Blog Rants: Good Agile, Bad Agile Learning from Obama: maneuver warfare on the campa. 1 comments: Desoja said.

Advertising 60

Advertising San Francisco Media Continuous Deployment 60

Startup Lessons Learned

MARCH 27, 2009

In fact, every single lean transformation documented in books like Lean Thinking took place in the midst of serious external threats. Customer Development : a disciplined approach to finding out if there is a market for your product before its too late. The hardest costs to cut are those that are embodied in sacred cows.

San Francisco 117

San Francisco Lean Continuous Deployment DC 117

The Next Web

AUGUST 26, 2012

For this reason you should find out as quickly as possible if the product is indeed offering real value to your customers by looking at real data. The metrics that matter the most are returning customers (user retention), turnover per customer and viral growth (k-factor). Keep the team small, agile and up-to-date.

Bankruptcy 121

Bankruptcy Technical Review Intellectual Property Due Diligence 121

Startup Lessons Learned

APRIL 7, 2010

At least, not in the traditional sense of trying to squeeze every tenth of a point out of a conversion metric or landing page. In fact, the curse of product development is that sometimes small things make a huge difference and sometimes huge things make no difference. For example, I’m a big believer in split-testing.

San Francisco 154

San Francisco Lean Metrics Design 154

Startup Lessons Learned

NOVEMBER 13, 2008

Now, everyone is learning together - about your product, process, and team. Each five whys email is a teaching document. Wed never heard of five whys, and we had plenty of "agile skeptics" on the team. Let me show you what this looked like after a few years of practicing five whys in the operations and engineering teams at IMVU.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

DECEMBER 6, 2008

When youve mastered that, consider adding operations, customer service, marketing, product management, business development - the idea is that when the team needs to get approval or support from another department, they already have an "insider" who can make it happen. Expo SF (May. Conference streaming, sponsors, discounted tickets.

San Francisco 74

San Francisco SCRUM Lean Continuous Deployment 74

steveblank.com

JULY 8, 2011

Github - Free public repositories, collaborator management, issue tracking, wikis, downloads, code review, graphs Pivotal Tracker – Agile project management tool that enables real time collaboration. WebSequenceDiagrams - sketch sequence diagrams. Lighthouse – Issue Tracking Tool.

Software Review 110

Software Review Startup Silicon Valley Analytics 110

Startup Lessons Learned

JANUARY 12, 2009

And I think a bad choice, a bad library, a horrible API, lack of documentation etc. You forgot to mention how awesome the documentation on php.net is. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev.

PHP 166

PHP Software Review Ruby San Francisco 166

www.vccafe.com

MARCH 11, 2013

For modifications, please edit the original document here. Scanning / Document Management. Startup Metrics for Pirates â?? SaaS Metrics Tutorial â?? Agile project management tool that enables real time collaboration. Great for visualizing work of product development. Agile project management.

Software Review 53

Software Review Technical Review Startup 53

Startup Lessons Learned

SEPTEMBER 11, 2009

I offered an educated opinion about the travesty called "profit based pricing" that the former "community manager" actually fabricated documents as the basis to forum ban me and threatened to permanently ban me as a means to censor the information I sought to share. To be so would be, in my opinion, disloyal to IMVU.

Community 158

Community Management Lean Software Review 158