---Presenter: Garrett ReistSubject: Communication Best PracticesDetails: How to communicate well with your team of developers; expectation setting; how to work through issuesDuration: 01:06:22---00:00:05.110 --> 00:00:06.628 - The main, uh? 00:00:07.600 --> 00:00:11.560 - Information in talking with developers that I feel is it 00:00:11.560 --> 00:00:14.728 - really important, especially with some of these senior 00:00:14.728 --> 00:00:19.480 - members of our staff of our stuff, is making sure that you 00:00:19.480 --> 00:00:23.836 - have a method to your escalation method of escalation method of. 00:00:25.010 --> 00:00:28.690 - Um? 00:00:29.750 --> 00:00:33.806 - The first thing I'd say if you like just going through and 00:00:33.806 --> 00:00:37.186 - finding the hey, there's an issue. There's this problem that 00:00:37.186 --> 00:00:41.242 - I'm noticing an either in the environment or in testing or in 00:00:41.242 --> 00:00:43.946 - the IW that I need to know if 00:00:43.946 --> 00:00:47.680 - this works. The best idea is to usually reach out into the 00:00:47.680 --> 00:00:51.390 - team's channel. That allows for tracking of the history of the 00:00:51.390 --> 00:00:54.750 - record. So if management's like Oh well, you know, I know that 00:00:54.750 --> 00:00:57.830 - was an issue. Whatever happened to that? They can go back 00:00:57.830 --> 00:01:01.750 - through the teams channel in and see kind of what the red was on 00:01:01.750 --> 00:01:04.830 - that. If someone dropped the ball or if there was something 00:01:04.830 --> 00:01:08.750 - going on, or if it wasn't ever resolved and we just need to get 00:01:08.750 --> 00:01:12.390 - the resolution that allows them to be able to go back and see 00:01:12.390 --> 00:01:13.510 - what's going on there. 00:01:13.550 --> 00:01:19.183 - I. And I if the discussion seems to 00:01:19.183 --> 00:01:23.371 - struggle, and I've seen this a lot lately on many projects that 00:01:23.371 --> 00:01:27.210 - we just started throwing stuff in team, saying, hey, this seems 00:01:27.210 --> 00:01:31.747 - to be fixed and then developers will go back and forth and back 00:01:31.747 --> 00:01:36.284 - and forth and back and forth and it will be days later and 00:01:36.284 --> 00:01:37.680 - there's still no resolution. 00:01:37.710 --> 00:01:40.914 - You see that struggle and I helped out a little bit on 00:01:40.914 --> 00:01:44.118 - people on few projects with this and even some of mine. But 00:01:44.118 --> 00:01:47.589 - having people go back and forth and say Oh yeah should be done 00:01:47.589 --> 00:01:51.327 - and then, well, I didn't see it. OK well, let me look into it 00:01:51.327 --> 00:01:53.997 - some more and then you don't hear back from it. 00:01:54.940 --> 00:01:59.716 - Waste a lot of time and usually you can get the developers 00:01:59.716 --> 00:02:01.706 - together in a quick sync. 00:02:02.550 --> 00:02:06.430 - Or use 00:02:06.430 --> 00:02:14.345 - pair programming. So this is the important part of 00:02:14.345 --> 00:02:15.860 - this is that. 00:02:16.660 --> 00:02:19.454 - We've all seen this in teams where developers will be going 00:02:19.454 --> 00:02:22.502 - back and forth and trying to decide what's the best way to 00:02:22.502 --> 00:02:25.296 - go. I'm having trouble with my local. I need help downloading 00:02:25.296 --> 00:02:28.344 - it. Let's write this. I will try this. Will try that. Just 00:02:28.344 --> 00:02:31.138 - being just going and say Hey, this doesn't seem to be 00:02:31.138 --> 00:02:33.678 - working. Let's get together and look at the same screen 00:02:33.678 --> 00:02:35.202 - and try and get this solved. 00:02:36.220 --> 00:02:39.900 - It's the quickest and easiest way to get things done. 00:02:39.900 --> 00:02:43.992 - It's not the most convenient, but that is not the point of 00:02:43.992 --> 00:02:46.379 - solving an issue. If you need it 00:02:46.379 --> 00:02:50.390 - done expediently. If there is additional issues after the pair 00:02:50.390 --> 00:02:54.540 - programming, that's what you need to escalate to either to 00:02:54.540 --> 00:02:57.445 - management or to see if James or 00:02:57.445 --> 00:03:01.010 - a senior. Management member can step in and 00:03:01.010 --> 00:03:02.830 - figure out a solution. 00:03:04.260 --> 00:03:10.440 - Task manager for the 00:03:10.440 --> 00:03:16.328 - next steps. You know, OK, so let's say that 00:03:16.328 --> 00:03:19.452 - developer A is needing help on this. Listen this they didn't 00:03:19.452 --> 00:03:22.860 - get out, they try to get help from developer be developers C 00:03:22.860 --> 00:03:26.552 - and from the PM none of us could help them. The client couldn't 00:03:26.552 --> 00:03:29.676 - help them. What's our next steps? The next step then would 00:03:29.676 --> 00:03:33.652 - be hey Kevin Chris, This is an issue I don't know how to solve 00:03:33.652 --> 00:03:35.072 - it. I need your help. 00:03:35.740 --> 00:03:38.798 - They are the best in that situation at trying to problem 00:03:38.798 --> 00:03:42.690 - solve and they may go. I don't know, but did you try this? Did 00:03:42.690 --> 00:03:46.026 - you try not to try this? All those answers are Yes, then 00:03:46.026 --> 00:03:49.084 - they'll know that this is a bigger issue and this is 00:03:49.084 --> 00:03:51.586 - something that they really need to get involved with. 00:03:52.210 --> 00:03:56.650 - If there's if the issue is more of a separated issue, I'm 00:03:56.650 --> 00:03:59.980 - getting a little more comfortable and offering help in 00:03:59.980 --> 00:04:05.530 - those, so feel free to rope me in or rope. James in or both of 00:04:05.530 --> 00:04:10.710 - us, or wrote in Aiken, wrote James. And how do you want to do 00:04:10.710 --> 00:04:14.410 - it? Because the world's voice here twice? Yeah, Yeah. But 00:04:14.410 --> 00:04:18.480 - anyway so that that allows you the opportunity to know. And 00:04:18.480 --> 00:04:22.550 - then if we have this all set up this way then. 00:04:22.590 --> 00:04:25.404 - It shouldn't be any problem for me to come in and say OK, what 00:04:25.404 --> 00:04:27.615 - have you tried? What's the issue? What's the next step? Did 00:04:27.615 --> 00:04:29.022 - you try this? Did you try that? 00:04:29.940 --> 00:04:34.560 - Uhm, and then that helps me. Then if I do need to escalate to 00:04:34.560 --> 00:04:38.190 - James to say, OK, well this isn't working, so James, what's 00:04:38.190 --> 00:04:42.480 - This this and this? And then James has an idea that he can 00:04:42.480 --> 00:04:46.770 - get on a sink and then get the solution easier to a developer. 00:04:46.770 --> 00:04:50.730 - I think this worked really well and trying to resolve this spot 00:04:50.730 --> 00:04:54.690 - see issue so I could understand why James was having an issue 00:04:54.690 --> 00:04:58.320 - with helping Jesse and Jesse was having issues and helping James. 00:04:58.320 --> 00:04:59.970 - It helped me get that 00:04:59.970 --> 00:05:03.981 - perspective to understand. Where the disconnects were so that I 00:05:03.981 --> 00:05:08.783 - can say, OK, James, this is what he needs Jesse. This is what he 00:05:08.783 --> 00:05:12.899 - needs so get that information. We have a sink at this time. 00:05:12.899 --> 00:05:17.015 - That's when we can go through all this information and we got 00:05:17.015 --> 00:05:20.788 - the issue resolved so it's that communicating and make sure that 00:05:20.788 --> 00:05:25.247 - you have the flow of escalation 'cause a lot of times you won't 00:05:25.247 --> 00:05:26.962 - need to go to James. 00:05:27.630 --> 00:05:32.232 - All right, for a lot of core issues, there's a lot of things 00:05:32.232 --> 00:05:36.480 - that are very complex in the system that do take the correct 00:05:36.480 --> 00:05:40.374 - data. The correct set up the correct configurations, and if I 00:05:40.374 --> 00:05:43.560 - can't solve those, usually James can sometimes, especially with 00:05:43.560 --> 00:05:47.454 - 2020.1 projects, there may be fixes that have been done in 00:05:47.454 --> 00:05:51.702 - other projects that just need to get pulled in. We've set up 00:05:51.702 --> 00:05:56.304 - everything within 2020.1 to be able to do this, so that is an 00:05:56.304 --> 00:05:57.720 - Ave open as well. 00:05:57.720 --> 00:06:03.096 - You know we had to do that with a DI believe this week so. 00:06:03.100 --> 00:06:10.498 - God. That can be like a kind of a flow 00:06:10.498 --> 00:06:17.602 - of like where you go in your discussions and how you ask 00:06:17.602 --> 00:06:24.114 - later those issues. Ideally it would be good if the developers 00:06:24.114 --> 00:06:29.442 - working on the individual projects can solve the problems 00:06:29.442 --> 00:06:35.954 - themselves, and then the other thing that I would add into 00:06:35.954 --> 00:06:43.246 - this. I think that the most important part of this is once 00:06:43.246 --> 00:06:49.306 - a resolution has been solved, someone should write an article 00:06:49.306 --> 00:06:51.730 - in Stackoverflow about it. 00:06:52.390 --> 00:06:55.140 - The reason is that's not the last time someone's going to 00:06:55.140 --> 00:06:58.890 - have that issue, and if they can go in and tag that and see what 00:06:58.890 --> 00:07:02.390 - that is and say OK, this is the question I had. These are the 00:07:02.390 --> 00:07:05.140 - screenshots I had. OK, that's similar to the issue I'm saying 00:07:05.140 --> 00:07:06.890 - you can go through and you can 00:07:06.890 --> 00:07:10.819 - find solutions. That's the whole point of stack overflow, and I 00:07:10.819 --> 00:07:12.996 - think it's underutilized, especially on the development 00:07:12.996 --> 00:07:17.039 - side and making sure that, like I often hear, oh, it's just a 00:07:17.039 --> 00:07:21.393 - minor issue. It's not a big thing. I think we need to do a 00:07:21.393 --> 00:07:24.503 - stack overflow about it. I disagree this block. Someone for 00:07:24.503 --> 00:07:28.857 - a week and a half. Absolutely it needs to be something that is in 00:07:28.857 --> 00:07:32.920 - Stackoverflow. So that should be an encouragement and you really 00:07:32.920 --> 00:07:36.660 - should follow up on that. If there are issues that were 00:07:36.660 --> 00:07:40.060 - resolved and we're not added to Stackoverflow because that is 00:07:40.060 --> 00:07:44.480 - going to be a problem for you later in a project, and then 00:07:44.480 --> 00:07:48.560 - you'll be like, Oh well, you know I bought this issue before. 00:07:48.560 --> 00:07:50.260 - Why is this not at 00:07:50.260 --> 00:07:52.960 - stackoverflow? Just an idea. 00:07:54.150 --> 00:07:58.290 - And when you're presenting the issue that to a developer. 00:07:59.020 --> 00:08:05.124 - The best it's best to think of the issue in a way that the 00:08:05.124 --> 00:08:09.920 - developer understands and give them as many details as you can. 00:08:10.910 --> 00:08:15.733 - So defining the problem you got to go in and say OK, so 00:08:15.733 --> 00:08:19.443 - the problem with FIFA is that they need two factor 00:08:19.443 --> 00:08:22.782 - authentication for you know for adding a new account. 00:08:24.190 --> 00:08:28.960 - The issue is is that we in in South if you turn on two factor 00:08:28.960 --> 00:08:30.868 - authentication that's for everything concerning an 00:08:30.868 --> 00:08:34.684 - account. So when you log in, when you update a record, when 00:08:34.684 --> 00:08:38.818 - you create a new record, when you delete a record, all of that 00:08:38.818 --> 00:08:41.362 - information is done with two factor authentication. Anti 00:08:41.362 --> 00:08:42.952 - factor authentication has to be 00:08:42.952 --> 00:08:46.465 - used. That is not a good 00:08:46.465 --> 00:08:51.004 - customer experience. But it is what we have currently in the 00:08:51.004 --> 00:08:54.464 - system, so here's that problem. So a potential solution. Is 00:08:54.464 --> 00:08:59.308 - there a way that we can separate those out so that we can select 00:08:59.308 --> 00:09:03.806 - by config how each one of those is separated out? Yes, we can. 00:09:03.806 --> 00:09:07.958 - OK, here's the estimation. OK, I took that to see past the 00:09:07.958 --> 00:09:12.110 - client. They're like Oh yeah, we don't really need that. Will put 00:09:12.110 --> 00:09:14.186 - that to a later base item. 00:09:14.880 --> 00:09:18.996 - Great, take it out of the IW and move it into a feature points. 00:09:19.780 --> 00:09:24.977 - Um? The other things that you want to go in there if you want 00:09:24.977 --> 00:09:27.667 - to repeat what they expected functionality is so in the 00:09:27.667 --> 00:09:30.626 - expected functionality. What what do you want to happen? So I 00:09:30.626 --> 00:09:34.123 - want to log in, but I don't want to do 2 factor authentication. 00:09:35.370 --> 00:09:38.634 - I want to be able to add a new account, but if I add a new 00:09:38.634 --> 00:09:40.878 - account, I want that to be 2 factor authentication so they 00:09:40.878 --> 00:09:42.918 - don't just had a bunch of accounts for no reason. 00:09:44.670 --> 00:09:47.410 - It does. The expectation is 00:09:47.410 --> 00:09:52.296 - great. Any caveats or hurdles for other functionality so? 00:09:52.860 --> 00:09:59.230 - In this. If there's anything you know up that's touching the this 00:09:59.230 --> 00:10:03.325 - individual piece that you're talking about that has is 00:10:03.325 --> 00:10:07.812 - customization specifically. So let's say for two factor 00:10:07.812 --> 00:10:13.558 - authentication. OK, well we have an SSL, a single sign on that we 00:10:13.558 --> 00:10:18.862 - need to integrate web. So we need to make sure that is 00:10:18.862 --> 00:10:23.282 - incorporated there as well. Is there any implications that we 00:10:23.282 --> 00:10:28.144 - need to work on that? Yes no, maybe otherwise cool whenever 00:10:28.144 --> 00:10:33.006 - you're going through an issue you want to. And talking with 00:10:33.006 --> 00:10:37.868 - the developer about it, you want to make sure that you 00:10:37.868 --> 00:10:39.194 - incorporate the total 00:10:39.194 --> 00:10:41.936 - functionality. Of the project that there's any customizations 00:10:41.936 --> 00:10:46.528 - that may go in there, you may want you want to make sure and 00:10:46.528 --> 00:10:51.120 - say OK, hey, So what would change if we did this, or if if 00:10:51.120 --> 00:10:52.760 - you're saying we need to? 00:10:53.290 --> 00:10:57.008 - Dumb. Build a new table. 00:10:57.640 --> 00:11:00.790 - And schema at his support this functionality. How does that 00:11:00.790 --> 00:11:04.570 - interact with everything else in the system? What else do we need 00:11:04.570 --> 00:11:08.350 - to make sure his support it to make sure that happens every 00:11:08.350 --> 00:11:11.815 - time you're going through? You want to make sure that the. 00:11:12.420 --> 00:11:15.136 - Uh, the functionality that you're looking for. 00:11:15.136 --> 00:11:18.240 - The total project and not just that individual 00:11:18.240 --> 00:11:20.180 - item, is kept in mind. 00:11:21.540 --> 00:11:26.820 - Last one and this one I do all of the time I know you all have 00:11:26.820 --> 00:11:30.450 - heard it. Probably even gotten annoyed at me about it and 00:11:30.450 --> 00:11:34.080 - that's cool. I'm fine. You can be wrong. That was good. 00:11:34.100 --> 00:11:38.636 - Ask questions if you don't ask questions, you're doing 00:11:38.636 --> 00:11:43.160 - something wrong. Quite honestly, if you don't 00:11:43.160 --> 00:11:45.266 - understand it, ask. 00:11:47.050 --> 00:11:50.030 - I couldn't agree more. 00:11:50.030 --> 00:11:53.498 - Damn got to sit in a. 00:11:54.120 --> 00:11:58.008 - I called this morning and it was a silly thing with regions 00:11:58.008 --> 00:12:01.248 - something where the were pulling off of the region code 00:12:01.248 --> 00:12:04.812 - without checking the country. And like I told her and it's 00:12:04.812 --> 00:12:08.052 - something that it took me along time to get comfortable 00:12:08.052 --> 00:12:11.616 - doing and I'm sure this is just kind of reinforcement you 00:12:11.616 --> 00:12:15.504 - all know already. Do not have any shame in asking if you've 00:12:15.504 --> 00:12:19.068 - been paying attention. Do not have any shame in asking a 00:12:19.068 --> 00:12:20.688 - question that might seem dumb. 00:12:22.010 --> 00:12:23.249 - It's totally OK. 00:12:23.810 --> 00:12:26.486 - Yeah, have you come across like oh, you're not supposed to be 00:12:26.486 --> 00:12:28.716 - the subject matter expert on that thing, right? That's why 00:12:28.716 --> 00:12:30.054 - you have a developer on the 00:12:30.054 --> 00:12:34.764 - call. Yeah, I don't know how many times a week I'll talk to a 00:12:34.764 --> 00:12:37.932 - developer another. Does that make sense? I'm like now I have 00:12:37.932 --> 00:12:41.964 - no idea if you could ask the developers. I say it all of the 00:12:41.964 --> 00:12:45.996 - time all of the time like I have no idea what that means. What 00:12:45.996 --> 00:12:49.740 - does that mean? How do I explain that? And sometimes it takes me 00:12:49.740 --> 00:12:53.196 - 10 minutes before I actually figure out I work my way around 00:12:53.196 --> 00:12:56.940 - to understanding what they do, but it helps me in the long run 00:12:56.940 --> 00:13:00.396 - and it helps the developer in the long run because then I 00:13:00.396 --> 00:13:01.836 - don't have that ambiguity about 00:13:01.836 --> 00:13:05.760 - what. The process is moving forward. I am willing to take 00:13:05.760 --> 00:13:09.420 - that time. To make sure that I understand what's going on so 00:13:09.420 --> 00:13:12.780 - that I know what to do, what's best for my client and then if 00:13:12.780 --> 00:13:15.420 - there's anything that I'm like. Oh yeah, that's not going to 00:13:15.420 --> 00:13:17.100 - work for this and this and this. 00:13:17.600 --> 00:13:21.212 - Then I can call that out and I can talk to the developer about 00:13:21.212 --> 00:13:24.050 - it and it solves the issues before they become an issue. 00:13:24.060 --> 00:13:28.800 - Can you get that? If I can just jump in really quick my I hate 00:13:28.800 --> 00:13:32.276 - to be like I bring this up. Probably every single training 00:13:32.276 --> 00:13:36.384 - and I hate to beat a dead horse, but I think the acceptance 00:13:36.384 --> 00:13:39.544 - criteria around each one of those features would be really 00:13:39.544 --> 00:13:42.704 - helpful in identifying whether something is an actual issue or 00:13:42.704 --> 00:13:46.180 - if it's gonna be like added functionality. Or like you know, 00:13:46.180 --> 00:13:49.656 - some type of scope creep. I mean, if we have those 00:13:49.656 --> 00:13:52.500 - acceptance criteria there, we know what the original scope 00:13:52.500 --> 00:13:54.080 - was, then we know whether. 00:13:54.120 --> 00:13:56.700 - Something that's happening right now that we're running into. If 00:13:56.700 --> 00:14:00.054 - it's actually an issue that we have to like track down, and if 00:14:00.054 --> 00:14:02.634 - it's something we're actually having to work through, or if 00:14:02.634 --> 00:14:05.214 - it's like added functionality like Oh well, this new thing 00:14:05.214 --> 00:14:07.020 - came along and now we need to 00:14:07.020 --> 00:14:10.670 - add it in. Yes, should I think that's true? But this would also 00:14:10.670 --> 00:14:12.665 - be like if there is a change 00:14:12.665 --> 00:14:16.050 - request coming. Making sure you understand the change request 00:14:16.050 --> 00:14:18.930 - and where that information is coming from. What that 00:14:18.930 --> 00:14:22.450 - implication is on the project and how it may affect other 00:14:22.450 --> 00:14:24.050 - parts of our customizations in 00:14:24.050 --> 00:14:27.904 - the system. So more than just from The Discovery 00:14:27.904 --> 00:14:31.224 - Park, it should be more along the lines of making 00:14:31.224 --> 00:14:34.544 - sure that you understand how that code is supposed to 00:14:34.544 --> 00:14:37.864 - work. If not, the how it works. Know why it's 00:14:37.864 --> 00:14:41.848 - working. I guess I'm at that end here too, and that's a 00:14:41.848 --> 00:14:44.172 - good point. Acceptance criteria should also apply 00:14:44.172 --> 00:14:48.156 - to change requests as well. I mean, I mean, I, I don't 00:14:48.156 --> 00:14:51.476 - want to say that the given, but that's definitely valid. 00:15:11.820 --> 00:15:13.020 - Who wanna dead air? 00:15:14.260 --> 00:15:17.950 - Hey man, it's update these nuts. These are important. 00:15:17.950 --> 00:15:22.050 - The This is the kind of documentation that I want. 00:15:23.220 --> 00:15:26.520 - To be able to help people like Sam's, they're kind of getting 00:15:26.520 --> 00:15:29.820 - used to things like Oh Man, I'm having issue, we'd say, Hey, 00:15:29.820 --> 00:15:30.920 - check out the Doc. 00:15:32.010 --> 00:15:37.483 - The duck it's here, and if it takes a little bit of time. 00:15:37.490 --> 00:15:42.290 - But yeah, so with that. Like I said, knowing why it's happening 00:15:42.290 --> 00:15:46.290 - is more important than to know how it's happening. Sometimes 00:15:46.290 --> 00:15:50.690 - the How is a little bit necessary to understand why, but 00:15:50.690 --> 00:15:53.090 - if you don't have that line. 00:15:53.720 --> 00:15:56.804 - Why we're doing it? Why it's going on when the client asks 00:15:56.804 --> 00:15:59.888 - you why you're going to get it, because that's what you wanted. 00:16:00.820 --> 00:16:03.724 - But being able to say the reason why we're having to set 00:16:03.724 --> 00:16:06.628 - up this sink in a different way is because your ERP doesn't 00:16:06.628 --> 00:16:10.016 - support data. Going this way to this way. So we have to pull it 00:16:10.016 --> 00:16:13.162 - back into our system, change it on our system, and then sync it 00:16:13.162 --> 00:16:15.824 - back to your system to make sure that you have accurate 00:16:15.824 --> 00:16:16.792 - information in your ERP. 00:16:18.700 --> 00:16:22.145 - And also the actor that Garrett is that they know why. I mean, 00:16:22.145 --> 00:16:25.060 - there's been so many times where after the developer knows why 00:16:25.060 --> 00:16:27.710 - they're developing, something will be like. Well, why don't we 00:16:27.710 --> 00:16:31.155 - just do it after they know what needs to be done? It's like, 00:16:31.155 --> 00:16:34.865 - well, why don't we just do it this way? It actually is so much 00:16:34.865 --> 00:16:37.250 - easier after they understand actually why they're doing it 00:16:37.250 --> 00:16:40.695 - instead of just right. This is how it needs to function or what 00:16:40.695 --> 00:16:41.755 - it needs to do. 00:16:41.830 --> 00:16:44.214 - Sending the business practices and expectations from the 00:16:44.214 --> 00:16:47.790 - client. and I do agree that that would be something that would 00:16:47.790 --> 00:16:48.982 - come from the acceptance 00:16:48.982 --> 00:16:52.906 - criteria as well. Um, moving on 00:16:52.906 --> 00:16:58.360 - the. I always almost always do this if I don't fully 00:16:58.360 --> 00:17:02.573 - understand the Hall of something, and I the why is a 00:17:02.573 --> 00:17:07.552 - little fuzzy for me is if KB said that Katie told me this 00:17:07.552 --> 00:17:12.914 - week. He's like I need to. I need to know if I don't have 00:17:12.914 --> 00:17:18.276 - that so Taylor this week was like oh hey, I am able to get 00:17:18.276 --> 00:17:23.255 - into the box for my are but I don't have credentials or for 00:17:23.255 --> 00:17:24.021 - their VM. 00:17:25.120 --> 00:17:28.760 - I'm like the what? What do you? What do you want? What do you 00:17:28.760 --> 00:17:31.620 - want for Maine? Well, can you get that from the client? 00:17:32.520 --> 00:17:35.170 - OK, I don't understand what you're telling me. So what 00:17:35.170 --> 00:17:38.350 - this like? This is the note that I've drafted and I just 00:17:38.350 --> 00:17:41.795 - like OK, you know, hey team we we seem to be have the 00:17:41.795 --> 00:17:44.445 - credentials to get into your system, but we don't know 00:17:44.445 --> 00:17:47.095 - where we're going from there. We need credentials for this 00:17:47.095 --> 00:17:50.010 - this and this. Send it to Dylan. Like does that answer 00:17:50.010 --> 00:17:52.925 - your question? It's like yeah that's perfect. So then I sent 00:17:52.925 --> 00:17:56.105 - it off to the client. They got the information. We got it 00:17:56.105 --> 00:17:57.165 - back the next day. 00:17:58.730 --> 00:18:03.695 - If I have anything that I am a little fuzzy on and I know that 00:18:03.695 --> 00:18:06.674 - Brandon has been really excellent about this. But for 00:18:06.674 --> 00:18:11.970 - CPA, an 40. Angie for me is I sent a note to him and say, hey? 00:18:12.560 --> 00:18:16.256 - This is something that you know you said you needed. Is this 00:18:16.256 --> 00:18:19.336 - information that I'm sending to the client all correct and 00:18:19.336 --> 00:18:22.108 - there's multiple times like actually this, this and this 00:18:22.108 --> 00:18:26.112 - needs to change 'cause this and this and this all filter up at 00:18:26.112 --> 00:18:28.360 - something else. Great. 00:18:28.890 --> 00:18:31.942 - And then I and then either I make a new node on my. Can 00:18:31.942 --> 00:18:34.122 - you update that and then send me back that paragraph? 00:18:35.270 --> 00:18:38.882 - Does brings it back and then I sent it off to the client so 00:18:38.882 --> 00:18:41.720 - there's not that ambiguity or confusion in what's going on. So 00:18:41.720 --> 00:18:45.332 - if I send if I send that note before I send it to Brandon, 00:18:45.332 --> 00:18:48.686 - what I would have ended up having is I would have had the 00:18:48.686 --> 00:18:51.782 - client go like well, but that doesn't go with this. This and 00:18:51.782 --> 00:18:52.814 - this is Brendan said. 00:18:53.870 --> 00:18:56.750 - So that makes the communication faster and easier, and it 00:18:56.750 --> 00:19:00.206 - removes that question mark from the client side. So I always if 00:19:00.206 --> 00:19:03.662 - I'm doing something I always want to send it by the developer 00:19:03.662 --> 00:19:07.694 - to make sure that they know what I'm saying and it makes sense to 00:19:07.694 --> 00:19:10.574 - them and they're getting what they need. If they're missing 00:19:10.574 --> 00:19:14.606 - anything in there, then that is on me. It's not on that, and I 00:19:14.606 --> 00:19:16.622 - don't like or things to be on 00:19:16.622 --> 00:19:19.308 - me. Not how I roll. 00:19:20.030 --> 00:19:25.256 - But just like you would send a note to manage to management to 00:19:25.256 --> 00:19:29.678 - check if you're worried about the customer, set up a note 00:19:29.678 --> 00:19:34.100 - which I don't do enough. Everyone should do that way more 00:19:34.100 --> 00:19:35.306 - than I do. 00:19:35.580 --> 00:19:38.490 - Always make sure you send the technical information by the 00:19:38.490 --> 00:19:41.691 - developers as well to make sure that you're actually getting the 00:19:41.691 --> 00:19:44.310 - documentation that you need to share. Hey guys, heathers 00:19:44.310 --> 00:19:48.384 - calling me on group chat. Do you mind if I switch over to her 00:19:48.384 --> 00:19:51.585 - real quick and come right back? Sorry to interrupt. OK, thanks. 00:19:51.630 --> 00:19:55.830 - We've already talked about, then now battery knows that we're 00:19:55.830 --> 00:19:57.090 - talking about next. 00:19:57.100 --> 00:20:01.924 - But it definitely applies to like those are good. 00:20:01.930 --> 00:20:04.970 - I would say definitely applied to discovery to like whenever 00:20:04.970 --> 00:20:07.402 - we're putting questions like really technical questions like 00:20:07.402 --> 00:20:10.746 - this for all the PMS. It's definitely good to run the 00:20:10.746 --> 00:20:13.786 - questions by the developers. You're going to be on the 00:20:13.786 --> 00:20:17.434 - project, so if they see anything that comes up, it's like, Oh 00:20:17.434 --> 00:20:20.474 - well, actually I would ask this question a little bit 00:20:20.474 --> 00:20:23.514 - differently because I actually need this information or any of 00:20:23.514 --> 00:20:26.554 - that information for the more technical sides of discovery at 00:20:26.554 --> 00:20:29.898 - least, and documenting all of that. My one addendum I would 00:20:29.898 --> 00:20:33.242 - add to that, though, is in this comes from personal experience 00:20:33.242 --> 00:20:38.643 - and. We can be a wider discussion, but I would bring it 00:20:38.643 --> 00:20:40.908 - up specifically to the senior 00:20:40.908 --> 00:20:45.373 - team members. And it's it's across the board, but I have 00:20:45.373 --> 00:20:48.766 - been bitten on, you know, asking certain team members. 00:20:48.770 --> 00:20:53.359 - Do you think of this and just 'cause of lack of experience the 00:20:53.359 --> 00:20:57.242 - same way I don't know. They don't necessarily know when they 00:20:57.242 --> 00:21:00.772 - give their best shot, but ultimately running it past a 00:21:00.772 --> 00:21:04.302 - senior dev, which I would include Eric Sebyan James or 00:21:04.302 --> 00:21:08.538 - Chris Reddick for that matter. And even Kevin are by far the 00:21:08.538 --> 00:21:12.774 - most important things and in my case I run everything past Erik 00:21:12.774 --> 00:21:14.186 - fits back. End related. 00:21:15.650 --> 00:21:19.979 - Yeah, and like for instance like what we did with a DI was 00:21:19.979 --> 00:21:22.976 - extremely good. Like we went through that first architecture 00:21:22.976 --> 00:21:26.306 - meeting and test everything out and then we got questions 00:21:26.306 --> 00:21:30.302 - straight from James and straight from Eric that we then sent out 00:21:30.302 --> 00:21:34.298 - which was extremely beneficial and it was saved a ton of time. 00:21:34.298 --> 00:21:36.962 - Just getting this question straight from them and. 00:21:37.930 --> 00:21:41.674 - Just to throw in there too, if we have something that's F 00:21:41.674 --> 00:21:45.788 - related. I'd say before it goes to James, if Garrett has the 00:21:45.788 --> 00:21:48.470 - workload for it but start showing it to him. 00:21:49.030 --> 00:21:52.820 - As he can pretty quickly and astutely assess what's actually 00:21:52.820 --> 00:21:55.094 - out of box and what's not. 00:21:56.910 --> 00:22:01.515 - Um, for most things I can do that. what I would say is if you 00:22:01.515 --> 00:22:03.050 - are going through discovery and 00:22:03.050 --> 00:22:05.760 - you have a. Customizations to 00:22:05.760 --> 00:22:11.218 - the platform. You really should talk to James before you 00:22:11.218 --> 00:22:12.466 - solidify those requirements. 00:22:13.150 --> 00:22:16.263 - The reason for that is because of how all of the 00:22:16.263 --> 00:22:18.527 - systems work together and how the schemas setup. 00:22:19.760 --> 00:22:24.008 - Yeah, there are. James usually has a lot of concerns with how 00:22:24.008 --> 00:22:28.256 - the back end works and making sure the back end is supporting 00:22:28.256 --> 00:22:32.150 - the functionality that's needed. So if you were like OK, we're 00:22:32.150 --> 00:22:33.566 - going to customize checkout. 00:22:34.210 --> 00:22:37.140 - Really should ask James about that because check out touches 00:22:37.140 --> 00:22:40.070 - literally almost every part of the platform. It's like all 00:22:40.070 --> 00:22:43.000 - parts of the platform just funneled into one little page. 00:22:43.760 --> 00:22:47.250 - So if you're wanting to create new functionality that hasn't 00:22:47.250 --> 00:22:51.438 - been worked before, like Jim, I know that one of them You've 00:22:51.438 --> 00:22:54.579 - worked with is the potential of the auction functionality. 00:22:54.579 --> 00:22:58.069 - Obviously, major changes like that you want to go through 00:22:58.069 --> 00:23:01.908 - James, but if you have any questions and if I'm going 00:23:01.908 --> 00:23:05.049 - through documentation in looking through the documentation to see 00:23:05.049 --> 00:23:09.935 - if I see any catches, I can bring that up. But if you are 00:23:09.935 --> 00:23:13.076 - noticing anything specifically where you like OK, this is 00:23:13.076 --> 00:23:15.170 - actually changing how out of box 00:23:15.170 --> 00:23:19.100 - functionality works. It's not a bad idea to run that by James, 00:23:19.100 --> 00:23:23.330 - say hey, how big of a pain with this be and what you may find. 00:23:23.330 --> 00:23:26.150 - Is that something you think that sounds really easy is 00:23:26.150 --> 00:23:29.252 - actually quite difficult. That has been kind of a saving Grace 00:23:29.252 --> 00:23:32.918 - for me in FIFA and helping them understand what is best for a 00:23:32.918 --> 00:23:36.866 - phase one phase to you. And now they even have a phase four and 00:23:36.866 --> 00:23:38.276 - five setup for the project. 00:23:39.590 --> 00:23:44.075 - It's a lot. But uhm, so that that's just some 00:23:44.075 --> 00:23:46.910 - information there. Does anyone else have any 00:23:46.910 --> 00:23:50.150 - questions on what we've already talked about here? 00:23:50.150 --> 00:23:51.365 - Going live on? 00:23:52.750 --> 00:23:56.520 - The rest of this is kind of like execution. That was the main 00:23:56.520 --> 00:23:59.710 - information. I want to get the rest. It's just kind of 00:23:59.710 --> 00:24:04.233 - execution. There's one thing I want to just put on here, just 00:24:04.233 --> 00:24:08.063 - 'cause I do wanna memorialize this document with the if 00:24:08.063 --> 00:24:11.510 - project printed Garrett and James resolved if DNN project 00:24:11.510 --> 00:24:15.168 - bring too. Ben or KBB to 00:24:15.168 --> 00:24:19.116 - resolve. Up at that, 00:24:19.116 --> 00:24:22.810 - eh? 485185. 00:24:26.350 --> 00:24:32.631 - OK I was gonna put that under discovery information here if 00:24:32.631 --> 00:24:37.730 - that's OK. Just mirroring that thing up on 185, whereas if Seth 00:24:37.730 --> 00:24:42.075 - Project brings with James shoes off for a method of discussion. 00:24:43.460 --> 00:24:47.730 - A5. 00:24:52.220 --> 00:25:02.090 - Hi. 00:25:03.780 --> 00:25:04.390 - Cool. 00:25:05.950 --> 00:25:09.562 - I don't know if they should necessarily go on the list, but 00:25:09.562 --> 00:25:12.873 - I don't know. I I've been getting second opinions a lot 00:25:12.873 --> 00:25:15.281 - lately 'cause I don't know. Developers think very 00:25:15.281 --> 00:25:18.291 - differently and sometimes you know you might not need to 00:25:18.291 --> 00:25:21.301 - customize something at all. Uhm, I don't know specifically for 00:25:21.301 --> 00:25:24.612 - that auction platform. They wanted to be at the ability to 00:25:24.612 --> 00:25:27.923 - like reassociate products in a store from user to user, and 00:25:27.923 --> 00:25:31.234 - that would be like a huge customization that was like, why 00:25:31.234 --> 00:25:34.244 - can't you just export the products, delete him and then 00:25:34.244 --> 00:25:35.749 - reimport them an associate onto 00:25:35.749 --> 00:25:39.178 - a new user? Uh, which would be a work around itself currently 00:25:39.178 --> 00:25:42.170 - does, but we don't need to customize anything, so I was 00:25:42.170 --> 00:25:44.890 - getting a second opinion is really kind of valuable too. 00:25:46.300 --> 00:25:50.248 - Yeah, and that would be an instance of if your client has 00:25:50.248 --> 00:25:53.867 - the bandwidth to do out of box functionality, or if they 00:25:53.867 --> 00:25:57.157 - actually need to build out the functionality because they don't 00:25:57.157 --> 00:25:59.460 - have the manpower to be able to 00:25:59.460 --> 00:26:01.968 - do that, but. Good call out. 00:26:03.290 --> 00:26:05.612 - Yeah, 'cause I had triple constraint their budget and 00:26:05.612 --> 00:26:08.708 - timeline and what they can do and all that. All that other 00:26:08.708 --> 00:26:11.546 - stuff in it. So that probably not relevant for this list 00:26:11.546 --> 00:26:12.578 - but just get info. 00:26:13.690 --> 00:26:17.870 - True enough, always good info. 00:26:24.090 --> 00:26:30.941 - Yeah, but also at the same time I will say that there's times 00:26:30.941 --> 00:26:36.738 - where I've taken a problem to jeans and said for Sica 00:26:36.738 --> 00:26:43.062 - specifically like Hey we need to do mappable images and he's like 00:26:43.062 --> 00:26:46.751 - there's no way we can do that. 00:26:46.751 --> 00:26:51.670 - That's impossible. And I'm going to tell you that we have a 00:26:51.670 --> 00:26:55.426 - module that allows us to do mappable images now on FIFA that 00:26:55.426 --> 00:26:59.182 - is already dimmable. An it can be pulled in for other client 00:26:59.182 --> 00:27:02.938 - projects and it took CD along with the training of the C-15 00:27:02.938 --> 00:27:06.694 - and at the documentation to support it. It took us 20 hours. 00:27:08.030 --> 00:27:11.782 - So feel free also to say why can't you do this? Why can't you 00:27:11.782 --> 00:27:15.534 - do that? It took a lot of need saying This is what we need. 00:27:15.534 --> 00:27:19.286 - This is what I need. This is what I mean. What about this and 00:27:19.286 --> 00:27:23.306 - trying to get him to agree that finally CB did it and he did a 00:27:23.306 --> 00:27:25.182 - great job. So keep that in mind 00:27:25.182 --> 00:27:30.210 - as well. Uh, but for any other questions for my move on. 00:27:32.810 --> 00:27:35.680 - Ray, thank 00:27:35.680 --> 00:27:41.826 - you now. Little intro, you probably don't get enough. 00:27:41.826 --> 00:27:47.442 - Don't want to put in here? Sam, Jim, Clint, Daniel, Kyle. Pay 00:27:47.442 --> 00:27:49.782 - close attention here. Thank you. 00:27:50.890 --> 00:27:55.250 - I'm part of one of our retrospectives. For pod a 00:27:55.250 --> 00:27:59.610 - is we went through and we actually got an in-depth 00:27:59.610 --> 00:28:00.918 - understanding of what. 00:28:02.260 --> 00:28:05.945 - Developers wanted to see in tickets and I had each developer 00:28:05.945 --> 00:28:09.630 - go through it. Actually create a ticket asking for exactly what 00:28:09.630 --> 00:28:14.655 - they needed so they had to set up a ticket just like we did and 00:28:14.655 --> 00:28:18.340 - I did the count in something was mentioned of something they 00:28:18.340 --> 00:28:22.695 - needed and then I also put in if there was something that should 00:28:22.695 --> 00:28:26.715 - not be included specifically and why, and so that that could be 00:28:26.715 --> 00:28:27.720 - understood by the. 00:28:28.720 --> 00:28:32.152 - By the developers as well, I sent this information out and 00:28:32.152 --> 00:28:35.584 - then since this information came from them, I wanted to share 00:28:35.584 --> 00:28:39.328 - that with y'all. I haven't really done a very good job of 00:28:39.328 --> 00:28:42.760 - that, besides sharing that file with you. But the main things 00:28:42.760 --> 00:28:46.504 - that they are asking boring they request is they want a wire 00:28:46.504 --> 00:28:50.560 - frame, a mock up or screenshot. They want to see what the issue 00:28:50.560 --> 00:28:53.992 - is. If they can. Along with that, they would like the 00:28:53.992 --> 00:28:57.736 - desired behavior. So OK, this is what is supposed to happen and 00:28:57.736 --> 00:28:58.984 - they want the reproduction 00:28:58.984 --> 00:29:02.968 - steps. I'm going to fix this bug. How exactly do I do that? 00:29:03.900 --> 00:29:07.464 - Uh, but usually the URL where the issue exists that the best 00:29:07.464 --> 00:29:11.325 - thing to do with this is not to include that in the screen 00:29:11.325 --> 00:29:14.295 - shot, but to actually include it as a separate something 00:29:14.295 --> 00:29:16.077 - that can be copied and pasted. 00:29:17.610 --> 00:29:23.840 - I don't know if that's a word, but it just became a word stuff 00:29:23.840 --> 00:29:28.735 - that's not. No, it's not a word mountains, it is now. 00:29:33.350 --> 00:29:36.392 - So you want to make sure that they can just take that copy 00:29:36.392 --> 00:29:37.796 - paste and go straight to where 00:29:37.796 --> 00:29:42.580 - the issue is. Little thing that speeds up the development. 00:29:43.090 --> 00:29:46.126 - Any integrations to keep in mind? So if any of these 00:29:46.126 --> 00:29:48.886 - integrations are, if this is an issue with hey, this 00:29:48.886 --> 00:29:51.646 - information is being pulled in from NetSuite, and I'm not 00:29:51.646 --> 00:29:55.510 - seeing it. OK, so I know this is NetSuite, so it may be that 00:29:55.510 --> 00:29:59.650 - we need to see if it's in the database or if we need to see 00:29:59.650 --> 00:30:02.686 - it Persephone for its Justin. That's we tend to stop being 00:30:02.686 --> 00:30:02.962 - pulled. 00:30:04.440 --> 00:30:07.399 - Gives the developer a little bit more information. If you have 00:30:07.399 --> 00:30:11.950 - the mappings. This is something that we have built out a little 00:30:11.950 --> 00:30:16.448 - bit better with the recently James did a lot of work for IA 00:30:16.448 --> 00:30:19.562 - that's actually going to be integral for mapping documents 00:30:19.562 --> 00:30:23.368 - moving forward. I've shared that in the PM channel, but basically 00:30:23.368 --> 00:30:27.520 - it will allow the client to be able to have a constantly 00:30:27.520 --> 00:30:30.980 - updated mappings list, so if they are ever curious about 00:30:30.980 --> 00:30:35.132 - where something is coming from in SAP, they can go to that 00:30:35.132 --> 00:30:39.284 - document. They can filter to it and then see exactly where that 00:30:39.284 --> 00:30:42.797 - information is. You can see if it's unidirectional or 00:30:42.797 --> 00:30:46.707 - bidirectional and they can help diagnose issues with the IPS 00:30:46.707 --> 00:30:51.399 - that way, so that is something that will be more available in 00:30:51.399 --> 00:30:57.329 - the future. Rabbit is really awesome definitions. It'll tell 00:30:57.329 --> 00:31:00.911 - you what up field is used 00:31:00.911 --> 00:31:05.630 - for phenomenal. Well, so you can see if it's a string you can see 00:31:05.630 --> 00:31:09.680 - if it's a decimal you can see if it's a boolean and you can see 00:31:09.680 --> 00:31:12.920 - if there's a character limit. I, so there's a lot of information 00:31:12.920 --> 00:31:16.700 - in there that is really helpful both to you as a PM and then 00:31:16.700 --> 00:31:19.940 - also as a client to make sure that you can communicate with 00:31:19.940 --> 00:31:22.640 - the developers on what the expectations are there. If you 00:31:22.640 --> 00:31:25.340 - would like to review that document, I'm glad to run 00:31:25.340 --> 00:31:29.390 - through that with you and kind of how that is set up and how to 00:31:29.390 --> 00:31:32.360 - use it and how to train your clients to use it. 00:31:32.400 --> 00:31:35.532 - But I don't think that any project has been set up with 00:31:35.532 --> 00:31:38.403 - that yet as we are setting up aseefa with it now. 00:31:39.780 --> 00:31:43.752 - Um, relevant files or details from the quiet. If you got an 00:31:43.752 --> 00:31:47.062 - email from a client with three attachments saying I don't 00:31:47.062 --> 00:31:50.703 - understand why this is happening and then just include that email 00:31:50.703 --> 00:31:55.337 - in the ticket, let the let the developer go in and read and say 00:31:55.337 --> 00:31:58.978 - OK, this is exactly what the what is. Frustrating the client 00:31:58.978 --> 00:32:02.288 - and here's the files they've done to support this information 00:32:02.288 --> 00:32:05.598 - that gives the developer more information as to what the 00:32:05.598 --> 00:32:08.908 - client is expecting and the temperature of that client. So 00:32:08.908 --> 00:32:11.225 - if they're like in all caps and 00:32:11.225 --> 00:32:14.272 - screaming. Then they can say Oh, so maybe this is an urgent 00:32:14.272 --> 00:32:17.418 - issue. I need to get into. You got it. But also there's some 00:32:17.418 --> 00:32:20.564 - people like at you AG that used to just type everything in caps 00:32:20.564 --> 00:32:24.194 - lock and I was like Oh my God, can you teach her to take caps 00:32:24.194 --> 00:32:25.646 - lock up? I feel like she's 00:32:25.646 --> 00:32:30.203 - yelling at me. Uh, but yeah, so I definitely if there's any 00:32:30.203 --> 00:32:34.247 - files from the client, make sure you include those in the tickets 00:32:34.247 --> 00:32:37.280 - documentation links if you have any information that's currently 00:32:37.280 --> 00:32:41.998 - in teams, you don't need to copy and drag that file over to the 00:32:41.998 --> 00:32:45.705 - attachments. You can include the link from teams in there and 00:32:45.705 --> 00:32:48.738 - that's something that everyone can use in SharePoint. Because 00:32:48.738 --> 00:32:53.119 - Ben was good enough to figure out how to do that. So thanks 00:32:53.119 --> 00:32:56.826 - Ben, that has been really helpful for me and going through 00:32:56.826 --> 00:32:58.174 - and finding the information. 00:32:58.180 --> 00:33:01.924 - Copying it and pasting it so that all the information can be 00:33:01.924 --> 00:33:06.292 - found in there and then also it can be edited in there so that 00:33:06.292 --> 00:33:09.724 - it's version controlled and you can see what happened, but what 00:33:09.724 --> 00:33:12.844 - the original file was versus what the developer went through 00:33:12.844 --> 00:33:15.964 - and figured out when they were building out information. So 00:33:15.964 --> 00:33:19.708 - it's a really useful tool and to make sure that you're getting 00:33:19.708 --> 00:33:23.140 - that information into teams and then that link then will connect 00:33:23.140 --> 00:33:26.884 - and for future in case anyone else has any questions of what's 00:33:26.884 --> 00:33:28.756 - going on, they can see that 00:33:28.756 --> 00:33:31.154 - documents update. As well, when they click on the link. 00:33:32.790 --> 00:33:37.350 - Business logic, so making sure that business logic is included 00:33:37.350 --> 00:33:42.822 - in your ticket. So there are things are clients ask for that 00:33:42.822 --> 00:33:45.558 - are stupid. I'm just going to 00:33:45.558 --> 00:33:51.920 - say it. There are Jim, one of the examples was making sure 00:33:51.920 --> 00:33:54.638 - that I billing is static and 00:33:54.638 --> 00:33:59.076 - doesn't change. If it makes sense for you ages, business 00:33:59.076 --> 00:34:03.782 - logic, it does not make sense to us, right? So making sure you 00:34:03.782 --> 00:34:07.402 - include that business logic and hey, billing addresses are not 00:34:07.402 --> 00:34:09.936 - able to be adjusted in. Here is 00:34:09.936 --> 00:34:15.360 - why. And we need to make sure that throughout the system that 00:34:15.360 --> 00:34:20.560 - this is only updatable by an admin user or by the GRP. It 00:34:20.560 --> 00:34:24.160 - should not ever be updated by the user itself. 00:34:25.560 --> 00:34:29.808 - Up to a developer that's like that's dumb. Why would you? Why 00:34:29.808 --> 00:34:31.578 - would you ever want that 00:34:31.578 --> 00:34:34.874 - functionality? That's why you want to provide that information 00:34:34.874 --> 00:34:37.910 - before hand so they don't have to ask that question. They can 00:34:37.910 --> 00:34:40.693 - just say, OK, cool, it's weird, but I got no problem. 00:34:41.500 --> 00:34:46.583 - I I think I clicked you deal with that a little bit with 00:34:46.583 --> 00:34:48.538 - Atlas is just strange business 00:34:48.538 --> 00:34:53.769 - logic. And then the other information that would be nice 00:34:53.769 --> 00:34:57.918 - to be included is the IW information the individual. 00:34:58.630 --> 00:35:02.410 - Feature information the user story. Most of that is exported 00:35:02.410 --> 00:35:05.812 - by Kyle into Azure, but including any information that 00:35:05.812 --> 00:35:09.214 - may be missing may be updated. Any change, request, 00:35:09.214 --> 00:35:12.994 - information, anything that goes to the original scope of the 00:35:12.994 --> 00:35:17.530 - project is always good to go, and then if there's any updates 00:35:17.530 --> 00:35:22.444 - to that or changes you want to make sure that that is updated 00:35:22.444 --> 00:35:24.334 - and the ticket as well. 00:35:24.910 --> 00:35:30.690 - Things to exclude from the tickets on is making sure 00:35:30.690 --> 00:35:33.580 - credentials are not in tickets. 00:35:34.170 --> 00:35:37.398 - Basically what we wanna do is every ticket should be made with 00:35:37.398 --> 00:35:40.357 - the understanding that the client may see it at some point. 00:35:41.970 --> 00:35:46.481 - The reason I say that is because there are clients and there are 00:35:46.481 --> 00:35:51.339 - there is an Ave for clients to go in and look through our Azure 00:35:51.339 --> 00:35:56.544 - if they have the credentials to do so. We can set that up and in 00:35:56.544 --> 00:36:00.708 - certain situations that is very desired by the client, but it is 00:36:00.708 --> 00:36:02.790 - also helpful to clarity as well. 00:36:03.400 --> 00:36:06.470 - So always make sure when you're creating tickets, you're you 00:36:06.470 --> 00:36:09.233 - understand that the client may one day see this. 00:36:11.090 --> 00:36:15.006 - And you don't want credentials in there because you don't want 00:36:15.006 --> 00:36:19.278 - people that can go in and see credentials and then stuff or 00:36:19.278 --> 00:36:22.482 - sensitive information for the client. You don't want that 00:36:22.482 --> 00:36:25.686 - information in there because that could be something that 00:36:25.686 --> 00:36:27.110 - could be seen later. 00:36:27.800 --> 00:36:30.986 - This also includes like third party providers or sass 00:36:30.986 --> 00:36:33.818 - providers. If there's any information about, like an 00:36:33.818 --> 00:36:38.066 - account number or something that someone could use to get into a 00:36:38.066 --> 00:36:41.252 - shipping provider and change information you don't want that 00:36:41.252 --> 00:36:42.314 - in a ticket. 00:36:43.550 --> 00:36:45.098 - In the wiki, right? 00:36:45.680 --> 00:36:48.650 - Yes, that all should be maintained in the wiki. 00:36:49.550 --> 00:36:52.660 - And also you don't really want to put duplicate information 00:36:52.660 --> 00:36:56.708 - from teams. Just because it's easier if everything's in teams 00:36:56.708 --> 00:37:00.686 - and you have the links in there so that they can be version 00:37:00.686 --> 00:37:03.440 - controlled and everyone is working from the same document, 00:37:03.440 --> 00:37:06.806 - that is going to be the best case scenario for maintaining 00:37:06.806 --> 00:37:09.560 - information and making sure everyone's on the same page. 00:37:10.450 --> 00:37:14.465 - So try not to pull information from 2 places and create 00:37:14.465 --> 00:37:18.480 - multiple documents for people to look at when you could just 00:37:18.480 --> 00:37:20.305 - create it all for one. 00:37:20.900 --> 00:37:25.366 - If that makes sense. Do you have any other questions on this? 00:37:26.430 --> 00:37:30.000 - Great. 00:37:31.610 --> 00:37:37.080 - Kay? Some of this information I've done in best practices I 00:37:37.080 --> 00:37:41.080 - know is salmon calcein, so Sam sorry if you're suffering 00:37:41.080 --> 00:37:43.080 - through some of this again. 00:37:43.090 --> 00:37:47.470 - Internal communication on and I kind of have the different 00:37:47.470 --> 00:37:52.288 - evidence we have for this base camp is there is the 00:37:52.288 --> 00:37:55.792 - possibility to set up information that the client 00:37:55.792 --> 00:37:57.544 - cannot see within Bayscape. 00:37:59.010 --> 00:38:03.079 - I think it's a poor choice to use it, but I understand in 00:38:03.079 --> 00:38:06.835 - certain situations that it can be there. If this is used, it 00:38:06.835 --> 00:38:09.339 - should always be understood that everything should be 00:38:09.339 --> 00:38:12.782 - written and made out as if the customer can see it. 00:38:14.480 --> 00:38:17.330 - That's an important distinction there, because if there's ever a 00:38:17.330 --> 00:38:20.180 - reason why someone changes that setting and their stuff in 00:38:20.180 --> 00:38:23.030 - there, that would upset the client and then they magically 00:38:23.030 --> 00:38:25.595 - they're seeing it, that's going to be an issue. 00:38:26.210 --> 00:38:28.430 - And it's happened. 00:38:29.370 --> 00:38:33.858 - I I didn't know what's happened, but not a good thing. 00:38:34.690 --> 00:38:37.290 - It's a really good just staging option, though. I mean 00:38:37.290 --> 00:38:40.930 - I I will always use it just to like stage. All the things I'm 00:38:40.930 --> 00:38:43.790 - actually posting on base camp until I know that it's going 00:38:43.790 --> 00:38:46.910 - to be sufficient and it's not going to come across a bad 00:38:46.910 --> 00:38:50.030 - way. Then I switch it on to all of the other users. 00:38:52.600 --> 00:38:58.858 - There are good uses for it. 00:38:58.860 --> 00:39:02.460 - I didn't even think about that, but yes, if you're wanting to 00:39:02.460 --> 00:39:05.460 - create a draft of something, someone else can review before 00:39:05.460 --> 00:39:09.360 - it's ready to go to the client, that's that's a good use of 00:39:09.360 --> 00:39:11.160 - that. So good call out, Kyle, 00:39:11.160 --> 00:39:13.420 - thank you. Uh. 00:39:14.110 --> 00:39:19.203 - James, on the information on I say almost all of the 00:39:19.203 --> 00:39:22.907 - information should be in the project channel. Almost 00:39:22.907 --> 00:39:26.611 - everything you're discussing with within your projects and 00:39:26.611 --> 00:39:30.778 - within the company really should be focused on being. 00:39:31.420 --> 00:39:37.188 - Tracks regulated and verifiable within eight public 4. 00:39:38.380 --> 00:39:42.412 - I say that because there's too many times where I have sent 00:39:42.412 --> 00:39:46.108 - individual messages to someone on a project and I can't ever 00:39:46.108 --> 00:39:49.804 - find that information again. Can't go back and figure it out. 00:39:49.804 --> 00:39:53.836 - I don't know where it is and then management might think that 00:39:53.836 --> 00:39:58.204 - I've not ever even done that and I have no record to say 00:39:58.204 --> 00:40:01.625 - otherwise. Something that's good to note about all this you're 00:40:01.625 --> 00:40:03.215 - talking about to visit. If I. 00:40:03.860 --> 00:40:09.416 - If it ever goes to litigation, um, everything can be can be 00:40:09.416 --> 00:40:13.583 - subpoenaed. Time logs private and public messages all alike. 00:40:13.583 --> 00:40:18.676 - Just throwing that out there. So be careful what you write, 00:40:18.676 --> 00:40:21.917 - regardless whether it's private or not. Yeah. 00:40:22.480 --> 00:40:27.310 - It can all be. It can all be subpoenaed if if things ever go 00:40:27.310 --> 00:40:31.795 - go sour. Yeah, and so I usually say saving direct pains for any 00:40:31.795 --> 00:40:35.590 - issues that are specific to just the developer. So time offer 00:40:35.590 --> 00:40:39.040 - private conversations, that sort of stuff really can be indirect 00:40:39.040 --> 00:40:43.525 - pain. Or if they had just a specific issue they like. Oh my 00:40:43.525 --> 00:40:47.665 - God, this is frustrating. You can talk to him about it in 00:40:47.665 --> 00:40:50.770 - pain, but if it's an actual functionality, actual blocker, 00:40:50.770 --> 00:40:52.840 - actual issue that needs to be 00:40:52.840 --> 00:40:56.469 - addressed. It really should be in a public forum and the reason 00:40:56.469 --> 00:40:59.937 - for that is then like if Heather needs help from Brendan on 00:40:59.937 --> 00:41:03.694 - something for Kathy. It does her no good to tell me about it. 00:41:04.730 --> 00:41:08.500 - Is she just puts it in the cache house? Hey, I'm having this 00:41:08.500 --> 00:41:11.690 - issue. Hey Garrett, I'm having this issue Brandon. Can you look 00:41:11.690 --> 00:41:14.880 - at this and then put the screenshot that has saved so 00:41:14.880 --> 00:41:18.360 - much time in telling me about the issue. Then I tell Brandon 00:41:18.360 --> 00:41:22.130 - the night Brandon gives me an answer and I give that back to 00:41:22.130 --> 00:41:24.740 - Heather. Just don't be the middleman. Allow the developers 00:41:24.740 --> 00:41:27.640 - to work together and not be the Intermediary for every 00:41:27.640 --> 00:41:30.830 - communication. It saves me so much time trying to training my 00:41:30.830 --> 00:41:31.990 - developers to do that. 00:41:33.810 --> 00:41:37.996 - This is a best practice. I just know that whenever you are just 00:41:37.996 --> 00:41:41.538 - creating a conversation in the general posts there, if you are 00:41:41.538 --> 00:41:44.436 - dragging air. If you're attaching a file to that 00:41:44.436 --> 00:41:47.978 - conversation, I just found that it's really I mean best practice 00:41:47.978 --> 00:41:52.486 - for me at least to put it in the folder structure it supposed to 00:41:52.486 --> 00:41:56.350 - be in first and then attaching you just press the attach button 00:41:56.350 --> 00:42:00.536 - on your post and do attach a document from a teams folders so 00:42:00.536 --> 00:42:04.078 - that it's just pulling it from that specific folder. 'cause If 00:42:04.078 --> 00:42:06.332 - you just put it in your post. 00:42:06.360 --> 00:42:09.935 - It's just going to drop it in the general files, and if I 00:42:09.935 --> 00:42:13.235 - don't know I just tried to go back and find that conversation 00:42:13.235 --> 00:42:16.810 - in those files before and it's really hard to go back and find 00:42:16.810 --> 00:42:20.110 - out when it's just dumped in just a general folder. So just 00:42:20.110 --> 00:42:23.410 - play the file and then attach it to your conversation just to 00:42:23.410 --> 00:42:24.510 - keep it all organized. 00:42:25.270 --> 00:42:29.456 - Yes, and that is a part of share point as well. So if you're 00:42:29.456 --> 00:42:32.446 - having trouble managing a SharePoint files and you can ask 00:42:32.446 --> 00:42:36.632 - me or you really should ask Ben because he's the best at it. But 00:42:36.632 --> 00:42:40.519 - I did do it and I went through the painstaking effort of making 00:42:40.519 --> 00:42:44.705 - sure that all my clients are there and I love it. So to be 00:42:44.705 --> 00:42:48.293 - honest, I kind of disagree with what you just said because when 00:42:48.293 --> 00:42:50.685 - you play something in a conversation it automatically 00:42:50.685 --> 00:42:55.170 - puts it in the root of the files and we're trying to keep it more 00:42:55.170 --> 00:42:56.665 - organized in that like that. 00:42:56.740 --> 00:43:01.381 - Using like a folder structure so it's better if you save the file 00:43:01.381 --> 00:43:05.665 - to where it's supposed to go in the folder structure and then 00:43:05.665 --> 00:43:09.949 - create a share link and post the share link in the conversation. 00:43:09.949 --> 00:43:14.590 - Yeah, that's why I said Oh, is that what you said? I'm sorry 00:43:14.590 --> 00:43:16.018 - that's what I said. 00:43:16.030 --> 00:43:18.998 - If you just do it straight in there, just it just dumps in the 00:43:18.998 --> 00:43:22.178 - team and you get, it's hard to find later if you just do it in 00:43:22.178 --> 00:43:23.238 - the in the post, yeah? 00:43:26.850 --> 00:43:27.460 - Over. 00:43:28.800 --> 00:43:32.793 - Um and Azure and communicating impediments. This is kind of a 00:43:32.793 --> 00:43:36.786 - big one. The first one is if you're assigned an impediment, 00:43:36.786 --> 00:43:38.964 - do you understand what the block 00:43:38.964 --> 00:43:44.608 - ads? If not in the then ask the uh you have to ask the PR 00:43:44.608 --> 00:43:47.641 - the developer For more information like it should be 00:43:47.641 --> 00:43:52.359 - one of those things that Ben is out for a week and I see 00:43:52.359 --> 00:43:56.403 - Brandon put a impediment on a bot task I should in bins 00:43:56.403 --> 00:44:01.121 - stead be able to go back, see what the issue is and be able 00:44:01.121 --> 00:44:03.143 - to help. Try and resolve it. 00:44:04.260 --> 00:44:07.872 - And if that man, that should be like, you know, just an 00:44:07.872 --> 00:44:09.979 - expectation that's more expectation for the developer. 00:44:09.979 --> 00:44:13.290 - But making sure that if you don't understand what that block 00:44:13.290 --> 00:44:15.096 - necessarily is or how to resolve 00:44:15.096 --> 00:44:17.791 - it. What needs to be resolved in the block and those are 00:44:17.791 --> 00:44:20.203 - questions you need to make sure to ask the developer to make 00:44:20.203 --> 00:44:23.990 - sure that are there. Um? 00:44:23.990 --> 00:44:27.180 - Communicating then, if there's a time frame for the block 00:44:27.180 --> 00:44:31.450 - release. So letting developer now hey, I have a meeting with. 00:44:32.450 --> 00:44:36.590 - TNG on this day to go through this information, get an answer 00:44:36.590 --> 00:44:40.577 - for you. Then the developer knows in your discussion on that 00:44:40.577 --> 00:44:44.213 - impediment. OK, cool. So he is working on this. The next steps 00:44:44.213 --> 00:44:48.758 - are this and this so I can look back at this ticket on this day 00:44:48.758 --> 00:44:50.273 - and ask Garrett For more 00:44:50.273 --> 00:44:52.300 - information. Um? 00:44:53.570 --> 00:44:56.810 - A moving block ticket. I don't remember what I was 00:44:56.810 --> 00:44:58.106 - gonna say about this. 00:44:59.740 --> 00:45:03.149 - Oh, if you have block block tasks. 00:45:05.400 --> 00:45:08.865 - We don't really have anything set up as best practices or 00:45:08.865 --> 00:45:12.015 - moving block tasks out of this print. Typically, if I 00:45:12.015 --> 00:45:15.795 - feel like there's no way I'm going to get both the block 00:45:15.795 --> 00:45:18.315 - removed and the task completed in the remaining 00:45:18.315 --> 00:45:22.095 - time, then the Sprint I move it out, then I tell the 00:45:22.095 --> 00:45:25.560 - client, hey, sorry you got this to me, but we're gonna 00:45:25.560 --> 00:45:28.710 - have to address this next Sprint because we don't have 00:45:28.710 --> 00:45:30.285 - the time to address it. 00:45:31.540 --> 00:45:32.908 - Sorry, talk cookies. 00:45:34.120 --> 00:45:38.266 - Hum. Then we all know how to make impediments correct. 00:45:40.000 --> 00:45:41.100 - Task level 00:45:42.340 --> 00:45:48.892 - Assuming yes, cool um linked tickets is another one. So do we 00:45:48.892 --> 00:45:52.714 - understand how predecessors, successors, parents and related 00:45:52.714 --> 00:45:55.990 - parent slash child is? This can 00:45:55.990 --> 00:46:02.630 - be. Does everyone know understand these 00:46:02.630 --> 00:46:05.972 - relationships in link 00:46:05.972 --> 00:46:09.906 - tickets? Call, but I'm not gonna go into more details on that. 00:46:09.906 --> 00:46:13.234 - Just making sure if you do have tickets that are linked to make 00:46:13.234 --> 00:46:16.306 - sure that those links are there so the developer knows what the 00:46:16.306 --> 00:46:19.890 - next steps are or if they need to be on the lookout for a 00:46:19.890 --> 00:46:22.706 - predecessor to be done so that they can start their task. 00:46:23.410 --> 00:46:25.980 - Or they can see if their successors in the spring 00:46:25.980 --> 00:46:28.807 - that they need to get done to make sure that next 00:46:28.807 --> 00:46:29.321 - persons unblocked. 00:46:30.360 --> 00:46:36.208 - That's a really important kind of thing to. 00:46:36.780 --> 00:46:39.120 - Circle in some good habits around as you're getting a 00:46:39.120 --> 00:46:40.290 - lot of these tickets in. 00:46:42.560 --> 00:46:49.593 - Yeah, I got it. Um, yeah I've used it and I understand, yeah. 00:46:49.600 --> 00:46:52.069 - I learned her. 00:46:52.070 --> 00:46:56.882 - Learning to run some Azure so we talk about it, she's awesome. 00:46:56.890 --> 00:47:03.632 - Yes. Tickets the discussion, and I usually say in this is I know 00:47:03.632 --> 00:47:07.342 - that then you don't necessarily agree with this. But um 00:47:07.342 --> 00:47:11.423 - discussion really should mostly be on the user story level. The 00:47:11.423 --> 00:47:16.246 - reason for that is that the that is the level that the product 00:47:16.246 --> 00:47:19.956 - owner is actually in charge of. That is where their 00:47:19.956 --> 00:47:23.295 - responsibility lies, and that's where the communication needs to 00:47:23.295 --> 00:47:26.634 - really center around task level. Communication should be used 00:47:26.634 --> 00:47:30.344 - sparingly, and it should only be for that task specific. 00:47:30.380 --> 00:47:33.188 - Implementation, so if it's OK, I don't know how this link needs 00:47:33.188 --> 00:47:36.230 - to be setup. OK, cool, I can help you set up that link. 00:47:36.230 --> 00:47:39.272 - Here's what we need to do and this is what needs to happen. 00:47:39.820 --> 00:47:43.527 - That isn't necessarily something that maybe the back end or needs 00:47:43.527 --> 00:47:47.234 - to know about setting up the email task because it's specific 00:47:47.234 --> 00:47:51.278 - to how the E Formatting is. But in general, if there's anything, 00:47:51.278 --> 00:47:54.648 - any discussion or confusion about a ticket, it really should 00:47:54.648 --> 00:47:59.366 - be done on the user story level so that everyone can go back and 00:47:59.366 --> 00:48:03.073 - see it, and it's not necessarily something that's hidden on a 00:48:03.073 --> 00:48:04.084 - separate developers task. 00:48:05.380 --> 00:48:07.930 - Um? There's that. 00:48:08.640 --> 00:48:12.280 - Um paired programming. This is something I was talking about 00:48:12.280 --> 00:48:16.284 - before about if someone is blocked and they just get the 00:48:16.284 --> 00:48:21.380 - same pay. Try this hey try that hey try this. Hey try that for 00:48:21.380 --> 00:48:24.656 - two hours on teams. That's not unblocking that developer. 00:48:25.400 --> 00:48:29.001 - It really should be a best practice for the PM to look back 00:48:29.001 --> 00:48:31.771 - at that information. Go hey, this isn't working. It doesn't 00:48:31.771 --> 00:48:34.818 - seem to be working in. This doesn't seem to be efficient. 00:48:34.818 --> 00:48:38.973 - Can I set up a meeting for you for you and you to get together 00:48:38.973 --> 00:48:40.081 - and figure this out? 00:48:41.740 --> 00:48:45.408 - Um, I've noticed that it saves me a lot of time I would love 00:48:45.408 --> 00:48:48.552 - for the developers just to be like, hey, I'm going to do 00:48:48.552 --> 00:48:51.434 - paired programming with this person at this time. Is that OK? 00:48:52.050 --> 00:48:57.211 - Great, you can invite me, I'll come play at the party yay but 00:48:57.211 --> 00:49:01.181 - um for right now that's not something that's happening on 00:49:01.181 --> 00:49:05.945 - the development side. So really, we need to be more cognizant of 00:49:05.945 --> 00:49:11.106 - how communications going down an ad in teams. And if we do see 00:49:11.106 --> 00:49:12.694 - that there's a large. 00:49:13.420 --> 00:49:16.860 - 23 comment thread about someone having trouble setting up a 00:49:16.860 --> 00:49:20.988 - local that is already taking up way more time for everyone than 00:49:20.988 --> 00:49:25.804 - a local ship. Just get a meeting together and get it set up and 00:49:25.804 --> 00:49:26.836 - get it back. 00:49:28.450 --> 00:49:29.700 - And. 00:49:31.030 --> 00:49:35.307 - Sorry, I was just going to China in and add something real quick 00:49:35.307 --> 00:49:39.584 - where I've noticed a lot of success. Since we are a lot of 00:49:39.584 --> 00:49:40.900 - us are working remote. 00:49:41.210 --> 00:49:45.630 - It's in my experience, been a good idea of just like hey, just 00:49:45.630 --> 00:49:50.050 - chat him up real quick here U available to get on the call. 00:49:50.050 --> 00:49:53.790 - Pull him into the call if somebody else is available, pull 00:49:53.790 --> 00:49:58.890 - them into the call and just make it an ad hoc meeting. Like a lot 00:49:58.890 --> 00:50:02.630 - of these guys. They don't really shouldn't have meetings on their 00:50:02.630 --> 00:50:05.690 - calendar unless their client meetings that have been agreed 00:50:05.690 --> 00:50:10.110 - to or something else. So if you can just get him together 9 00:50:10.110 --> 00:50:13.170 - times outta 10 it resolves issues so much quicker. 00:50:13.190 --> 00:50:17.493 - And then what I've done is I'll just sit in the background and 00:50:17.493 --> 00:50:21.796 - do other work, but it allows me to come do these small course 00:50:21.796 --> 00:50:25.437 - corrections and as frustrating as it might seem, it takes so 00:50:25.437 --> 00:50:29.078 - much less energy than having to constantly check in. And like, 00:50:29.078 --> 00:50:33.050 - did you guys meet? Did you guys actually meet what's going on 00:50:33.050 --> 00:50:36.691 - here as opposed to just taking the reins, so to speak? 00:50:36.720 --> 00:50:40.092 - I I will agree with everything you said except for ad hoc 00:50:40.092 --> 00:50:42.902 - meetings. I always like to schedule something so that they 00:50:42.902 --> 00:50:45.712 - know what's coming and then miss. Specifically if there's a 00:50:45.712 --> 00:50:48.803 - major block like I know we experience with this with spot. 00:50:48.803 --> 00:50:51.894 - See setting up the expectation of what developer is going to 00:50:51.894 --> 00:50:54.985 - bring blood to the table. So specifically Jesse. I need you 00:50:54.985 --> 00:50:58.638 - to go through and make sure that we can see the information for 00:50:58.638 --> 00:51:02.291 - the white list so that we can see what's going on there. James 00:51:02.291 --> 00:51:05.663 - I really need you to bring some information more and make sure 00:51:05.663 --> 00:51:07.349 - that those are all set up 00:51:07.349 --> 00:51:10.058 - correctly. And let the developers know, especially if 00:51:10.058 --> 00:51:13.182 - there's someone helping someone else with an issue so that you 00:51:13.182 --> 00:51:16.590 - can bring the issue to light and then they can be prepared 00:51:16.590 --> 00:51:20.566 - to solve the issue at hand. I do think that that is the best 00:51:20.566 --> 00:51:23.974 - way to handle it if you get results with ad hoc meetings, 00:51:23.974 --> 00:51:26.814 - great, I'm not telling you you're wrong for doing that, 00:51:26.814 --> 00:51:30.506 - just my method of doing it is much more. I'm a control freak 00:51:30.506 --> 00:51:31.926 - I guess, and that's fine. 00:51:32.990 --> 00:51:37.115 - I will say that some clients, I mean David for C, uh, the one we 00:51:37.115 --> 00:51:40.415 - were just on the phone with biking even think of their name 00:51:40.415 --> 00:51:43.165 - right now. Basically some clients are like I don't care. 00:51:43.165 --> 00:51:46.190 - Like if you're going if your developer is spending, you know 00:51:46.190 --> 00:51:49.215 - there 2 hours of this tickets time trying to get something 00:51:49.215 --> 00:51:52.790 - done for my site and they get blocked on something he was like 00:51:52.790 --> 00:51:56.090 - literally just call me. I don't care what it is, just just 00:51:56.090 --> 00:51:59.665 - literally call me will have an ad hoc meeting and I'll help you 00:51:59.665 --> 00:52:03.240 - figure it out or or help you like understand how it needs to 00:52:03.240 --> 00:52:07.270 - go. Some clients are definitely like that, um, didn't want you 00:52:07.270 --> 00:52:11.698 - to call them like right when it happens, rather than you know 00:52:11.698 --> 00:52:16.495 - getting you know too far down the line on this tile. This is 00:52:16.495 --> 00:52:19.078 - specifically for internal communication is what we're 00:52:19.078 --> 00:52:20.185 - talking about here. 00:52:21.090 --> 00:52:24.538 - Oh OK, that's fine. 00:52:24.540 --> 00:52:26.050 - Agree in client issues that 00:52:26.050 --> 00:52:30.551 - that's the case. And in the case that I've used literally today, 00:52:30.551 --> 00:52:34.280 - it's it's a scenario of this person doesn't have other work. 00:52:34.280 --> 00:52:38.009 - They need work. They need to be unblocked. This is critical. 00:52:38.009 --> 00:52:42.416 - Uhm, so I agree with you though normally you would want to put 00:52:42.416 --> 00:52:46.145 - these at a later date. Make sure the developer understands you 00:52:46.145 --> 00:52:49.874 - should be working on something else, but if the developer is 00:52:49.874 --> 00:52:53.942 - blocked and that's all they have, then you kind of have to 00:52:53.942 --> 00:52:58.010 - take the onus of being like let's see what we can do. 00:52:58.030 --> 00:53:01.450 - Now, as opposed to putting it off where they're not going to 00:53:01.450 --> 00:53:04.870 - have work or they're going to have to find some other work 00:53:04.870 --> 00:53:06.580 - which is not ideal for the 00:53:06.580 --> 00:53:11.346 - company. Last time I yeah and I I just do things a little 00:53:11.346 --> 00:53:15.076 - differently. Sometimes I set up the meeting for five minutes 00:53:15.076 --> 00:53:17.687 - from now, but like I said, under 00:53:17.687 --> 00:53:21.653 - control freak. One thing I will say though is I peered 00:53:21.653 --> 00:53:25.937 - programming. I don't think is used enough and I know that a 00:53:25.937 --> 00:53:27.722 - lot of our junior developers. 00:53:28.320 --> 00:53:32.298 - I get frustrated a lot of times when they have issues and they 00:53:32.298 --> 00:53:35.052 - don't have anyone that actually stops and helps them. 00:53:36.050 --> 00:53:39.886 - I talked to a few of them and then that's been the case so 00:53:39.886 --> 00:53:43.174 - please just check in with them and make sure if they're having 00:53:43.174 --> 00:53:46.462 - issues and struggling, check in with them and say Hey so you're 00:53:46.462 --> 00:53:49.750 - having issues. What can I help with? You know? What are the 00:53:49.750 --> 00:53:53.038 - major issues? Who do you need help from reaching out to them? 00:53:53.038 --> 00:53:56.600 - Usually is a good place to start. If you see that they are 00:53:56.600 --> 00:54:03.100 - struggling. Email For internal purposes, I would 00:54:03.100 --> 00:54:07.962 - say really I used this just to transfer importing from the 00:54:07.962 --> 00:54:13.708 - client. I very rarely use email and I try to leave emails that 00:54:13.708 --> 00:54:18.570 - are important in share point so that they can be referenced 00:54:18.570 --> 00:54:24.316 - later on the project, but I in general I don't. I don't use 00:54:24.316 --> 00:54:29.620 - email a lot, I feel like really email should be saved for 00:54:29.620 --> 00:54:33.598 - internal emails to really be safer management for important 00:54:33.598 --> 00:54:34.924 - updates and information. 00:54:35.110 --> 00:54:38.422 - You guys going to disagree with me? If you want on that, 00:54:38.422 --> 00:54:41.458 - but that's how I feel it should be, and that's how 00:54:41.458 --> 00:54:42.562 - typically I work so. 00:54:43.610 --> 00:54:45.114 - Feel free to use that as you want. 00:54:46.460 --> 00:54:51.816 - Um, setting up meetings. This is a little bit more into the pair 00:54:51.816 --> 00:54:56.760 - programming, but every time you do set up a meeting along with 00:54:56.760 --> 00:55:00.880 - the teams notification and the login, you should set the 00:55:00.880 --> 00:55:05.000 - expectation of what the meeting is, what it will be 00:55:05.000 --> 00:55:09.120 - accomplishing, and if anyone needs to bring anything to the 00:55:09.120 --> 00:55:13.240 - table. I also make sure that if there is anything. 00:55:13.270 --> 00:55:16.630 - If I do, expect that Kevin is going to be bringing certain 00:55:16.630 --> 00:55:19.430 - information into a meeting, I will message him hours before 00:55:19.430 --> 00:55:22.230 - saying, hey, I have you bringing this information to this 00:55:22.230 --> 00:55:26.150 - meeting. Do you need? Do you have? Do you have that or do you 00:55:26.150 --> 00:55:30.070 - need help with that? You know? Is that going to be ready? do I 00:55:30.070 --> 00:55:33.430 - need that set? This meeting back? If not, but making sure to 00:55:33.430 --> 00:55:36.790 - set expectations with the people that will be in that meeting and 00:55:36.790 --> 00:55:38.470 - make sure they have their ducks 00:55:38.470 --> 00:55:43.496 - in a row. No, it's not something that we should have to do, but 00:55:43.496 --> 00:55:47.786 - it is something that we do need to do and it does help things go 00:55:47.786 --> 00:55:51.504 - a lot smoother if, for instance, I'm going to get Sterling on the 00:55:51.504 --> 00:55:54.364 - phone and we're going to be going through instances and 00:55:54.364 --> 00:55:58.082 - mappings for CII have sci on the phone. I need to let Sterling 00:55:58.082 --> 00:56:01.800 - now. Hey, you need to get in before hand and make sure you 00:56:01.800 --> 00:56:05.804 - have access to Sage X3. You need to make sure that you have the 00:56:05.804 --> 00:56:08.950 - local setup and that you have your information that is being 00:56:08.950 --> 00:56:12.668 - pulled in so that they can see the information they can see the 00:56:12.668 --> 00:56:14.457 - data. And we can see it in life 00:56:14.457 --> 00:56:20.887 - in real time. That it should be an expectation I give to 00:56:20.887 --> 00:56:24.105 - Sterling. But then also internal meetings are the same way. 00:56:24.850 --> 00:56:29.426 - Uhm, I do have escalations on here. If you have an issues with 00:56:29.426 --> 00:56:33.650 - the developer, it really should be poured into the PM. Oh and 00:56:33.650 --> 00:56:36.670 - developers manager. Edina, through teams that could be done 00:56:36.670 --> 00:56:37.990 - through email, whatever you 00:56:37.990 --> 00:56:42.395 - feel, is better. Usually you know I just sent a paying real 00:56:42.395 --> 00:56:45.935 - quick saying hey, I've got this concern. Is there anything I can 00:56:45.935 --> 00:56:50.065 - do to help or this person seems like they're a little out of it 00:56:50.065 --> 00:56:53.310 - this week? Is there something I don't know about and then 00:56:53.310 --> 00:56:56.555 - usually the manager will kick back. Oh hey, yeah it's cool. 00:56:56.555 --> 00:57:00.095 - Don't worry about it. Or no, I don't know. Thank you for 00:57:00.095 --> 00:57:01.570 - bringing that to my attention, 00:57:01.570 --> 00:57:07.412 - but yeah. Um, for client communication. I do have in 00:57:07.412 --> 00:57:12.802 - Basecamp things that have definitely helped me is I allow 00:57:12.802 --> 00:57:16.036 - the developers to respond to the 00:57:16.036 --> 00:57:20.900 - client correctly. Uh, not not all of my projects do I have 00:57:20.900 --> 00:57:24.100 - that on, but definitely in Basecamp. If a developer is 00:57:24.100 --> 00:57:27.940 - asking a question, I encourage them to go ahead and put that 00:57:27.940 --> 00:57:31.780 - information on base camp. Let the client see it, and then wait 00:57:31.780 --> 00:57:35.620 - for the response at respond with the client back and forth. I 00:57:35.620 --> 00:57:38.500 - think that it's important that they're getting the information 00:57:38.500 --> 00:57:42.980 - they need, and that allows me a lot more time to not be the 00:57:42.980 --> 00:57:45.590 - intermediary there. Summit 00:57:45.590 --> 00:57:46.790 - What was that? 00:57:47.520 --> 00:57:50.770 - Sorry, I was just agreeing. 00:57:50.770 --> 00:57:53.389 - Yeah, thank you. 00:57:53.390 --> 00:57:57.434 - But one a definite benefit in this is that this gives the 00:57:57.434 --> 00:58:00.467 - developers a little more ownership of the project, so 00:58:00.467 --> 00:58:04.848 - they have a little more onus on them to make sure they are 00:58:04.848 --> 00:58:07.881 - communicating well and getting the information they need. I 00:58:07.881 --> 00:58:11.925 - will say KB, Heather and Heather are fantastic at this and making 00:58:11.925 --> 00:58:15.969 - sure to communicate with the client. They even do it when I'm 00:58:15.969 --> 00:58:20.013 - out of the office like it's wonderful and it's made my life 00:58:20.013 --> 00:58:24.057 - so much easier. So just making sure to have that information in 00:58:24.057 --> 00:58:28.292 - there. And things that I don't think help is making sure that 00:58:28.292 --> 00:58:32.164 - the developer knows not to ever provide estimates aside from a 00:58:32.164 --> 00:58:35.684 - low, medium, high effort that should always come from a 00:58:35.684 --> 00:58:38.852 - project manager, and I think that's a general communication 00:58:38.852 --> 00:58:42.724 - outline. Is that all estimations should come from the PM and 00:58:42.724 --> 00:58:46.948 - should not come from a developer ever. And if you haven't set 00:58:46.948 --> 00:58:50.468 - that expectation with your developers, please do so as soon 00:58:50.468 --> 00:58:54.692 - as possible because that is one thing that will get you into. 00:58:54.710 --> 00:58:58.742 - In over your head, in way too deep, faster than anything that 00:58:58.742 --> 00:59:00.758 - I've ever seen in my life. 00:59:00.770 --> 00:59:04.839 - Yeah, it's it's not here it is there. It is there like a 00:59:04.839 --> 00:59:07.030 - default place where the developer should be 00:59:07.030 --> 00:59:10.473 - communicating with the client, or does it kind of differ based 00:59:10.473 --> 00:59:12.351 - on the client? 'cause I know 00:59:12.351 --> 00:59:15.793 - like base camp. Gotcha, OK? I'm just wondering 'cause I know a 00:59:15.793 --> 00:59:18.840 - teams channel can also be created for that client as well. 00:59:18.840 --> 00:59:21.887 - I just wonder if there should be one of the other. 00:59:21.900 --> 00:59:26.476 - We can create a client in teams and I do have clients that 00:59:26.476 --> 00:59:29.996 - communicate with me directly in teams and I definitely recommend 00:59:29.996 --> 00:59:34.220 - that all of that communication go on in base camp. The reason 00:59:34.220 --> 00:59:38.444 - for that is a client is sending direct messages to a developer 00:59:38.444 --> 00:59:41.612 - and not including the PM. That becomes an issue. 00:59:43.440 --> 00:59:47.844 - Yeah my I have two collaboration channels and in both I'm pretty 00:59:47.844 --> 00:59:52.615 - hard line about this is just for not even real questions. I just 00:59:52.615 --> 00:59:57.019 - make it about like quick follow UPS. Hey what's the status on 00:59:57.019 --> 01:00:00.689 - this or something like that? Just because those can overload 01:00:00.689 --> 01:00:04.726 - base camp but if there are questions or their estimates or 01:00:04.726 --> 01:00:08.396 - anything like that those shouldn't be in in a cloud. 01:00:08.560 --> 01:00:12.520 - Basecamp three has a ping feature that's pretty cool. I've 01:00:12.520 --> 01:00:14.500 - used that quite a bit. 01:00:14.500 --> 01:00:17.700 - Yeah, you could just ping 01:00:17.700 --> 01:00:22.396 - someone. Only work one way where is sometimes you want to have a 01:00:22.396 --> 01:00:25.776 - conversation with multiple people. I could be wrong on that 01:00:25.776 --> 01:00:27.128 - though now it works. 01:00:27.150 --> 01:00:30.920 - Uh, it's just like any chat protocol. I mean, if you want or 01:00:30.920 --> 01:00:34.690 - you would just create a thread and just add the right people to 01:00:34.690 --> 01:00:38.170 - it. I mean, that's what she would do in Basecamp. You could 01:00:38.170 --> 01:00:41.650 - do that. Well, that plant is saying, then is that when you 01:00:41.650 --> 01:00:46.000 - send a ping you can only send a pain to one person and you can't 01:00:46.000 --> 01:00:47.740 - say anything to three or four. 01:00:47.760 --> 01:00:53.402 - So yeah, and that can be handled however you want, but I just as 01:00:53.402 --> 01:00:57.029 - long as you're making sure I do encourage developer 01:00:57.029 --> 01:01:01.059 - communication to go slowly through base camp. I do allow. 01:01:01.690 --> 01:01:06.154 - Alright, do I don't mind not that I allow 'cause That's more 01:01:06.154 --> 01:01:09.502 - of a Asser Tatian of dominance. That's not true. 01:01:09.540 --> 01:01:13.140 - I do appreciate when there's emails going back and forth 01:01:13.140 --> 01:01:16.740 - between clients. For instance, tianji is an older client and 01:01:16.740 --> 01:01:21.060 - they don't have the base camp setup, and the idea of getting 01:01:21.060 --> 01:01:25.380 - the base camp gives me anxiety, but 'cause I don't know the 01:01:25.380 --> 01:01:28.543 - label. But I with the information if there's 01:01:28.543 --> 01:01:32.560 - information coming back and forth. I mean I can go and I can 01:01:32.560 --> 01:01:36.268 - say OK, so you're reading this data in this information to come 01:01:36.268 --> 01:01:40.285 - from us. And then I can go to Brendan and be like, Hey, 01:01:40.285 --> 01:01:43.684 - Brandon, What do we need to say here instead? Brandon is 01:01:43.684 --> 01:01:47.083 - included on those threads and he just sent the information back. 01:01:47.083 --> 01:01:50.791 - And if they need like a quick data pool from SQL 'cause 01:01:50.791 --> 01:01:53.263 - they're technically doesn't know how to use SQL. 01:01:54.020 --> 01:02:00.128 - Gulp. Um, then they can ask that Brandon Brandon can run it 01:02:00.128 --> 01:02:04.108 - real quick and have that information for them. So that 01:02:04.108 --> 01:02:10.355 - does help. As far as I paired programming with a client 01:02:10.355 --> 01:02:12.535 - information, this is where. 01:02:13.250 --> 01:02:17.444 - This is what you're talking about, Kyle. The expectation 01:02:17.444 --> 01:02:23.502 - should be set with the client. You should know if we have an 01:02:23.502 --> 01:02:28.162 - issue. We have a block, just call me immediately. Cool, 01:02:28.162 --> 01:02:30.492 - there's other people that like. 01:02:31.070 --> 01:02:34.515 - Like some of my clients, I have to schedule a meeting like 2, 01:02:34.515 --> 01:02:37.430 - two or three days from now because they are so busy. 01:02:38.180 --> 01:02:42.657 - Cool, no problem will be blocked longer, but that's that's you 01:02:42.657 --> 01:02:48.212 - decision. Uh, again in this you want to make sure that you uhm, 01:02:48.212 --> 01:02:50.378 - like, uh, kind of the meetings 01:02:50.378 --> 01:02:54.960 - information. Thanks Lee, I'm just kind of have that here but. 01:02:56.340 --> 01:02:59.544 - You should have the description and information information that 01:02:59.544 --> 01:03:03.460 - is expected as well within those paired programming. So if you're 01:03:03.460 --> 01:03:05.240 - doing it with a client. 01:03:06.550 --> 01:03:11.911 - I. I just copied and pasted. Can you tell that's great, um. 01:03:13.330 --> 01:03:26.296 - Prepared programming 01:03:26.296 --> 01:03:35.165 - on. With when you have technical 01:03:35.165 --> 01:03:38.275 - resources that don't connect the dots. When I have information 01:03:38.275 --> 01:03:42.007 - coming in from NetSuite and it doesn't, it's not in the same 01:03:42.007 --> 01:03:45.428 - format were wanting. It's on the same format we're expecting. I 01:03:45.428 --> 01:03:46.983 - really should at that point, 01:03:46.983 --> 01:03:51.485 - pull in. Other other resource like perceive a I need to have a 01:03:51.485 --> 01:03:54.510 - meeting with the Creek and say OK. Here's the mappings were 01:03:54.510 --> 01:03:57.260 - planning to do. This is the information we have. What 01:03:57.260 --> 01:04:00.285 - feedback do you have for us? They had absolutely nothing and 01:04:00.285 --> 01:04:04.918 - I'm like. Uh, this is a concern for me. Why are you? Why do you 01:04:04.918 --> 01:04:07.990 - not have anything? For like? Why are? Why do you have no 01:04:07.990 --> 01:04:10.038 - questions about everything that we just sent you? 01:04:10.800 --> 01:04:12.610 - So. 01:04:13.660 --> 01:04:21.076 - Anyway, so making sure that if there is an issue or a 01:04:21.076 --> 01:04:22.930 - complication within data 01:04:22.930 --> 01:04:27.010 - integration. Then that really should be handled in a meeting 01:04:27.010 --> 01:04:30.210 - and you really should set up paired programming and you 01:04:30.210 --> 01:04:33.730 - really should be on that call with the developers, making sure 01:04:33.730 --> 01:04:36.930 - to guide the conversation the way it needs to go. 01:04:36.960 --> 01:04:40.092 - But there is another PM resource from the client. You might want 01:04:40.092 --> 01:04:43.485 - them on there as well and just do a sync with them afterwards 01:04:43.485 --> 01:04:46.617 - to make sure. OK, here's what I understood. This is what you 01:04:46.617 --> 01:04:48.966 - understood. We're on the same page, good to go. 01:04:50.610 --> 01:04:54.562 - Uhm, I notice that a lot of times when you have those paired 01:04:54.562 --> 01:04:57.906 - programming's, you have to speak developer back to the client and 01:04:57.906 --> 01:05:02.162 - say OK, this is what they're at. This is what you know. This is 01:05:02.162 --> 01:05:05.810 - what Taylor means when he's saying This is he is this and 01:05:05.810 --> 01:05:07.330 - this. And this is the 01:05:07.330 --> 01:05:09.538 - expectation. So be prepared for 01:05:09.538 --> 01:05:13.530 - that. Um, one thing on the email already kind of talked about 01:05:13.530 --> 01:05:16.610 - this. The PM should always be copied. Goes without saying. I 01:05:16.610 --> 01:05:19.970 - think you all know that I don't want not telling you anything 01:05:19.970 --> 01:05:24.201 - you don't know. And then also just kind of meetings 01:05:24.201 --> 01:05:25.813 - information at letting them 01:05:25.813 --> 01:05:30.130 - know. Also, if you for a client communication, if you're having 01:05:30.130 --> 01:05:33.419 - a developer on a meeting to demo something or explain something 01:05:33.419 --> 01:05:37.605 - the best way to handle that is to have the developer on and set 01:05:37.605 --> 01:05:41.492 - that as the first agenda item, so then you can save the clients 01:05:41.492 --> 01:05:45.379 - budget by letting them go after the first 10 or 15 minutes and 01:05:45.379 --> 01:05:49.565 - then continue on with the rest of your call. So if you have a 01:05:49.565 --> 01:05:53.153 - feature that's a little complex, you can't quite demo it or you 01:05:53.153 --> 01:05:56.442 - have questions that need to be answered in a technical way. 01:05:57.070 --> 01:06:01.330 - You can feel free to bring that developer on at the beginning 01:06:01.330 --> 01:06:05.945 - and then move forward without them so that they can move on to 01:06:05.945 --> 01:06:08.075 - their next step or the mix. 01:06:08.700 --> 01:06:11.340 - Like about their last and you 01:06:11.340 --> 01:06:16.072 - well. Not have to ruin their budget to do so. 01:06:17.270 --> 01:06:18.110 - Um? 01:06:19.420 --> 01:06:22.610 - Oh yeah, so that I just put all that together today.