Remove 2008 Remove SCRUM Remove Software Remove Software Development
article thumbnail

Rally Software Acquired By CA Technologies for $480 Million

Feld Thoughts

Congrats to my friends at Rally Software on the announcement that they’ve signed a definitive agreement to be acquired by CA Technologies for $480 million. For example, from a post in 2008 about Rally’s $16.85m financing , I riffed on the origins of the company. We weren’t the first investor in Rally.

article thumbnail

Lessons Learned: The lean startup

Startup Lessons Learned

Lessons Learned by Eric Ries Monday, September 8, 2008 The lean startup Ive been thinking for some time about a term that could encapsulate trends that are changing the startup landscape. But by taking advantage of open source, agile software, and iterative development, lean startups can operate with much less waste.

Lean 168
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Lessons Learned: Combining agile development with customer development

Startup Lessons Learned

In most agile development systems, there is a notion of the "product backlog" a prioritized list of what software is most valuable to be developed next. The breakthrough idea of agile is that software should be built iteratively, with the pieces that customers value most created first.

Agile 111
article thumbnail

Social, Agile, and Transformation: Strategic Agile Thinking: Balancing Value, Innovation and Research

ctotodevelopers.blogspot.com

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
article thumbnail

The four kinds of work, and how to get them done: part three

Startup Lessons Learned

Lessons Learned by Eric Ries Saturday, December 6, 2008 The four kinds of work, and how to get them done: part three Those startups that manage to build a product people want have to deal with the consequences of that success. Scrum recommends 30 days; I have worked in one or two-week cycles up to about three months.