Startup Lessons Learned

MARCH 16, 2009

Lessons Learned by Eric Ries Monday, March 16, 2009 Combining agile development with customer development Today I read an excellent blog post that I just had to share. Jim Murphy is a long-time agile practitioner in startups. But startups sometimes have trouble applying agile successfully.

Agile 111

Agile Customer Development Developer San Francisco 111

crowdSPRING Blog

MAY 11, 2012

These posts and videos are about logo design , web design , startups, entrepreneurship, small business, leadership, social media, marketing, and more! How to Increase Trust for a Landing Page Design – [link]. Better Agile Than Smart – [link]. Six Myths of Product Development – [link].

Social Media 92

Social Media Small Business Design Media 92

Steve Blank

MAY 6, 2015

Waterfall Development. While it sounds simple , the Build Measure Learn approach to product development is a radical improvement over the traditional Waterfall model used throughout the 20 th century to build and ship products. Waterfall Development was all about execution of the requirements document.

Lean 120

Lean Agile Business Model Customer Development 120

View from Seed

NOVEMBER 6, 2014

You always want to be careful with how tightly you schedule things to make sure you stay agile and responsive to evolving business needs, but you also need to make sure your overall journey makes sense and that you’re building things in the right order, as well as taking on risks in a measured way. We did that for a lot of reasons.

Technology 334

Technology Ruby Startup Engineer 334

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. We''ve had to design and implement training programs to help on-board people to our culture and technology.

Lean 167

Lean Startup Software Engineering Agile 167

Startup Lessons Learned

APRIL 25, 2011

It may be hard to remember that there was a time when people in the agile software development community thought Lean Startup was incompatible with agile practices. Design + Lean Startup = Lean UX. Like last year, we’ll have three huge keynote speakers. Wealthfront CTO Pascal-Louis Perez will show you how.

San Francisco 146

San Francisco Silicon Valley Lean Agile 146

Startup Lessons Learned

MARCH 25, 2009

Lessons Learned by Eric Ries Wednesday, March 25, 2009 The Lean Startup at Agile Vancouver April 21st A surprising number of respondents in the latest Lessons Learned survey hail from one of the flourishing startup hubs in Canada. This workshop brings together leading thinkers from Lean Production and Lean software.

Agile 60

Agile Lean San Francisco Continuous Deployment 60

Steve Blank

AUGUST 31, 2009

After 20 years of working in startups, I decided to take a step back and look at the product development model I had been following and see why it usually failed to provide useful guidance in activities outside the building – sales, marketing and business development. So what’s wrong the product development model?

Customer Development 244

Customer Development Developer Customer Silicon Valley 244

Steve Blank

NOVEMBER 24, 2010

Compressing the Product Development Cycle. In the past, the time to build a first product release was measured in months or even years as startups executed the founder’s vision of what customers wanted. A hardware startup had to spend money building prototypes and equipping a factory to manufacture the product.

Silicon Valley 335

Silicon Valley United States Venture Capital Software Review 335

Steve Blank

MAY 9, 2017

The second thing that’s changed is that we’re now Compressing the Product Development Cycle. In the 20 th century startups I was part of, the time to build a first product release was measured in years as we turned out the founder’s vision of what customers wanted. We now have specific management tools to grow startups.

Restful 243

Restful Silicon Valley Puerto Rico San Jose 243

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. The lean startup is an application of Lean Thinking.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

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. A/B testing is set-based design.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

A Smart Bear: Startups and Marketing for Geeks

JULY 19, 2010

