Anybody has a good reference on this? Including managing teams from different backgrounds and details on documentation and artifacts that support web projects?
Anybody has a good reference on this? Including managing teams from different backgrounds and details on documentation and artifacts that support web projects?
At an agency I worked for a few years back we had a sheet called "Getting to Done" -- looked something like this:
* General Web Project Overview - Google Sheets || https://docs.google.com/spreadsheets/d/1rGSHT2kZQCahDqoQkryL...
I've got a huge file on process, with sample documents... but every time I sit down to put it all together into something that can help new hires I hit a wall around who it needs to be written for. What size of company, what focus of the site, what department of the company, what role on the team...? I think the sample "technical alignment" document we used when taking over a web property was about 15 pages worth of questions... and we still had to verify all that stuff and look at the code and various metrics.
Point being this stuff is all a learning process for everyone... best practices evolve, technology evolves, standards evolve... if you manage web projects it's more about ongoing learning rather than memorization / repetition.
I don't think we will end up getting this on to our site right now, but I would love to see it.
Edit: Spelling.
But in that wider interpretation of the title of course the management is key.
I am wondering though, aren't the most important aspects of managing web projects shared with managing other types of (technology) projects?