Lets assume you have already “bought” plenty of base functionality such as .Net, enterprise library, user interface controls, workflow, etc. You may even have an Enterprise Architecture.
To a typical developer, it all just looks like a pile of stuff. Or a list in SharePoint somewhere
The point is: just because you bought something terrific doesn’t mean it is diffused throughout your organization. And similarly, just because you are going to start calling it a framework doesn’t mean the developers will jump for joy and start using it.
Therefore, you are going to have to “build it”. By that I mean put together the program/ organizational changes PLUS the actual technical “bits and bytes” wrapped up in an easy-to-use package.
Lets start with the basics.
First you likely have loads of good or even great code written in your organization. You also will find that tools have been purchased and are in-use. So you can start with that for the “bits and bytes” portion. Use what you’ve already got. At least to start with.
[pullquote]Does governance apply?[/pullquote]Secondly, organize and communicate. Think through how the framework will be applied across software projects. Does governance apply? Will you market it to new projects? Is there a charge-back? What kinds of projects can immediately benefit? What team is going to support the framework code if it is the cause (or held to blame) for an outage in Prod? What development model will best work for your framework: central team or a quasi-open-source model? How long are you going to keep paying for this framework?
The way I wrapped my head around all the questions was to apply a “Product Management” model to the task of framework development. The way my manager thought about it was to apply a “Program Management” model to me and my team. In that way we first set out our vision, sponsors, funding model, (ahem) metrics etc. Next I worked with the stakeholders to define the actual ‘product’, it’s ‘customers’, features roadmap, pricing, support policy, and marketing strategy.
Three months later, me and my newly dedicated (er 35% dedicated!!!) team started the actual work of the build-out. LOL I was surprised it took so long to get started.
|This book is a very helpful read if you are facing the task of building out a new framework. The fact is that there are existing patterns in place across the organization. To implement a framework fully and successfully will require a great deal of change through the development teams. For a techie who thrives on change, this book really helped me get in the heads of those who … don’t. Highly recommended.|