Startup Lessons Learned

SEPTEMBER 15, 2008

But by taking advantage of open source, agile software, and iterative development, lean startups can operate with much less waste. I am heavily indebted to earlier theorists, and highly recommend the books Lean Thinking and Lean Software Development. Labels: customer development , lean startup 8comments: Amy said.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

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

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. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Lean 68

Lean San Francisco Continuous Deployment DC 68

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. Customer development.

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

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

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

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." Usually, whatever is used as a development cycle. How long does the software sit un-deployed? You can tell a lot about a company from their deployment flow.

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.

Lean 60

Lean Austin San Francisco Continuous Deployment 60

femgineer.com

JULY 18, 2010

HOME About the Femgineer Speaking Engagements Reading List Recruiting Startup Engineers With the startup market taking off, there is always a clamor to find good engineers, developers, and designers. I think its important to keep that in mind rather than always trying to covet a rock star developer with a proven track record.

Engineer 41

Engineer Software Review Startup Technical Review 41

Altgate

SEPTEMBER 16, 2010

For the vast majority of software startups, the actual code / development process is infrequently a competitive advantage; ergo, you ought to consider outsourcing. Having managed a lot of software development both local and offshore, this is a topic I plan to write more on. .]… Engineering/QA.

Software Review 65

Software Review Offshore Startup Boston 65

Hearpreneur

DECEMBER 3, 2017

After saying I wanted to develop a product that would make a client’s glossy and then she would just toss it around (I like careless hair) I said I didn’t know what to call it and said you just called it yourself – GLOSS & TOSS. I was a developer so I could write code, but not blog posts. 5- Simple way.

Naming 78

Naming Entrepreneur LLC Social Media 78

ConversionXL

FEBRUARY 28, 2017

Smoke tests are specifically designed to be run quickly and frequently during the software development stages. Consider these two situations… You have a new business idea that you’re excited about and want to develop. You have a new product feature idea that you’re excited about and want to develop.

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. The Customer Development process (and the Lean Startup) is one way to do that.

Lean 260

Lean Silicon Valley Startup RSS 260

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. They’ve also done a lot to actually remove options from the menu and navigation.

Technical Review 47

Technical Review Design Las Vegas Product 47

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. These problems can be anything: development mistakes, site outages, marketing program failures, or even internal missed schedules.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

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. For one, capacity development. August 1, 2009 7:39 AM Ravi Mohan said.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

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

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. They’ll increase code quality, prevent defects and educate your developers.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

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

One of the sayings I hear from talented managers in product development is, “good enough never is.&# And, most importantly, it helps team members develop the courage to stand up for these values in stressful situations. One of the sayings I hear from talented managers in product development is, “good enough never is.&#

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

DECEMBER 7, 2008

Sometimes, a great hacker has the potential to grow into the CTO of a company, and in those cases all you need is an outside mentor who can work with them to develop those skills. At the end of the day, the product development team of a startup (large or small) is a service organization. So, fellow hackers, Id love to hear from you.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 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. No departments The Five Whys for Startups (for Harvard Business R.

San Francisco 74

San Francisco SCRUM Lean Continuous Deployment 74

rapidrollout.wordpress.com

OCTOBER 23, 2010

And James doesn’t have any money to pay for development. You’ll probably need to contact two dozen serial entrepreneurs with a very well-developed project before you get actionable advice and referrals. In the process of gathering feedback, you’re beginning to develop a network of advisers and supporters.

Technical Review 40

Technical Review Fractional CTO Partner CTO Hire 40

blog.expensify.com

APRIL 24, 2012

Or, rather, more offensively to Facebook and Google employees, less offensive to.NET developers, though the underlying message is the same.). But just to clarify a couple points, 24-hours into the storm: Yes,NET developers are great at what they do. It’s the most modern platform for application development on the planet.

Java 107

Java PHP Software Review Coder 107

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

Steve Blank

MAY 9, 2017

Defense and Intelligence organizations drove the pace of innovation in Silicon Valley by providing research and development dollars to universities, and defense companies built weapons systems that used the Valley’s first microwave devices and semiconductor components. and there were no books, blogs or YouTube videos about entrepreneurship.

Restful 243

Restful Silicon Valley Puerto Rico San Jose 243