Startup Lessons Learned

JULY 30, 2009

Lessons Learned by Eric Ries Thursday, July 30, 2009 Techstars brings The Lean Startup to Boulder Im very excited to announce a pair of events that will kick off a very busy fall speaking tour. July 30, 2009 7:35 AM Hazem Awad said. Ill be in Boulder for two days. Stay tuned for more details.) Labels: events 2comments: Andy said.

Lean 68

Lean San Francisco Continuous Deployment DC 68

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. After all, the worst kind of waste in software development is code to support a use case that never materializes. Expo SF (May.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

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. Can this methodology be used for startups that are not exclusively about software?

Customer Development 131

Customer Development Engineer San Francisco Developer 131

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. Keep posting and thank you!

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

OCTOBER 4, 2008

In 2007, BusinessWeek named Ries one of the Best Young Entrepreneurs of Tech and in 2009 he was honored with a TechFellow award in the category of Engineering Leadership. January 2, 2009 8:54 AM mancjew said. January 2, 2009 8:57 AM Abbas said. Abbas February 22, 2009 3:33 PM cwillu said. Would love to get in touch.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

FEBRUARY 9, 2009

Lessons Learned by Eric Ries Monday, February 9, 2009 The lean startup @ Web 2.0 Expo San Francisco 2009 The current macroeconomic climate presents unparalleled opportunities for those that can thrive with constrained resources. It uses principles of agile software development, open source and web 2.0,

Lean 68

Lean San Francisco Web Advisory Board 68

Startup Lessons Learned

JUNE 15, 2009

Lessons Learned by Eric Ries Monday, June 15, 2009 Why Continuous Deployment? Of all the tactics I have advocated as part of the lean startup , none has provoked as many extreme reactions as continuous deployment , a process that allows companies to release software in minutes instead of days, weeks, or months.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

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." Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. How fast do they iterate? Expo SF (May.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

MAY 27, 2009

Lessons Learned by Eric Ries Wednesday, May 27, 2009 Austin: the Lean Startup tour continues Next week I head to Austin, TX for my first visit ever. It uses principles of agile software development, open source and web 2.0, Thanks, Alexandre Gomes May 28, 2009 8:59 AM Eric Overton said. Expo SF (May.

Lean 60

Lean Austin San Francisco Continuous Deployment 60

Altgate

SEPTEMBER 16, 2010

Another tip (whether outsourcing or developing in-house, make sure you follow the “2-man&# rule, which means that you should have at least 2 people familiar with your code which gives you insurance in case one goes away or moves on. link] fnazeeri I’ve seen it work (and not). link] Alex Cook Outsourcing is incredible.

Software Review 65

Software Review Offshore Startup Boston 65

femgineer.com

JULY 18, 2010

We engineers know that need to be agile in a startup and be able to scrap code and rebuild, but want we don’t want is to have a founder who manic or aimless. If you’re a founder who is still trying to grasp the product roadmap and create a company vision its probably not a good time to hire an engineer. Sweat equity or salary?

Engineer 41

Engineer Software Review Startup Technical Review 41

Hearpreneur

DECEMBER 3, 2017

The Hacker Chick Blog ended up becoming one of the top agile software development blogs on the Internet. It grew much bigger and faster than I planned for, and after my then 2-year old son had surgery for a brain tumor in 2009 (he’s now a healthy honor student!) while, by the way, my company’s did not).

Naming 90

Naming Entrepreneur LLC Social Media 90

ConversionXL

FEBRUARY 28, 2017

Smoke tests are specifically designed to be run quickly and frequently during the software development stages. This type of agile thinking is what matters. Here’s what Flowtown looked like in February 2009… Image Source. Does clicking the key functionality do anything? ’ That is true validation.” (via

Product 48

Product Audience Stock Conversion 48

Steve Blank

NOVEMBER 2, 2009

For those of you who have been following the discussion, a Lean Startup is Eric Ries ’s description of the intersection of Customer Development , Agile Development and if available, open platforms and open source. Reply links for 2009-11-02 « Blarney Fellow , on November 2, 2009 at 5:10 pm Said: [.]

Lean 264

Lean Silicon Valley Startup RSS 264

Startup Lessons Learned

DECEMBER 16, 2009

Lessons Learned by Eric Ries Wednesday, December 16, 2009 What is Lean about the Lean Startup? 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. There is a dark side to naming.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

andrewchenblog.com

MARCH 10, 2010

Coupled with A/B testing, customer development, and thinking through business problems in a scientific, hypothesis-driven way, you end up with a powerful cocktail of techniques to build a modern startup in the most iterative way possible. If you liked this post, please subscribe or follow me on Twitter. You can also find more essays here.

Technical Review 47

Technical Review Design Las Vegas Product 47

Startup Lessons Learned

AUGUST 1, 2009

Lessons Learned by Eric Ries Saturday, August 1, 2009 The Steve Jobs method Image via CrunchBase Its been a long time since I did a post that was primarily a link to another blog with commentary, but I came across something today that I really want to share. August 1, 2009 7:39 AM Ravi Mohan said. August 1, 2009 8:11 AM Michael said.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

FEBRUARY 10, 2009

Lessons Learned by Eric Ries Tuesday, February 10, 2009 Continuous deployment and continuous learning At long last, some of the actual implementers of the advanced systems we built at IMVU for rapid deployment and rapid response are starting to write about it. Heck, thats what it says right there in the agile manifesto. But it worked.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

JULY 2, 2009

Lessons Learned by Eric Ries Thursday, July 2, 2009 How to conduct a Five Whys root cause analysis In the lean startup workshops , we’ve spent a lot of time discussing the technique of Five Whys. Labels: five whys root cause analysis , product development 15comments: Anonymoussaid. July 3, 2009 3:11 AM Eric Williamson said.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

FEBRUARY 28, 2009

Lessons Learned by Eric Ries Saturday, February 28, 2009 Throwing away working code Lean startups work by systematically eradicating waste. 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.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

SEPTEMBER 27, 2010

Lean manufacturing , agile software development , and Theory of Constraints are all examples of this idea in action. Lean manufacturing , agile software development , and Theory of Constraints are all examples of this idea in action. However, a commitment to quality alone is not enough. Expo SF (May.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

DECEMBER 7, 2008

Our CTO is the CEO himself, but he lacks the understanding of the new software development processes and the new technologies. In school I was being pounded day and night with anything that has to do with agile software development. In this group, I am the only technical guru with very little industry experience.

Software Review 94

Software Review Technical Review San Francisco Part-Time VPE 94

Startup Lessons Learned

FEBRUARY 22, 2010

Even if men have an innate advantage at software development, the gap would have to be massive in order to explain why startup after startup has an all-male team. Even if men have an innate advantage at software development, the gap would have to be massive in order to explain why startup after startup has an all-male team.

San Francisco 167

San Francisco Lean Sweden 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

rapidrollout.wordpress.com

OCTOBER 23, 2010

In the process of gathering feedback, you’re beginning to develop a network of advisers and supporters. First Things First: Your Requirements You seem to feel that your project isn’t ready to move forward without a software developer (a “programmer&# , as you say). says: July 25, 2009 at 3:56 am [.]

Technical Review 40

Technical Review Fractional CTO Partner CTO Hire 40

Startup Lessons Learned

JANUARY 28, 2009

Lessons Learned by Eric Ries Wednesday, January 28, 2009 Refactoring yourself out of business Let me start out by saying I am a big fan of refactoring , the ongoing process of changing code so that it performs the same behaviors but has more elegant structure. Its an essential discipline of good software development, especially in startups.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

crowdSPRING Blog

FEBRUARY 4, 2010

Top 12 Logos of 2009 As Voted By You - [link]. Legal Contracts for Software Developers Who Hate Contracts (w/free contract template to use today) – [link]. Apply Agile Thinking To Everything You Do (especially helpful for startups & small businesses) - [link]. 50 Inspiring Portfolio Designs – [link].

Social Media 92

Social Media Small Business Design Media 92

blog.expensify.com

APRIL 24, 2012

This literally the dumbest, most ignorant piece that I’ve ever read about software development and/or hiring programmers. I also know numerous other programming languages and have worked with many software development platforms over the last 25 years. What would you say to an ALT.NET developer?

Java 107

Java PHP Software Review Coder 107

Steve Blank

MAY 9, 2017

A company developing software would have to buy computers and license software from other companies and hire the staff to run and maintain it. Today open source software has slashed the cost of software development from millions of dollars to thousands. Andreessen realized that the game had changed.

Restful 249

Restful Silicon Valley San Jose Puerto Rico 249