Hearpreneur

DECEMBER 29, 2021

Thanks to Wes Marlan, Lighthouse Web Design, Inc ! #2- 7- Providing employee engagement software. My #1 goal for 2022 is to help my company become the number one provider of employee engagement software. It's important to keep business agile. 2- Scaling up. Photo Credit: Michael Peres. Photo Credit: Logan Mallory.

Entrepreneur 137

Entrepreneur Social Media Employee Los Angeles 137

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. Thank you so much!)

Agile 60

Agile Lean San Francisco Continuous Deployment 60

Up and Running

APRIL 18, 2017

My team and I launched crowdSPRING in early 2008. Xerox, Polaroid, Blockbuster, and other market leaders lost to smaller, more agile competitors because the market leaders assumed that they would dominate forever. One person was in charge of how we qualified designers and writers to work on crowdSPRING. We were wrong.

Campaign 90

Campaign Agile Design Software Developers 90

Startup Lessons Learned

OCTOBER 20, 2008

Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their product development process. They just assumed it was the way software companies worked. Sound good?

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

SEPTEMBER 15, 2008

Lessons Learned by Eric Ries Monday, September 8, 2008 The lean startup Ive been thinking for some time about a term that could encapsulate trends that are changing the startup landscape. But by taking advantage of open source, agile software, and iterative development, lean startups can operate with much less waste.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Startup Lessons Learned

OCTOBER 5, 2008

Lessons Learned by Eric Ries Sunday, October 5, 2008 The product managers lament Life is not easy when youre working in an old-fashioned waterfall development process, no matter what role you play. These specs are handed to a designer, who builds layouts and mockups of all the salient points. First, he writes it nice and clear.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

FEBRUARY 11, 2009

Lessons Learned by Eric Ries Wednesday, February 11, 2009 The free software hiring advantage This is one of those startup tips Im a little reluctant to share, because its been such a powerful source of competitive advantage in the companies Ive worked with. Especially for a startup, not taking maximum advantage of free software is crazy.

Software Review 68

Software Review Software Hiring San Francisco 68

Startup Lessons Learned

OCTOBER 4, 2008

Lessons Learned by Eric Ries Saturday, October 4, 2008 About the author ( Update January, 2010: This post originally dates from October, 2008 back when I first started writing this blog. I know many people who think that software works like magic, but to me it actually was magic. October 13, 2008 6:47 PM Luke G said.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

SEPTEMBER 7, 2008

Lessons Learned by Eric Ries Sunday, September 7, 2008 Customer Development Engineering Yesterday, I had the opportunity to guest lecture again in Steve Blank s entrepreneurship class at the Berkeley-Columbia executive MBA program. 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 30, 2008

Lessons Learned by Eric Ries Tuesday, September 30, 2008 What does a startup CTO actually do? 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?

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

NOVEMBER 4, 2008

Lessons Learned by Eric Ries Tuesday, November 4, 2008 Principles of Lean Startups, presentation for Maples Investments Image via Wikipedia Steve Blank and I had the opportunity to create a presentation about lean startups for Maples Investments. Agile software development. How dare you! =) November 4, 2008 10:58 PM IMVU said.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

SEPTEMBER 2, 2008

Lessons Learned by Eric Ries Tuesday, September 2, 2008 Just-In-Time Scalability At my previous company, we pioneered an approach to building out our infrastructure that we called "Just-In-Time Scalability." 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

NOVEMBER 8, 2008

Lessons Learned by Eric Ries Saturday, November 8, 2008 What is customer development? For software, we have many - you can enjoy a nice long list on Wikipedia. This is a self-published book, originally designed as a companion to Steves class at Berkeleys Haas school of business. November 9, 2008 5:40 PM Chris said.

Customer Development 168

Customer Development Developer San Francisco Customer 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. For software, the easiest batch to see is code. Similar results apply in product management, design, testing, and even operations. I dont think so.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

NOVEMBER 13, 2008

Lessons Learned by Eric Ries Thursday, November 13, 2008 Five Whys Taiichi Ohno was one of the inventors of the Toyota Production System. Best of luck, Your Software." (OK, Wed never heard of five whys, and we had plenty of "agile skeptics" on the team. November 13, 2008 8:59 PM eisrael said. Good stuff.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

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

Startup Lessons Learned

NOVEMBER 29, 2008

Lessons Learned by Eric Ries Saturday, November 29, 2008 The ABCDEFs of conducting a technical interview I am incredibly proud of the people I have hired over the course of my career. The six key attributes spell ABCDEF: Agility. For software engineers, I think this absolutely has to be a programming problem solved on a whiteboard.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

SEPTEMBER 10, 2008

