SLA NWRC session notes, cont. (end of October 6)
Understanding Web Project Management: Build a Better Relationship with IT – Christina Zeller, VPL’s InfoAction
Christina Zeller is well-qualified to talk about working with IT on web projects, and her presentation was full of useful (if not overwhelming!) tips. The main points I took from the presentation:
- Planning takes the most time but really is crucial. It turns out that the Gantt chart, that pesky organization tool we were forced to use in college, is widely used and pretty much can’t be lived without during large projects
- If you have a year-long project, it’s much easier to think about it in terms of weeks
- There’s all sorts of PM & IT terminology you should be familiar with: work package, work breakdown structure, requirements document, resources (what a revolting term for “people”!!), environment, work, duration (fixed or variable), dependencies, deliverables
- Where you delegate or let others make decisions, reinforce that you trust them to choose the appropriate solution
- Status meetings should occur once a week, or more often if needed
On a familiar note, according to Christina, the project kick-off is essential, and there must be snacks. Same with the launch – treat it like the celebration it is!
The Human Factor of CM – Rahel Anne Bailie, Strategy A Business Consulting
Bailie began the presentation with a series of great quotes. This was my favourite: Content management is 50% change management, 40% process control, 10% technology (Howard McQueen).
The top reason CM fails? Resistance in corporate culture. If everyone is on board, they’ll find a way to make it work even if the CMS is crappy. Often we’re too busy worrying about process management that we forget about the human performance side. This is troublesome when you consider that 10-15% of the population just don’t “do” change. At all.
If the CMS project is a second or third attempt, people will be gun shy. That is why having a communication plan (and then sticking to it) is crucial. During the training phase, create a “wish list” from complaints, and air technical issues openly.