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. Consider the classic project that was essential to the creation of extreme programming , the Chrysler Comprehensive Compensation System.

Agile 111

Agile Customer Development Developer San Francisco 111

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. Agile allows companies to build higher quality software faster.

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." The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Thoughts on scientific product development Lo, my 5 subscribers, who are you?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

FEBRUARY 9, 2009

It uses principles of agile software development, open source and web 2.0, ► 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. Learning is better than optimization (the local ma.

Lean 68

Lean San Francisco Web Advisory Board 68

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!) for Harvard Business Revie.

Agile 60

Agile Lean San Francisco Continuous Deployment 60

blog.nahurst.com

JULY 19, 2010

Nathan Hursts Blog Thoughts on Software, Technology, and Startups « Back to blog Im on the technical side of entrepreneurship in NYC. I love programming, board games, and my wife. The graphic below balances the risks cofounders take with their relative contributions to help answer this question.

Technical Cofounder 43

Technical Cofounder Cofounder Equity Salary 43

Startup Lessons Learned

MAY 27, 2009

It uses principles of agile software development, open source and web 2.0, This will be an in-depth discussion with a handful of entrepreneurs and founders that have been pre-selected. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? for Harvard Business Revie.

Lean 60

Lean Austin San Francisco Continuous Deployment 60

Startup Lessons Learned

JUNE 15, 2009

Why do software developers think this is acceptable? ► 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. June 22, 2009 10:07 AM Khris said. I should think not. Thanks for this.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

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. I believe this is one reason why the myth of the dictatorial startup founder has such enduring appeal.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

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. I have personally taught many “non-technical&# people to program – graphic designers, QA folks, even artists and animators.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

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

maplebutter.com

JANUARY 8, 2013

what are the most crucial steps to be taken by a new tech startup when outsourcing major part of the tech to IT firms or outsourcing “product development” eg new social media website project? Near shoring development with your team (ex: your team is based in Canada / India) is cool, but not outsourcing.

Technical Review 44

Technical Review Startup Cofounder Software Review 44

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 assumed he was there to refute my critique of extreme programming, but nothing could be further from the truth. Was that really the Kent Beck?

Lean 140

Lean San Francisco Continuous Deployment Startup 140

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

www.quora.com

JANUARY 16, 2011

Find Questions, Topics and People Add Question Add Question Non-Technical Co-Founders Co-Founders Technical Co-founders Finding Co-Founders Startups & "How Important Are Ideas?" " Web Development Startups Solo Founders I am a creative guy with a startup idea.

Developer 42

Developer Technical Review Cofounder Technical Cofounder 42

Startup Lessons Learned

JULY 2, 2009

These problems can be anything: development mistakes, site outages, marketing program failures, or even internal missed schedules. I pick that example on purpose, for two reasons: 1) most of the companies I work with deal with this problem and yet 2) almost none of them have any kind of training program in place for new employees.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

DECEMBER 7, 2008

Use pair programming and collective code ownership. These are two other Extreme Programming practices that are explicitly designed to counteract the problems inherent in this situation. Pair programming is the most radical, but also the most helpful. So, fellow hackers, Id love to hear from you. Does this sound familiar?

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

AUGUST 1, 2009

For startups that are tempted to mimic this behavior, I suggest reading the great account of the early Apple in Founders at Work.) Also SJ's obsession with better taste (positively) contributes to the overall product development process. Regardless, they must cull a lot of bad ideas for every one that we hear about.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Software By Rob

AUGUST 18, 2010

Before: After: And thenI ran into a Mixergy interview where 37signals founder, Jason Fried, talks about their free plan (6:00 into the interview): “… The majority of the revenues for our products come from people who sign up for the paid versions upfront. I saw that 37signals had hidden theirs. But is it the right data?

Software Review 78

Software Review Software Revenue Cofounder 78

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. No departments The Five Whys for Startups (for Harvard Business R.

San Francisco 74

San Francisco SCRUM Lean Continuous Deployment 74

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

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