> My experience using MLS and working with support has led me to believe > that there is some gross incompetence going on somewhere. I think that > the system is very poorly designed, and easily-reproducible (and > easily-fixable) bugs that I first reported a year and a half ago are still > irritating me.
Something both revealing and hopeful I learned last fall while, out of curiosity, attending a Church IT Open House here in the SF Bay Area. (It was basically a recruiting event.) Revealing in that after the meeting the newly hired QA Manager for the Church (from Symantec, I believe) acknowledged that MLS and LUWS (Local Unit Web Sites) were released without going through any QA. He also pointed out that before his arrival, there as no systematic way to process and track bug reports and feature requests. In addition, the development and support teams for MLS and LUWS were greatly understaffed. I sensed that MLS and LUWS were only a small part of the Church's technology beast. This may explain the "deaf ears" that many of us have experienced. However, I left the meeting hopeful. The Church staff there clearly recognized the technology needs and were making a very obvious push to attract and hire fresh talent. At the time, it was mentioned that some 30+ newly created, full-time positions in technology were available, and if you are familiar with how protective the Church is of full-time positions, that's a big deal. I hope they pulled in some great talent. The Church does so many things first-class such as temples, meeting houses, visitors centers, printed publications, and broadcasts, to name a few. It hasn't happened with the membership management software yet. Maybe it will take showing how these tools improve the Perfecting, Proclaiming, and Redeeming, before tithing resources are really allocated. -Greg _______________________________________________ Ldsoss mailing list [email protected] http://lists.ldsoss.org/mailman/listinfo/ldsoss
