Thanks for the feedback. You’re absolutely correct: the SIP model was developed for a web agency. Internal teams are an entirely different matter. I would look at past projects, perhaps over a few years, to determine any trends. Is there any “product” that can be defined as a goal? Volume of requests, nature of the work, the industry of the company and executive support for technology projects would all come into play.

For me it was a content management system. I developed a dynamic CMS in my last days in a more tech role. Every client might ask for something different, but the base model is flexible enough to respond as needed.

I’m interested in your SIPs approach - I’m assuming that this is what you’d use for an agency web team, as my experience of internal teams is that you rarely get multiple clients asking for the same thing (it’s the other end of the scale - they all want something different).

Having said that it seems like quite a sound approach - I was just wondering how you’d run it when your basis wasn’t producing the same code for multiple clients?