Startup Lessons Learned

JULY 30, 2009

I want to thank Techstars for putting this event together and giving me a chance to experience the scene, even if it lacks a name. Building on this, I’ve recently become fascinated with the notion of continuous deployment , a concept that has been popularized by Eric Ries and others. Read the rest. Amazon PostRank

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

SEPTEMBER 10, 2008

Of the techniques he mentioned, I think four are fundamental and critical for any lean startup: TDD (or the even more politely named TATFT ) Continuous integration Automate your deployments Collect statistics The tools to help you do these things are getting better and better every day, but dont confuse tools with process.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

SEPTEMBER 12, 2008

It’s easy to overestimate the impact of this kind of traffic because it just feels good to have your name and company featured. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

MARCH 16, 2009

Consider the classic project that was essential to the creation of extreme programming , the Chrysler Comprehensive Compensation System. I think Jim Murphys confusion comes where many peoples did, with the XP term "Customer", which was XPs name for the product management role. Case Study: Continuous deployment makes releases n.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

SEPTEMBER 15, 2008

If she is, return the name of the hypothesis she was exposed to before. Return the name of the hypothesis chosen or assigned. From the point of view of the caller of the function, they just pass in the name of the experiment and its various hypotheses. Case Study: Continuous deployment makes releases n.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

JANUARY 19, 2009

Much of what I have found effective is counter-intuitive, because it requires investing more effort in each hire - all in the name of efficiency. Even if you have a referral bonus program, even if youve talked to that person about your company, and even if youve sent a recruiter to call her, I bet you could do more.

Lean 140

Lean Hiring San Francisco Continuous Deployment 140

Startup Lessons Learned

OCTOBER 26, 2009

In previous posts, I’ve mentioned quite a few of these, including these most important ones: having engineers post on the forums in their own name when they make a change routinely split-testing new changes routinely conducting in-person usability tests and interviews Net Promoter Score Each of these techniques is fundamentally bottoms-up.

Advisory Board 151

Advisory Board Customer San Francisco Lean 151

Startup Lessons Learned

JUNE 5, 2009

We're starting our new business, fanminder.com, to help small merchants instantly communicate with their customers, and I'm increasingly hearing your name and reading your keen insights. Case Study: Continuous deployment makes releases n. Pivot, don't jump to a new vision Why Continuous Deployment?

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

NOVEMBER 8, 2008

The book takes its name from Steves theory of the four stages of growth any startup goes through. 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? Amazon PostRank

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

APRIL 14, 2009

Now, in some situations, this over-selling would lead to a secondary problem, namely, that customers would realize they had been duped and refuse to re-subscribe. Case Study: Continuous deployment makes releases n. That leads to cashing many checks. But here’s where a truly great sales artist comes in. Amazon PostRank

Customer 167

Customer San Francisco Lean Hockey Stick 167

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. The Extreme Programming folks call those "spikes", and generally don't check them in.) One last thought.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

OCTOBER 20, 2008

When I was working my first programming jobs, I was introduced to the following maxim: "time, quality, money - pick two." When I first encountered agile software techniques, in the form of extreme programming , I thought I had found the answer. a is name, b is address, and c is tax percentage. Whats wrong with this picture?

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

FEBRUARY 7, 2010

If youre a startup investor, and you support the goals of the Startup Visa proposal, wed like you lend your name to our efforts. If youre a startup investor, and you support the goals of the Startup Visa proposal, wed like you lend your name to our efforts. Case Study: Continuous deployment makes releases n.

San Francisco 118

San Francisco DC Startup Lean 118

Startup Lessons Learned

FEBRUARY 11, 2009

The same is true of brand-name products in almost every category (and it can be measured ). 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? for Harvard Business Revie.

San Francisco 102

San Francisco Continuous Deployment Lean DC 102

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. Eric Names matter. There is a dark side to naming.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

Startup Lessons Learned

AUGUST 3, 2009

MVP, despite the name, is not about creating minimal products. Alan mentions above what I believe is the critical learning element your team needs to gain insight into via the Minimum Viable Product, Compelling Product Offering or other named approach. Case Study: Continuous deployment makes releases n.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

JUNE 22, 2009

Pivotal Labs doesn't carry "Pivot" in its name by accident. I'm glad there's a 'name' for this part of the process Eric. Case Study: Continuous deployment makes releases n. Pivot, don't jump to a new vision Why Continuous Deployment? Thank you for your nice posting.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

AUGUST 8, 2012

Many conferences and programs complain that they don't get a diverse group of applicants. We believe that part of the reason this happens is that people naturally don't bother applying to programs they don't think they'll be accepted to. When we're evaluating your application, we won't know your name, ethnicity, gender or age.

Lean 164

Lean Houston Continuous Deployment Technical Review 164

Startup Lessons Learned

OCTOBER 11, 2010

The key to understanding Lean Startup is to recognize two things: Lean Startup techniques confer maximum benefit in the upper-right quadrant, namely high market uncertainty coupled with fast cycle time. It is written by Ronald Mannak, who is currently the CEO of a startup named Yobble. What follows are solely his opinions.

Continuous Deployment 164