Lessons Learned by Eric Ries Wednesday, September 10, 2008 A new version of the Joel Test (draft) (This article is a draft - your comments are especially welcome as I think through these issues. 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

Altgate

SEPTEMBER 16, 2010

The presentation was on outsourcing generally, not just software engineering and the audience was very early stage companies (some yet to be founded). Almost certainly accounting is a support service and should be outsourced (unless, perhaps, you’re selling accounting software and you need to eat your own dogfood!).

Software Review 65

Software Review Offshore Startup Boston 65

Startup Lessons Learned

AUGUST 3, 2009

Refreshing to finally see lean and agile thinking emerge in product/business-floors and not only in technology. My experience is in Enterprise Software - where we are forced to chunk features into formal releases. Revisiting the Software Design Manifesto (and what. Thank you. I know it's going to help me immensely!

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Cracking the Code

APRIL 13, 2007

Thoughts from a Venture Capitalist on Software, Software-as-a-Service (SaaS), Cloud Computing, Internet and more. Software 2.0: How the use of internet is transforming the software industry. In the past seven years, Internet has changed the business landscape and software has not been an exception to the rule.

Software Review 48

Software Review Internet Software Technical Review 48

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

MARCH 31, 2014

Today’s workforce has radically different expectations, brands are losing their power, physical channels are being destroyed by virtual ones, market share is less important than market creation, and software is eating world. These will enable firms to embrace innovation by design not by exception. Act Like a Startup.

Private Equity 328

Private Equity Metrics China Intellectual Property 328

Startup Lessons Learned

DECEMBER 7, 2008

Lessons Learned by Eric Ries Sunday, December 7, 2008 The hackers lament One of the thrilling parts of working and writing in Silicon Valley is the incredible variety of people Ive had the chance to meet. 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

SoCal CTO

DECEMBER 1, 2010

Five Reasons You Haven’t Launched - Software By Rob , November 10, 2010 Photo by stevendepolo. It’s Easy to Be Great…It’s Hard to Be Consistent - Software By Rob , November 4, 2010 No link from TechCrunch, write-up on Mashable, mention by Leo Laporte, or Tweet by Ashton Kucher is going to make your business. This post is an accusation.

Technical Review 175

Technical Review Technology Product CTO Hire 175

Startup Lessons Learned

JULY 5, 2010

When I wrote a review of Four Steps on this blog in November, 2008, I did my best to be candid and warn of a few shortcomings: And Steve is the first to admit that its a "turgid" read, without a great deal of narrative flow. Four Steps primarily centers its stories and case studies on B2B hardware and software startups.

Customer Development 166

Customer Development Developer San Francisco Customer 166

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. February 9, 2009 7:45 PM Joseph Flahiff said.

Lean 68

Lean San Francisco Web Advisory Board 68

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. Yes, building software is cheap and fast unlike other products. Sweat equity or salary?

Engineer 41

Engineer Software Review Startup Technical Review 41

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). Read the rest.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

SEPTEMBER 2, 2008

Lessons Learned by Eric Ries Tuesday, September 2, 2008 Ideas. 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. Were a software company, so what we do everyday is turn ideas into code. Learn I like theory too much.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

DECEMBER 8, 2008

Lessons Learned by Eric Ries Monday, December 8, 2008 Continuous integration step-by-step Lets start with the basics: Martin Fowlers original article lays out the mechanics of how to set up a CI server and the essential rules to follow while doing it. December 10, 2008 6:37 AM Anonymoussaid. March 26, 2010 8:42 AM ankur aggarwal said.

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136

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. a guide for hackers) You buy virtual goods The free software hiring advantage Continuous deployment and continuous learning The lean startup @ Web 2.0

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

FEBRUARY 10, 2009

That leads to a seemingly-obvious question: what is progress in software development? Heck, thats what it says right there in the agile manifesto. Labels: agile , continuous deployment , lean startup , product development , Test-driven development 4comments: Nivi said. But it worked. We made it. So can you. I am not a developer.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Steve Blank

MARCH 18, 2011

Software companies had to buy specialized computers and license expensive software. Customer Development , Agile Engineering and the Lean methodology enforced a process of incremental and iterative development. Rules for building a company in 2011 are different than they were in 2008 or 1998. The New Exits.

Internet 334

Internet IPO Silicon Valley Agile 334

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. Automated tests make defects visible. Expo SF (May. Conference streaming, sponsors, discounted tickets.

San Francisco 68

San Francisco Developer Continuous Deployment DC 68

Startup Lessons Learned

SEPTEMBER 27, 2010

This is precisely the dilemma that the doctrine of minimum viable product is designed to solve. When people start using quality, reliability, or design as an excuse to delay, it used to make me nervous, even when these suggestions were well intentioned. Rules of thumb can be infuriatingly unhelpful. And it’s really hard.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

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. And one last specific practice that came up at this session: feverishaaron : UI, design and programmers are all in the same department, all have the same title, and all are evaluated the same. Expo SF (May.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113