Is packaged software the best way to accomplish something? I recently read The True Cost of Off-the-Shelf from Computerworld. This article questions the common practice of buying pre-packaged software.
How does this thinking relate to a Church Management System (ChMS)?
How does open-source play into this? Would a community developed ChMS that allows for local customizations solve the problem?
At one point Crossroads struggled with the decision to go with Fellowship One or continue development of our own system. Sometimes I wonder if we made a mistake. Don’t get me wrong, Fellowship One is a very good system and we benefit from it. But we have (as the article states) had to change some of our practices to fit the software instead of changing the software to fit our practices.
In addition, it has taken us a long time to grow (and we’re still not done) into the software and use all of its features. Perhaps it wouldn’t have been much different if we had grown into our own custom developed software as we developed it.
I still think that the best alternative is a community developed open-source package that provides an existing base to work from but allows customization.