Startup Professionals Musings

JANUARY 15, 2020

In his classic book, “ The Leadership Capital Index ,” Dave Ulrich, a best-selling author, business consultant, and business school professor, provides some real insights and metrics on what makes up the elements of goodwill in the minds of top valuation experts. I have paraphrased his key points here as follows: Leader personal impact.

Valuation 311

Valuation Technical Review Due Diligence Leadership 311

SoCal CTO

MAY 21, 2012

Many of the factors are not obvious and include building mystery to drive margin, why boring B2B companies often win but are challenging in other ways, how bootstrapping wins, integrating metrics from the start and many other similar lessons. What parts Agile addresses and the big problems with Agile for early-stage startups?

Fractional CTO 175

Fractional CTO CTO Hire Startup Social Network 175

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

Both Sides of the Table

MAY 27, 2013

But the thing I am most proud of about Rob is that he has taken a company with a uniquely talented founder & CTO – Nick Halstead – and managed to build a very tight working relationship with Nick where we drive world-class product development without having the usual founder / CEO conflicts. The Agile Board.

Advisory Board 365

Advisory Board CTO Hire Fractional CTO Los Angeles 365

Startup Lessons Learned

NOVEMBER 6, 2008

Lessons Learned by Eric Ries Thursday, November 6, 2008 Steveys Blog Rants: Good Agile, Bad Agile I thought Id share an interesting post from someone with a decidedly anti-agile point of view. Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

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

MARCH 6, 2013

. + 1,000 startup founders, investors, and press! Vinod Khosla Founder Dave McClure Founding Partner Eric Ries Author Steve Blank Serial Entrepreneur & Professor Todd Park CTO Travis Kalanick CEO & Co-Founder Joe Zadeh Director of Product Sam Shank Co-Founder & CEO NEW!

Lean 165

Lean Cofounder Startup Software Engineering 165

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

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. But along with Intuit founder Scott Cook, Brad is a leader that recognizes that entrepreneurship is critical to his company’s success.

San Francisco 146

San Francisco Silicon Valley Lean Agile 146

Startup Lessons Learned

JULY 9, 2010

Lessons Learned by Eric Ries Friday, July 9, 2010 Founder personalities and the “first-class man&# theory of management At any given time, something like four percent of the US population is engaged in some form of new-company-creation. Are we solving the right problem? We can do better by focusing on process instead of personality.

San Francisco 161

San Francisco Management Founder Lean 161

Startup Lessons Learned

AUGUST 3, 2009

In a lot of cases, this requires a lot of energy invested in talking to customers or metrics and analytics. Refreshing to finally see lean and agile thinking emerge in product/business-floors and not only in technology. In fact, MVP is quite annoying, because it imposes extra overhead. Thank you. August 13, 2009 3:43 AM Robert said.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

YoungUpstarts

APRIL 21, 2013

Enter “ The Lean Startup: How Today’s Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses “, a New York Times bestseller by founder of IMVU (creator of 3D avatars) Eric Ries. This reduces guesswork, time, money and effort. Key ideas from the book include the following: 1.

Lean 193

Lean Technical Review North America Startup 193

Startup Professionals Musings

MARCH 4, 2022

I’m sorry to predict it will never happen, so the agility you may have learned over the past couple of years will continue to be critical to your survival. In this context, the late great Andy Grove , founder of Intel, believed that no change breeds failure. New blood and new ideas are keys to agility.

Agile 371

Agile Metrics Demand Internet 371

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

Startup Lessons Learned

NOVEMBER 13, 2008

Because five whys kept turning up a few key metrics that were hard to set static thresholds for, we even had a dynamic prediction algorithm that would make forecasts based on past data, and fire alerts if the metric ever went out of its normal bounds. Wed never heard of five whys, and we had plenty of "agile skeptics" on the team.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

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. Instead, we do everything possible to validate the founders belief. We dont just abandon the vision of the company at every turn.

