I've been hired for a new job (hence the enthusiasm and the question). I have finally been able to get out of my dead end job working in a small library. I'll be working for a medium sized property management company in San Diego. Their entire intranet has been built by telling freelancers what they want and implementing what they've been given. And they're not particularly pleased with the results.
Here are some of my initial thoughts:
1) break up the assignments logically. Master pages to the designers, .cs files to the programmers, and content pages to the content managers (granted some people including myself will be wearing multiple hats).
2) I want to require mockups that I can present to the end users for feedback before proceeding further (I think they haven't been doing this and it's one of the reasons they're not happy with their results.)
3) I don't know how quickly I will actually be receiving reinforcements and equipment, but they have expressed the desire to grow the my currently one employee into a real department. So I'm also considering what priorities are most important to include first: testing boxes, content managers, an in-house programmer, etc.
My questions... obviously, is how this worked in your experience? I have 7 years in management and a good tech background, but I'm interested in how you've built or managed a web department or seen your department built and managed. I will basically be building a web department from the ground up. Comments and advice. Please!
-------------------------
Whatever you can do or dream you can, begin it. Boldness has genius, power and magic in it. Begin it now.
-Johann von Goethe
When Two Hearts Race... Both Win.
-Dove Chocolate Wrapper
Chroniclemaster1, Founder of
www.EarthChronicle.com
A Growing History of our Planet, by our Planet, for our Planet.
Building a .NET web department
