Localization Academy

How To Use Nifty As Localization Project Manager

•      Was this content helpful?

Was this content helpful?

Is Nifty any good for localization project managers? 

Welcome to another episode in this series, where every month we’ll check out a new project management platform and see how viable it is for localization. All online software will be either free or with a free trial, so you can try it on your own.

In this video, I’ll show you how to use Nifty for project management. We’ll plan a simple localization project and see how you can monitor all your projects in one place ✅

Andrej Zito

If you’re wondering how to use Nifty for your localization projects, in this video, I’m going to give you a very quick tutorial and show you how I set it up. I’m going to show you how to utilize the milestones, how to set up the structure of tasks and subtasks, and a simple way how you can monitor all your projects in one place. So let’s get right into Nifty.

So this is how we start. First thing that we’re going to do is we’re going to create our first simple project A. So on the left panel, as you can see here, we have toggled the projects, and I’m going to click here to create a new project. And then Project A, I’m going to make public, the default task view will be a List. And we’re going to start with a blank project. In order for us to show a nice hierarchy on a timeline view, we’re going to utilize the roadmap, which actually requires you to set up milestones. Now, we’re going to use the let’s say the top level tasks of our project as milestones. So that we can use this view and drill down into subtasks. So this will not be the typical milestone that you’re used to from added on bigger projects, like something special that needs to happen in the project.

Yes, anyway. So I’m going to start creating the milestones, which are our top level tasks for this project. And we’re going to add some translation. And for this one, we have 30,000 words. So we can start, let’s say today, and we’ll have people work during the holidays. And they should finish on January 6th. And create. I’m going to add another one, this will be review. Already hours it starts right after and no help needed. I think the review will start on January 9th, and and on 13th. And then we’ll do the final delivery, which will be on the 13th. And there we go. So this is our first… basically that’s the structure of the project. Like I mentioned, it’s a very simple one transition review, and then we deliver to the client.

Now next thing that we want to do is we want to create the sub tasks. Because we added the main tasks as milestones, we’re going to be adding the sub tasks, sub tasks as just tasks. So under translation milestone, here, on the right side of the milestone, I’m going to add tasks or sub tasks for each language. In this one we do German, French, Japanese, and Korean. As you can see, the due date is automatically set to January 6th, based on the due date of the milestone. And the reason why we set it up this way is that now we can kind of toggle here on the roadmap on the timeline view. And here we can see the individual tasks. Now the reason why they’re appearing at the end is because we didn’t set a start date for the tasks. You can fix that by simply dragging it here, or we’re going to then utilize the task list view. For now I’m going to continue adding sub tasks for view, Korean, right. And then we have the delivery, which is for all languages.

So going back to the tasks, here, we have everything but now it’s grouped by status. If we group it by the milestone, it should correspond to what we have on the roadmap. And here we have a bunch of fields, some of them we don’t need. So I’m going to edit the columns that we have here. status, we can keep it assignees. We can keep it as well, we have a due date, but we’re missing the start date. I’m going to drag it to the top, we don’t need any tax, and milestone, we can show that because that’s important information for us. Even though we are also showing the milestone here in this way because it’s already grouped by milestones.

Next thing I’m going to do is I’m going to add the start date. So we said that we start today, and here in Nifty you can also pick the date right away. problem here is a little bit with navigation. Like it’s very mouse based. I cannot use arrow keys, and I certainly cannot copy the start date and paste it into the other values into the other tasks. which is a little bit annoying 12pm, select. Alright, so now that we have our start date and due date, we go back to the roadmap and open things up, it should show that the sub tasks were the task for each language ours starting way earlier, they’re basically starting the same way as the milestone, think, right? That’s what we want.

I believe this is it for now, for our simple Project A, if you want to add more statuses, for example, right now, here, we only have the to do status, you’d have to change the grouping by status. And then you can add more statuses, you can also change the colors of the statuses. But if we are keeping it very simple, as something that needs to be done, and that is done, you are completely okay, just keeping these default checkboxes for each task. And then as your project goes, let’s say, I don’t know we complete the European languages, you tick it off page, also, highlight here on your roadmap, which I would say is your main viewed you want to use to monitor where you are. And that gets very nice, it kind of like fills up the milestone, the progression of the milestone. And then of course, as you add more languages, it’s going to be up even more. So now we should have. So now we should have 75% Complete, right. So that is our simple project a now let me create quickly another Project B, where I’m going to add a bunch of other tasks to make it a little bit more complicated, but I’m going to keep the same structure as here.

Okay, so this is my project B that I just created in a couple of extra tasks. We have Pre-processing, we have MTPE, DTP, QA, DTP 2, QA 2 and Delivery. So this project is for roughly two and a half weeks, and for MTPE, in and for QA. Just to illustrate, I also added the sub tasks for each different language. Now the reason why we created Project B is so that I can show you as we usually used to do is an overview of all your projects. And for that you don’t need to create anything special, all you have to do is just go to overview, which as you can see right here shows you your both projects that you have created. So here we have project A and you can also nicely drill down here into the individual tasks. And I can do the same thing for Project B.

So that’s it my friends. That was my quick tutorial for Nifty and how I would have used it for localization projects. If you have any comments or suggestions feel free to use the comments section below this video. And if by any chance this video gave you some value if you want to continue. If you want to see me continue the series, give this video a thumbs up and consider subscribing to our Localization Academy channel. And thank you again for your time and watching this video and I’ll see you in the next one. Bye bye!

We’re always creating new localization content

Make sure you don’t miss anything. Join 3877 other professionals on our mailing list and be the first to get our upcoming newsletter. 

If you enjoyed that, you’ll love these…

Word Count Analysis 🎮

Watch this video and learn what is Word Count Analysis in localization using Cities: Skylines 🎮 Get ready to level up your knowledge of the localization industry!


Why hello there!

Enjoy 10% off

on your first course when you join our mailing list.

* All information collected will be used in accordance with our privacy policy. You may unsubscribe at any time.