Customer Development 168

Customer Development Developer San Francisco Customer 168

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. In order to reduce my incredible ignorance about other such hubs, Im heading to Vancouver. Thank you so much!)

Agile 60

Agile Lean San Francisco Continuous Deployment 60

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

Startup Lessons Learned

OCTOBER 5, 2008

Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more. I went through some of this in bringing agile methodologies to my current firm - except that I am the product manager in question at this case. October 6, 2008 12:17 AM r& said. Expo SF (May.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

MARCH 24, 2009

Lessons Learned by Eric Ries Tuesday, March 24, 2009 The metrics and levers of engagement, presentation on Engagement Loops for Facebook Developer Garage SF Ill be presenting a talk at the Facebook Developer Garage SF Wednesday evening. Unfortunately, its easy to lose track of positioning effects when optimizing for a single metric.

Metrics 88

Metrics San Francisco Lean Viral 88

Startup Lessons Learned

SEPTEMBER 15, 2008

Focus on the output metrics of that part of the product, and you make the problem a lot more clear. To promote this metrics discipline, we would present the full funnel to our board (and advisers) at the end of every development cycle. Max Levchin of Slide and Paypal has noted that 10% of Slides headcount is devoted to metrics only.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

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. I will come back for more. Expo SF (May.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

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. Every board meeting, the metrics of success change. These founders have not managed, to borrow a phrase from Steve Blank , to create a scalable and repeatable sales process.

Customer 167

Customer San Francisco Lean Hockey Stick 167

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.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

ReadWriteStart

OCTOBER 20, 2023

With such daunting statistics, it’s clear that maintaining a startup becomes an uphill battle for founders without the right foundations. Meeting growth metrics, achieving profitability, and ensuring a substantial return on investment are now integral parts of the startup journey.

Technical Review 137

Technical Review Startup Silicon Valley Agile 137

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. Two Ways to Hold Entrepreneurs Accountable Beware of Vanity Metrics For Startups, How Much Process Is Too Much? Techniques from lean manufacturing can be part of a startups innovation culture. Expo SF (May.

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

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. Now, this webcast was packed, hundreds of people were logged in.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

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? Thats an important job, for sure, and Ive been called upon to do it from time to time. Expo SF (May.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

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. I used to think that investments in metrics were a form of waste. I used to think that investments in metrics were a form of waste.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

MARCH 3, 2009

In order to give people the data they need to apply the strategy, we were very open with our company metrics, making all reports generally available and easy to run. When you think a certain feature will give a 50% boost to a given metric, and it only eeks out a 5% boost, you cant spin that as failure. March 9, 2009 8:35 AM Eric said.

Employee 146

Employee San Francisco Lean Software Review 146

Startup Lessons Learned

FEBRUARY 20, 2009

Sounds very similar to agile development which is the way. ► 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. No doubt about it, small batches are the way to go RT www.anonymity.eu.tc

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

JULY 29, 2009

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. Yet other agile principles suggest the opposite, as in YAGNI and DoTheSimplestThingThatCouldPossiblyWork. Reconciling these principles requires a little humility.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

YoungUpstarts

NOVEMBER 12, 2020

Founders Institute defines pivoting as shifting the business to encompass a new strategy that may entail changing how the entire company functions. Pivoting only works if a business is small and agile and can shift its operations quickly and flawlessly in a different direction. They should be able to aim for self-sufficiency early on.

Bankruptcy 165

Bankruptcy Startup Agile Technical Review 165

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

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

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

The Next Web

SEPTEMBER 8, 2013

I also want to explain that it is possible to have a truly agile work environment based on small, autonomous teams. It’s completely up to them if they want to listen or ignore outside advice – even if it’s from one of the founders. Being agile. All KPIs and metrics are available to everyone in the company. Conclusion.

Software Review 146

Software Review Agile Analytics SCRUM 146