Hi, and welcome back. In this video we'll have a look at a weekly workflow. And it's also role based. So this is usually suitable for teams that have a focus on a single project at a time and would have more than one person in a particular role, I don't mean. So we'll have a look at the workflow. Again, we're referencing the GTD process, which is collect, process, organize, plan, and execute or do so the first thing you want to do when it comes to collection of information is in this case, we define the milestone and we give some details is quantifiable within the milestone.

Milestones can range between one month to three months, any shorter than that would not be efficient. So the goal must be significant enough that the team feels significant achievement. So if we look at the example board that we have set up, we have one card that explains the main focus and the milestone. So in this case is a prototype demo for investor. There's a short description. And most importantly, there is a breakdown that makes it measurable or quantifiable to the team.

So you can use checklists, and detail out a few high level items. And don't worry about the details yet. This is just to set direction and the focus for the team. Because after that, we're going to sit down with the team and list down tasks that are required in order first complete milestone, and then you're going to put all these tasks into the milestone list itself. So right here, we have a whole bunch of stuff being put into the milestone list. And this looks pretty long already.

But actually in reality, for most cases, this will be significantly larger in scope and much longer in terms of what kind of items they'll be in. And it can be pretty scary for a lot of team members to look at it. It shows how far you are from your milestone and also from your ultimate goal of launching your project or finishing your project. So going back to our process, once you've list down everything that is required to complete the milestone, we don't process at all organize all of this tasks, and we clean all the relevant information into it. In this Trello board will define roles or domains. So for example, 3d artists, 2d artists, programmers, it can be an action as well programming, 3d art, game design, whatever that your project requires.

And then from there you also need to assign team members to each task. So in our board, for example, we have this one right here. We have the members assigned and the labels assigned as well. So if you have a look at the kind of labels that we're going to use, we have 2d for 2d art. Since this is a game project Instructions is just as per usual, it's to indicate that the card is there to guide you when you're using this board or your own reference. It's not really a role doesn't represent a role.

And then we have 3d artists. So these artists will be doing 3d modeling, and texturing, perhaps rigging a character's building environment. And then last but not least, we have some coding tasks and it involves programming and programmers. So once you have all that laid out, you then need to sit down with the team and discuss what can be done within a week. You can choose to slightly tweak this process and make it maybe a two week kind of cycle. A lot agile Scrum teams uses that kind of duration.

It's not really set in stone. It's really up to you During this discussion that you can define due dates for each task, and of course, the sequence, which is based on the priority of which task needs to be done first, there's dependencies and there's also the level of importance or value of a task to the owner of the project. This will help you and the rest of your team members to get together and figure out which items that need to be postponed if something goes wrong, and which items maybe need to be dropped altogether if there's, you know, issues and costs and time. So when we look at our board, for example, this is when we have discussions with our teams. And let's say you drag the items that you can do within the week. quick example here.

This is also usually when you have micro discussions that happen between each sub team. For example, for 3d we have two different resources here. And they might have their own discussion amongst each other before they come back to the team on certain concerns, or certain ideas on which tools you should be using, or which kind of workflows we can improvise to further increase the chance of achieving the milestone. So it's natural that that happens. You can allow that discussion to happen even during the meeting, if that is something that you're okay with. If not, you can let them do those discussions offline.

And then Have another meeting to kind of collectively present their point of views. So throughout the week we'll have as per usual tasks that are in progress. And then once they are done as usual, we'll put them in the done list. So, at the end of the week, you'll have a weekly review on what was done. And then you can see which tasks are in the list of done. And then once you finish note, taking notes and discussing about it, you can move it to done archive.

So you're supposed to see how much you have accomplished and what is leftover and this Guess with each team members, what can you do to prevent this from happening again in the future? What was the challenges that each of us were facing as a team or as an individual perhaps a process problem perhaps as miscommunication. Perhaps as even an actual resource concern, you thought that you just needed two programmers perhaps you need three or four. So in this way, you can find ways to justify management and quickly bring it up. So what you want to focus on is how you can increase the quantity one maintaining quality as much as possible. Having said that, priority will always go to quality first.

So looking back at the board, the reason why we have this labels as role based What is important is because when you have sub teams, meaning there are a few people within your team that have similar roles, for example, in our case, we have two 3d artists. And we have two programmers. So at a glance, we can easily see what's happening with our 3d tasks. So that don't mean the 3d don't mean, you can quickly filter through and monitor what's going on. Perhaps there's a lot of tasks being piled just to that particular domain or roll, which might be a concern. You can quickly compare when you click two different roles.

And of course, you could always put it just under the team members role and filter it that way. However, because there's more than one person, you have to constantly click To get a whole idea and identify problems of a domain or a specific role, so it kind of defeats the purpose, especially when you have like three, four or five people in that same role or domain. It's much easier if you just label them like so. So whether it's using pixel mistakes, monthly based process, or this weekly role based process, there are pros and cons to both and they suit different needs and situations. So if you're working with a team, give it a try and see the difference between the two. Because until you actually use it, you won't really fully understand the pros and cons.

So have fun. delegating