Localization Project Management Office is a Trello board (referred to “board” hereafter) that contains the workflow of a localization project (referred to “project” hereafter) and templates that can be used in future projects. This board is built by me and my group members in the Localization Project Management class.
Board Overview
In the board, we use lists to represent each stage in the project cycle. Typically, a project contains 11 stages, but our group decided to add one more at the very end. The 12 stages are:
- Submission
- Project Specifications
- Quote
- Preparation
- Translation
- Editing
- Proofreading
- Post Layout Review
- Final Verification
- Delivery
- Post Production
- Client Feedback
Stage
Submission
This is the very first stage of the whole project cycle. Everything related to the project should be set up correctly so that the project can get off to a flying start. For example, a Client Page form will be filled out to document any important information regarding the client. The files submitted from the client will be properly placed in our network. At the end of the stage, a checklist will be run to make sure nothing is left out in this stage.
Project Specifications
In this stage, a Specification form will be used to establish the scope of the project. All of the requirements, agreements, resources provided, and clarifications should be included in this form. It will be a go-to document if something comes up later in the project cycle. We also have a checklist in place for project managers to quickly gauge the outcomes of this stage.
Quote
After the establishment of the scope of the project, a thorough analysis on the files from the client will be conducted. Combined with their experience, project managers can show the client how much time and money the project will cost. The quote checklist will be used to revisit every step in this stage.
Preparation
In this stage, as project managers, we need to prepare as much as we can to facilitate the processes down the road. The work includes: finding competent translators, preparing project specific translation kits, writing detailed work instructions to make sure everyone knows what the client’s expectations are and so forth. In light of the amount of work in this stage, having a checklist at the end of the process is extremely important.
Translation, Editing, and Proofreading
These three stages are the most related to the quality of the product. During these periods, translators, editors, and proofreaders are working with bi-text files. Each person will review the work from the previous one and give feedback. The files will not be passed down until the person finds no mistakes. While translators and editors are people who can read the target language, that is not necessarily a requirement for proofreaders since not understanding the target language can allow proofreaders to find mistakes that translators and editors cannot. The checklists in these three stages are divided into “before,” “during,” and “after” to encompass every task that should be finished before the project moves onto the next stage.
Post Layout Review & Final Verification
As opposed to the previous stages, people in these two stages work with files in the target language only. This allows them to see the products through target customers’ eyes . Usually, the person carrying out Post Layout Review understands the target language in order to mimic the real situation of a customer getting the product. Finally, a project manager, who may or may not understand the target language, will conduct a final check before delivery.
Delivery, Post Production, and Client Feedback
In the final stages, deliverables are delivered to the client. Any lessons learned during the processes will be documented for future improvement. We will also follow up with clients to ask for feedback so that the future cooperation will be smooth.
What I Learned and Gained
- Not only were we developing the overall workflow of the project, we were also doing a mock project at the same time. At the end of the semester, I had a clear picture of the whole project life cycle and the roles of different stakeholders.
- Documenting everything along the way is really helpful for future projects. For example, when we had to create a quote for our imaginary client, we didn’t have any experience to rely on. However, when going through the whole project, we tracked our time with TopTracker and got the time we spent on every task. That statistics can help us the next time we create a quote.
- We produced a lot of templates checklists while completing our mock project. Although they are far from perfect, I will have something to start with when I start working.
This course is really valuable. It’s like I just spent a whole semester doing an internship.