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. More to come.

Agile 40

Agile Architecture Offshore Software Developers 40

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

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. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Thank you so much!) Expo SF (May.

Agile 60

Agile Lean San Francisco Continuous Deployment 60

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. April 6, 2010 8:23 AM Colie Brice said. No more, no less. Good stuff.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

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. Berkeley in 2010 to run the Lester Center for Entrepreneurship in the Haas School of Business we were teaching entrepreneurship the same way as when I was a student back in 1995.

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. I help lead the Engineering Leadership SIG at SDForum and wonder if you would be interested in speaking to our group about lean starups. Blew my mind.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

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

SEPTEMBER 30, 2008

So I initially gravitated to the CTO title, and not VP of Engineering. If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? But since I spent a long time in a hybrid CTO/VP Engineering role, I still have this nagging question. They might do anything !

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

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

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

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

Startup Lessons Learned

SEPTEMBER 22, 2008

I break the answer to that question down into three engines: Viral - this is the business model identified in the presentation as "Get Users." Thats why eBay advertises on search engines, and Facebook doesnt. Labels: search engine marketing 0comments: New comments are not allowed. Thats where Id like to pick up the discussion.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Steve Blank

JUNE 25, 2009

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.) They couldn’t keep up with the fast product development times that were enabled by using standard microprocessors. Their engineers hated us.

Technology 138

Technology Silicon Valley Fractional VPE Part-Time VPE 138

Startup Lessons Learned

FEBRUARY 20, 2009

Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. I owe it originally to lean manufacturing books like Lean Thinking and Toyota Production System. The batch size is the unit at which work-products move between stages in a development process.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

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. Five Whys has its origins in the Toyota Production System. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

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? Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Venture Chronicles

AUGUST 2, 2013

and more on point is that the best product is a result of what you learn from your customers, not what you think you should be doing. If we did anything egregiously wrong at Get Satisfaction in the 2010-1012 time period it was to under-invest in the product with the assumption that the existing product was good enough.

Product 62

Product CTO Hire Architecture Startup 62

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. Hopefully others will find it useful as well.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

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

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. Labels: agile , listening to customers 3comments: hauteroute said. Expo SF (May.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

JUNE 17, 2010

Lessons Learned by Eric Ries Thursday, June 17, 2010 No departments Big companies have departments. I was an engineer on the engineering team. For one, the engineers consider the artists stupid; the artists consider the engineers arrogant. Startups are companies. Startups aspire to become big companies.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

NOVEMBER 7, 2008

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. Seems like a fairly low-cost method of gauging customer interest for a would-be product. Eric -- This is a pretty interesting idea. Expo SF (May.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

JULY 13, 2009

Lessons Learned by Eric Ries Monday, July 13, 2009 The Principles of Product Development Flow If youve ever wondered why agile or lean development techniques work, The Principles of Product Development Flow: Second Generation Lean Product Development by Donald G. Reinertsen is the book for you.

Product Development 153

Product Development Developer San Francisco Product 153

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. You can learn about customer development, and quite a bit more, in Steves book The Four Steps to the Epiphany. Expo SF (May.

Customer Development 168

Customer Development Developer San Francisco Customer 168

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 12, 2008

0comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Expo SF (May.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

JULY 30, 2009

During the same period (1987 – 1990) and I did some work at MIT under Eric von Hippel on “user driven innovation with regard to software development&# which today would probably fall under the heading of “open source software development approaches.&# Expo SF (May. Conference streaming, sponsors, discounted tickets.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

AUGUST 8, 2009

I thought a good place to start was with the origins of the idea that "software design" should be considered a discipline in its own right, on par with computer science, software engineering, and computer programming. Great engineers see it and smile. This is called set-based concurrent engineering (SBCE). [1]

Software Review 87

Software Review Design Software San Francisco 87

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 Continuous Deployment 113

Startup Lessons Learned

JUNE 15, 2009

The agile software movement has made numerous contributions: continuous integration, which helps accelerate feedback about defects; story cards and kanban that reduce batch size; a daily stand-up that increases tempo. Continuous deployment is another such technique, one with a unique power to change development team dynamics for the better.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

JULY 28, 2010

Lessons Learned by Eric Ries Wednesday, July 28, 2010 Case Study: kaChing, Anatomy of a Pivot (The following guest post is a new experiment for this blog. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, It was written by Sarah Milstein in collaboration with kaChing CEO Andy Rachleff. Expo SF (May.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

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

San Francisco 68

San Francisco Developer Continuous Deployment DC 68

Startup Lessons Learned

SEPTEMBER 14, 2008

Later, when the company was much larger, we had everyone on our engineering team agree to sit in on one usability test every month. It wasnt a huge time commitment, but it meant that every engineer was getting regular contact with an actual customer, which was invaluable. Expo SF (May.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Lessons Learned

AUGUST 2, 2008

0comments: Post a Comment Newer Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) April 23, 2010 in San Francisco. Expo SF (May.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

JANUARY 7, 2010

Lessons Learned by Eric Ries Thursday, January 7, 2010 Is Entrepreneurship a Management Science? Although much of it will sound familiar to readers of this blog, whats new is my first step towards the " new entrepreneurship " that is my goal for 2010. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

San Francisco 119

San Francisco Management Continuous Deployment Lean 119

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 Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Expo SF (May.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

NOVEMBER 17, 2008

Strategy - startups first encounter this when they have the beginnings of a product, and theyve achieved some amount of product/market fit. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Stevey's Blog Rants: Good Agile, Bad Agile Learning from Obama: maneuver warfare on the campa.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88