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. Labels: sllconf Kent Beck keynote, "To Agility, and Beyond" Kent Beck will give the opening keynote at the Startup Lessons Learned conference on April 23.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Startup Lessons Learned

OCTOBER 4, 2008

He previously co-founded and served as Chief Technology Officer of IMVU. He is the co-author of several books including The Black Art of Java Game Programming (Waite Group Press, 1996). While an undergraduate at Yale Unviersity, he co-founded Catalyst Recruiting. October 13, 2008 6:47 PM Luke G said. Eric, love the blog.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

SoCal CTO

APRIL 28, 2014

I guess it should not be a surprise that Founders have lots of challenges working with developers. Challenges I started by asking the founders in the room to tell me some of the challenges they have working with developers. Developers (and Founders) are challenged to know how much is okay in terms of bugs.

Technical Cofounder 280

Technical Cofounder Developer Fractional CTO CTO Hire 280

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. So far, I have found "lean startup" works better with the entrepreneurs Ive talked to than "agile startup" or even "extreme startup.") Of course, many startups are capital efficient and generally frugal.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Steve Blank

MAY 9, 2017

The founders were simply wrong about their assumptions about customer needs. It turns out the term “visionary founder” was usually a synonym for someone who was hallucinating. Founders Need to Run the Company Longer. So, almost like clockwork 20 th century startups fired the innovators/founders when they scaled.

Restful 252

Restful Silicon Valley San Jose Puerto Rico 252

Steve Blank

NOVEMBER 13, 2018

During the first year of the company’s life, I was a fireball – relentless in creating and pursuing opportunities – getting on an airplane at the drop of a hat to fly anywhere, anytime, to get a design win. Our chip was nearing completion, and I had convinced early lighthouse customers to design it into their computers.

Part-Time VPE 335

Part-Time VPE Employee Cofounder Hiring 335

YoungUpstarts

OCTOBER 2, 2020

Now, anyone can create apps and websites, design chatbots, automate processes, open ecommerce stores, and lots more — all without typing out a single line of code. As a result, entrepreneurs, founders, CEOs, marketers, and anyone in between can take advantage. The point of no-code tools is to empower non-engineers to create.

CTO Hire 264

CTO Hire eCommerce Engineer Software 264

Startup Lessons Learned

OCTOBER 5, 2008

These specs are handed to a designer, who builds layouts and mockups of all the salient points. Then the designs are handed to a team of programmers with various specialties. The programmers keep asking for more say in the designs and direction that they work on. First, he writes it nice and clear.

San Francisco 158

San Francisco Management Software Review Product 158

The Next Web

OCTOBER 18, 2013

Anthony Bosschem is the founder and head of Darwin Analytics. Hire a designer on day one. If your job isn’t design-based, find someone who can give you that advantage. Great design maximizes the impact of technical innovation. Search for your non-technical cofounder. It’s efficient without too much back and forth.

Technical Cofounder 130

Technical Cofounder Cofounder Agile Design 130

Startup Lessons Learned

JULY 29, 2009

Like a financial debt, the technical debt incurs interest payments, which come in the form of the extra effort that we have to do in future development because of the quick and dirty design choice. We can choose to continue paying the interest, or we can pay down the principal by refactoring the quick and dirty design into the better design.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Steve Blank

JULY 7, 2015

Jon Sebastiani , founder and CEO of KRAVE Jerky , a company that got its start in my class at Berkeley back in 2011 and was recently acquired by Hershey. Eric Ries co-founded Catalyst Recruiting while attending Yale, and continued his entrepreneurial career as a Senior Software Engineer at There.com. Taking My Class.

Lean 120

Lean Silicon Valley Technical Cofounder Channel 120

Startup Lessons Learned

NOVEMBER 8, 2008

This theory has become so influential that I have called it one of the three pillars of the lean startup - every bit as important as the changes in technology or the advent of agile development. This is a self-published book, originally designed as a companion to Steves class at Berkeleys Haas school of business. Heres the catch.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

AUGUST 3, 2009

Refreshing to finally see lean and agile thinking emerge in product/business-floors and not only in technology. ► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Thank you. Thanks Eric.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

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. Similar results apply in product management, design, testing, and even operations. Take the example of a design team prepping mock-ups for their development team. I dont think so.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

A Smart Bear: Startups and Marketing for Geeks

AUGUST 30, 2010

He blogs to 10,000 web entrepreneurs at Software by Rob and co-hosts the podcast Startups for the Rest of Us. A virtual assistant (VA) is a remote worker hired to complete tasks you should not be doing as the founder of a startup. Not automating this process creates the ongoing repetitive work that computers are designed to handle.

Software Review 284

Software Review Startup Technical Review Hosting 284

Startup Lessons Learned

SEPTEMBER 30, 2008

So what does CTO mean, besides just "technical founder who really cant manage anyone?" If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? Your CTO might be a great architect, evangelist, interface designer or incredible debugger. Great piece!

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

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. Ive attempted to embed the relevant slides below. What about a hardware business with some long-lead-time components?

Customer Development 131