Continuous Deployment Technical Cofounder Cofounder San Francisco 164

Startup Lessons Learned

JULY 2, 2009

These problems can be anything: development mistakes, site outages, marketing program failures, or even internal missed schedules. Pay attention to whether people are comfortable “naming names&# in the meeting. The reason is simple: setting up a training program is seen as too much work to be justified by the problem.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

FEBRUARY 22, 2010

I have personally taught many “non-technical&# people to program – graphic designers, QA folks, even artists and animators. Instead of focusing on programs designed to specifically benefit any one group, I think our focus should be on making our companies as meritocratic as possible. “Who is this guy?&#

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

Startup Lessons Learned

JULY 9, 2009

All the good domain names were taken, all the good ideas were being implemented. If Id bought just a handful of the "best of the rest" domain names that were available at the time (for a whopping $70 each), I probably could have just retired right then. Case Study: Continuous deployment makes releases n. Amazon PostRank

San Francisco 94

San Francisco Lean Continuous Deployment DC 94

Startup Lessons Learned

OCTOBER 7, 2008

If necessary, consider doing this under a different brand name than the one you are wedded to using. 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? Amazon PostRank

San Francisco 68

San Francisco Lean Retention SEM 68

Startup Lessons Learned

JULY 13, 2009

It moves at a rapid clip, each argument backed up with the relevant math and equations: marginal profit , Littles law , Markov processes , probability theory , you name it. Case Study: Continuous deployment makes releases n. The book is structured as a series of principles, logically laid out and briefly discussed - 175 in all.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

JULY 31, 2009

lets you post a description of a job without having to reveal the name of the company who is offering it, or the contact information of the hiring manager. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

San Francisco 68

San Francisco Lean Startup Continuous Deployment 68

Startup Lessons Learned

SEPTEMBER 27, 2010

In fact, we know so much that we already know what they will care enough about (namely, the product’s quality – as opposed to, say, missing features). The second misunderstanding is a concern for what will happen if things turn out exactly as we originally predicted (namely, badly). I understand this fear.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

SEPTEMBER 18, 2008

All I see is a name, an icon, a price, the developers name, and a review star-rating. 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? I cant really tell.

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74

Startup Lessons Learned

MARCH 13, 2009

Who doesnt want to see their name in print? Now that were beginning our first marketing, the key partners we need have heard our name long enough to trust us. Case Study: Continuous deployment makes releases n. See if their answer is about tactics or strategy. Founders push for it. In some ways, founders are even worse.

San Francisco 168

San Francisco PR Lean Early Stage 168

Startup Lessons Learned

SEPTEMBER 13, 2008

We would pretty much bid on any phrase that was "[name of competitive product] chat" and variations like that. 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?

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

AUGUST 1, 2009

In talking with Mary Poppendieck about it, she said that the Chief Engineer role at 3M was called a "Product Champion" The name is less important than understanding the depth of competence that this person has, and what it takes to build it. Case Study: Continuous deployment makes releases n. Amazon PostRank

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

MARCH 24, 2009

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? Case Study: Continuous deployment makes releases n. Learning is better than optimization (the local ma.

Metrics 88

Metrics San Francisco Lean Viral 88

Startup Lessons Learned

OCTOBER 11, 2009

Ironically, meetings like this had given data and experimentation a bad name inside this company. Ironically, meetings like this had given data and experimentation a bad name inside this company. Case Study: Continuous deployment makes releases n. What a waste. And who can blame them? What a waste. And who can blame them?

San Francisco 133

San Francisco Lean Metrics Continuous Deployment 133

Startup Lessons Learned

SEPTEMBER 22, 2008

Simply put, we upload all the tasks and assign a name to each task. 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? Case Study: Continuous deployment makes releases n.

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68

Startup Lessons Learned

DECEMBER 14, 2009

This attention is valuable to yet another set of people: namely, the traditional businesses (see above) who are using marketing to grow, and are looking to advertise to new prospects. Case Study: Continuous deployment makes releases n. The value of the attention that the media company collects determines how profitable it is.

Customer 156

Customer San Francisco Viral Lean 156

Startup Lessons Learned

JANUARY 4, 2009

Imagine you want to store data about customers, each of whom has "last name" field in your database. The problem should be familiar to anyone who plays Scrabble: not all letter are equally likely to be used as the first letter of someones name. Give each entity a name. For example, consider this simple scheme.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

APRIL 7, 2010

I’m sure other disciplines have their own names for it; even protozoans exhibit this behavior (its called taxis ). I’m sure other disciplines have their own names for it; even protozoans exhibit this behavior (its called taxis ). Case Study: Continuous deployment makes releases n. for Harvard Business Revie.

San Francisco 154

San Francisco Lean Metrics Design 154

Startup Lessons Learned

SEPTEMBER 13, 2010

Or take a recent TechCrunch article about a startup I wont name: “X billion messages sent since June 2009.&# Or take a recent TechCrunch article about a startup I wont name: “X billion messages sent since June 2009.&# Case Study: Continuous deployment makes releases n. for Harvard Business Revie.

San Francisco 154

San Francisco Metrics Lean PR 154