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

NOVEMBER 8, 2008

Lessons Learned by Eric Ries Saturday, November 8, 2008 What is customer development? Steve Blank has devoted many years now to trying to answer that question, with a theory he calls Customer Development. 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

JULY 5, 2010

I believe it is the best introduction to Customer Development you can buy. As all of you know, Steve Blank is the progenitor of Customer Development and author of The Four Steps to the Epiphany. I have personally sold many copies of his book, and continue to recommend it as one of the most important books a startup founder can read.

Customer Development 166

Customer Development Developer San Francisco Customer 166

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. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Expo SF (May.

Agile 60

Agile Lean San Francisco Continuous Deployment 60

Steve Blank

APRIL 10, 2009

Customer Development ) to help you quickly recognize and reverse any incorrect decisions. That’s why startups are agile. Startups that are agile have mastered one other trick – and that’s Tempo – the ability to make quick decisions consistently over extended periods of time.

Silicon Valley 300

Silicon Valley RSS Startup Agile 300

Steve Blank

DECEMBER 13, 2010

Here’s the course announcement from Professor Vergara (in English): Customer Development Course in Chile – Lean Launchpad. In this blog post I will add more information about the development of this course when I have it.

Chile 235

Chile Silicon Valley Lean Agile 235

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. Labels: customer development , lean startup 8comments: Amy said.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

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. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Expo SF (May.

San Francisco 68

San Francisco Developer Continuous Deployment DC 68

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

JUNE 11, 2009

Agile – you may find the real opportunities for your company was somewhere else. However, you will be dealing with almost daily change, (new customer feedback/insights from a Customer Development process and technical roadblocks ,) as the company searches for a repeatable and scalable business model. How quickly will you recover?

Cofounder 219

Cofounder Founder Silicon Valley Technical Cofounder 219

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

Steve Blank

JULY 7, 2015

Eric was the very first practitioner of my Customer Development methodology which became the core of the the Lean methodology. He was named entrepreneur-in-residence at Harvard Business School in 2010 and is currently an IDEO Fellow. Listen to my entire chat with Eric: If you can’t hear the interview, click here. Taking My Class.

Lean 120

Lean Technical Cofounder Silicon Valley Channel 120

Steve Blank

MARCH 3, 2015

Berkeley were heavily funded to develop Cold War weapon systems. Starting in the 1950’s, Stanford’s engineering department became “outward facing” and developed a culture of spinouts and active faculty support and participation in the first wave of Silicon Valley startups. —– When I came to U.C. Seeing Is Believing.

Business Plan 120

Business Plan Silicon Valley Saudi Arabia Lean 120

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. Ken Yagen (@kenyagen) KenAtYagenDotCom January 3, 2010 1:38 PM Paramendra Bhagat said. My first time at your blog. You are a great blogger.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

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. I met one recently that is working on a really innovative product, and the stories I heard from their development team made me want to cringe.

San Francisco 158

San Francisco Management Software Review Product 158

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. Customer development. Excellent ideas!

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Steve Blank

JULY 25, 2023

I’ve known Professor Cristobal Garcia since 2010 when he hosted my first visit to Catholic University in Santiago of Chile and to southern Patagonia. Co mpanies also face Wicked problems. In contrast, designing AI-driven enterprise software or building dating apps are comparatively simple problems.) Class Flow Week 1 What is a simple idea?

Lean 294

Lean Chile Ukraine Spain 294

Startup Lessons Learned

JUNE 2, 2010

Lessons Learned by Eric Ries Wednesday, June 2, 2010 The Five Whys for Startups (for Harvard Business Review) I continue my series for Harvard Business Review with the Lean Startup technique called Five Whys. As start-ups scale, this agility will be lost unless the founders maintain a consistent investment in that discipline.

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

APRIL 25, 2011

If you somehow missed SLLCONF 2010 , you can get caught up with a complete video recording here.) 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. Wealthfront CTO Pascal-Louis Perez will show you how.

San Francisco 146

San Francisco Silicon Valley Lean Agile 146

Startup Lessons Learned

NOVEMBER 7, 2008

Oops - there went several precious weeks of development effort down the drain. And if you dont know who your customer is, perhaps some customer development is in order? Labels: customer development , search engine marketing 13comments: Jim Lindstrom said. Eric -- This is a pretty interesting idea. What a great post.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

