Startup Lessons Learned

APRIL 4, 2010

Lessons Learned by Eric Ries Sunday, April 4, 2010 Kent Beck keynote, "To Agility, and Beyond" Kent Beck will give the opening keynote at the Startup Lessons Learned conference on April 23. Kent is a significant figure in the field of software development. Kent is a significant figure in the field of software development.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

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

ctotodevelopers.blogspot.com

JULY 11, 2012

Social, Agile, and Transformation. I cover several topics including agile software development, software startups, web 2.0, Strategic Agile Thinking: Balancing Value, Innovation and Research. 2) The agile "happy place". Agile teams sprint when value is known, implementation is low risk.

Agile 40

Agile Architecture Offshore Software Developers 40

Startup Lessons Learned

APRIL 26, 2009

Lessons Learned by Eric Ries Sunday, April 26, 2009 Product development leverage Leverage has once again become a dirty word in the world of finance, and rightly so. But I want to talk about a different kind of leverage, the kind that you can get in product development. Its a key lean startup concept.

Product Development 88

Product Development Developer San Francisco Product 88

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

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. Engineers love to build, solve tough problems, and make progress. When to start recruiting? Sweat equity or salary?

Engineer 41

Engineer Software Review Startup Technical Review 41

Startup Lessons Learned

AUGUST 8, 2009

Lessons Learned by Eric Ries Saturday, August 8, 2009 Revisiting the Software Design Manifesto (and whats changed since then) My recent article on technical debt and its positive uses generated a fair bit of controversy. The same might be said of good software. Here we have the beginnings of a theory of design for software.

Software Review 87

Software Review Design Software San Francisco 87

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

MARCH 3, 2015

During the Cold War with the Soviet Union, science and engineering at both Stanford and U.C. Berkeley were heavily funded to develop Cold War weapon systems. The disadvantage is that its methodology was based on the old waterfall model of product development and not the agile and lean methods that startups use today.

Business Plan 120

Business Plan Silicon Valley Saudi Arabia Lean 120

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

Steve Blank

JANUARY 6, 2014

For the last 75 years products (both durable goods and software) were built via Waterfall development. This process forced companies to release and launch products by model years, and market new and “improved” versions. The Old Days – Waterfall Product Development. Waterfall – The Customer View.

Continuous Deployment 331

Continuous Deployment Customer Agile Cloud 331

Hearpreneur

SEPTEMBER 22, 2021

Tesla has always put a huge emphasis on product development and technological advancement. This software enables us to communicate with coworkers and connect with family members that we hope to see safely again soon. Lastly, Microsoft Office remains the most popular corporate productivity software program.

Technical Review 124

Technical Review Entrepreneur Software Review SEO 124

Startup Lessons Learned

SEPTEMBER 10, 2008

I am convinced one of Joel Spolskys lasting contributions to the field of managing software teams will turn out to be the Joel Test , a checklist of 12 essential practices that you could use to rate the effectiveness of a software product development team. Please leave feedback!) Can you make a build in one step?

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

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

FEBRUARY 20, 2009

Lessons Learned by Eric Ries Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. For software, the easiest batch to see is code.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Both Sides of the Table

NOVEMBER 1, 2009

Getting Customers Involved in Product Priorities – Around the time that Salesforce.com acquired my company we also acquired a company called CrispyNews. They had decided to take a Digg style approach to product development. Customers had requested that we build out a more robust solution than our current product had.

Customer 280

Customer Technical Review Software Review Mexico 280

Startup Lessons Learned

JULY 29, 2009

The human tendency to moralize about debt affects engineers, too. I hope to show why lean and agile techniques actually reduce the negative impacts of technical debt and increase our ability to take advantage of its positive effects. The biggest source of waste in new product development is building something that nobody wants.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

SEPTEMBER 30, 2008

So I initially gravitated to the CTO title, and not VP of Engineering. It became harder and harder to separate how the software is built from how the software is structured. If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? Heres my take.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

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. Those early text-based games were programmed by their own users, and it was by far the best tutorial I could ever have received in the power of software.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

JUNE 15, 2009

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. One is used by engineers to refer to the process of getting code fully integrated into production.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

NOVEMBER 12, 2013

On November 14 (that’s this Thursday) at 1p PT, Eric Ries will speak with Kent Beck, a creator of Agile software development, about facilitating the work of engineers and product teams. This Thursday’s webcast will get to the heart of how product groups work—and how they can work better.

