The Pragmatic Craftsman :: Simplicity from complexity ::

«
»

Raganwald: What I’ve learned from failure

January 28th, 2006 | In Learning / Thoughts | Comments Off

What are the key elements that ensure the success of your project? What are the keys that will tell you not to continue with the project? I don’t know to tell you the truth. :-( But the four things that are outlined below, and explained by Reganwald blog, I are crucial, in my opinion. This is a very good, must-read and re-read (notice new category :-) ), article.

Excerpts from the entry:

the four things which matter most are:

1. The quality of the people doing the development2. The expected value of the product to its stakeholders3. The fitness of the proposed solution4. The quality of project management and expectations communication

In my experience, you need all four working to have a successful project. I’ve personally failed when even one of those four things was bad and not corrected immediately. If two, three, or all four were wrong, my discovery is that I’ve been unable to avert disaster. (This list obviously doesn’t cover all of the factors needed for business success: I’m just talking about getting the software to ship).

I’ve read the whole article and it is one of the best I’ve read on the subject! I concur that these things are crucial.

Reference What I’ve learned from failure, Raganwald blog

Comments are closed.

Random Quote

Topics

Tags

Archive

Recent Entries

  • Staying Sharp
  • Make fields final, objects immutable
  • Beginning Java EE 6 with Glassfish 3
  • Java EE 6 – Job Well Done
  • Java Inner Classes – Part 4 – Multiple Inheritance and Closures
  • Java Inner Classes – Part 3 – Nested Classes
  • Java Inner Classes – Part 2 – Anonymous
  • Java Inner Classes – Intro
  • What makes a great software engineer?
  • Design Patterns Explained

    • Currently Reading

    Shelfari: Book reviews on your book blog

    :: The Pragmatic Craftsman recommends

    :: The Pragmatic Craftsman book reviews

    Info

    © 2001-2010 Stanley Kubasek About me :: Contact me

    @PragCraftsman on Twitter

    SOLID principles come in handy here. Especially, "Open of Extension, Closed for Modification." One of the best principles I've learned. - 6 hours agoI actually try to follow @unclebobmartin's rule all the time. Sort of. I try not to make it worse. But to make it better? Great challenge! - 6 hours agoAlways check a module in cleaner than when you checked it out (via @unclebobmartin in 97 Things Every Progr.). I love the idea! - 7 hours agoI put Code Complete #1 over Martin's book because it has "awaken" me as a programmer. But other than that, Martin's book is the best! - 1 day ago@mcory1 First of all, @unclebobmartin is my hero! Agile Software Development, Principles, Patterns, and Practices is my #2. SOLID rules! :) - 1 day ago