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).

Lean 68

Lean San Francisco Continuous Deployment DC 68

ctotodevelopers.blogspot.com

JULY 11, 2012

I cover several topics including agile software development, software startups, web 2.0, Labels: about me , agile planning , agile software development , cio , innovation , it management , organizational change , product management , project management , software development , software qa.

Agile 40

Agile Architecture Offshore Software Developers 40

crowdSPRING Blog

OCTOBER 20, 2010

Power of Social Cloud – [link]. Legal Contracts for Software Developers Who Hate Contracts (w/free contract template tco use today) – [link]. Amazon’s Approach to Product Development – [link]. Where’s @oldspice on Twitter these days, asks @edwardboches – [link]. – [link].

Social Media 91

Social Media Small Business Design Media 91

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. Thoughts on scientific product development Lo, my 5 subscribers, who are you?

Customer Development 131

Customer Development Engineer San Francisco Developer 131

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. I had a background in lean manufacturing (book knowledge, anyway) and lean software development (hands on) before encountering Lean Startups.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

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. Take a look and let me know what you think.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

SEPTEMBER 27, 2010

One of the sayings I hear from talented managers in product development is, “good enough never is.&# And, most importantly, it helps team members develop the courage to stand up for these values in stressful situations. Lessons Learned by Eric Ries Monday, September 27, 2010 Good enough never is (or is it?)

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

NOVEMBER 4, 2008

It is becoming easier and cheaper for companies to bring products to market, leveraging free and open source software , cloud computing, open social data (Facebook, OpenSocial ), and open distribution (AdWords, SEO). Agile software development. This post has been removed by the author.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

SEPTEMBER 2, 2008

Lessons Learned by Eric Ries Tuesday, September 2, 2008 On deployment My favorite question to ask a software development team is "how do you do a release." Thoughts on scientific product development Lo, my 5 subscribers, who are you? You can tell a lot about a company from their deployment flow. How fast do they iterate?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

MARCH 16, 2009

Ever since that time, I have struggled to explain how the feedback loop in customer development should interface with the feedback loop in product development. What causes projects like this to fail in traditional software development is that the solution is unknown. What do you do if the problem itself is unknown?

Agile 111

Agile Customer Development Developer San Francisco 111

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. None of it would have happened if we had plenty of cash, or were content to count our progress by traffic or product development milestones.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

FEBRUARY 10, 2009

You cant make these global efficiency improvements until you get clear about the goal of your development process. That leads to a seemingly-obvious question: what is progress in software development? It would be hard to argue against this product development strategy, in general. If a feature worked, wed keep it.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

AUGUST 1, 2009

Also SJ's obsession with better taste (positively) contributes to the overall product development process. There are some good anecdotes about Chief Engineers in the Toyota Product Development Book. I really enjoyed this article, my first time reading any of your stuff. Will start to pay attention. Great post Eric.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Software By Rob

MAY 21, 2010

They thought people would flock to their idea, fumbling for their credit cards the moment they heard someone had developed a re-tweeting cloud app for Facebook fan pages. The bottom line here is to take your launch seriously, as seriously as you’ve taken your product development. Ask any startup founder.

Software Review 55

Software Review Startup RSS Software Developers 55

Startup Lessons Learned

DECEMBER 7, 2008

Sometimes, a great hacker has the potential to grow into the CTO of a company, and in those cases all you need is an outside mentor who can work with them to develop those skills. At the end of the day, the product development team of a startup (large or small) is a service organization. Does this sound familiar?

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

JANUARY 28, 2009

Its an essential discipline of good software development, especially in startups. Because, unless you are working in an extremely static environment, your product development team is learning and getting better all the time. Labels: agile , product development , Test-driven development 11comments: William Pietri said.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

Startup Lessons Learned

MARCH 25, 2009

Agile Vancouver : Lean Development for Lean Times On Tuesday April 21st, we are hosting an afternoon event on the application of Lean Principles to software development. 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

Startup Lessons Learned

FEBRUARY 9, 2009

It uses principles of agile software development, open source and web 2.0, The Lean Startup is a practical approach for creating and managing a new breed of company that excels in low-cost experimentation, rapid iteration, and true customer insight. Take a look and let me know what you think.

Lean 68

Lean San Francisco Web Advisory Board 68

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. Take a look and let me know what you think.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

MAY 27, 2009

It uses principles of agile software development, open source and web 2.0, The Lean Startup is a practical approach for creating and managing a new breed of company that excels in low-cost experimentation, rapid iteration, and true customer insight. Take a look and let me know what you think.

Lean 60

Lean Austin San Francisco Continuous Deployment 60

Startup Lessons Learned

JULY 2, 2009

Labels: five whys root cause analysis , product development 15comments: Anonymoussaid. Furthermore, I think most of what you are suggesting is applicable in companies/ industries that are not software development. Leave your thoughts in a comment. If you’ve tried Five Whys, please share your experiences so far.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

blog.nahurst.com

JULY 19, 2010

Ex: theyre primarily a back-end programmer, who can code basic front-end specs, and who can administer cloud hosting. 2a] Has paying customers -10%: If the company already has paying customers, the non-technical cofounder has already eliminated a huge risk for the business; someone wants the product. [2b]

Technical Cofounder 43

Technical Cofounder Cofounder Equity Salary 43

mashable.com

MAY 24, 2011

May 23, 2011 by Christina Warren 20 Share on Tumblr email share Share on Tumblr email share The Mobile App Trends Series is supported by Sourcebits , a leading product developer for mobile platforms. Sourcebits offers design and development services for iOS, Android, Mobile and Web platforms.

Mobile 90

Mobile Web Social Media Software Review 90

Startup Lessons Learned

FEBRUARY 22, 2010

Even if men have an innate advantage at software development, the gap would have to be massive in order to explain why startup after startup has an all-male team. Even if men have an innate advantage at software development, the gap would have to be massive in order to explain why startup after startup has an all-male team.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

Startup Lessons Learned

DECEMBER 6, 2008

When youve mastered that, consider adding operations, customer service, marketing, product management, business development - the idea is that when the team needs to get approval or support from another department, they already have an "insider" who can make it happen. Take a look and let me know what you think.

San Francisco 74

San Francisco SCRUM Lean Continuous Deployment 74

Startup Lessons Learned

JUNE 15, 2009

Why do software developers think this is acceptable? Part of putting this into action is requiring your team to have a very deep understanding of their customers. June 22, 2009 10:07 AM Khris said. Would you buy a car that constantly had to go back to the dealer to be improved? I should think not. Thanks for this.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

www.quora.com

JANUARY 16, 2011

As a developer, I feel that design/creative is undervalued in the early stages of product development. Notwithstanding examples like Plentyofish, people respond to well designed, well branded products, and that can be important in getting traction early on. Ryan Hornbeck , Computer and Cloud Systems Integrator.

Developer 42

Developer Technical Review Cofounder Technical Cofounder 42