During a lull in her practice she got a serendipitous opportunity to shift gears completely and ended up leading software product development teams. But now she has the vision and ability to design her own software, capitalizing on modern trends (e.g. After the talk typically 5-20 people want to chat one-on-one.

Software Review 325

Software Review Technical Review Development Team Review Bolivia 325

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. This is precisely the dilemma that the doctrine of minimum viable product is designed to solve.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

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

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

I thought Id share a little bit of that, too: I’ve been interested in different approaches to software development going back to 1987 when – in my first company Feld Technologies – my partner Dave Jilk and I started talking about “semi-custom software development&# (way ahead of its time).

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. Expo SF (May.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

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. Theme: Digg 3 Column by WP Designer. Blog at WordPress.com.

Lean 260

Lean Silicon Valley Startup RSS 260

Startup Lessons Learned

FEBRUARY 28, 2009

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. None of it would have happened if we had plenty of cash, or were content to count our progress by traffic or product development milestones.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

AUGUST 1, 2009

Apple has a track record of creating lots of interesting enabling infrastructure, like Quicktime and Bonjour, which sometimes become key to their products and othertimes not. My guess is they have lots of people constantly working on interesting new tools for their designers to play with. Will start to pay attention. Great post Eric.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

FEBRUARY 10, 2009

You cant make these global efficiency improvements until you get clear about the goal of your development process. That leads to a seemingly-obvious question: what is progress in software development? Heck, thats what it says right there in the agile manifesto. If a feature worked, wed keep it. If it didnt, wed trash it.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

FEBRUARY 9, 2009

The Lean Startup: a Disciplined Approach to Imagining, Designing, and Building New Products.: It uses principles of agile software development, open source and web 2.0, Hey Someone else who is extending the agile/lean approach beyond just developing software. Check out what I am doing at.

Lean 68

Lean San Francisco Web Advisory Board 68

Startup Lessons Learned

DECEMBER 7, 2008

Even if, in a previous life, you were a world expert in some functional specialty, like in-depth market research or scalable systems design, the compressed timeline of a startup makes it irrelevant. These are two other Extreme Programming practices that are explicitly designed to counteract the problems inherent in this situation.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

OCTOBER 4, 2008

Although Catalyst folded with the dot-com crash, Ries continued his entrepreneurial career as a Senior Software Engineer at There.com, leading efforts in agile software development and user-generated content. While an undergraduate at Yale Unviersity, he co-founded Catalyst Recruiting. hey eric, love the blog.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

bhargreaves.com

MARCH 7, 2010

The reasons why I am not a big fan of development shops are too numerous to go into here. In brief, startups succeed because there is strong alignment of interests among all parties, especially with the people who are actually building the product. Actually any shop that does agile development with daily and weekly releases should.

Hiring 40

Hiring Technical Review Agile Software Review 40

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." Thoughts on scientific product development Lo, my 5 subscribers, who are you? You can tell a lot about a company from their deployment flow. How fast do they iterate?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

JANUARY 28, 2009

Its an essential discipline of good software development, especially in startups. Because, unless you are working in an extremely static environment, your product development team is learning and getting better all the time. Labels: agile , product development , Test-driven development 11comments: William Pietri said.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

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. I have personally taught many “non-technical&# people to program – graphic designers, QA folks, even artists and animators.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

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. If they’re coming up to speed with the product, development cycle, and company dynamics is good to let them ramp up slowly.

Engineer 41

Engineer Software Review Startup Technical Review 41

Startup Lessons Learned

MAY 27, 2009

It uses principles of agile software development, open source and web 2.0, 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? Expo SF (May.

Lean 60

Lean Austin San Francisco Continuous Deployment 60

Startup Lessons Learned

DECEMBER 6, 2008

Lets start with the most important thing you can do to help product teams succeed: make them cross-functional. To begin with, see if you can get designers, programmers, and QA on the same team together. That means every team should have a representative from absolutely every department that the team will have to interact with.

San Francisco 74

San Francisco SCRUM Lean Continuous Deployment 74

mashable.com

MAY 24, 2011

Sourcebits offers design and development services for iOS, Android, Mobile and Web platforms. Choosing Between Mobile and Native Apps One of the resounding themes for mobile software developers in 2011 is the debate between building a native app or building a mobile web app. Have an account?

Mobile 90

Mobile Web Social Media Software Review 90

Startup Lessons Learned

JULY 2, 2009

Five Whys is designed to avoid these nebulous arguments. Labels: five whys root cause analysis , product development 15comments: Anonymoussaid. Furthermore, I think most of what you are suggesting is applicable in companies/ industries that are not software development. Leave your thoughts in a comment.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

JUNE 15, 2009

The agile software movement has made numerous contributions: continuous integration, which helps accelerate feedback about defects; story cards and kanban that reduce batch size; a daily stand-up that increases tempo. Why do software developers think this is acceptable? June 22, 2009 10:07 AM Khris said. Thanks for this.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167