A continuation of last week's look at what's wanted from a Digital Project Manager's Role.
Here's an amalgamation of several wish lists from job descriptions for a Senior post. The promising thing is that there is no question of what a Project Manager is now, whereas there used to be - and the role wasn't described in this way or by job title. Now there's career progression from Junior, Digital Project Manager to Senior Project Manager. Overall we're positive about this trend. But the recruiters seem to ask for the earth in some cases!
Senior Digital Project Manager
Experience: 5 years minimum of web and social media sites. Prince 2 or equivalent, and/or Agile certification
Salary: £30-60k (non London, but UK based) up to £80k London
Role: managing projects from initiation to launch, managing cross-functional teams, clients, and non-technical personnel, get projects out on time, to brief and to budget. Manage new and potential clients, advising on usability/user planning, accessibility, making business cases, online marketing and branding, delivering successful and profitable projects across technologies, extracting and clarifying requirements from clients, assess risks, manage stakeholders.
Knowledge needed: User-focused website design, user experience and user psychology, Digital project planning, Project management tools and techniques, Team/studio management, Relationship building and account management, Managing suppliers, Open-source frameworks, Technical limitations and constraints, Search engine marketing, Social media marketing
Competence in: Taking briefs and listening to what the client is looking to achieve, Writing proposals with recommendations, have an eye for detail but also be creative, producing an outline of the site/app's proposed functionality with costs, Information architecture planning and mapping, Producing wireframes, Facilitating and contributing to discussion around a project's creative treatment, Writing project specifications, Producing realistic project timelines and then managing the project in accordance with that timescale, Setting and controlling project budgets, Managing change requests effectively, presenting outcomes of campaigns with recommendations, quality assurance, managing conflict, have strong presentation and negotiating skills.
Technical abilities: (Some jobs state several front-end and back end skill sets, internet security, and content management systems among others.)
Thursday 31 May 2012
Friday 25 May 2012
Digital Project Managers: who wants what? (Part A)
Despite the economic vagaries, the job market for Digital Project Managers appears strong. So what skill-sets are companies looking for? Do you measure up? Below we’ve amalgamated what's been asked for under a Digital Project Manager role and next week we look at the Senior role. Quite an eye-opener!
The most whacky but apposite description about a skill was "to be able to talk the technical" or "talk coding and creative". We interpret those as managing cross-functionally. Then we found "produce a clear paper-trail across the project development", we interpret that as use project management tools. And to "get" creative processes (dude?), we interpret as to understand the mind-set of your creatives – the diversity of the cross-functional team? What about the "can-do" approach which also asks for strong control of clients? What about "some kind of coding background" but to manage creatives?
Recruiters expect understanding and experience across all the digital platforms and media types (site builds, micro sites, social media, game builds, ecommerce, web tv, imedia, apps, campaigns, etc.). The job types were sometimes specific to industry sector (publishing, finance, luxury products, retail, medical, fashion, telecoms, broadcasting, etc.), but the expectations of the role were pretty similar.
This is only scratching the surface of the variety and type of role available. The good news is that the wider needs of Project Management for digital are being identified better now than a few years ago. There is more emphasis on managing the stakeholders/clients, as well as the developers; there is recognition of making a business case that suits the clients' business needs; there is more recognition of how complex it is to manage cross-functional teams. Digital sector specific experience becomes crucial. The mix of platforms is growing and the knowledge associated with their development through experience is key. Happy job hunting.
Next week we’ll be looking at the Senior Digital Project Manager’s Role.
Digital Project Manager
Experience: 2-5 years
Salary: £25-35k (non London, but UK based) up to £80k London
Role: managing projects and programmes from concept to delivery, confidently managing internal development teams to deliver briefs, managing internal and external clients/stakeholders, planning digital campaigns, managing various delivery platform development, producing time, cost and scope documentation, managing and allocating resources, manage schedule, budgets, assets, monitor and anticipate risks like scope creep with timely solutions to mitigate them, link objectives of the client to present and future needs, exceed expectations for delivery and performance,
Knowledge needed: understanding of the technical landscape, strategic marketing ideas translated into digital solutions, enthusiasm for technologies and digital communication, brief designers, developers, Art Directors, Information Architects,
Competence in: experience of using appropriate project management tools including Prince 2, Agile, Scrum Master, Basecamp, Merlin, Sifter, MS Project etc., SEO techniques and metrics, content production/copywriting for web, high-volume, quick-turnaround projects, working alongside Account Teams, managing up to 20 projects a day, excellent project management skills, excellent administrative skills, managing change control in projects, meeting budgets.
The most whacky but apposite description about a skill was "to be able to talk the technical" or "talk coding and creative". We interpret those as managing cross-functionally. Then we found "produce a clear paper-trail across the project development", we interpret that as use project management tools. And to "get" creative processes (dude?), we interpret as to understand the mind-set of your creatives – the diversity of the cross-functional team? What about the "can-do" approach which also asks for strong control of clients? What about "some kind of coding background" but to manage creatives?
Recruiters expect understanding and experience across all the digital platforms and media types (site builds, micro sites, social media, game builds, ecommerce, web tv, imedia, apps, campaigns, etc.). The job types were sometimes specific to industry sector (publishing, finance, luxury products, retail, medical, fashion, telecoms, broadcasting, etc.), but the expectations of the role were pretty similar.
This is only scratching the surface of the variety and type of role available. The good news is that the wider needs of Project Management for digital are being identified better now than a few years ago. There is more emphasis on managing the stakeholders/clients, as well as the developers; there is recognition of making a business case that suits the clients' business needs; there is more recognition of how complex it is to manage cross-functional teams. Digital sector specific experience becomes crucial. The mix of platforms is growing and the knowledge associated with their development through experience is key. Happy job hunting.
Next week we’ll be looking at the Senior Digital Project Manager’s Role.
Digital Project Manager
Experience: 2-5 years
Salary: £25-35k (non London, but UK based) up to £80k London
Role: managing projects and programmes from concept to delivery, confidently managing internal development teams to deliver briefs, managing internal and external clients/stakeholders, planning digital campaigns, managing various delivery platform development, producing time, cost and scope documentation, managing and allocating resources, manage schedule, budgets, assets, monitor and anticipate risks like scope creep with timely solutions to mitigate them, link objectives of the client to present and future needs, exceed expectations for delivery and performance,
Knowledge needed: understanding of the technical landscape, strategic marketing ideas translated into digital solutions, enthusiasm for technologies and digital communication, brief designers, developers, Art Directors, Information Architects,
Competence in: experience of using appropriate project management tools including Prince 2, Agile, Scrum Master, Basecamp, Merlin, Sifter, MS Project etc., SEO techniques and metrics, content production/copywriting for web, high-volume, quick-turnaround projects, working alongside Account Teams, managing up to 20 projects a day, excellent project management skills, excellent administrative skills, managing change control in projects, meeting budgets.
Sunday 13 May 2012
Those elusive perfect project management tools
Yes, where are they?
The range and number of project management (PM) tools has increased significantly and some work across mobile too. But there still seems to be the basic problem of the tool not exactly suiting how you work. People complain that they have to tailor the way they work to suit the tool. For example, Microsoft Project came out of the large, very long, and detailed software development projects prior to the Internet. It has myriad features; so many that it is hard to get started because you have to understand its logic and relate it to what you are doing.
Then the communication flow tools, like Basecamp, proved popular because they allowed people to stay in contact and pass information around efficiently whilst keeping a record of the communication. Some say it grew out of the Lotus 123 type of corporate communication tracking but was web based and therefore more versatile.
Now we have tools that concentrate on the costing and automated billing processes. These are time trackers that allocate a rate according to the person or role, and as you enter the time they have spent on a task, the program calculates exactly how much the effort has cost. These are popular with ad agencies because they tend to suit the way they have worked with clients in the past for traditional media, and now interactive media is added into the equation, they want it to operate in the same way.
Project management tools have an inherent logic in the way they are structured. They mirror a human approach, a philosophy, despite trying to offer a systematic process to make projects flow efficiently for all involved, and to fairly cost the work done as the project unfolds. In the end, the biggest clash is still between the visual creatives (web designers, graphics) and the way they work, and the programmers who are creative but within their own systematic logic inherent in the symbolic, abstract computer languages they have to work with. The wordsmiths (content creators, marketers) also embody their own approaches in the words used.
We get back to that thorny problem of coordinating across cross-functional teams to produce any interactive application on any platform. The mix of people reflects the mix of philosophies that drive their expertise and so that's why one PM tool never seems to fit all. Does that leave us any closer to a solution? Well, people can adapt. They can appreciate or learn to appreciate how a system can help them despite causing them some teething problems. Tools are getting more versatile. People are getting more used to having to use some form of PM tool.
After trawling the web trying to find people in our industry raving about "the perfect pm tool", I only found the one: but that's refreshing. See Phil Matthews and Trello, my Perfect Project Management App.
Anyone else have a PM tool to rave about?
The range and number of project management (PM) tools has increased significantly and some work across mobile too. But there still seems to be the basic problem of the tool not exactly suiting how you work. People complain that they have to tailor the way they work to suit the tool. For example, Microsoft Project came out of the large, very long, and detailed software development projects prior to the Internet. It has myriad features; so many that it is hard to get started because you have to understand its logic and relate it to what you are doing.
Then the communication flow tools, like Basecamp, proved popular because they allowed people to stay in contact and pass information around efficiently whilst keeping a record of the communication. Some say it grew out of the Lotus 123 type of corporate communication tracking but was web based and therefore more versatile.
Now we have tools that concentrate on the costing and automated billing processes. These are time trackers that allocate a rate according to the person or role, and as you enter the time they have spent on a task, the program calculates exactly how much the effort has cost. These are popular with ad agencies because they tend to suit the way they have worked with clients in the past for traditional media, and now interactive media is added into the equation, they want it to operate in the same way.
Project management tools have an inherent logic in the way they are structured. They mirror a human approach, a philosophy, despite trying to offer a systematic process to make projects flow efficiently for all involved, and to fairly cost the work done as the project unfolds. In the end, the biggest clash is still between the visual creatives (web designers, graphics) and the way they work, and the programmers who are creative but within their own systematic logic inherent in the symbolic, abstract computer languages they have to work with. The wordsmiths (content creators, marketers) also embody their own approaches in the words used.
We get back to that thorny problem of coordinating across cross-functional teams to produce any interactive application on any platform. The mix of people reflects the mix of philosophies that drive their expertise and so that's why one PM tool never seems to fit all. Does that leave us any closer to a solution? Well, people can adapt. They can appreciate or learn to appreciate how a system can help them despite causing them some teething problems. Tools are getting more versatile. People are getting more used to having to use some form of PM tool.
After trawling the web trying to find people in our industry raving about "the perfect pm tool", I only found the one: but that's refreshing. See Phil Matthews and Trello, my Perfect Project Management App.
Anyone else have a PM tool to rave about?
Friday 4 May 2012
Databases: relational instances or NoSQL
Rather like that man who would occasionally emerge from a shed on the Fast Show, these days I am mostly working on databases.
So far they have been relational databases, based on a plan devised in 1970 by a man named Edgar Codd who worked for IBM in California. In this model data is split into tables and they are interlinked by using keys (usually numbers). A table is basically a flat file, like a spreadsheet and has a number of records (eg people) with fields (such as their name). If you want to record the companies they work for you could have a field in the people table with the company name but, more likely, you will have another table of companies which contains the information about each company. The relational bit is that there would be a reference number (an ID) for each company and it is this ID that would be included, in a 'companies' field, in the people table in order to link the person to the company. In this way several people can work for the same company. Incidentally, the process of separating out data so that repeated stuff (like the company data) is in another table and is cross-referenced is known as normalisation.
This model starts to fall down, by becoming more complex, if the relationships become multi-connected. Let me give you an example.
You have a database of CDs. A CD has, as what we call its attributes, such things as a title, an artist, a release data and a list of songs. Two things are problematic here: artist names can vary subtly between albums and each album has a different number of songs on it. Because of this you can't have a simple relationship between the record for an artist (in the artist table) and the CD or between a song (in the song table) and the CD. This is because the artist has more than one name and a song may be on more than one CD.
To deal with this you can use instances of the links between the tables and all these instances go into a separate table. For the artist there is one instance for one name by which the act is known (eg Prince) and one for another (the Artist Formerly Known as Prince) and the album links to whichever instance is appropriate (and gets the artist's name from it) and the instance then links to the main artist information. Similarly with songs, although usually ... but not always ... the song's name remains the same for each instance.
Doing this adds versatility to the database but it increases the number of tables and can also reduce performance.
Such complexity is one of the reasons that the 21st Century approach to databases is widening beyond the relational model (scalability is an even more crucial one) and although many of the big players on the web, such as Facebook and Twitter, use such a database there are others. Google's Big Table being perhaps the best known. These collectively seem to be known as NoSQL (because they don't use the SQL query language), although if you read the discussion page associated with the previous Wikipedia link, it does seem to be a controversial topic. I should add that Wikipedia's Talk pages are always worth checking.
I don't think relational databases are quite dead yet, and not all of us have Google's voracious appetite for data ... but it's clearly something to keep an eye on. What do you think?
So far they have been relational databases, based on a plan devised in 1970 by a man named Edgar Codd who worked for IBM in California. In this model data is split into tables and they are interlinked by using keys (usually numbers). A table is basically a flat file, like a spreadsheet and has a number of records (eg people) with fields (such as their name). If you want to record the companies they work for you could have a field in the people table with the company name but, more likely, you will have another table of companies which contains the information about each company. The relational bit is that there would be a reference number (an ID) for each company and it is this ID that would be included, in a 'companies' field, in the people table in order to link the person to the company. In this way several people can work for the same company. Incidentally, the process of separating out data so that repeated stuff (like the company data) is in another table and is cross-referenced is known as normalisation.
This model starts to fall down, by becoming more complex, if the relationships become multi-connected. Let me give you an example.
You have a database of CDs. A CD has, as what we call its attributes, such things as a title, an artist, a release data and a list of songs. Two things are problematic here: artist names can vary subtly between albums and each album has a different number of songs on it. Because of this you can't have a simple relationship between the record for an artist (in the artist table) and the CD or between a song (in the song table) and the CD. This is because the artist has more than one name and a song may be on more than one CD.
To deal with this you can use instances of the links between the tables and all these instances go into a separate table. For the artist there is one instance for one name by which the act is known (eg Prince) and one for another (the Artist Formerly Known as Prince) and the album links to whichever instance is appropriate (and gets the artist's name from it) and the instance then links to the main artist information. Similarly with songs, although usually ... but not always ... the song's name remains the same for each instance.
Doing this adds versatility to the database but it increases the number of tables and can also reduce performance.
Such complexity is one of the reasons that the 21st Century approach to databases is widening beyond the relational model (scalability is an even more crucial one) and although many of the big players on the web, such as Facebook and Twitter, use such a database there are others. Google's Big Table being perhaps the best known. These collectively seem to be known as NoSQL (because they don't use the SQL query language), although if you read the discussion page associated with the previous Wikipedia link, it does seem to be a controversial topic. I should add that Wikipedia's Talk pages are always worth checking.
I don't think relational databases are quite dead yet, and not all of us have Google's voracious appetite for data ... but it's clearly something to keep an eye on. What do you think?
Subscribe to:
Posts (Atom)
Posts
