  |
Group Commons Philosophy
In any development process there are five distinct processes that occur:
In practice this turns out to be a cumbersome view. In point of fact, the process is much generally much more fluid. Requirements generate tickets, which in turn generates QA items. But it turns out that QA generates requirements as well. And often Tickets generate requirements. Most systems do not attempt to try to handle this kind of complexity. Group Commons does attempt to create the more fluid approach that matches reality better. In doing so, we believe we can spead of the development process for any project. Often requirements are too difficult to write out of context of an existing application. Sometimes the best approach is to write some basic requirements, implement some code, do a QA process on what you know is right, then use the QA process to spec out more requirements. This process does not have the concept of "finality" that most people desire in the development process; Its hard to say when the project is DONE. However, it tends to produce faster, better quality product that meets the real needs of the project owner. Too many projects fail to be implemented because they can't complete the requirements. Most often projects could be implemented and turned live if there was a willingness to change requirements to match technology constraints. |