Product Development 167

Product Development Software Review Technical Review Developer 167

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

Startup Lessons Learned

OCTOBER 5, 2008

For some reason, though, despite the increased buy-in, the final product often doesnt look anything like the original spec. The VP Engineering spends all of his time trying to make sure the programmers understand and implement the spec. Labels: product development 8comments: Vincent van Wylick said. Nice write-up.

San Francisco 158

San Francisco Management Software Review Product 158

Austin Startup

MARCH 17, 2017

If a technology makes sense on the roadmap, make sure it can also deliver quality software that people will want to use today. Engineer the experience so you can evolve the product. The key to rapid validation is to have designers and engineers at the same table. In his free time, Farouk is a beast in the kitchen.

Texas 54

Texas Software Engineering Austin Engineer 54

Venture Chronicles

JUNE 29, 2010

I was on vacation last week with my family and did not post anything but I have been wanting to write about a meeting I had with Accept Software a few weeks ago so I went through my notes and refreshed myself on the conversation, which was interesting in many dimensions. Tags: Uncategorized accept software.

Software 34

Software Portfolio Agile Retention 34

Startup Lessons Learned

SEPTEMBER 2, 2008

Its inspired by the classic OODA Loop and is really just a simplified version of that concept, applied specifically to creating a software product development team. There are three stages: We start with ideas about what our product could be. Were a software company, so what we do everyday is turn ideas into code.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

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

DECEMBER 28, 2009

Or, phrased more hopefully, "I see how you can use continuous deployment to run an online consumer service, but how can it be used for B2B software?" That continuous deployment leads to lower quality software than software built in large batches. Or variations thereof. Implicit in these concerns are two beliefs: 1.

Continuous Deployment 122

Continuous Deployment San Francisco Lean Metrics 122

Startup Lessons Learned

APRIL 14, 2009

Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. Their product development team is hard at work on a next-generation product platform, which is designed to offer a new suite of products – but this effort is months behind schedule.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

SEPTEMBER 1, 2008

Lessons Learned by Eric Ries Monday, September 1, 2008 Test-Driven Development as andon cord You cannot control what you cannot see, and the hardest part of managing software projects is that the final product is so intangible. These tests are written by the engineers themselves, and they must all pass every time.

San Francisco 68

San Francisco Developer Continuous Deployment DC 68

Steve Blank

JUNE 25, 2009

Business customers were starting to ask for “office automation solutions” – word processing, spreadsheets, graphing software on a desktop. Their engineering teams didn’t have the expertise using off-the-shelf microprocessors (back then “real” computer companies designed their own instruction sets and operating systems.)

Technology 143

Technology Silicon Valley Fractional VPE Part-Time VPE 143

Startup Lessons Learned

NOVEMBER 14, 2013

The site visits include stops at Square (the payments startup founded by Twitter co-creator Jack Dorsey), WeWork Soma (an amazing co-working space) and Pivotal Labs (leaders in Lean and Agile consulting), along with one more super-interesting location we’ll announce shortly. If there’s a problem in production, developers need to own it.

Continuous Deployment 162

Continuous Deployment Norway Lean Analytics 162

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." How long does the software sit un-deployed? Software is generally always getting better or getting worse. Do the engineers understand what they are building?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

NOVEMBER 8, 2008

Lessons Learned by Eric Ries Saturday, November 8, 2008 What is customer development? When we build products, we use a methodology. For software, we have many - you can enjoy a nice long list on Wikipedia. You can learn about customer development, and quite a bit more, in Steves book The Four Steps to the Epiphany.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

FEBRUARY 9, 2009

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

Gregg Fraley, Author of Jack's Notebook

AUGUST 12, 2021

Leverage the innate agility. Prototyping — including: design, graphic arts, and concept writing are skills that go beyond engineering. New ideas need to integrate product development with marketing and sales as well. Look at what GigX is doing, or Toptal in the software/financial space. Here’s why.

Framework 71

Framework Agile Product Development Hiring 71

Startup Lessons Learned

AUGUST 26, 2009

Thank you @ericries for drastically altering my perception of agile startup Thank you all so much for your kind words. You can learn more about that by reading The engineering managers lament.) leanstartup We organized our engineering team at IMVU to try and maximize cross-functional collaboration. Expo SF (May.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113