SEPTEMBER 10, 2008

Lessons Learned by Eric Ries Wednesday, September 10, 2008 Smarticus — 10 things you could be doing to your code right now Smarticus — 10 things you could be doing to your code right now A great checklist of techniques and tools for making your development more agile, written from a Rail perspective. Expo SF (May.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Steve Blank

SEPTEMBER 17, 2009

This post describes a solution – the Customer Development Model. In future posts I’ll describe how Eric Ries and the Lean Startup concept provide the equivalent model for product development activities inside the building and neatly integrates customer and agile development. This post describes such a model.

Customer Development 242

Customer Development Developer Customer Silicon Valley 242

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. Joel said it: "Top notch development teams dont torture their programmers."

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

MARCH 25, 2010

Lessons Learned by Eric Ries Thursday, March 25, 2010 Speed up or slow down? This is the first post that moves into making specific process recommendations for product development. Labels: product development Speed up or slow down? The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

FEBRUARY 20, 2009

The batch size is the unit at which work-products move between stages in a development process. Take the example of a design team prepping mock-ups for their development team. And over time, the development team may be able to start anticipating your needs. For software, the easiest batch to see is code. I dont think so.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

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. And this was a huge product, which took years to develop.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

SEPTEMBER 30, 2008

When Ive asked mentors of mine who have worked in big companies about the role of the CTO, they usually talk about the importance of being the external face of the companys technology platform; an evangelist to developers, customers, and employees. Labels: product development 15comments: mukund said. What made them exceptional?

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

MAY 31, 2010

Lessons Learned by Eric Ries Monday, May 31, 2010 Thank you The past month has been an incredible roller coaster: #sllconf was a trending topic (briefly topping Justin Bieber before the wifi in the hotel gave out), the Web 2.0 When I first encountered customer development , it was considered pure lunacy by mainstream entrepreneurs and VCs.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

www.scottporad.com

NOVEMBER 15, 2010

Scott Porad About Scott Contact Schedule Setting Up Shop: The Book Subscribe Mailbag: How do I find a developer to help me with my idea? For example, we have a mailing list in Seattle called “Seattle Tech Startups&# which is a great place to find a co-founder or developer-type. to help him develop the idea.

Fractional CTO 40

Fractional CTO Developer Philadelphia Seattle 40

YoungUpstarts

JULY 14, 2015

By the time you realize it’s a bad fit, you’ve lost months of potential revenue stream development. Before leaving GE Healthcare in late 2010 to start Caremerge, Asif was responsible for a portfolio of healthcare products generating $140 million annually with over 3000 customers (Hospitals and large centers) worldwide.

Startup 100

Startup Agile Sales Conversion 100

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. Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Steve Blank

APRIL 9, 2009

But what I wanted was an agile marketing team capable of operating independently without day-to-day direction. Reply steveblank , on October 10, 2009 at 10:59 am Said: Sales material developed by marketers who have never left the building is more often that not completely useless.

Silicon Valley 259

Silicon Valley Technical Review RSS PR 259

Startup Lessons Learned

SEPTEMBER 22, 2008

Sometimes we have the attitude that the Product Development team is the one responsible for Activation and Retention (hey, a great product would do that naturally) or that the Marketing team is responsible for Revenue and Referral (hey, go get me some money or free customers already). Expo SF (May.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Steve Blank

APRIL 27, 2009

So I started to read all I could find on the development of microwaves. A Stanford professor was at Harvard in World War II because the head of the Office of Scientific Research and Development thought Terman was the best radio engineer in the country. And in hindsight, we seemed a bit more agile and innovative in WWII.)

Silicon Valley 180

Silicon Valley Technical Review Europe Germany 180

Startup Lessons Learned

JUNE 15, 2009

If youre looking for resources on getting started, see " Continuous deployment in 5 easy steps ") The goal of continuous deployment is to help development teams drive waste out of their process by simultaneously reducing the batch size and increasing the tempo of their work. How severely is failure punished?

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

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

Lean 68

Lean San Francisco Continuous Deployment DC 68

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. Labels: agile , listening to customers 3comments: hauteroute said. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 142

San Francisco Continuous Deployment Lean DC 142