We were talking to one of our leads who wanted to develop a product and deliver it as a service to his end-customers. Yes, we are talking about the buzzword Software-as-a-Service. The lead had a few things clearly identified in terms of the market he wants to serve, the kind of features that his product should have, the architectural complexity of it, the engineering time-frame, and the release plan.
After a series of discussions on the technology to be used, the product management methodology to be followed and the kind and size of team that he would require, we came around to discussing about the architecture of the product. Essentially the requirements here were on releasing the first version of the product quickly and keeping it scalable for subsequent releases and versions.
The lead was very particular that he would own the product management and architecture of the product and he would look at expertise only for the development. Then, we offered to provide architectural services separately away from our development, which was liked by the lead.
Essentially, the lead was very clear in his mind that he didn’t want to mix the architecture with the development and he wanted to validate the architecture before getting into development.
