3 ms·

Missing: "managing web projects". Anybody has a good reference on this? Including managing teams from different backgrounds and details on documentation and ar

by ssn 10y ago

Missing: "managing 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?

ilaksh 10y ago
I think the title of the article (strike that, I mean the section heading above the title) is a bit misleading because it implies a wider context than was intended. 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?
kinlan 10y ago
Heh, I actually wanted to include something like this in the original site. The very first version of the site we had a massive IA planning doc and guide, style-guides, mocks, prototypes, user-stories and user-profiles (the type of developers we wanted to write for). I've still got all the information. 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.
- mhoad 10y ago
  Any chance at all of getting that out "unofficially"? I would love to see that and I think a lot of us would get a huge amount of value from that.
  - kinlan 10y ago
    Let me try somethings...
dbg31415 10y ago
So much of this would depend on the budget, and size of the project. What works great for an enterprise site... is total overkill for a small project. Likewise... it's seldom one person, or even one team, that does everything end-to-end... so like... maybe your role is only to get to UAT, and their team will take over for security screening, performance testing, hardening, launch... Do we include what dev, design, devops, marketing, sales, legal teams all care about? I'm sure that's not even a complete list of teams... 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/1rGSHT2kZQCahDqoQkryLJ1b3rEq_uVLEX2Qe10RCxB8/edit 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.

by ssn 10y ago

Missing: "managing 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?

ilaksh 10y ago

I think the title of the article (strike that, I mean the section heading above the title) is a bit misleading because it implies a wider context than was intended. 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?

kinlan 10y ago

Heh, I actually wanted to include something like this in the original site. The very first version of the site we had a massive IA planning doc and guide, style-guides, mocks, prototypes, user-stories and user-profiles (the type of developers we wanted to write for). I've still got all the information. 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.

mhoad 10y ago
Any chance at all of getting that out "unofficially"? I would love to see that and I think a lot of us would get a huge amount of value from that.
- kinlan 10y ago
  Let me try somethings...

dbg31415 10y ago

So much of this would depend on the budget, and size of the project. What works great for an enterprise site... is total overkill for a small project. Likewise... it's seldom one person, or even one team, that does everything end-to-end... so like... maybe your role is only to get to UAT, and their team will take over for security screening, performance testing, hardening, launch... Do we include what dev, design, devops, marketing, sales, legal teams all care about? I'm sure that's not even a complete list of teams... 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/1rGSHT2kZQCahDqoQkryLJ1b3rEq_uVLEX2Qe10RCxB8/edit 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.