Startup Lessons Learned

JUNE 17, 2010

But scope negotiations between departments are an example of an “iterated prisoner’s dilemma&# situation, where the same parties repeatedly negotiate, and rely on their previous experience to inform their choices in the current round. Case Study: Continuous deployment makes releases n. Here’s why.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

SEPTEMBER 18, 2008

I agree with the other comments, more information on yourself and what topics youll focus on would be helpful. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. More of the same.

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

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. Case Study: Continuous deployment makes releases n. One last thought. He’s right. Take a look and let me know what you think.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

OCTOBER 20, 2008

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. By shipping software early, you give them continuous feedback about how it well its working. Case Study: Continuous deployment makes releases n. Computing was a closed society.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

FEBRUARY 11, 2009

Many virtual goods generate only mediocre returns when they draw from only one source of value, as Facebook has been finding out with their only-social-utility gifts, or dozens of startups have found out with their just-the-functionality technology offerings. Case Study: Continuous deployment makes releases n.

San Francisco 102

San Francisco Continuous Deployment Lean DC 102

Startup Lessons Learned

AUGUST 20, 2009

Heres the excerpt: Today’s high-tech entrepreneurs have at their command more than just the ability to invent new technologies — they have mastered the discipline and the methodology required to harness those technologies in order to serve customers. Case Study: Continuous deployment makes releases n.

Lean 68

Lean San Francisco Startup Continuous Deployment 68

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. The actual exchange of information occurs in private, in email. Case Study: Continuous deployment makes releases n. Using it to recruit takes less than a minute.

San Francisco 68

San Francisco Lean Startup Continuous Deployment 68

Startup Lessons Learned

AUGUST 1, 2009

Figuring out whether and how to incorporate that new information into your vision is your job. I do hope that someday more information about the _real_ internal process comes out, so we can get some answers to our open questions: - how much internal (secret) iteration goes into each product? -

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

SEPTEMBER 18, 2008

They cant present much information, unless you take the box off the shelf and look at it. Im on the team that released one of the Taxi apps, and we agree that the "SEO" and placement on the App Store can sometimes leave users with insufficient or inaccurate information to make decisions. Hey Eric, very interesting post.

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74

Startup Lessons Learned

SEPTEMBER 13, 2008

Thanks so much for sharing this information. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. May 8, 2009 2:39 PM VictusFate said. Two Ways to Hold Entrepreneurs Accountable (for Ha.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

SEPTEMBER 8, 2009

I'll add two ideas: The modern structure of university patent licensing and technology transfer works really well in the life sciences and other fields with expensive product development processes. For more information see [link] September 10, 2009 9:53 AM John Seiffer said. Case Study: Continuous deployment makes releases n.

DC 90

DC Washington San Francisco SBIR 90

Startup Lessons Learned

FEBRUARY 22, 2010

Now, whenever I screen resumes, I ask the recruiter to black out any demographic information from the resume itself: name, age, gender, country of origin. Now, whenever I screen resumes, I ask the recruiter to black out any demographic information from the resume itself: name, age, gender, country of origin. “Who is this guy?

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

Startup Lessons Learned

SEPTEMBER 22, 2008

Accurate - if youve ever been managed by task-tracking software, youll relate to the feeling that you either have to spend ludicrous amounts of time posting updates or the information goes stale. Case Study: Continuous deployment makes releases n. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68

Startup Lessons Learned

APRIL 7, 2010

Whole product " is a term I learned from Bill Davidows classic Marketing High Technology. Testing the parts simply gives us information that can help us refine the vision – like a sculptor removing just the right pieces of marble. The bad news: entrepreneurship requires judgment.

San Francisco 154

San Francisco Lean Metrics Design 154

SoCal CTO

JANUARY 5, 2011

Some really great stuff in 2010 that aims to help startups around product, technology, business models, etc. First Principles. Steve Blank , January 25, 2010 10 Tips for Adding Game Mechanics to a Non-Gaming Service - ReadWriteStart , September 21, 2010 Startups & VCs: Learn How to Design, Market, & Eat Your Own. -

Silicon Valley 378

Silicon Valley Startup Term Sheet Venture Capital 378

Startup Lessons Learned

MARCH 22, 2010

The cost of creating new companies is falling rapidly, and access to markets, distribution, and information is within the reach of anyone with an Internet connection. The United States is locked in a new arms race for that most precious resource -- the future entrepreneurs upon whom economic growth depends.

San Francisco 121

San Francisco Indiana Lean Startup 121

Startup Lessons Learned

MARCH 20, 2009

I think the OReilly audience is particularly important, as so many entrepreneurs got their start in technology (as I did) from their worn-down copy of Programming Perl. So if youre a reader of this blog and also of Radar, what kinds of information from this blog would you want to see explained over there?

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

JANUARY 12, 2009

Its an example of an information cascade - as PHP started to pull ahead of the platform pack, more and more people started working on it, increasing the size of the community and therefore making it more likely that even more people would choose it. However, it made me remember that Im tired of technology arguments. Nice article.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

NOVEMBER 5, 2008

Observe At the end of each day, wed laboriously enter data, updating the campaigns voter database with information about every voter contact we accomplished that day. Orient And then the voter data would be crunched, by someone at statewide HQ, and each night wed start the process of creating new packets of instructions for the next day.

Campaign 84

Campaign San Francisco Lean Agile 84