| Topic | Presenter | Summary | Duration | Tags | Certification Quiz | Captions |
| -------------------------------------------------------------- | ----------- | ------------------------------------------------------------------------------------------------------ | -------- | ------------------------------------------------------------------------------------ | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Helpful Information for Project Managers and Clarity Employees | Daniel Ohly | This video spells out more best practices that pertain to both the PM role and the company in general. | 48:55 | #ProjectManagement, #BestPractices, #ClarityNewHire, #NewHireOnboarding, #Onboarding | N/A | BestPractices_Training_Daniel_AutoGeneratedCaption.txt |00:00:05.040 --> 00:00:09.824 - CNN Let me go through that one real quick and this is like 00:00:09.824 --> 00:00:14.976 - it'll be don't at any point feel bad at all. Like you know, I've 00:00:14.976 --> 00:00:19.760 - been with the company for a little over a year and I still 00:00:19.760 --> 00:00:24.912 - every single day on at least twice a day on a call. Will go 00:00:24.912 --> 00:00:29.328 - OK. What does that mean? Yeah, alright cool. Don't feel bad at 00:00:29.328 --> 00:00:33.008 - all. So dnsstandsfor.net nuke, Dotnetnuke. Is this CMS we used, 00:00:33.008 --> 00:00:35.584 - you know? See Ms Yes, OK, so. 00:00:35.590 --> 00:00:40.320 - Seneca, the see Ms. A platform that we are most commonly. 00:00:41.010 --> 00:00:48.094 - Working with. Uh, there are of course we deal with 00:00:48.094 --> 00:00:52.824 - WordPress. We deal with a handful of other. CNS is. 00:00:52.824 --> 00:00:58.027 - Dotnetnuke is the one that we sort of go by natively. 00:00:58.040 --> 00:01:04.735 - And because of that, it's kind of ingrained with a lot of our 00:01:04.735 --> 00:01:08.538 - systems. Yeah, I'll tell you right off the bat. 00:01:08.540 --> 00:01:14.273 - Dot net nuke is not a very popular CMS with the larger Web 00:01:14.273 --> 00:01:18.683 - Development Society you know, of course WordPress is King there. 00:01:18.683 --> 00:01:23.534 - An rightfully so. WordPress is very robust as a lot of 00:01:23.534 --> 00:01:27.062 - resources and stuff. Likethat.net nuke is much more 00:01:27.062 --> 00:01:33.236 - secure cool, so let me just kind of go through your kind of what 00:01:33.236 --> 00:01:38.528 - I think is the most important thing is like going through your 00:01:38.528 --> 00:01:42.540 - day. So right now you're in training and such, so you'll 00:01:42.540 --> 00:01:46.812 - have a lot of calendar pieces locked in for you. Yeah, the 00:01:46.812 --> 00:01:49.304 - very first thing I would suggest doing. 00:01:51.240 --> 00:01:59.000 - Is downloading uh a the Microsoft todo app? 00:01:59.000 --> 00:02:03.570 - OK. This is an immensely important thing, and you know, I 00:02:03.570 --> 00:02:06.243 - remember in your interview you're definitely, you know, an 00:02:06.243 --> 00:02:09.213 - organized person. You've got your own things, and I'm sure 00:02:09.213 --> 00:02:13.668 - you have your own way you like to do things, so I don't want to 00:02:13.668 --> 00:02:17.826 - say this is the end all be all. But this is my personal favorite 00:02:17.826 --> 00:02:22.478 - and I think. Just the amount of integration it has with 00:02:22.478 --> 00:02:26.088 - everything. It's really useful. Uhm, you can break down your 00:02:26.088 --> 00:02:30.420 - tasks to specific things. As a PM you're just going to be 00:02:30.420 --> 00:02:34.030 - seeing a lot of things to come flying at you. 00:02:34.930 --> 00:02:40.260 - On a daily basis on an hourly basis and at times the easiest 00:02:40.260 --> 00:02:45.590 - way for them to slip to the cracks is if you don't write 00:02:45.590 --> 00:02:50.920 - them down. Yeah, so where I'm going in notes is great and it's 00:02:50.920 --> 00:02:55.840 - wonderful to have those be sort of a standard for you it. 00:02:56.460 --> 00:03:00.854 - Can at times get lossed in all the other notes. So anytime I 00:03:00.854 --> 00:03:05.924 - have a call out for an action item in a note, I will go right 00:03:05.924 --> 00:03:10.318 - over to this To Do List and just quick put it on there. 00:03:10.320 --> 00:03:13.986 - And let's take you a quick tour on teams that use teams much 00:03:13.986 --> 00:03:20.110 - yet. Just, uh, this function. I haven't really figured out. I 00:03:20.110 --> 00:03:23.296 - guess the rest of it, OK? 00:03:23.300 --> 00:03:28.630 - Um, so this is kind of your basic chat. You're going to be 00:03:28.630 --> 00:03:31.500 - spending a lot of time in teams 00:03:31.500 --> 00:03:35.875 - chatting, etc. Um now teams is our primary communication 00:03:35.875 --> 00:03:40.550 - device, so it used to be thinking about with teams as 00:03:40.550 --> 00:03:44.375 - anything that you want to get across that needs. 00:03:45.060 --> 00:03:49.878 - I think of it kind of like I say almost immediate 00:03:49.878 --> 00:03:51.192 - attention, or, uh. 00:03:52.900 --> 00:03:57.859 - Media attention or to the collaboration in real time? 00:03:57.859 --> 00:04:03.920 - Yeah, then to keep emails more for memorializing or kind of 00:04:03.920 --> 00:04:08.690 - longer form. OK, often times you'll see with a lot of what 00:04:08.690 --> 00:04:12.291 - Kristen needs for you. She will ask you to email it to someone 00:04:12.291 --> 00:04:13.399 - after you teams it. 00:04:14.030 --> 00:04:16.995 - And that is for that 00:04:16.995 --> 00:04:20.646 - memorialization. Um, now in teams. There's a lot of 00:04:20.646 --> 00:04:24.466 - different functionality you can have, and again, all of it. 00:04:25.310 --> 00:04:28.720 - Relies around a lot of kind of what you're more comfortable 00:04:28.720 --> 00:04:33.060 - with and you got to get your own feeling for things, but I just 00:04:33.060 --> 00:04:37.090 - want to point out a few things that are super important. One is 00:04:37.090 --> 00:04:40.810 - if you're going to type a message here, so I'm OK, Sam, 00:04:40.810 --> 00:04:45.650 - what's up? If I press enter, that's just going to get sent 00:04:45.650 --> 00:04:49.290 - right? Yeah, so if you did something mistakenly, you can 00:04:49.290 --> 00:04:52.930 - immediately just press the up button twice to edit it. 00:04:54.060 --> 00:04:55.930 - Like on the D pad. 00:04:56.500 --> 00:05:01.390 - You can always do shift to break it up etc, but what you can do 00:05:01.390 --> 00:05:05.628 - if you need to write a longer form thing is hit that format 00:05:05.628 --> 00:05:09.214 - button right there and then. You essentially get like a nice 00:05:09.214 --> 00:05:12.800 - little mini word processor, or you can just press enter around 00:05:12.800 --> 00:05:18.122 - you know. OK, all this other kind of fun things and all your 00:05:18.122 --> 00:05:19.810 - sort of standard although 00:05:19.810 --> 00:05:23.666 - limited uh. Formatting options 00:05:23.666 --> 00:05:26.588 - OK. Few things that are 00:05:26.588 --> 00:05:32.778 - important. You may at times need to do code snippets. Uhm, it's 00:05:32.778 --> 00:05:37.458 - possible, so that's in here. Other options in there. This 00:05:37.458 --> 00:05:42.138 - important piece here. OK, so mark is important. Control shift 00:05:42.138 --> 00:05:47.754 - I. This is a very important tool, but it must be used 00:05:47.754 --> 00:05:52.930 - sparingly. If you use it sparingly, it works. Uh, if you 00:05:52.930 --> 00:05:58.182 - use it too much, it will not work. Uh, I know that sounds 00:05:58.182 --> 00:06:02.222 - pretty standard, but I've had to go through that specifically 00:06:02.222 --> 00:06:06.800 - with people. In these three dots here you can add different apps 00:06:06.800 --> 00:06:10.914 - to different parts of your teams. You're going to get a 00:06:10.914 --> 00:06:14.654 - pretty lengthy training on, um, Azure, from a Bleep. Garrett 00:06:14.654 --> 00:06:19.142 - will be doing that with you. Anything I'll be falling in on 00:06:19.142 --> 00:06:24.378 - it, or maybe being part of it. Or maybe it's back up one with 00:06:24.378 --> 00:06:27.744 - that, Azure is our ticket or task management software. 00:06:28.450 --> 00:06:33.535 - Mostly for the Devs, as PMS do not track our time on it yet. We 00:06:33.535 --> 00:06:38.281 - may switch over to that in the future, but as of right now we 00:06:38.281 --> 00:06:39.298 - don't do that. 00:06:39.350 --> 00:06:44.758 - But it is the only way a developer will work on a task. 00:06:44.760 --> 00:06:47.020 - Gotcha. 00:06:48.260 --> 00:06:52.096 - So if there's ever like, even if it's like, Oh Man, I just need 00:06:52.096 --> 00:06:55.658 - an hour real quick or hey, can you put in here 1520 minutes 00:06:55.658 --> 00:06:57.028 - whatever? All things well and 00:06:57.028 --> 00:07:02.120 - good. You know they love to help and you know, truly. If I'm 00:07:02.120 --> 00:07:06.020 - being 100% honest they will still do it without a task. But 00:07:06.020 --> 00:07:09.920 - get in your mind and kind of work around the mindset always 00:07:09.920 --> 00:07:13.820 - just for your own best practices for your kind of history with 00:07:13.820 --> 00:07:17.395 - the company history of your future with the company it will 00:07:17.395 --> 00:07:19.995 - be to make sure that you have a 00:07:19.995 --> 00:07:22.270 - task for anything. OK. 00:07:22.920 --> 00:07:30.004 - So let's go into this. Is teams OK and then last but not least, 00:07:30.004 --> 00:07:35.570 - so this Azure DevOps you can enter specific tasks here for 00:07:35.570 --> 00:07:38.100 - reference, so let's say 54461. 00:07:38.110 --> 00:07:39.538 - Product owner, whoops. 00:07:43.290 --> 00:07:45.810 - OK, cool, here's this cat validation logic, you know, and 00:07:45.810 --> 00:07:49.086 - I send it over to you. Then the developer could click on this 00:07:49.086 --> 00:07:52.362 - and go in there. But like I said, that's kind of going a 00:07:52.362 --> 00:07:54.882 - little off the rails. My apologies, so that's teams that 00:07:54.882 --> 00:07:57.654 - it overview mostly going to be chat smaller. You can always 00:07:57.654 --> 00:07:58.662 - start a new chat. 00:07:59.710 --> 00:08:05.814 - In here, when you start chat I can add you and I can add 00:08:05.814 --> 00:08:11.046 - Kristen and then I can name this group chat. You know. PM 00:08:11.046 --> 00:08:11.918 - training overview. 00:08:15.460 --> 00:08:20.153 - So you can break people out into small little chats if you don't 00:08:20.153 --> 00:08:24.485 - want to create a whole teams channel for them. Yeah, you can 00:08:24.485 --> 00:08:28.095 - also turn that into a quick audio call or meeting 00:08:28.095 --> 00:08:30.990 - immediately. Plenty of functionality with that play 00:08:30.990 --> 00:08:35.610 - around a little bit. It's not super complicated, but it is 00:08:35.610 --> 00:08:37.290 - dense. Like any Microsoft 00:08:37.290 --> 00:08:40.990 - product. Team wise you will have your kind of broader 00:08:40.990 --> 00:08:44.290 - channels, so if you have I'm sure there's like marketing 00:08:44.290 --> 00:08:48.910 - ones that I'm not part of. But you know I have all my projects 00:08:48.910 --> 00:08:53.200 - in each of these. I have the kind of overview of the chat 00:08:53.200 --> 00:08:57.160 - thread you want to make sure that you are using your apps. 00:08:57.160 --> 00:09:01.450 - If you're talking to anybody. So if I wanted to bring you in 00:09:01.450 --> 00:09:05.080 - here, I would say at Sam or whatever here. Cool every 00:09:05.080 --> 00:09:07.390 - single team has its own file repository. 00:09:08.620 --> 00:09:14.740 - Sorry, I'm a dog bark in the background and then every single 00:09:14.740 --> 00:09:19.840 - team also has its own wiki with its specific information, 00:09:19.840 --> 00:09:21.880 - passwords, environments in the 00:09:21.880 --> 00:09:27.478 - like. Would you say the files tab kind of takes the place of, 00:09:27.478 --> 00:09:31.718 - say, the team having a drop box, correct? Yeah 100%. 00:09:31.720 --> 00:09:36.374 - Yeah, so we don't have we instead of drop box we use the 00:09:36.374 --> 00:09:41.028 - teams and with that in this time. So this is my project and 00:09:41.028 --> 00:09:45.324 - it's a mess. My apologies, but we have a thing called one 00:09:45.324 --> 00:09:49.900 - drive. One drive you can sync to your local machine an so you 00:09:49.900 --> 00:09:53.475 - will have, especially in the cloud, all the files that you'll 00:09:53.475 --> 00:09:57.375 - need to access. You able to sync between your local machine and 00:09:57.375 --> 00:10:01.900 - one drive. And teams, I keep them all organs. Hence again my 00:10:01.900 --> 00:10:05.409 - embarrassment for showing you this one. This one is a little 00:10:05.409 --> 00:10:07.323 - bit better here. Let's go here. 00:10:08.940 --> 00:10:14.148 - There we go. OK, woof, that's how it's supposed to look. OK, 00:10:14.148 --> 00:10:19.621 - so. You have your kind of basic files and then you can get them 00:10:19.621 --> 00:10:22.330 - all organized across from everything. Great question. 00:10:22.840 --> 00:10:25.530 - Do you have any other questions right off the bat? 00:10:26.090 --> 00:10:28.729 - Uhm, I guess also along with the 00:10:28.729 --> 00:10:33.112 - files question. Are there naming conventions that are 00:10:33.112 --> 00:10:37.088 - different for each Department, or is there like 00:10:37.088 --> 00:10:41.561 - a general naming convention for files? The only naming 00:10:41.561 --> 00:10:45.537 - convention for file specifically that I know of 00:10:45.537 --> 00:10:47.028 - excellent question is. 00:10:48.110 --> 00:10:50.700 - Uh. 00:10:52.380 --> 00:10:59.800 - To be the year. OK, so like if I was in a record this 00:10:59.800 --> 00:11:03.510 - would be 2020 and in the date 00:11:03.510 --> 00:11:09.754 - 18.05. Um, if its internal we use CV, I let me share the 00:11:09.754 --> 00:11:14.341 - screen. That's what I would name this file here. OK, cool 00:11:14.341 --> 00:11:18.094 - and honestly for me. Sometimes I will do something 00:11:18.094 --> 00:11:20.179 - like this just out of. 00:11:22.110 --> 00:11:28.268 - Uh, habits. So there's no spaces. 00:11:28.300 --> 00:11:32.808 - But you don't have to, um, but as long as these are here and 00:11:32.808 --> 00:11:36.672 - then I just actually don't. I think the brackets don't work. I 00:11:36.672 --> 00:11:41.180 - think you just do so I don't think they do so often. Have to 00:11:41.180 --> 00:11:45.366 - look up and see how I do it. 'cause it's now that I'm 00:11:45.366 --> 00:11:46.976 - thinking about. OK, no brackets. 00:11:47.910 --> 00:11:51.040 - Just a CBI. Clarity adventures 00:11:51.040 --> 00:11:56.612 - uhm? I don't know what the ice internal. Yeah there we go. CBI 00:11:56.612 --> 00:11:58.016 - is clearly bunches internal. 00:11:58.750 --> 00:12:05.110 - Project management overview. OK, now that's teams that are big 00:12:05.110 --> 00:12:10.834 - level, have used much outlook in the past, yes. 00:12:10.950 --> 00:12:14.262 - So you know all that, I don't need to do anything specific 00:12:14.262 --> 00:12:16.746 - there. Let me quick. Just as an overview though. 00:12:17.770 --> 00:12:21.730 - So this is my calendar for. 00:12:22.390 --> 00:12:28.520 - The week. Whenever you are booking time 'cause I think 00:12:28.520 --> 00:12:34.640 - you're gonna be helping a lot with Chris Correct? Yes OK so 00:12:34.640 --> 00:12:36.680 - here is Christmas calendar. 00:12:37.210 --> 00:12:42.410 - Chris works in a used to be a lot more complicated, and I 00:12:42.410 --> 00:12:47.210 - think that we need documentation on this is the way his calendars 00:12:47.210 --> 00:12:51.610 - outlined from what I gather right now, it's working on a 00:12:51.610 --> 00:12:54.010 - red, yellow, green, OK, so Reds 00:12:54.010 --> 00:12:56.350 - are booked. Um? 00:12:57.080 --> 00:13:02.744 - Greens are what is it? Greens are open or greens are tentative 00:13:02.744 --> 00:13:08.880 - I think, and then yellows are. He can miss with the kind of 00:13:08.880 --> 00:13:13.600 - idea of him not really having any yellows or greens. 00:13:14.960 --> 00:13:18.760 - So that would be that. 00:13:18.760 --> 00:13:23.104 - Uh, yeah. So this is, say, my week, um, everyone's got their 00:13:23.104 --> 00:13:27.810 - own kind of specific thing, but one thing that we do a lot 00:13:27.810 --> 00:13:31.068 - of here with booking is if someone has open. 00:13:32.490 --> 00:13:37.287 - You are free to book in their cool, OK, and that's really kind 00:13:37.287 --> 00:13:41.715 - of. This would be like things to work um, someones open other 00:13:41.715 --> 00:13:46.512 - than Chris and I think has some specific things so I won't speak 00:13:46.512 --> 00:13:50.940 - for her. But it started the whole PM team goes an developers 00:13:50.940 --> 00:13:55.737 - are tech side of things. If you have something you need like say 00:13:55.737 --> 00:14:00.534 - like, OK Daniel I need I need 30 minutes with Daniel on Tuesday. 00:14:00.540 --> 00:14:04.020 - Hour block feel right ahead. 00:14:04.020 --> 00:14:08.676 - Uh, and you can just pop it right in there. I strongly 00:14:08.676 --> 00:14:12.556 - suggest in these covid times to make everything you possibly 00:14:12.556 --> 00:14:14.108 - need a meeting, yeah? 00:14:14.950 --> 00:14:21.655 - It is just the best way to go. You will not. Even if you know 00:14:21.655 --> 00:14:26.572 - people are in back to back meetings all day, it's OK. 00:14:26.590 --> 00:14:30.598 - And if it's 10 minutes 11:30 that's also OK. So like for 00:14:30.598 --> 00:14:34.606 - instance, Eric weather is, did you get a chance to meet him? 00:14:34.606 --> 00:14:39.282 - I'm not. No OK, he's our back end manager and he and I work 00:14:39.282 --> 00:14:42.956 - with each other. Probably the guy work with the absolute most. 00:14:43.040 --> 00:14:47.660 - You'll see with him. what I do is I fully just block in heads 00:14:47.660 --> 00:14:51.620 - down development time forum and the like. So in the very same 00:14:51.620 --> 00:14:56.240 - way where if he's got a meeting that's cool. But I also want to 00:14:56.240 --> 00:15:00.860 - make sure with him that he has time to actually do the job job. 00:15:00.860 --> 00:15:05.480 - Yeah, you and I can be chatting all day and follow up on our 00:15:05.480 --> 00:15:08.780 - todo's in between. But for developers you really want to 00:15:08.780 --> 00:15:12.410 - imagine that it's going to take them even a small task. 00:15:13.520 --> 00:15:15.760 - Think of it in blocks of like 00:15:15.760 --> 00:15:20.779 - ours. OK, has even 30 minutes where even if it is a 30 minute 00:15:20.779 --> 00:15:24.332 - task, it's going to take some time to get the environment 00:15:24.332 --> 00:15:28.208 - setup, get their brain locked in on it and move into it. 00:15:28.210 --> 00:15:32.114 - Cool, so everything is always around an hour. 00:15:32.120 --> 00:15:35.935 - Yeah, for development yeah, OK 00:15:35.935 --> 00:15:39.885 - well. Yeah, what's there in say 00:15:39.885 --> 00:15:43.569 - like? Say we're making it. Say you have a small project for 00:15:43.569 --> 00:15:46.437 - them runs like OK. It's only four hours and they're going to 00:15:46.437 --> 00:15:49.305 - do this one thing. It will take 15 minutes. Then this other 00:15:49.305 --> 00:15:52.173 - thing. It will take him 15 minutes and this thing will take 00:15:52.173 --> 00:15:55.041 - him 20 minutes. That's totally cool, but you want to make sure 00:15:55.041 --> 00:15:58.626 - that they have at least an hour to do all of them, or that one 00:15:58.626 --> 00:16:01.494 - 15 minute thing could take 45 minutes 'cause they have to spin 00:16:01.494 --> 00:16:04.123 - up the instance and get the thing and get situated. Looking 00:16:04.123 --> 00:16:09.640 - through the code. Total Billable on a week. Your life is gonna be 00:16:09.640 --> 00:16:13.516 - different. Yeah, 'cause you're gonna be working on interior 00:16:13.516 --> 00:16:17.443 - projects. And also like I kind of was mentioning yesterday as 00:16:17.443 --> 00:16:22.441 - you're going to be doing some of this work in regards to some of 00:16:22.441 --> 00:16:25.654 - these smaller client based projects that maybe we don't 00:16:25.654 --> 00:16:29.581 - have client billable hours for but Ron and Chris have both 00:16:29.581 --> 00:16:33.865 - decided that cool we need to spend 2 hours on this project 00:16:33.865 --> 00:16:38.506 - this week in order to land the client, which is then going to 00:16:38.506 --> 00:16:39.934 - land us, you know. 00:16:40.790 --> 00:16:45.506 - A large client. So yeah, we don't have a billable per se, 00:16:45.506 --> 00:16:51.008 - but yes, I'm going to do this, so we'll find out. So the kind 00:16:51.008 --> 00:16:52.187 - of General Day. 00:16:52.760 --> 00:16:58.870 - Is different for us PM that is for developers. The 00:16:58.870 --> 00:17:02.536 - developers have a kind of broad. 00:17:02.540 --> 00:17:08.564 - Expectation to finish out their Sprint in a two week period. Now 00:17:08.564 --> 00:17:14.588 - we went over sprints at a super high level yesterday, so sprints 00:17:14.588 --> 00:17:19.608 - fall into agile methodology. I won't even attempt to presume 00:17:19.608 --> 00:17:25.130 - myself as any sort of Master and asset agile methodology. Garrett 00:17:25.130 --> 00:17:31.656 - is very good at it. He's done a lot of exterior learning about 00:17:31.656 --> 00:17:35.170 - it and he is very right brained 00:17:35.170 --> 00:17:41.390 - individual. Who kind of can latch onto um for methodology in 00:17:41.390 --> 00:17:46.502 - that way, the broad concept of it though, is. 00:17:46.770 --> 00:17:52.190 - Development work. Angels on the day. 00:17:53.050 --> 00:17:57.190 - What does that mean? Uhm, if I have three client projects, one 00:17:57.190 --> 00:18:01.330 - project might be blocked for a client decision. One part of the 00:18:01.330 --> 00:18:05.125 - other work might not be functional in the way it needs 00:18:05.125 --> 00:18:09.955 - right now, so we need to make sure that we can get it re 00:18:09.955 --> 00:18:14.095 - Architected, and the third one is good to go each day. Those 00:18:14.095 --> 00:18:17.545 - three pieces of work might change drastically. I might get 00:18:17.545 --> 00:18:21.685 - the client information back on the next day so it's green light 00:18:21.685 --> 00:18:25.135 - there. The second project is now yellow because something else, 00:18:25.135 --> 00:18:27.205 - and then the third project is, 00:18:27.205 --> 00:18:31.468 - you know. Also green so I have to prioritize basically the 00:18:31.468 --> 00:18:33.428 - agile methodology is we have. 00:18:34.480 --> 00:18:40.928 - A Sprint, which in this case is going 00:18:40.928 --> 00:18:46.570 - to be a defined amount of time. 00:18:47.120 --> 00:18:50.150 - In both, uh? 00:18:50.160 --> 00:18:53.229 - Uh, work done. 00:18:54.210 --> 00:18:55.992 - I guess it's fine amount of 00:18:55.992 --> 00:18:59.645 - work. Done in a specific amount of time. 00:19:02.930 --> 00:19:10.514 - So for instance, what we have in both pods is we have 00:19:10.514 --> 00:19:13.042 - a two week sprints. 00:19:14.270 --> 00:19:17.390 - With Seven hour 00:19:17.390 --> 00:19:24.856 - days. So does that mean end of the 00:19:24.856 --> 00:19:31.160 - day each developer has a 70 hour Sprint? 00:19:32.090 --> 00:19:37.942 - Now what does that mean to us as PMS, right? But that means the 00:19:37.942 --> 00:19:43.794 - US is PMS is that we have 70 hours of estimated work that we 00:19:43.794 --> 00:19:48.392 - can possibly give to a developer. So if I have, let's 00:19:48.392 --> 00:19:50.482 - just make this really clean. 00:19:51.600 --> 00:19:59.270 - 10 a 5 hour tasks and 10 two hour tasks. 00:19:59.770 --> 00:20:05.920 - They've got that for my developer. 00:20:06.230 --> 00:20:10.110 - That's going to be their whole Sprint, right? Because that's 00:20:10.110 --> 00:20:14.378 - the whole 70 hours, 7 hours a day for two weeks. 00:20:14.450 --> 00:20:18.366 - What does Sprint is? Well actually, what and this is where 00:20:18.366 --> 00:20:21.926 - the methodology and stuff? If you are a strong methodology 00:20:21.926 --> 00:20:25.486 - learner, there's ample writing and research about this, and you 00:20:25.486 --> 00:20:29.758 - know you can find out pretty much anything you want in that. 00:20:29.758 --> 00:20:33.318 - If you have that sort of mindset. My suggestion with 00:20:33.318 --> 00:20:38.658 - diving deep an agile is that we do not do it to spec, and that's 00:20:38.658 --> 00:20:42.574 - actually kind of part of agile methodology is every company. It 00:20:42.574 --> 00:20:45.778 - will do it slightly different to what they need. 00:20:46.010 --> 00:20:48.010 - Since we have client facing 00:20:48.010 --> 00:20:53.000 - projects. We never have all the information we need. Almost, you 00:20:53.000 --> 00:20:57.466 - know, there's always going to be some aspect to something that 00:20:57.466 --> 00:20:59.090 - will need some clearance. 00:20:59.930 --> 00:21:03.635 - Uh, you know, we might have a huge chunk of the client project 00:21:03.635 --> 00:21:06.770 - outlined and Architected and all the way through, but there might 00:21:06.770 --> 00:21:09.905 - be something like some field mapping that we just don't know 00:21:09.905 --> 00:21:13.325 - until we start coding it. And then when we find out what's 00:21:13.325 --> 00:21:17.030 - wrong with it then we can go back to the client, bring it 00:21:17.030 --> 00:21:18.170 - back up to him.00:21:19.750 --> 00:21:23.910 - So the bottom line is that is that a Sprint is essentially a. 00:21:24.730 --> 00:21:29.361 - A agreement between the PM's and the developers about work, what 00:21:29.361 --> 00:21:35.255 - work they're going to do in a two week section so that we as 00:21:35.255 --> 00:21:39.758 - PMS can. Properly set expectation to our clients about 00:21:39.758 --> 00:21:42.242 - what work is being done then. 00:21:43.770 --> 00:21:47.235 - What will free spirit this for a 00:21:47.235 --> 00:21:53.760 - second? OK, so with That being said, where this changes every. 00:21:55.070 --> 00:21:59.618 - Midpoint of a Sprint. You should be doing what's called a backlog 00:21:59.618 --> 00:22:05.982 - refinement. OK, now what this means is we have theoretically 00:22:05.982 --> 00:22:13.278 - we should have enough works in the backlog at any given time. 00:22:13.410 --> 00:22:17.016 - That if one task gets blocked. 00:22:17.540 --> 00:22:21.554 - And we can accurately and succinctly ascertain that it 00:22:21.554 --> 00:22:24.676 - won't be blocked by the end of 00:22:24.676 --> 00:22:28.944 - the Sprint. We can move it out so we can get work in there. 00:22:29.630 --> 00:22:34.740 - To keep them busy, 'cause how that works is so say I've got my 00:22:34.740 --> 00:22:36.930 - developer with these 70 hours of 00:22:36.930 --> 00:22:43.792 - tasks. Let's say there's do 7 hours of work a day, and let's 00:22:43.792 --> 00:22:47.038 - say half of these five are 00:22:47.038 --> 00:22:50.320 - blocks are. Blocked right. 00:22:56.240 --> 00:22:58.668 - And these are completed. 00:22:59.560 --> 00:23:06.050 - Let's say. Four of these two R Block. 00:23:07.450 --> 00:23:11.498 - Are completed as well. 00:23:12.800 --> 00:23:15.278 - And then these sex to our blocks. 00:23:17.460 --> 00:23:23.060 - Are, uh? Let's say will just sit there, blocked it will keep it 00:23:23.060 --> 00:23:25.786 - really simple. Right now, say I've heard developers at this 00:23:25.786 --> 00:23:28.306 - point and we haven't done any backlog refinement. They come 00:23:28.306 --> 00:23:29.818 - into work and don't know what 00:23:29.818 --> 00:23:36.360 - they're gonna do. So like for instance, my wife is a front end 00:23:36.360 --> 00:23:39.995 - developer. And so it's been a really interesting thing this 00:23:39.995 --> 00:23:41.720 - whole week she's been blocked. 00:23:41.720 --> 00:23:46.855 - Yeah, and like last last week too. So she has been, you know, 00:23:46.855 --> 00:23:50.805 - going through and doing some like code cleanup and different 00:23:50.805 --> 00:23:55.150 - like revisions to thing like really kind of minor work as 00:23:55.150 --> 00:23:59.890 - well as just sort of like doing some coding challenges and sort 00:23:59.890 --> 00:24:03.885 - of like. Learning about some new technologies and stuff for the 00:24:03.885 --> 00:24:08.500 - stack that they work on, but as far as her manager is concerned, 00:24:08.500 --> 00:24:11.695 - she's not doing anything right 'cause the productivity is 00:24:11.695 --> 00:24:15.955 - taking a nosedive so every day her manager has to go handle 00:24:15.955 --> 00:24:20.215 - their PM and be like Yo dude, where's my work app developer? 00:24:20.215 --> 00:24:23.410 - Who's you know? Basically sitting on their hands? So 00:24:23.410 --> 00:24:28.380 - that's kind of the way we break it into either 2 weeks or one 00:24:28.380 --> 00:24:29.445 - weeks is essentially. 00:24:30.030 --> 00:24:31.990 - Going back to your day as a PM. 00:24:32.630 --> 00:24:36.434 - Kind of think about it as in a really high level you're 00:24:36.434 --> 00:24:38.019 - gathering works for the next 00:24:38.019 --> 00:24:43.244 - Sprint. You are, um, refining work in the Sprint unblocking 00:24:43.244 --> 00:24:48.596 - sodas. They're kind of like the really high level now. What does 00:24:48.596 --> 00:24:52.610 - that look like, right? Like unblocking tickets in the 00:24:52.610 --> 00:24:56.624 - Sprint, these are client meetings. Yeah, you know again, 00:24:56.624 --> 00:25:00.638 - for the next Sprint, reviewing code and developer meetings 00:25:00.638 --> 00:25:04.652 - refine worker in the sprints, listening to developer feedback, 00:25:04.652 --> 00:25:10.004 - you know you're going to work on those three things every single 00:25:10.004 --> 00:25:14.988 - day. And the reason why we do it in the sprints. So it's not just 00:25:14.988 --> 00:25:18.530 - like a scramble everyday. Yeah, you're always trying to get at 00:25:18.530 --> 00:25:22.394 - least two weeks out, and when you're really lucky you can get 00:25:22.394 --> 00:25:26.580 - like 3 sprints out. Or you know two Sprint Part 2 full sprints 00:25:26.580 --> 00:25:31.088 - out where you can like cool. I got this print done, I guess it 00:25:31.088 --> 00:25:35.596 - expert done and I know what else is going to go on. 'cause you're 00:25:35.596 --> 00:25:38.816 - basically just continually adding wood to the pile for the 00:25:38.816 --> 00:25:40.104 - developers. Gotcha, OK, that 00:25:40.104 --> 00:25:44.196 - makes sense. Now, what does that look like, actually, right? 00:25:44.196 --> 00:25:48.494 - That's kind of the big question, yeah, so let me just go over my 00:25:48.494 --> 00:25:53.099 - day with you and it's just going to give you an idea of what your 00:25:53.099 --> 00:25:56.783 - day could look like. So I generally even when we were in 00:25:56.783 --> 00:25:58.932 - the office, try to get in around 00:25:58.932 --> 00:26:02.830 - eight 8:30. Um, so I do 8 to 00:26:02.830 --> 00:26:05.180 - 9. Heads down work. 00:26:05.730 --> 00:26:07.089 - I check emails. 00:26:07.810 --> 00:26:10.336 - Look at my To Do List. 00:26:12.290 --> 00:26:14.992 - 9 two 9:30 I have a meeting 00:26:14.992 --> 00:26:20.960 - every day. 9:30 to 10:00 I have a. 00:26:21.600 --> 00:26:24.240 - Kind of more heads down work. 00:26:25.250 --> 00:26:28.575 - 10 to 10:30 I have stand up. 00:26:29.820 --> 00:26:36.008 - Have you gone over stand up at all yet? 'cause I know that it's 00:26:36.008 --> 00:26:40.428 - going to be expected of you, right? Chris mentioned having 00:26:40.428 --> 00:26:45.750 - standups. Can't detail OK, cool? Let's talk about that. Stand up, 00:26:45.750 --> 00:26:49.159 - stand out as part of the agile 00:26:49.159 --> 00:26:52.826 - methodology. Stand ups in traditional agile methodology we 00:26:52.826 --> 00:26:56.984 - SPM's would not be involved in them. They are generally lead. 00:26:56.984 --> 00:27:00.386 - Will an actually agile standup comes from scrum methodology 00:27:00.386 --> 00:27:05.300 - which is like a subset of agile method like this is where I'm 00:27:05.300 --> 00:27:10.214 - talking about. Like if you want to get into it, yeah you can 00:27:10.214 --> 00:27:14.750 - learn so much and there's so much valid stuff that we can 00:27:14.750 --> 00:27:20.042 - kind of taken break and put into our model and we've done a lot 00:27:20.042 --> 00:27:21.176 - of that already. 00:27:21.210 --> 00:27:26.384 - And you will learn a lot and it's valid. But just keep in 00:27:26.384 --> 00:27:30.762 - mind that it's not the way it's a methodology, meaning it's 00:27:30.762 --> 00:27:34.344 - something to kind of. Look at and move towards. 00:27:34.430 --> 00:27:36.966 - So Stand Up is a daily check in. 00:27:39.310 --> 00:27:41.308 - Uh, this is generally a 15 00:27:41.308 --> 00:27:46.534 - minute meeting. Roughly 15 minutes. It's called a stand up 00:27:46.534 --> 00:27:51.847 - because you should not be sitting during it if you're in 00:27:51.847 --> 00:27:56.677 - person. Of course. Right now we're in odd circumstances and 00:27:56.677 --> 00:28:01.507 - what you should be doing is going over three things. 00:28:02.150 --> 00:28:04.529 - What you did? 00:28:04.530 --> 00:28:05.770 - What you're gonna do? 00:28:07.550 --> 00:28:15.195 - Any blockers? Now what you did? That's 00:28:15.195 --> 00:28:19.087 - what you did yesterday. 00:28:19.680 --> 00:28:23.667 - USAPM should be watching this because whether you developers 00:28:23.667 --> 00:28:27.654 - or in this case you'll have developers and marketing 00:28:27.654 --> 00:28:32.970 - friends, whether they know it or not, you might have a better 00:28:32.970 --> 00:28:36.957 - idea of what time lines are, what's going on. 00:28:36.980 --> 00:28:41.732 - It's going to happen. It might happen right away, but it will 00:28:41.732 --> 00:28:44.900 - happen where you'll have a developer who, uhm? 00:28:45.400 --> 00:28:48.334 - You know might have two projects. They're working on. 00:28:48.334 --> 00:28:52.572 - One of them is a really fun like, you know, kind of more 00:28:52.572 --> 00:28:56.810 - Greenfield thing where they can spend a lot of time and then the 00:28:56.810 --> 00:29:01.048 - other one they have to do is just like a maintenance on a 00:29:01.048 --> 00:29:02.352 - front end web site. 00:29:02.390 --> 00:29:05.786 - There's gotta change all these pictures and it takes 6 hours to 00:29:05.786 --> 00:29:07.767 - do it. But man, what a bummer 00:29:07.767 --> 00:29:11.470 - yeah. And you know it's just human nature is not nothing 00:29:11.470 --> 00:29:14.794 - against them. It's nothing? Uh, not they don't want to work or 00:29:14.794 --> 00:29:17.841 - that they have anything in general. It's just that we have 00:29:17.841 --> 00:29:19.780 - to keep on track. That's part of 00:29:19.780 --> 00:29:24.070 - our job. Um, what you're gonna do. Same thing with that you 00:29:24.070 --> 00:29:28.186 - know if you look at them and they say, Oh Man, I'm gonna work 00:29:28.186 --> 00:29:31.420 - on source market today. I'm going to be getting that done 00:29:31.420 --> 00:29:35.242 - and you go Oh cool, I've got a phone call source mark tomorrow. 00:29:35.770 --> 00:29:39.618 - I need to make sure to check back in with that developer by 00:29:39.618 --> 00:29:43.762 - the end of the day you know, so these kind of small things where 00:29:43.762 --> 00:29:47.314 - you can just kind of basically plan your day around what your 00:29:47.314 --> 00:29:50.274 - developers are doing again to help hold them accountable to 00:29:50.274 --> 00:29:52.346 - the. What did you do from the 00:29:52.346 --> 00:29:55.662 - day before? So if your developers said I'm gonna work 00:29:55.662 --> 00:29:59.218 - on source market today and you make a little note of it and the 00:29:59.218 --> 00:30:02.774 - next day you go around to check on him and he didn't do anything 00:30:02.774 --> 00:30:05.822 - on service mark, you can say Yo dude, what the heck? Yeah, 00:30:05.822 --> 00:30:08.870 - where's my source? Mark work. I got my meeting with them today. 00:30:08.870 --> 00:30:10.902 - You said you were going to do it 00:30:10.902 --> 00:30:14.573 - yesterday. And again, it's just that kind of bog, standard 00:30:14.573 --> 00:30:17.876 - accountability. I there's very rarely ever issues with this, 00:30:17.876 --> 00:30:21.913 - but it happens. It's human nature. No one is doing anything 00:30:21.913 --> 00:30:25.216 - wrong or mean spirited, just the way it is. 00:30:25.270 --> 00:30:29.183 - OK, does that kind of and then, uh, any blockers. So this is 00:30:29.183 --> 00:30:32.795 - kind of the place where you're going to be listening to the 00:30:32.795 --> 00:30:38.775 - most. If this is not brought up and you don't have a plan for 00:30:38.775 --> 00:30:40.080 - it, you should. 00:30:40.090 --> 00:30:45.984 - So if they say, uh, I blocked on source mark right now, I don't 00:30:45.984 --> 00:30:47.247 - have client credentials. 00:30:47.940 --> 00:30:51.671 - You should at that point either say Oh, you know what I saw 00:30:51.671 --> 00:30:53.393 - that. Note that you put up 00:30:53.393 --> 00:30:58.416 - yesterday. Um? And I already reached out to Melissa there in 00:30:58.416 --> 00:31:01.540 - teams. Check him out. Let me know if they don't work. 00:31:02.280 --> 00:31:06.336 - Hello on the other side of things say Oh OK, well you know 00:31:06.336 --> 00:31:10.392 - can you please make sure you post that in teams or can you 00:31:10.392 --> 00:31:13.512 - make sure that that's posted somewhere else? This is the 00:31:13.512 --> 00:31:16.944 - first I'm hearing about it. I'll get with Melissa right now. 00:31:18.180 --> 00:31:21.897 - OK, again it kind of builds your day, yeah? 00:31:23.100 --> 00:31:25.737 - Is sometimes it you know, sometimes you're developer were 00:31:25.737 --> 00:31:29.546 - working for the night and you know you Clock out at 6 or 00:31:29.546 --> 00:31:33.355 - whatever and they find out that this isn't a habitat. 9 is your 00:31:33.355 --> 00:31:34.820 - first your hearing, but that's 00:31:34.820 --> 00:31:37.881 - OK. Maybe it's like they just forgot to write down with a 00:31:37.881 --> 00:31:40.893 - blocker, which is not OK on their side of things. But again, 00:31:40.893 --> 00:31:44.156 - it's going to happen. It's not the end of the world, we just 00:31:44.156 --> 00:31:46.917 - gotta keep moving and keep pressing. But those are just the 00:31:46.917 --> 00:31:48.172 - three things you're going to 00:31:48.172 --> 00:31:55.614 - think about. Oh OK, that happens every day. They will. 00:31:55.620 --> 00:32:00.324 - And the kind of the last thing that I need to work on. Very, 00:32:00.324 --> 00:32:02.340 - uh, to refine quite a bit. 00:32:02.850 --> 00:32:06.725 - But, uh. Is, uh, how's your burn 00:32:06.725 --> 00:32:11.050 - down? So burn down is the accomplished work through the 00:32:11.050 --> 00:32:16.230 - Sprint. This is going to make a lot of sense once you see the 00:32:16.230 --> 00:32:19.930 - Azure side of things with Garrick's. Yeah, go too deep 00:32:19.930 --> 00:32:24.370 - into it right now, but remember our friends with his 20 hour 00:32:24.370 --> 00:32:28.440 - tasks and stuff like that. Yeah, if he's not accomplishing those, 00:32:28.440 --> 00:32:32.880 - maybe 1 task ran long so his burned down doesn't look good 00:32:32.880 --> 00:32:37.690 - 'cause he was scheduled for 70 hours of work and he might have. 00:32:37.770 --> 00:32:42.478 - Done. 20 hours of work in the first week or whatever it is, 00:32:42.478 --> 00:32:46.365 - but one task went long and it pushed his other work back. His 00:32:46.365 --> 00:32:50.252 - burn downs looking bad so we might need to push some of those 00:32:50.252 --> 00:32:54.438 - tasks into the next week. Or you might just need to pull a little 00:32:54.438 --> 00:32:55.933 - bit of a longer day. 00:32:57.070 --> 00:33:02.501 - OK. Cool is it also can cut the other way right? So if they 00:33:02.501 --> 00:33:07.079 - knockout all 70 hours of there a lot of time, yeah, and it's the 00:33:07.079 --> 00:33:11.330 - end of the week and you know they might get a short day. 00:33:12.030 --> 00:33:17.255 - Yeah, it rarely happens. There's always work to do, but it's 00:33:17.255 --> 00:33:22.955 - possible. At least 'cause we do work on a billable model versus 00:33:22.955 --> 00:33:24.855 - a hours allotted model. 00:33:24.860 --> 00:33:28.230 - OK. So back to the kind of the schedule. 00:33:30.050 --> 00:33:33.950 - Uhm, and then pretty much 10:30. 00:33:34.650 --> 00:33:37.110 - Test around six. 00:33:37.720 --> 00:33:42.940 - Changes on a daily basis, um, throughout that time I will have 00:33:42.940 --> 00:33:47.335 - different meetings. I will have different in a internal 00:33:47.335 --> 00:33:50.800 - meetings, uh, specific developer check ends. You know, I 00:33:50.800 --> 00:33:55.805 - generally like to take like a. I generally work around at my desk 00:33:55.805 --> 00:34:00.425 - or sorry, eat lunch at my desk, but you're also of course 00:34:00.425 --> 00:34:03.505 - welcome. That's not a requirement. Totally access to 00:34:03.505 --> 00:34:08.125 - me. It's like OK, just jewel. I'm reading this thing or yeah. 00:34:08.440 --> 00:34:13.000 - I'd rather my standpoint, things that generally I'd rather get 00:34:13.000 --> 00:34:15.736 - done with work sooner and then 00:34:15.736 --> 00:34:20.260 - fully unplugged. I agree. OK, so that's kind of a standard day. 00:34:20.260 --> 00:34:22.336 - That's the general thing that it 00:34:22.336 --> 00:34:27.313 - looks like. So when we're talking about meetings with 00:34:27.313 --> 00:34:31.804 - clients and kind of time management in general, my 00:34:31.804 --> 00:34:35.297 - strong, strong, strong, strong suggestion, specifically with 00:34:35.297 --> 00:34:41.285 - the amount of work that your schedule is kind of being broken 00:34:41.285 --> 00:34:47.772 - out into, is that you put blocks on your calendar, or some of 00:34:47.772 --> 00:34:51.764 - these more firm requirements, like the marketing collateral 00:34:51.764 --> 00:34:54.259 - and the different admin time. 00:34:54.270 --> 00:34:57.266 - And backlog refinement and backlog creation. Everything 00:34:57.266 --> 00:35:00.262 - like that. Put the time on your 00:35:00.262 --> 00:35:04.900 - calendar. It might not seem like a thing right now, and you're 00:35:04.900 --> 00:35:08.310 - kind of Halcyon days. You're starting time here. I got all 00:35:08.310 --> 00:35:12.340 - the time in the world you wanna meet now. Let's meet now, you 00:35:12.340 --> 00:35:16.200 - know. I'll wait till people are done talking to me and that will 00:35:16.200 --> 00:35:20.035 - work for an hour until the next time someone wants to talk to 00:35:20.035 --> 00:35:24.516 - me. I was there too, but it's gonna get to the point where you 00:35:24.516 --> 00:35:27.736 - will just eventually get meeting upon meeting upon meeting and 00:35:27.736 --> 00:35:31.922 - then you'll end up working till like 8 when in reality some of 00:35:31.922 --> 00:35:35.786 - those meetings could have been pushed to the next day or two 00:35:35.786 --> 00:35:37.396 - days from then or whatever. 00:35:37.396 --> 00:35:44.674 - Yeah. So if you have work you need to do be the cop of 00:35:44.674 --> 00:35:46.706 - your own outlook, OK? 00:35:46.720 --> 00:35:52.480 - And like I do that for my fate, but my my my Eric developer. I 00:35:52.480 --> 00:35:56.320 - talked about this a little bit yesterday where I essentially 00:35:56.320 --> 00:36:00.544 - set his calendar up with working blocks. Oh yeah, yeah, you're 00:36:00.544 --> 00:36:01.696 - telling me that. 00:36:02.560 --> 00:36:04.462 - Uh, OK. Do you have any 00:36:04.462 --> 00:36:06.980 - questions about anything? Um? 00:36:07.550 --> 00:36:13.066 - No, that was that was great. I mean, I knew a little bit about 00:36:13.066 --> 00:36:17.006 - agile and scrum methodology, but that really helped alot. Um, 00:36:17.006 --> 00:36:22.522 - defining more and how it how it is going to be applied to, uh, 00:36:22.522 --> 00:36:24.492 - what I do here, OK? 00:36:25.150 --> 00:36:30.023 - Cool, let's go over Microsoft Todo's real quick. We got about 00:36:30.023 --> 00:36:35.782 - 10 minutes and I don't Garrett is a very punctual person so I 00:36:35.782 --> 00:36:40.212 - want to make sure you're on time for his thing. 00:36:40.240 --> 00:36:44.692 - OK, so I actually do not. Let's do Org chart real quick 'cause I 00:36:44.692 --> 00:36:49.462 - can type it out and send it to you. And again with that kind of 00:36:49.462 --> 00:36:53.278 - deliverables, I think that would be pretty cool. So this is not 00:36:53.278 --> 00:36:55.504 - going to be an Org chart in 00:36:55.504 --> 00:37:02.845 - terms of managerial. I will let that fall to a upper management 00:37:02.845 --> 00:37:06.536 - there. So that's pretty straightforward. You have your 00:37:06.536 --> 00:37:13.046 - marketing team. And that's Jeremy, Uh, with Ron kind of 00:37:13.046 --> 00:37:15.374 - the head of it. 00:37:16.280 --> 00:37:18.248 - Ron, Jeremy and Riley 00:37:18.920 --> 00:37:21.260 - You have pod A. 00:37:21.930 --> 00:37:24.610 - Your PM's on Pas DE. 00:37:25.260 --> 00:37:28.288 - Are Ben and Garrett. 00:37:29.170 --> 00:37:33.370 - Your front Enders football whoops, this does not look good. 00:37:33.370 --> 00:37:38.830 - It's gonna be Chris Black. OK, and you've heard I I won't say 00:37:38.830 --> 00:37:43.030 - at the same time just how many Christmas there are. 00:37:43.060 --> 00:37:47.480 - You should have heard the mall, I'm sure, uh, OK. 00:37:48.220 --> 00:37:51.164 - There's just a lot. It's no joke, OK? 00:37:52.320 --> 00:37:55.470 - And one of the things when I was like, Oh, you could put two each 00:37:55.470 --> 00:37:56.730 - Chris Black on a different, uh? 00:37:57.380 --> 00:38:00.284 - Pod Nope. OK, so have Chris 00:38:00.284 --> 00:38:04.496 - Black. For your, this is for your information. Chris Black, 00:38:04.496 --> 00:38:06.152 - the manager, has tattoos. 00:38:06.970 --> 00:38:11.470 - OK, and that Chris Black, then not manager does not 00:38:11.470 --> 00:38:15.520 - have tattoos or maybe not visible tattoos that Chris 00:38:15.520 --> 00:38:17.320 - Black the manager has. 00:38:19.150 --> 00:38:23.320 - It's like a big neck tattoo and stuff like that. 00:38:23.320 --> 00:38:24.630 - With Heather 00:38:25.340 --> 00:38:32.414 - Bar. Uh, another part, and I think that's it 00:38:32.414 --> 00:38:39.470 - for front end for Patte and your back end we have Brendan 00:38:39.470 --> 00:38:42.240 - Flarity. Sterling Runyon 00:38:42.970 --> 00:38:45.328 - And Taylor Duncan. 00:38:45.920 --> 00:38:53.534 - Cool. Uhm, I put Chris Black here as a 00:38:53.534 --> 00:38:57.650 - DNN Wiz, 'cause DNN is a lot of this marketing pages. You're 00:38:57.650 --> 00:39:01.080 - probably working with Chris Black and Patrick Lang the most 00:39:01.080 --> 00:39:03.138 - for those kind of things, cool. 00:39:03.890 --> 00:39:06.378 - I'm so pod be. 00:39:07.750 --> 00:39:10.878 - Yes, you have me. 00:39:11.580 --> 00:39:13.780 - And you have clients. 00:39:14.370 --> 00:39:19.640 - I am the PM manager. 00:39:22.040 --> 00:39:28.990 - Uh, for front end we have Jesse web and Patrick 00:39:28.990 --> 00:39:31.770 - weighing for back end. 00:39:32.910 --> 00:39:36.538 - We have Igor Ivanovic. 00:39:37.720 --> 00:39:42.250 - And Eric. My God, am I forgetting Eric's last name 00:39:42.250 --> 00:39:43.660 - right now? What is wrong with 00:39:43.660 --> 00:39:46.950 - Maine? Holy smokes. 00:39:46.950 --> 00:39:50.830 - Broke Eric Oh my goodness. What's going on? 00:39:52.320 --> 00:39:57.122 - I talked this man really 8 hours a day and Alice is recorded. Oh 00:39:57.122 --> 00:40:01.238 - my God, Eric weather's OK, Uhm, and he's the back end manager. 00:40:03.560 --> 00:40:09.725 - OK, so back in manager is an architect to. 00:40:11.220 --> 00:40:18.626 - And then you have the kind of stuff team and that is going to 00:40:18.626 --> 00:40:20.213 - be Kyle Sanford. 00:40:21.360 --> 00:40:23.850 - The business analyst. 00:40:24.730 --> 00:40:28.564 - We have, um, 00:40:28.564 --> 00:40:34.231 - Christian Papic Pop each actually is how you pronounce 00:40:34.231 --> 00:40:38.114 - his last name. Serbian, Serbian. What is it? I think it's 00:40:38.114 --> 00:40:39.879 - serving. Actually he's our QA 00:40:39.879 --> 00:40:47.366 - engineer. And then James Gray, who is a self architect. 00:40:47.600 --> 00:40:49.130 - Senior developer. 00:40:50.570 --> 00:40:56.230 - Um? 00:40:57.440 --> 00:41:03.550 - Cool, now for these things and I'll send it over to you. 'cause 00:41:03.550 --> 00:41:09.660 - you got 5 minutes before that thing up again. This is a non. 00:41:10.300 --> 00:41:13.358 - I don't know where the lines go to everyone, I'm sure. 00:41:13.940 --> 00:41:18.570 - The specific my team specifically are all the PM is 00:41:18.570 --> 00:41:23.663 - just the four, including myself and then there is the senior 00:41:23.663 --> 00:41:27.830 - management with Kevin and Kristen and Chris. And then 00:41:27.830 --> 00:41:32.923 - there's Phil and ran in their own kind of circle there. 00:41:32.930 --> 00:41:38.078 - But like I said, that'll that'll leave for them to. This is just 00:41:38.078 --> 00:41:41.246 - functional. Keep it completely functionless. Actually, I'll 00:41:41.246 --> 00:41:45.107 - even leave the marketing off 'cause I'll let them speak to 00:41:45.107 --> 00:41:48.760 - that. So just this here, uhm. 00:41:49.900 --> 00:41:54.619 - Will be kind of your broad strokes if we are doing. 00:41:55.240 --> 00:42:01.040 - Uh. Any kind of I'm gonna put architects on any of these other 00:42:01.040 --> 00:42:08.135 - ones have here. The architect architecture. So for any and 00:42:08.135 --> 00:42:12.060 - he can help for estimates. 00:42:13.040 --> 00:42:15.585 - Uhm, 00:42:15.585 --> 00:42:21.398 - OK. So when projects are coming in, 00:42:21.398 --> 00:42:25.528 - these are the three guys essentially who were gonna wanna 00:42:25.528 --> 00:42:30.071 - be bringing into the loop on anything that needs estimates or 00:42:30.071 --> 00:42:34.614 - we need to talk about how it's going to be made. 00:42:34.650 --> 00:42:36.020 - Yeah. 00:42:37.070 --> 00:42:42.982 - If. The three of them can't make it. Jesse Web is a front end. 00:42:43.740 --> 00:42:48.887 - Possibility. If it's a DNN project, Chris Black can help 00:42:48.887 --> 00:42:50.299 - out on that too. 00:42:51.140 --> 00:42:53.660 - OK, now. 00:42:54.670 --> 00:42:58.300 - Once those kind of things happen, if it's going to be 00:42:58.300 --> 00:43:01.270 - brought into like under the larger PM discussion, that's 00:43:01.270 --> 00:43:05.230 - when I kind of come in. But generally I'm pretty hands off 00:43:05.230 --> 00:43:08.530 - and we just kind of do organizing and kind of 00:43:08.530 --> 00:43:09.850 - coordination for those guys, 00:43:09.850 --> 00:43:14.321 - yeah? But those will be your kind of big guys to talk to, but 00:43:14.321 --> 00:43:18.759 - I think past that you'll want to be checking with the PM's of the 00:43:18.759 --> 00:43:22.880 - developers on that team so we can make sure we get ours and 00:43:22.880 --> 00:43:26.684 - their Sprint. And how does that. Ours is. The Sprint thing makes 00:43:26.684 --> 00:43:30.171 - sense, I'm sure you've heard it like 12 times another. Probably 00:43:30.171 --> 00:43:33.658 - like clicking a little bit. Yeah, it definitely makes a lot 00:43:33.658 --> 00:43:37.779 - more sense and how broken out. So it's like you know, if Ron 00:43:37.779 --> 00:43:41.266 - says hey, I need this quick little proof of concept thing. 00:43:41.320 --> 00:43:44.830 - To be done on a website I need front end or should I 00:43:44.830 --> 00:43:46.180 - take about 6 hours, um? 00:43:47.300 --> 00:43:51.655 - You know you can say it again project, and if it's like Yep, 00:43:51.655 --> 00:43:56.010 - is that cool. I think Chris Black can do that. Let me reach 00:43:56.010 --> 00:44:00.030 - out to better Garrett to get some time into Sprint for Chris 00:44:00.030 --> 00:44:04.050 - Black and they might straight up tell ya hey Sam, no dice. 00:44:04.550 --> 00:44:08.774 - Not happening, but I can plan for next Sprint. Cool sounds 00:44:08.774 --> 00:44:12.614 - good. Here's my biggest advice for anything like this. Whenever 00:44:12.614 --> 00:44:16.838 - you have 'cause it's going to happen again and this is 00:44:16.838 --> 00:44:20.678 - something that will happen with a little more frequency, you're 00:44:20.678 --> 00:44:21.830 - going to get. 00:44:22.640 --> 00:44:25.480 - What sound like conflicting 00:44:25.480 --> 00:44:31.450 - information OK? And it's going to be frustrating and it is one 00:44:31.450 --> 00:44:36.130 - of the more frustrating aspects of being a PM is dealing with 00:44:36.130 --> 00:44:40.420 - conflicting information. Yeah, and the best way to do deal with 00:44:40.420 --> 00:44:45.100 - this. And as far as I'm concerned, the only way to deal 00:44:45.100 --> 00:44:48.610 - with this is get all the information about the 00:44:48.610 --> 00:44:51.620 - conflicting information. That percent that's right so. 00:44:52.400 --> 00:44:55.590 - Get you know. Essentially think of yourself is almost like a 00:44:55.590 --> 00:44:59.370 - judge. But you aren't gonna be you. Essentially you are a 00:44:59.370 --> 00:45:02.615 - judge, right? So you're going to get the information from both 00:45:02.615 --> 00:45:06.745 - people, Ron says. I need this done by the end of the week and 00:45:06.745 --> 00:45:10.875 - it's only four hours. So you go to bed and Garrett, he guys. I 00:45:10.875 --> 00:45:15.300 - need 4 hours from KB that by the end of this week and Ben says, 00:45:15.300 --> 00:45:17.365 - well, I got he's booked. I have 00:45:17.365 --> 00:45:22.208 - a deadline. OK, I understand. Yeah, take those two things 00:45:22.208 --> 00:45:25.496 - and then you bring them to Senior Management. 00:45:26.530 --> 00:45:30.166 - And they say OK, both. These other things are 00:45:30.166 --> 00:45:32.186 - heard. What can we do? 00:45:33.410 --> 00:45:36.534 - Gotcha, and that is the strongest piece of advice I can 00:45:36.534 --> 00:45:40.226 - give you, even if you're you know if you're dead set on it. 00:45:40.226 --> 00:45:42.782 - Like for instance, this literally happened to me today 00:45:42.782 --> 00:45:47.042 - and as a manager I like to think I have a decent amount of cloud, 00:45:47.042 --> 00:45:50.734 - but I was straight up just like, OK, cool. Here's the two pieces 00:45:50.734 --> 00:45:54.142 - I got. Yeah, it seems to happen. I need this to happen. 00:45:54.910 --> 00:45:55.860 - Chris, what do you think? 00:45:57.060 --> 00:46:00.876 - And then when he says what's up, you go great. That's the 00:46:00.876 --> 00:46:04.374 - marching orders. They still ask for your input, you know, and 00:46:04.374 --> 00:46:08.190 - he'll want to make sure that it is a holistic idea, but. 00:46:08.820 --> 00:46:12.460 - Yeah, OK, I'll send this over to you there. And hey, if you have 00:46:12.460 --> 00:46:15.580 - more questions please feel free. I'm free later in the day too, 00:46:15.580 --> 00:46:19.740 - so if you have to kind of follow up. Like I said, I don't want to 00:46:19.740 --> 00:46:22.600 - keep you from Garrett. Do you have any followups right now 00:46:22.600 --> 00:46:26.318 - that I can? Send out to you. 00:46:28.420 --> 00:46:33.124 - If you have like, I guess if you have a recommendation on how to 00:46:33.124 --> 00:46:36.820 - organize my to-do ZAP, I like start adding some pass into 00:46:36.820 --> 00:46:41.188 - there and I created some like main sections for it. But if you 00:46:41.188 --> 00:46:45.220 - have any recommendations for how you use it, that would be really 00:46:45.220 --> 00:46:49.588 - great. Yeah, so like I was saying before I do the teams or 00:46:49.588 --> 00:46:53.620 - the different sections in it. Yeah, and then other than that I 00:46:53.620 --> 00:46:57.652 - do with the I don't have any plan stuff right now. 'cause 00:46:57.652 --> 00:46:59.332 - basically all my things here. 00:46:59.380 --> 00:47:03.670 - Every day I don't have anything specific other than I just. 00:47:04.330 --> 00:47:08.432 - Do try to break them down. So if I know some things in a 00:47:08.432 --> 00:47:12.241 - management side, I don't have to worry about it on every day, but 00:47:12.241 --> 00:47:16.050 - it's something that I have to get done or something I want to 00:47:16.050 --> 00:47:19.566 - bring up for a specific thing. So similarly I would just create 00:47:19.566 --> 00:47:21.617 - a new list for every project you 00:47:21.617 --> 00:47:25.158 - have OK? That makes sense. 00:47:25.160 --> 00:47:27.422 - Marketing operations, project management, and like 00:47:27.422 --> 00:47:31.192 - miscellaneous but that at that works? That sounds. That's a 00:47:31.192 --> 00:47:36.470 - good start. And then I think you can. I don't know if it doesn't 00:47:36.470 --> 00:47:42.125 - really let you do sub list. I mean you can do sub list on a 00:47:42.125 --> 00:47:47.026 - item. OK so I can add steps to a task so call Kevin. 00:47:48.300 --> 00:47:50.289 - You know, uh? 00:47:51.350 --> 00:47:55.354 - Get access whatever so you can do this, and I've done this to 00:47:55.354 --> 00:47:59.443 - some success. Cool, OK, uhm where you can just kind of 00:47:59.443 --> 00:48:00.751 - market different parts or 00:48:00.751 --> 00:48:05.689 - completed and man. OK, now it's all done up so you can do that 00:48:05.689 --> 00:48:09.706 - in a very specific way and then also like I said with the 00:48:09.706 --> 00:48:13.529 - different. Breakouts for different clients. I strong is 00:48:13.529 --> 00:48:18.053 - just meant for each client 'cause as you do it for each 00:48:18.053 --> 00:48:22.200 - client you can. Essentially your meetings will be a breeze, an 00:48:22.200 --> 00:48:25.593 - writing agenda. Sarah Breeze, Cool, Yeah, it sounds good. 00:48:26.130 --> 00:48:30.282 - Doing it for a plot, each client that I'm coming and honestly, 00:48:30.282 --> 00:48:34.780 - you could even further and **** you gotta get going but I would 00:48:34.780 --> 00:48:38.586 - have it for each marketing team members. If you're running that 00:48:38.586 --> 00:48:39.970 - team like that, OK? 00:48:40.600 --> 00:48:43.504 - So, So what you're talking to Riley, you say, Riley, I got 00:48:43.504 --> 00:48:46.650 - these six things that need doing with you. How are you on them? 00:48:46.650 --> 00:48:48.344 - Yeah, add notes to them in the 00:48:48.344 --> 00:48:51.730 - like. OK, no uhm. 00:48:52.310 --> 00:48:54.459 - What's going on with it, you know?