Customer Development Engineer San Francisco Developer 131

YoungUpstarts

JULY 21, 2019

While large corporations are struggling with the digital transformation, small agile firms emerge every day and challenge traditional retailers. One of the cofounders explains how he witnessed first-hand while working at a bank that a lot of traditional retailers were in trouble as internet retailers ate away their margins.

Cofounder 113

Cofounder Technical Review Technology Netherlands 113

Startup Lessons Learned

SEPTEMBER 15, 2008

The new design improved on the old one in several ways, but these improvements didnt translate all the way through the funnel. Usually, I think that means youve lost some good aspect of the old design. The designers might be telling you that the new design looks much better than the old one, and thats probably true.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

DECEMBER 14, 2017

Guest Post by Misti Yang, Writer for Lean Startup Co. To confidently answer no, co-founder of Strategyzer Alex Osterwalder told our attendees, “What you really want to do is work more like Amazon. … You’re kind of looking for founders,” not friends, remarked Jeff. “If Second, don’t simply hire your buddies. It's amazing.”

Lean 245

Lean Startup CTO Hire Cofounder 245

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 argument itself got me thinking a lot about design and its role in building products.

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

NOVEMBER 7, 2008

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Stevey's Blog Rants: Good Agile, Bad Agile Learning from Obama: maneuver warfare on the campa. Expo SF (May.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

www.women2.org

MARCH 8, 2012

female founders. founder friday. Lessons learned from female founders and women entrepreneurs. Startup Quote: Wendy Tan White on Building a Successful Startup » FounderDating: How I Found My Co-Founder. Tweet By Elizabeth Knopf (Co-Founder & CEO, Sorced). Conference 2012.

Cofounder 47

Cofounder Technical Review San Francisco Founder 47

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

Lean 140

Lean San Francisco Continuous Deployment Startup 140

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. Combining agile development with customer developm. And when did there get to be 3000 of you?

Agile 60

Agile Lean San Francisco Continuous Deployment 60

Startup Lessons Learned

SEPTEMBER 10, 2008

I know plenty of people who prefer more advanced source control system, but my belief is that many agile practices diminish the importance of advanced features like branching. Its not that the idea behind them is wrong, but I think agile team-building practices make scheduling per se much less important. Youd better.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

APRIL 9, 2009

Thats the essence of so many of the lean startup techniques Ive evangelized: customer development , the Ideas/Code/Data feedback loop , and the adaptation of agile development to the startup experience. Creating a company-wide feedback loop that incorporates both customer development and agile development is a challenge.

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

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. You can also download our presentation, " Just-In-Time Scalability: Agile Methods to Support Massive Growth." Expo SF (May. Take a look and let me know what you think.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

The Startup Magazine

MARCH 7, 2024

Guest Author: Danish Ahmed, Founder of startuptools.ai. Being able to design personalized products enables companies to stand out from the crowded marketplace. What’s more, organizations equipped with scalable AI solutions are more agile in navigating unexpected changes and industry fluctuations.

Artificial Inteligence 155

Artificial Inteligence Entrepreneur Algorithm Cofounder 155

Startup Lessons Learned

NOVEMBER 13, 2008

Wed never heard of five whys, and we had plenty of "agile skeptics" on the team. ► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. We didnt even practice TDD across our whole team.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

FEBRUARY 22, 2010

I have personally taught many “non-technical&# people to program – graphic designers, QA folks, even artists and animators. Instead of focusing on programs designed to specifically benefit any one group, I think our focus should be on making our companies as meritocratic as possible.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

Startup Lessons Learned

APRIL 14, 2009

It should be even more important to the founders themselves, because it demonstrates that their business hypothesis is grounded in reality. 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

JUNE 2, 2010

As start-ups scale, this agility will be lost unless the founders maintain a consistent investment in that discipline. As start-ups scale, this agility will be lost unless the founders maintain a consistent investment in that discipline. Techniques from lean manufacturing can be part of a startups innovation culture.

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

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. This speeds up the Ideas-Code-Data feedback loop.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

MARCH 25, 2010

for Harvard Business Review) Over at Harvard Business Review, Ive been building up a series designed to introduce the Lean Startup methodology to a business-focused audience. Lessons Learned by Eric Ries Thursday, March 25, 2010 Speed up or slow down? Labels: product development Speed up or slow down? Expo SF (May.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

AUGUST 30, 2008

Lessons Learned by Eric Ries Saturday, August 30, 2008 Refactoring for TDD and interaction design In TDD , we follow a rhythm of “test-code-refactor.&# The same process works in Interaction Design. This basic pattern is useful in all aspects of product development. Expo SF (May. Conference streaming, sponsors, discounted tickets.

Software Review 74

Software Review San Francisco Design Continuous Deployment 74

Steve Blank

APRIL 27, 2009

He started the Stanford Honors Co-op in 1954 which allowed companies in the valley to send their engineers to Stanford graduate engineering programs. So they systematically designed electronic devices called “jammers&# to shut down each part of the German air defense system. How was this possible?

Silicon Valley 213

Silicon Valley Technical Review Europe Germany 213