1. sten
    29. January 2010 @ 18:06

    The top -> down approach is very common, so starting with the essentials is the best idea in most cases. Unfortunately it’s sometimes hard to find out what the essentials really are and if they are stable enough to stay valid until shipping. If this is easy to handle or not highly depends on the team or partner you are working with. It always gets tougher than you thought.


  2. Manuel Koelman
    29. January 2010 @ 21:03

    Yes, I absolutely agree. It is not always easy to find what is essential. However, that is the part you need to figure out fast. Therefore, I suggest: Build something small, throw it out there, check how the people use it. Then adapt/enhance. This is even more important as it is terribly hard to take away features (unless really nobody uses them). In the beginning many products are really beautiful until they reach a certain point were feature creep sets in. Feature creep is very toxic. That’s when I suggest to make a strict rule: When somebody wants to develop a new feature, he has to take another one out (unless it is a “new” product or fulfills a completely new purpose).The hard part is not adding all kind of new features. The hard part is saying no.


  3. Manuel Koelman
    30. January 2010 @ 11:48


Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Back to top