Converting a department to OOP design...

[SharkTooth]

I have just been tasked with developing and executing a plan to move the developers to an OOP design and development process. There are 4 developers including myself and I am the only one with any OOP experience. I am the new guy on the block so I have to be careful. We are a Microsoft shop and will be using .Net (looks like my boss wants VB.Net). Most of the new activity will be web applications (ASP.Net).

My manager’s expectations (they are still evolving):
1.) Just about all new development in VB.NET mostly web based.
2.) Create a development process that is easy to follow for use in an environment where smaller applications are the norm.
3.) Create and document code libraries.
4.) Create coding standards.
5.) Create a pear review process.
6.) Implement a 3-tear architecture. (Presentation, Business Rules, Data Sources)

I right off the top I know I have to:
1.) Get an understanding of the existing processes (we really don’t have one)
2.) Get input for the other developers; get them involved in the decision-making.
3.) Get advise from people that have had this experience (you guys).

I would like to hear:
1.) Suggestions for a design methodology (books too).
2.) Suggestions for building the foundation of the libraries.
3.) Possibly some architecture suggestions

Actually any ideas or suggestions you have to offer would be great. I have a great opportunity to get this off the ground the right way and don’t want to screw it up.

Thanks for your ideas.

 

[stevexff]

If none of your developers use OOP methods already, send them on a course. Then you won't have to convince them of the benefits yourself, which is a big ask as you are the new boy. Once they are on-side, it should be easier to do the rest.

Good luck with those pears, by the way. Will you be reviewing any other fruits?

 

[SharkTooth]

If none of your developers use OOP methods already, send them on a course. Then you won't have to convince them of the benefits yourself, which is a big ask as you are the new boy. Once they are on-side, it should be easier to do the rest."
>>> Good idea.

"Good luck with those pears, by the way. Will you be reviewing any other fruits?"
>>> lol took me a minute to figure out what you were saying. "peers".

Thanks

 

[jby1]

In terms of programming methodologies, you might want to take a look at Extreme Programming (

http://www.extremeprogramming.org).

A lot of this may seem like overkill, but there is some good stuff in there. Also have a look at Agile Methodology, which shares many of the same idea.

For design methodology, it is worth getting hold of a copy of Design Patterns. There is also a lot of stuff on the web on Design Patterns, so get googling!

Good luck with changing the working practices, this is a very difficult task. Try and get the guys on-side asap, easier said than done I know. Without them the whole thing is doomed to failure.