00:00:03.015 --> 00:00:08.082 Really, really powerful for the project management team to truly
00:00:08.082 --> 00:00:12.992 understand the nuance and the requirements and complexities of
00:00:12.992 --> 00:00:14.005 our projects.
00:00:15.305 --> 00:00:19.586 So we're going to have to really step it up and inspect what we
00:00:19.586 --> 00:00:23.734 expect and start doing some of our own QA. I'm not saying all
00:00:23.734 --> 00:00:27.814 of it. There is a QA line item that happens on every project
00:00:27.814 --> 00:00:31.092 and that can be given to developers. They should
00:00:31.092 --> 00:00:34.771 definitely be validating the work that they're putting
00:00:34.771 --> 00:00:38.919 forward and inspecting that and making sure that there are no
00:00:38.919 --> 00:00:42.799 regressions. So it's going to be a group effort. It's not
00:00:42.799 --> 00:00:45.675 something that's going directly to the PM.
00:00:46.105 --> 00:00:50.088 But it is something that I want all of us to be able to do. I
00:00:50.088 --> 00:00:54.199 want us to be able to pull up a ticket that's in code complete,
00:00:54.199 --> 00:00:58.247 read the ticket and go and make sure that what it's asking for
00:00:58.247 --> 00:01:02.037 is actively working on this site. If it's not, that's your
00:01:02.037 --> 00:01:05.891 cue to fail that and ask the developers what's going on. So
00:01:05.891 --> 00:01:09.681 there's a couple of things that I typically do during this
00:01:09.681 --> 00:01:10.195 process.
00:01:11.335 --> 00:01:13.825 Let me get Azure.
00:01:14.585 --> 00:01:18.598 Pulled up. Oh, good. I do have it up. OK, so I'm going to go
00:01:18.598 --> 00:01:22.874 through Max real quick and show you what I typically do with Max
00:01:22.874 --> 00:01:25.965 when I have tickets that are in code complete.
00:01:28.825 --> 00:01:33.586 So just ad hoc, I'm just looking at the Azure board. What I would
00:01:33.586 --> 00:01:38.130 typically do, rather than just going through the board itself,
00:01:38.130 --> 00:01:42.025 is go into. Does everyone have a code complete query?
00:01:44.265 --> 00:01:45.155 Everybody should.
00:01:45.625 --> 00:01:46.045 Yes.
00:01:47.045 --> 00:01:47.495 OK.
00:01:47.985 --> 00:01:48.915 I think so.
00:01:50.055 --> 00:01:53.899 OK, everybody should know how to do a code complete query for
00:01:53.899 --> 00:01:55.325 your specific projects.
00:01:55.405 --> 00:01:58.445 On before we go past that hands.
00:01:59.505 --> 00:02:00.015 Umm.
00:02:00.785 --> 00:02:01.465 Thank you, Daniel.
00:02:01.105 --> 00:02:04.775 If if you have one, if you have one, raise your hand.
00:02:05.655 --> 00:02:07.105 You don't over talking about.
00:02:07.755 --> 00:02:08.175 OK.
00:02:08.335 --> 00:02:12.443 I wrote an awesome nuclino on that. It's so good it'll change
00:02:11.155 --> 00:02:12.195 Hell yeah, you did.
00:02:12.443 --> 00:02:13.105 your life.
00:02:13.555 --> 00:02:16.665 There was a there was one and it was bad, and now it's good.
00:02:13.975 --> 00:02:15.645 Shameless plug.
00:02:14.245 --> 00:02:15.515 Yeah, that's how I made mine.
00:02:17.515 --> 00:02:17.835 OK.
00:02:18.975 --> 00:02:22.985 OK. So you would go through and you would grab your your code
00:02:22.985 --> 00:02:26.025 complete query. I'm sure I've got one in here.
00:02:27.435 --> 00:02:28.425 Queries.
00:02:32.285 --> 00:02:36.638 I've set them all to be various different projects, so I have a
00:02:36.638 --> 00:02:40.515 few of them, so give me just a minute. I will edit this.
00:02:42.855 --> 00:02:46.095 Take that out and I'm just going to do Max.
00:02:54.035 --> 00:02:58.145 Do I not have any code completes for Macs? Terrible.
00:03:03.095 --> 00:03:06.807 The process we're being shown works so well that there are
00:03:06.807 --> 00:03:08.065 literally none left.
00:03:11.025 --> 00:03:11.985 I got you, Steph.
00:03:11.195 --> 00:03:12.285 That is a potential.
00:03:11.805 --> 00:03:14.655 Ohh no, it's Steph. It's your work item type.
00:03:13.755 --> 00:03:15.555 Yeah, it's your work item type.
00:03:15.325 --> 00:03:15.705 Ohh.
00:03:17.355 --> 00:03:20.025 Ohh, got it. OK thanks.
00:03:19.655 --> 00:03:22.195 And then also your your tree.
00:03:24.275 --> 00:03:26.015 You might just wanted to.
00:03:25.745 --> 00:03:26.965 Just the flat tree.
00:03:27.585 --> 00:03:28.015 Yeah.
00:03:28.595 --> 00:03:28.795 OK.
00:03:30.255 --> 00:03:31.685 Oh yeah, yeah.
00:03:33.425 --> 00:03:38.175 Close top left hand side just above the end door and door.
00:03:39.095 --> 00:03:39.965 And or.
00:03:41.555 --> 00:03:41.955 Scott.
00:03:43.195 --> 00:03:43.695 But tree.
00:03:43.765 --> 00:03:47.615 Just up right, we're under with the editor is highlighted.
00:03:48.005 --> 00:03:48.295 Hmm.
00:03:48.965 --> 00:03:50.635 Yep, there we go. Flat list.
00:03:49.355 --> 00:03:51.345 There you go. Let's do that one Bing bong.
00:03:52.835 --> 00:03:58.167 I do have code completes. I knew I did OK, so I'm gonna go in and
00:03:58.167 --> 00:04:02.045 I'm going to look at these code complete items.
00:04:06.055 --> 00:04:09.970 So this is optimizing the search. This I know is a fail
00:04:09.970 --> 00:04:14.234 because it it's probably been sitting in code complete for a
00:04:14.234 --> 00:04:18.428 minute because I actually moved this over to Tim because it
00:04:18.428 --> 00:04:20.245 ended up being a back end.
00:04:23.085 --> 00:04:26.715 So I wonder if the Tim one has been closed.
00:04:32.935 --> 00:04:34.045 When that be?
00:04:37.055 --> 00:04:41.862 OK, so because this one got reassigned to Tim, I'm actually
00:04:41.862 --> 00:04:46.990 going to just close this because he has a new ticket. Well, Tim
00:04:46.990 --> 00:04:52.118 has a new user story assigned to him. So I'm gonna go ahead and
00:04:52.118 --> 00:04:56.925 close this and that will remove that from my code complete.
00:04:58.905 --> 00:05:01.395 And then I'm going to go back to my query.
00:05:02.615 --> 00:05:06.205 And e-mail confirmations so.
00:05:07.355 --> 00:05:11.307 With this we need to know that a user has successfully registered
00:05:11.307 --> 00:05:14.600 an account. They get a notification that they're quote
00:05:14.600 --> 00:05:18.253 has been updated. They get a notification that they're quote
00:05:18.253 --> 00:05:21.785 status has been updated and is shipping confirmation once.
00:05:23.065 --> 00:05:28.100 Epicor sinks the tracking number back in and that they also get
00:05:28.100 --> 00:05:32.820 an e-mail notification for passwords if it's been reset. So
00:05:32.820 --> 00:05:37.539 if I were going to go in and code complete this and kind of
00:05:37.539 --> 00:05:41.315 validate and test what would be my first steps.
00:05:44.625 --> 00:05:44.995 Kyle.
00:05:46.605 --> 00:05:51.349 I was gonna say, well, is this just verifying that the emails
00:05:51.349 --> 00:05:56.170 fire off or is this verifying what's in the emails as in their
00:05:56.170 --> 00:05:56.935 templates?
00:05:58.655 --> 00:06:01.175 I'm looking that each of these emails fire off.
00:06:01.735 --> 00:06:03.305 Ohh OK gotcha.
00:06:04.695 --> 00:06:07.985 And have an unrelated question. Sometime later, just whatever.
00:06:07.265 --> 00:06:07.665 OK.
00:06:08.705 --> 00:06:09.105 Trenton.
00:06:08.895 --> 00:06:11.555 Or it's related, but not specifically to this ticket.
00:06:11.825 --> 00:06:15.175 OK, come back to that Trenton. Your hands up, bud.
00:06:16.175 --> 00:06:21.243 So the first thing you would do is go to the stage or QA site
00:06:21.243 --> 00:06:24.185 and try to register for an account.
00:06:43.375 --> 00:06:43.885 So.
00:06:44.615 --> 00:06:45.885 The first thing I notice.
00:06:46.865 --> 00:06:49.565 Is that this form is very confusing.
00:06:59.085 --> 00:07:02.441 Yeah, I just read that as Stephanie Austin. Like your
00:07:02.441 --> 00:07:04.865 name? Stephanie Austin Johnson, Texas.
00:07:02.805 --> 00:07:03.455 Uh-huh.
00:07:05.345 --> 00:07:06.035 So.
00:07:08.375 --> 00:07:10.885 If I get my e-mail here.
00:07:12.695 --> 00:07:15.325 I can mark this one as code complete.
00:07:17.415 --> 00:07:20.544 But that means that I need to get another bug to update the
00:07:20.544 --> 00:07:20.805 form.
00:07:22.745 --> 00:07:23.695 Does that make sense?
00:07:25.805 --> 00:07:26.235 Yeah.
00:07:27.995 --> 00:07:29.565 Oh, did I get an e-mail?
00:07:32.445 --> 00:07:34.195 Yay. Ohh.
00:07:35.135 --> 00:07:40.205 Update the Fort. Well, yeah. If we update the form it should fix
00:07:40.205 --> 00:07:44.105 the very strange request that has been submitted.
00:07:46.495 --> 00:07:50.174 So we know that the emails are firing off at least four account
00:07:50.174 --> 00:07:53.738 registration, but that doesn't mean I'm necessarily done with
00:07:53.738 --> 00:07:54.255 this yet.
00:07:55.475 --> 00:07:59.725 So there's a couple of points where I am blocked.
00:08:00.945 --> 00:08:04.789 So I can't log in right now because of this workflow, which
00:08:04.789 --> 00:08:08.377 means I need to know this workflow. I need to know that
00:08:08.377 --> 00:08:11.901 because just because I registered doesn't mean that my
00:08:11.901 --> 00:08:15.937 account is officially set up. The workflow for this particular
00:08:15.937 --> 00:08:19.973 client is that they need to go into Epicor, set up the account
00:08:19.973 --> 00:08:22.215 to the correct business, and then.
00:08:23.535 --> 00:08:27.121 Think it over to Steph. Steph will then fire off a. Your
00:08:27.121 --> 00:08:30.959 account has been successfully set up. Go here to update your
00:08:30.959 --> 00:08:31.965 password e-mail.
00:08:33.275 --> 00:08:37.969 Once I get that, I can go in and register, so I can't test this
00:08:37.969 --> 00:08:42.663 ticket further, so I need to tag this in some way that I either
00:08:42.663 --> 00:08:47.283 need to get with the client to create my account, or I need to
00:08:47.283 --> 00:08:51.684 somehow go back into stuff into stuff admin and register my
00:08:51.684 --> 00:08:56.377 account in QA myself. So that's the next question is, well, how
00:08:56.377 --> 00:09:01.071 do I do that? So if you guys are not familiar enough with stuff
00:09:01.071 --> 00:09:05.472 to be able to do that, then you have to get with the client
00:09:05.472 --> 00:09:07.965 which is going to take more time.
00:09:08.445 --> 00:09:12.286 And block this ticket from being something that you can show them
00:09:12.286 --> 00:09:15.895 in a demo, so it's advantageous for you to know how to go and
00:09:15.895 --> 00:09:19.561 manipulate stuff so that you can actually complete this and go
00:09:19.561 --> 00:09:22.995 through and make sure that all of these steps are working.
00:09:24.605 --> 00:09:25.935 Kyle, your hand came up again.
00:09:26.525 --> 00:09:30.023 That you just nailed it on the head. I was like, yeah, even
00:09:30.023 --> 00:09:33.580 though the workflow might have a step that, you know, in the
00:09:33.580 --> 00:09:37.020 happy path might require the integration, you can still go
00:09:37.020 --> 00:09:40.634 into Seth Admin manipulate the data and still get that e-mail
00:09:40.634 --> 00:09:44.366 to fire off. The other thing is even if SMTP is not configured,
00:09:44.366 --> 00:09:47.864 you can still go in to set admin, look at the e-mail queues
00:09:47.864 --> 00:09:51.420 and verify that the system is trying to send out that e-mail
00:09:51.420 --> 00:09:54.918 just because we don't have an e-mail server set up yet, you
00:09:54.918 --> 00:09:57.775 can still go in and verify some of these things.
00:10:00.185 --> 00:10:02.135 Kyle, you wanna walk me through as if I'm 5.
00:10:03.015 --> 00:10:07.999 Yeah. So we'll just go into Seth Admin to the admin slash clarity
00:10:07.999 --> 00:10:09.585 ecommerce dash admin.
00:10:14.425 --> 00:10:15.205 Ohh.
00:10:17.745 --> 00:10:21.637 Of that might be the link is. Yeah. Take off it from inventory
00:10:18.795 --> 00:10:19.145 It's.
00:10:21.637 --> 00:10:22.625 to the end, the.
00:10:24.135 --> 00:10:24.945 Yippers.
00:10:25.125 --> 00:10:25.835 Trying.
00:10:37.265 --> 00:10:40.774 So one of the easier ways to kind of think about this
00:10:40.774 --> 00:10:44.219 especially well and it's something that we should be
00:10:44.219 --> 00:10:48.053 actively doing as we're building out the FSD, it should be
00:10:48.053 --> 00:10:52.082 something that we're thinking about as we're creating tickets
00:10:52.082 --> 00:10:56.111 is adding the basic acceptance criteria. So that when you get
00:10:56.111 --> 00:10:59.815 to this point, you know what it is you need to be doing.
00:11:02.465 --> 00:11:06.036 Ah, I have to go find the password because I have a new
00:11:06.036 --> 00:11:08.905 computer and LastPass is not working for me.
00:11:10.825 --> 00:11:11.695 Oh really?
00:11:12.645 --> 00:11:13.375 Ah.
00:11:14.655 --> 00:11:17.545 It's OK bad. I just haven't taken the time to.
00:11:18.725 --> 00:11:20.405 Configure everything properly yet.
00:11:22.365 --> 00:11:23.805 Happy to help if needed.
00:11:24.355 --> 00:11:27.765 Nah, I just need to sit down and do it instead of.
00:11:28.615 --> 00:11:29.355 Ignoring it.
00:11:30.005 --> 00:11:31.515 I can pester you if you want.
00:11:33.435 --> 00:11:34.655 I do love a good pastor.
00:11:33.505 --> 00:11:36.675 Just kidding. I know you do same.
00:11:51.665 --> 00:11:57.327 Where fit. Yep. Drop down the home drop down at the top and
00:11:57.327 --> 00:12:03.365 then over in the system section. The third one down on the left
00:12:03.365 --> 00:12:07.045 is e-mail queues and we should have a.
00:12:07.115 --> 00:12:10.535 Do you? That's a reset token.
00:12:11.475 --> 00:12:11.755 Uh.
00:12:13.165 --> 00:12:16.885 Oh, was that form built with action forms? Because I noticed
00:12:16.885 --> 00:12:20.422 that it says your form was submitted to the administrator
00:12:20.422 --> 00:12:23.715 for review, but it's not an actual set e-mail, is it?
00:12:25.275 --> 00:12:26.905 Excellent. Thank you.
00:12:30.415 --> 00:12:35.865 So if I needed to get into DNN to check this.
00:12:40.005 --> 00:12:43.191 Which I mean those we can verify pretty easy because we don't
00:12:43.191 --> 00:12:46.171 does that need SMTP setup or does action form has its own
00:12:46.171 --> 00:12:48.175 thing that it does its own thing with?
00:12:48.825 --> 00:12:51.465 You have to set up SMTP in DNN.
00:12:50.805 --> 00:12:52.235 OK. Gotcha.
00:12:57.225 --> 00:12:59.125 Does everyone know how to log into DNN?
00:13:03.755 --> 00:13:04.325 Hands.
00:13:09.865 --> 00:13:11.385 He don't know that I do.
00:13:11.635 --> 00:13:11.925 OK.
00:13:13.215 --> 00:13:15.825 And so I did that a little quick.
00:13:15.905 --> 00:13:20.188 These. So essentially there's two different ways to get to
00:13:20.188 --> 00:13:24.688 various admin areas within the platform. So DNN is .net nuke,
00:13:24.688 --> 00:13:29.333 it is our CRM. It is basically where the client can control all
00:13:29.333 --> 00:13:33.761 of their content and then we have, of course, the CEF admin,
00:13:33.761 --> 00:13:38.406 which is where we deal with all of the orders, all of that kind
00:13:38.406 --> 00:13:42.761 of stuff, updating products, administrating for categories,
00:13:42.761 --> 00:13:46.535 users, sales orders, invoices, quotes, all of that.
00:13:46.895 --> 00:13:47.905 Daniel, go ahead. But.
00:13:49.825 --> 00:13:52.605 I was trying my hammer sells up from the DNN login he.
00:13:52.195 --> 00:13:58.506 Ah, OK, uh, so there's the URL's are gonna be the same for all of
00:13:58.506 --> 00:14:04.720 our clients when we're in the QA and development cycle, it might
00:14:04.720 --> 00:14:10.744 change a little bit depending, but I don't know that I've ever
00:14:10.744 --> 00:14:16.480 had a client request that we change this F admin URL or the
00:14:16.480 --> 00:14:17.245 DNN URL.
00:14:18.465 --> 00:14:23.243 So to get it to DNN, it's the domain of the client and then
00:14:23.243 --> 00:14:28.420 forward slash login to get into CEF admin. It is the name of the
00:14:28.420 --> 00:14:33.118 client and then forward slash admin forward slash clarity,
00:14:33.118 --> 00:14:37.737 dash, ecommerce, dash admin and I would suggest those are
00:14:37.737 --> 00:14:42.755 actually located in the general channel under clarity ventures
00:14:42.755 --> 00:14:47.692 in the wiki under passwords, the SEV admin appended URL is in
00:14:47.692 --> 00:14:49.205 there and then DNN.
00:14:49.285 --> 00:14:52.785 Is just log in, so let me go ahead and add that to the to the
00:14:52.785 --> 00:14:54.535 wiki because it's not in there.
00:15:04.615 --> 00:15:08.166 So it's just an appendage on the URL at the end, so you can
00:15:08.166 --> 00:15:11.835 actually just copy paste that into any of your clients and it
00:15:11.835 --> 00:15:14.025 should get you to CEF admin and DNN.
00:15:15.285 --> 00:15:19.650 So once you're in here, Kyle, do you know where to check the SMTP
00:15:19.650 --> 00:15:21.435 settings? Or maybe Brandon?
00:15:26.115 --> 00:15:30.501 I think yeah. In the settings there is it under, it's not
00:15:30.501 --> 00:15:32.165 under server is is it?
00:15:34.555 --> 00:15:36.185 It might be. It's been a minute.
00:15:38.155 --> 00:15:42.755 But if you are spending a ton of time digging into this and you
00:15:42.755 --> 00:15:44.695 find that you're just. Yep.
00:15:43.405 --> 00:15:43.865 There it is.
00:15:45.835 --> 00:15:49.785 That we've got the SMTP and that we can look at the logs.
00:15:54.975 --> 00:15:59.271 Potentially it depends on how DNN is set up. This is an older
00:15:59.271 --> 00:16:03.635 version so but you can also test your SMTP settings from here.
00:16:07.485 --> 00:16:10.671 And see the e-mail that it's currently being set to, so you
00:16:10.671 --> 00:16:13.591 could change this. So if I wanted this to come to me I
00:16:13.591 --> 00:16:15.715 could change this to my e-mail address.
00:16:18.255 --> 00:16:22.365 If you're spending a ton of time, I don't want you to feel
00:16:22.365 --> 00:16:26.824 like you have to go through all of these steps in QA, reach out
00:16:26.824 --> 00:16:28.565 to myself to a developer.
00:16:30.225 --> 00:16:33.985 You know Brandon, Eric, anybody that if you have questions, we
00:16:33.985 --> 00:16:37.864 can do probably a quick dive to kind of review it. I would start
00:16:37.864 --> 00:16:39.475 with your development team.
00:16:41.335 --> 00:16:44.799 Her ticket, I would say no more than like 10 to 15 minutes
00:16:44.799 --> 00:16:48.381 validating what's going on just to make sure that you have a
00:16:48.381 --> 00:16:51.728 clear understanding. That way we're still protecting our
00:16:51.728 --> 00:16:55.310 project management time. We're still protecting that QA line
00:16:55.310 --> 00:16:59.126 item. I do want you guys to make sure that while you're doing QA
00:16:59.126 --> 00:17:02.884 on your site, you are logging it to the right item just to help
00:17:02.884 --> 00:17:06.290 make sure that you are being responsible with the EP line
00:17:06.290 --> 00:17:07.405 items as well, but.
00:17:08.115 --> 00:17:11.782 You know, keep it on average about 10 to 15 minutes per
00:17:11.782 --> 00:17:16.037 ticket depending on the level of complexity, which also leads me
00:17:16.037 --> 00:17:17.805 to another point, the more.
00:17:18.505 --> 00:17:23.644 Giant, you make your user stories the more in depth you
00:17:23.644 --> 00:17:25.295 have to get in QA.
00:17:25.935 --> 00:17:26.525 Yes.
00:17:26.065 --> 00:17:26.575 Because.
00:17:28.925 --> 00:17:32.266 And the longer you're repro cause you gotta write down
00:17:31.425 --> 00:17:31.945 Mm-hmm.
00:17:32.266 --> 00:17:36.092 exactly how to reproduce that issue as well. In the longer the
00:17:32.315 --> 00:17:32.925 Look.
00:17:36.092 --> 00:17:37.975 workflow, the longer the repro.
00:17:38.545 --> 00:17:40.515 And the more chances for failure.
00:17:40.855 --> 00:17:41.265 Yep.
00:17:41.345 --> 00:17:41.995 Umm.
00:17:43.145 --> 00:17:46.045 Remember what's the biggest the user story should.
00:17:46.155 --> 00:17:48.405 He, Amy.
00:17:52.485 --> 00:17:56.461 Umm well I'm thinking in connect brain. So like I've seen ones
00:17:55.315 --> 00:17:55.765 That's OK.
00:17:56.461 --> 00:18:00.248 that are 2024 for that. But in regards to staff I would say
00:18:00.248 --> 00:18:02.015 like nothing longer than 10.
00:18:02.655 --> 00:18:03.415 But I could be wrong.
00:18:03.725 --> 00:18:07.436 You're close. Yeah, I know. It's cool. And including Kinect, no
00:18:07.436 --> 00:18:09.755 user story should be more than 8 hours.
00:18:11.345 --> 00:18:13.895 If it's more than 8 hours, it should be split.
00:18:15.415 --> 00:18:19.091 Ideally nothing longer than four, but eight is the absolute
00:18:19.091 --> 00:18:22.584 longest any user story can or should be. We do have some
00:18:22.584 --> 00:18:23.625 allowance for it.
00:18:25.045 --> 00:18:28.445 But that is one of these, like now that we have Azure tickets
00:18:28.445 --> 00:18:31.791 being updated more frequently and we're getting this side of
00:18:31.791 --> 00:18:35.301 our, you know this one thread is kind of turning into the rope,
00:18:35.301 --> 00:18:38.756 one of the next big ones gonna be breaking user stories on The
00:18:38.756 --> 00:18:38.975 Reg.
00:18:39.625 --> 00:18:41.745 It should never be more than 8 hours.
00:18:39.965 --> 00:18:40.385 Mm-hmm.
00:18:45.515 --> 00:18:51.240 So if you've got a user story in CEF, and let's let's kind of
00:18:51.240 --> 00:18:53.825 jump over and look at a few.
00:18:53.905 --> 00:18:58.779 Umm, Charlie, do you think you've got anything for bid
00:18:58.779 --> 00:19:01.615 currently in QA I would imagine.
00:19:02.455 --> 00:19:06.589 Yeah, yeah, yeah. I got. I got all kinds of stuff that's in
00:19:06.589 --> 00:19:10.515 code complete waiting for invoicing or in QA waiting for
00:19:10.515 --> 00:19:12.995 me to go through it. So absolutely.
00:19:13.415 --> 00:19:16.545 OK, so in QA you said.
00:19:18.185 --> 00:19:22.250 Uh, you know what? It's probably deployed to QA. There wouldn't
00:19:22.250 --> 00:19:25.870 be much in QA because most of that I've gone through and
00:19:25.870 --> 00:19:26.505 pushed to.
00:19:26.625 --> 00:19:29.785 UM past QA or in UAT?
00:19:31.025 --> 00:19:35.435 All right. So let's dive in on one of these. UM, and I'm gonna
00:19:35.435 --> 00:19:38.515 actually, can you request control, Charlie?
00:19:39.635 --> 00:19:42.815 Let's drive through it, pick one and have you QA it.
00:19:49.865 --> 00:19:57.498 So the tricky thing will be for me to find one that is ready for
00:19:57.498 --> 00:20:01.255 QA, pickup schedule or invoices.
00:20:02.375 --> 00:20:03.575 And how would you know that?
00:20:05.135 --> 00:20:09.848 Umm, I know that because I've gotten blocked on on actually
00:20:09.848 --> 00:20:14.640 running QA for many of these because they require successful
00:20:14.640 --> 00:20:15.425 invoicing.
00:20:18.985 --> 00:20:19.485 Times.
00:20:24.885 --> 00:20:27.755 Because adding a seller requires successful invoicing.
00:20:31.695 --> 00:20:34.005 No, it does not. We could add a seller.
00:20:35.435 --> 00:20:36.045 Alright.
00:20:40.885 --> 00:20:45.161 Can we do something though? Because of everything that the
00:20:45.161 --> 00:20:48.495 share does, can I just do this on my desktop?
00:20:48.765 --> 00:20:49.795 Ohh 100%.
00:20:49.585 --> 00:20:52.623 And and switch the share out. I think it'll be easier for me to
00:20:52.623 --> 00:20:53.335 drive that way.
00:20:53.715 --> 00:20:53.985 Yeah.
00:20:55.275 --> 00:20:56.995 Let me stop real quick if I can.
00:20:59.245 --> 00:20:59.815 There we go.
00:21:02.925 --> 00:21:06.551 Quick question because that's actually segues into it. If if
00:21:03.045 --> 00:21:03.845 All right.
00:21:06.551 --> 00:21:10.057 you guys find regressions or anything like that, like it's
00:21:10.057 --> 00:21:13.920 not necessarily a user story and it's not necessarily associated
00:21:13.920 --> 00:21:17.367 with either the one you're testing or any other is in the
00:21:17.367 --> 00:21:21.111 project like what do you guys just leave it? Is that up to the
00:21:21.111 --> 00:21:24.558 developers or kind of who's associated with logging those
00:21:24.558 --> 00:21:24.855 bugs?
00:21:27.095 --> 00:21:28.985 So I'm sorry, Kyle, one more time.
00:21:29.385 --> 00:21:32.549 Like I deploy user story. Let's say it's for the shopping cart
00:21:32.549 --> 00:21:35.663 or for this registration but it breaks something else totally
00:21:35.663 --> 00:21:38.275 unrelated. It's a regression, something went wrong.
00:21:40.125 --> 00:21:43.429 It's not as associated with this user story directly, but it
00:21:43.429 --> 00:21:45.595 still broke another part of the system.
00:21:46.305 --> 00:21:48.355 But I see that happen a lot.
00:21:49.995 --> 00:21:55.155 So do you have like a specific example that you could?
00:21:54.525 --> 00:21:57.824 Like I was working on checkout and they were messing with the
00:21:57.824 --> 00:22:01.069 shipping provider but all of a sudden that shipping provider
00:22:01.069 --> 00:22:03.835 broke the shipping section of account registration.
00:22:06.485 --> 00:22:11.013 I would say that would just be logged as a new bug. Brandon, do
00:22:10.675 --> 00:22:11.175 Yep.
00:22:11.013 --> 00:22:12.215 you have any? OK.
00:22:12.025 --> 00:22:12.765 Newberg.
00:22:13.415 --> 00:22:16.516 And that's one that. So the PM is going to be kind of doing
00:22:16.516 --> 00:22:18.325 kind of those regressions as well.
00:22:19.585 --> 00:22:25.629 Potentially this can be a group effort, like if I I do want the
00:22:21.235 --> 00:22:21.685 OK.
00:22:25.629 --> 00:22:30.822 developers to have some time associated and Daniel I'm
00:22:30.822 --> 00:22:33.655 curious your thoughts on this.
00:22:33.815 --> 00:22:34.705 Yeah.
00:22:35.055 --> 00:22:39.848 Should we be adding time to each ticket for them to go in and
00:22:39.848 --> 00:22:44.719 validate the work or should we be doing like a AQA run through
00:22:44.719 --> 00:22:49.125 of the site at the end of the Sprint for each developer?
00:22:49.835 --> 00:22:52.785 Time is already built into their task to do that.
00:22:53.285 --> 00:22:54.075 Oh, OK.
00:22:55.655 --> 00:22:58.696 So we don't really need to do anything, we just need them to
00:22:58.696 --> 00:22:58.845 be.
00:22:59.525 --> 00:23:01.670 Well, that, yeah, that's part of the development part of
00:23:01.595 --> 00:23:01.975 Yeah.
00:23:01.670 --> 00:23:02.685 development should be that.
00:23:03.645 --> 00:23:05.615 You're not, you know, let's say I'm.
00:23:07.275 --> 00:23:08.745 What's a good analogy for this?
00:23:10.725 --> 00:23:16.836 Cooking right. You know, if I tell you I'm making you a
00:23:16.836 --> 00:23:23.165 heaping that of posole, right, which I'm doing right now.
00:23:20.955 --> 00:23:21.525 Hmm.
00:23:23.585 --> 00:23:28.259 Uh, and I make it for you and I drop it off at your house and
00:23:28.259 --> 00:23:32.255 you go to taste it and there's no salt in it at all.
00:23:33.025 --> 00:23:36.416 Right. Did I make you posole or did I just make you a bunch of
00:23:36.416 --> 00:23:37.115 ****** broth?
00:23:39.725 --> 00:23:43.515 You know, like and that's the same situation with developing
00:23:43.515 --> 00:23:47.430 if if someone just is throwing code into a repository, sending
00:23:47.430 --> 00:23:50.972 it up in the PR and then hoping for the best, that's not
00:23:50.972 --> 00:23:51.655 developing.
00:23:53.505 --> 00:23:56.330 Yeah, who's doing the taste test while you're cooking it? You
00:23:56.330 --> 00:23:57.925 know, making sure it's up to spec.
00:23:56.475 --> 00:23:57.035 Me.
00:23:57.795 --> 00:24:01.500 Yeah, I'm tasting my broth, making sure my stuff on point,
00:23:58.975 --> 00:23:59.425 Yep.
00:23:59.205 --> 00:24:00.085 As you do it.
00:24:01.500 --> 00:24:02.065 you know.
00:24:03.605 --> 00:24:06.525 That's part of the whole. That's part of development.
00:24:07.165 --> 00:24:08.195 OK, beautiful.
00:24:07.905 --> 00:24:11.339 Yeah. And I don't, I don't. I don't wanna try to break
00:24:11.339 --> 00:24:15.335 everyone's brain. But I do wanna give you guys something that I
00:24:15.335 --> 00:24:19.206 say to the developers. If we gave our clients two options, we
00:24:19.206 --> 00:24:22.952 can use Azure and Basecamp and all this cool stuff and they
00:24:22.952 --> 00:24:26.324 would get like a mediocre website that may or may not
00:24:26.324 --> 00:24:30.320 work. Or we can tell them that we just handwrite everything and
00:24:30.320 --> 00:24:34.253 we send it through snail mail to communicate amongst our team.
00:24:34.253 --> 00:24:36.875 But they're gonna have a perfect website.
00:24:37.085 --> 00:24:38.045 Which one would they choose?
00:24:41.655 --> 00:24:42.985 They want the perfect site.
00:24:43.295 --> 00:24:46.268 They want the perfect site. They don't care about this. They
00:24:46.268 --> 00:24:49.387 don't they they could not care less about what is on the screen
00:24:49.387 --> 00:24:50.215 right now, right?
00:24:50.705 --> 00:24:54.588 Umm, so when it comes to things like bug tickets like we care
00:24:54.588 --> 00:24:58.658 internally for a processes, but we need to learn to be adaptable
00:24:58.658 --> 00:25:02.603 and flexible. The worst thing one of the worst things that the
00:25:02.603 --> 00:25:06.423 development team can do is just say ohh this is what my task
00:25:06.423 --> 00:25:10.369 tells me to do. This is what I'm going to do. I'm not gonna do
00:25:10.369 --> 00:25:11.245 anything else.
00:25:12.445 --> 00:25:15.601 When that happens, they're going to go to the site and they're
00:25:15.601 --> 00:25:18.807 gonna notice something is wrong. Like with that form. Stephanie
00:25:18.807 --> 00:25:21.963 was looking at the registration form, and a developer may look
00:25:21.963 --> 00:25:24.869 at that, know that something's wrong and not say anything
00:25:24.869 --> 00:25:28.175 because they don't have a ticket for it. So why should they care?
00:25:28.995 --> 00:25:32.723 And carrying that logic forward when it comes to QA stuff, if
00:25:32.723 --> 00:25:36.571 there's a regression and it's a single regression and you think
00:25:36.571 --> 00:25:40.419 in and, I'm just gonna kind of give someone kudos and call them
00:25:40.419 --> 00:25:44.208 out in a positive way here, I think that Charlie would be able
00:25:44.208 --> 00:25:48.116 to to be really good at this. If you think you could just hop on
00:25:48.116 --> 00:25:51.543 a call with Justin Sacco and say, hey, look, I was going
00:25:51.543 --> 00:25:52.565 through the site.
00:26:08.085 --> 00:26:08.675 Umm.
00:26:08.735 --> 00:26:12.322 Going against the budget, so one of the things that we have to do
00:26:12.322 --> 00:26:15.311 with this is learn to be flexible and adapt. There are
00:26:15.311 --> 00:26:17.865 times where bug tickets make sense, obviously.
00:26:19.765 --> 00:26:23.178 One of the really cool things that we did at the end of a
00:26:23.178 --> 00:26:27.003 product Sprint and I think Eric has adapted and they still do it
00:26:27.003 --> 00:26:30.534 as he just gets in a working session with the developers at
00:26:30.534 --> 00:26:34.182 the end of the Sprint and he's like, OK, this is what we need
00:26:34.182 --> 00:26:34.535 to do.
00:26:35.855 --> 00:26:39.324 And they get in a working session together and they just
00:26:39.324 --> 00:26:43.219 work on the site. And if the you guys's PM's would do that more
00:26:43.219 --> 00:26:46.809 frequently with the dev team, I mean Daniel could tell you
00:26:46.809 --> 00:26:50.339 stories about him and Jesse working on GLV and doing that
00:26:50.339 --> 00:26:53.929 kind of thing. And other PMS have done it too. But that is
00:26:51.845 --> 00:26:52.415 Yeah.
00:26:53.929 --> 00:26:57.703 the most powerful thing that you're gonna do. And I mean does
00:26:57.703 --> 00:27:01.536 does that developer have a task that says hang out with Daniel
00:27:01.536 --> 00:27:05.005 and that call and do random stuff, you know? Not really.
00:27:05.085 --> 00:27:08.655 But is that going to make the client happy? Yeah, it is.
00:27:09.085 --> 00:27:10.875 And you do just bake it into that.
00:27:09.515 --> 00:27:13.608 Can I just reinforce that with like all the credibility that I
00:27:13.608 --> 00:27:17.441 can possibly weigh in with, like, whatever credibility you
00:27:16.475 --> 00:27:17.835 I think that's a good amount.
00:27:17.441 --> 00:27:18.285 think I have?
00:27:19.315 --> 00:27:21.745 Just 100% agree with that.
00:27:22.955 --> 00:27:26.254 Because because the it's a couple different things too,
00:27:26.254 --> 00:27:30.084 right? It's one you're getting, like, just on a pure personality
00:27:30.084 --> 00:27:33.560 basis, you're going to spend time with your developers and
00:27:33.560 --> 00:27:35.445 everyone who works here is cool.
00:27:36.355 --> 00:27:40.199 You know, like it's it's. Yeah, I suck. But everyone else is
00:27:36.845 --> 00:27:37.955 Umm hmm.
00:27:37.425 --> 00:27:38.385 That Daniel guy.
00:27:40.199 --> 00:27:40.955 pretty cool.
00:27:42.475 --> 00:27:45.582 But so it's that, which is fun. It does make the work day more
00:27:45.582 --> 00:27:48.344 fun, and there's just no other way around that. I know.
00:27:48.344 --> 00:27:51.401 Sometimes it's like I'd rather work on these little tasks and
00:27:51.401 --> 00:27:54.508 listen to my music right now, which I get. I do that, I get my
00:27:54.508 --> 00:27:55.445 weird little holes.
00:27:56.565 --> 00:28:00.417 But working with developers is fun. Secondly, you learn the
00:28:00.417 --> 00:28:04.461 product itself, right? So you learn what you're making for the
00:28:04.461 --> 00:28:08.377 client because you're actively queuing it. So when something
00:28:08.377 --> 00:28:12.036 doesn't work, you don't the client. It's not telling you
00:28:12.036 --> 00:28:16.209 you're telling the client, hey, this isn't working just yet, but
00:28:16.209 --> 00:28:20.125 it is going this way. Working with the developers, you learn
00:28:20.125 --> 00:28:23.848 to debug better and faster. You learn to make better user
00:28:23.848 --> 00:28:25.645 stories, better bug tickets.
00:28:26.035 --> 00:28:29.185 It's invaluable, absolutely invaluable.
00:28:27.905 --> 00:28:28.375 Uh-huh.
00:28:31.755 --> 00:28:32.425 What's up, Mickey?
00:28:31.815 --> 00:28:33.725 Uh, 100%.
00:28:34.765 --> 00:28:38.224 I just had a question. I know we've generally been trying to
00:28:38.224 --> 00:28:41.797 avoid meeting tickets, bucket tickets that we don't know we're
00:28:41.797 --> 00:28:45.256 gonna use, but is this what you're describing? A good reason
00:28:45.256 --> 00:28:48.716 for us to utilize that? Because if we're gonna need to, say,
00:28:48.415 --> 00:28:48.955 Yeah.
00:28:48.716 --> 00:28:52.345 grab an hour of Justin Sacco's time to sit with him, I mean, we
00:28:51.075 --> 00:28:51.795 Yeah.
00:28:52.345 --> 00:28:55.464 need to plan that into the Sprint, right? So, like, we
00:28:55.155 --> 00:28:55.885 Yeah.
00:28:55.464 --> 00:28:57.165 should be doing that for that.
00:28:57.475 --> 00:29:01.345 100% dude. Yeah, like you can just set that up and like, like
00:28:57.645 --> 00:28:58.215 So.
00:28:59.295 --> 00:28:59.635 Cool.
00:28:59.315 --> 00:28:59.605 If.
00:29:01.345 --> 00:29:05.278 I said, those meeting tickets and bucket tickets and stuff are
00:29:05.278 --> 00:29:07.275 super bunk. But let's say, like.
00:29:08.445 --> 00:29:11.781 You know, this is what I was doing with Jesse when we're like
00:29:11.781 --> 00:29:14.954 finishing at UAT and GLV was, I would put something on his
00:29:14.954 --> 00:29:17.375 calendar like hey, next Tuesday from 2 to 5.
00:29:18.125 --> 00:29:21.951 You know, and me as the PM that two to five time wasn't fully on
00:29:21.951 --> 00:29:25.599 GLV, but I would just have that and I'd have my list of small
00:29:25.599 --> 00:29:29.013 bug fixes that don't really require their own tasks every
00:29:29.013 --> 00:29:32.897 time. You know, cuz it's like we said earlier, sometimes creating
00:29:32.897 --> 00:29:36.192 all those tasks is more time than it would take to just
00:29:36.192 --> 00:29:39.665 bullet them out, know what's going on there. And then just
00:29:39.665 --> 00:29:42.195 sit in the call and work on them with him.
00:29:43.335 --> 00:29:46.653 So I would do that. I put that on his calendar. That would be
00:29:46.653 --> 00:29:49.863 locked in for him. And then I would go to that meeting with
00:29:49.863 --> 00:29:53.235 that list. And I knew the repro steps he would do the fixes on
00:29:53.235 --> 00:29:56.659 QA, push the code right then I would QA them as he's working on
00:29:56.659 --> 00:30:00.137 the next thing. So it's a 3 hour task, but it's not a three hour
00:30:00.137 --> 00:30:02.545 task for me because we know the PM time can.
00:30:02.645 --> 00:30:06.538 Uh, explode a bit, right? So for me, I'm basically just reading
00:30:06.538 --> 00:30:10.127 those out. I'm working on completely other things. It ends
00:30:10.127 --> 00:30:13.595 up being about, you know, an hour or so of GLV time, but
00:30:13.595 --> 00:30:17.305 that's for QA. That saves me time from making 1000 miniscule
00:30:17.305 --> 00:30:18.035 bug tickets.
00:30:18.775 --> 00:30:22.931 Are, as Brendan would call them, little chicken bones. We get
00:30:22.931 --> 00:30:27.153 stuff done. I know my project really well. I know it works. So
00:30:27.153 --> 00:30:30.035 when I sign off I'm on Basecamp, you know.
00:30:30.525 --> 00:30:33.327 But that client was very particular, so sometimes it
00:30:33.327 --> 00:30:36.445 would come back, but by and large, you know, you know, you
00:30:36.445 --> 00:30:37.555 know what's going on.
00:30:38.575 --> 00:30:42.218 And so you have that confidence and it helps your budget, helps
00:30:42.218 --> 00:30:43.925 everything. Sorry dietra done.
00:30:44.005 --> 00:30:47.594 No, that was beautiful. So Trenton and Jessica, that's
00:30:47.594 --> 00:30:51.510 essentially what we did with DERM the other days. So Justin
00:30:51.510 --> 00:30:55.556 was going in and fixing some of those small things kind of in
00:30:55.556 --> 00:30:59.733 the moment that we were able to review with the client. There's
00:30:59.733 --> 00:31:03.909 a couple that he still needs to do, but that's essentially what
00:31:03.909 --> 00:31:06.715 we were doing yesterday with that meeting.
00:31:07.375 --> 00:31:13.544 And Jessica, this is gonna be incredibly powerful for you with
00:31:13.544 --> 00:31:13.935 ADI.
00:31:16.185 --> 00:31:18.305 So definitely something to keep in mind there.
00:31:20.785 --> 00:31:23.565 Got it. Yeah. I I've already caught on that. She's very.
00:31:23.825 --> 00:31:27.104 Uh hours conscious, but she also wants to make sure that we're
00:31:27.104 --> 00:31:30.331 taking care of everything for them, but then they go and make
00:31:30.331 --> 00:31:32.465 sure it's all good on their end as well.
00:31:32.965 --> 00:31:38.314 100% Yep. Absolutely sorry, Charlie, back to your your QA
00:31:37.875 --> 00:31:43.673 No, no, quite alright. So So what I have up on screen now is
00:31:38.314 --> 00:31:38.775 here.
00:31:43.673 --> 00:31:48.425 the ticket which is front end for adding sellers.
00:31:49.785 --> 00:31:53.520 So alright, our description is the affiliate exporter should
00:31:53.520 --> 00:31:57.316 have UI to set up sellers, not necessarily sub affiliates and
00:31:57.316 --> 00:32:00.989 associate commissions to a seller. And then it has a screen
00:32:00.989 --> 00:32:03.315 shot that's too small for me to read.
00:32:04.355 --> 00:32:07.655 So I got a new tab with the screenshot.
00:32:10.385 --> 00:32:11.095 And.
00:32:12.175 --> 00:32:18.146 Then I'm over here, logged into the only place that I know in
00:32:18.146 --> 00:32:23.924 the X portal to update any kind of a user, whether it be an
00:32:23.924 --> 00:32:29.798 affiliate, a sub affiliate, an admin, or a seller. Right now
00:32:29.798 --> 00:32:35.961 that is all driven by the user tab and what I'm seeing is I can
00:32:35.961 --> 00:32:36.635 create.
00:32:37.435 --> 00:32:38.125 A user.
00:32:39.675 --> 00:32:48.265 And I can assign many types, but I do not see a type of seller.
00:32:49.955 --> 00:32:55.995 And I see unrelated information on status, but I get nothing
00:32:55.995 --> 00:32:58.965 that says I can make a seller.
00:33:00.065 --> 00:33:02.655 So and my layout.
00:33:03.555 --> 00:33:08.805 Does not in any way match the screenshot so.
00:33:10.215 --> 00:33:14.425 Generally speaking, this would fail QA on multiple levels.
00:33:15.165 --> 00:33:15.735 Umm.
00:33:17.015 --> 00:33:19.265 And so I'm going to.
00:33:20.805 --> 00:33:22.755 Oh yeah, it's cute old.
00:33:20.875 --> 00:33:21.875 Hold hold.
00:33:23.085 --> 00:33:27.377 Halt. The next thing I want you to do is go over to where it
00:33:27.377 --> 00:33:31.529 says development and click on that so that we can see that
00:33:31.529 --> 00:33:34.765 drop down and see if there's a PR associated.
00:33:37.365 --> 00:33:39.405 Or is it under deployments? Check both.
00:33:38.935 --> 00:33:40.455 It is under deployment, sorry.
00:33:40.285 --> 00:33:40.555 Yep.
00:33:42.395 --> 00:33:48.053 So I don't see that there is a deployment or a PR linked to
00:33:48.053 --> 00:33:53.805 this. So now what would be my next step before failing that?
00:33:53.885 --> 00:33:59.021 So the other mitigating factor is that there is a ticket, there
00:33:59.021 --> 00:34:03.274 is a line here in the description referencing a Miro
00:34:03.274 --> 00:34:03.755 board.
00:34:04.795 --> 00:34:06.145 That I can't get to.
00:34:06.855 --> 00:34:07.185 OK.
00:34:07.215 --> 00:34:12.281 So what I would do generally speaking, because failing QA on
00:34:12.281 --> 00:34:17.348 a on an item generally like like Brandon was saying, it just
00:34:17.348 --> 00:34:22.248 creates a loop of additional work. Now is I'm gonna hit up
00:34:22.248 --> 00:34:26.982 Michael and say, hey, what's going on here? What was the
00:34:26.982 --> 00:34:31.799 status of this, where, what and where is the actual work?
00:34:31.799 --> 00:34:36.865 Because what I'm seeing to the best of my knowledge on this.
00:34:37.145 --> 00:34:41.850 It doesn't match up in any way with the description and the
00:34:41.850 --> 00:34:46.711 ticket, and it's so far away that it doesn't doesn't pass the
00:34:46.711 --> 00:34:51.180 sniff test. I think there's something up I will say that
00:34:51.180 --> 00:34:56.042 when we open this up, there was A tag on it, not yet testable
00:34:56.042 --> 00:34:56.355 and.
00:34:57.255 --> 00:35:01.227 I also know separate from anything listed here that we
00:35:01.227 --> 00:35:05.633 need to do some rewrites on the exportable to change it from
00:35:05.633 --> 00:35:10.111 brands to stores, so potentially there's something about this
00:35:10.111 --> 00:35:14.661 that Michael's got all wrapped up in that and before I fail it
00:35:14.661 --> 00:35:19.066 cause right now I don't know what I would put in my notes to
00:35:19.066 --> 00:35:23.689 Michael for subsequent work. I would ping him in a chat and say
00:35:23.689 --> 00:35:27.805 help me out. What do I need to do to get you to a point?
00:35:27.885 --> 00:35:29.315 Where this pass is QA.
00:35:30.195 --> 00:35:33.797 And another point to add to that, Charlie, I would even go
00:35:33.797 --> 00:35:37.521 one step further and in that user story right there, it says
00:35:37.521 --> 00:35:41.305 and associate commissions to a seller that is only something.
00:35:39.995 --> 00:35:41.865 Which is like a whole different user story.
00:35:42.095 --> 00:35:44.921 That is something that acquit, bid does and is totally
00:35:44.921 --> 00:35:48.158 unrelated to the X portal that they're affiliates are going to
00:35:48.158 --> 00:35:51.395 be using. So I'm not even sure that that's something you would
00:35:51.395 --> 00:35:54.631 test and the X portal, that's might be something that they use
00:35:54.631 --> 00:35:57.457 the admin portal for whenever they're setting up a new
00:35:57.457 --> 00:36:00.694 auctioneer, a new seller, and they're getting their Commission
00:36:00.694 --> 00:36:03.623 set up and then the exporters for creating the auctions,
00:36:03.623 --> 00:36:06.654 putting in the lots, things like that. But they the seller
00:36:06.654 --> 00:36:09.788 doesn't have a way to control their own commissions, so that
00:36:09.788 --> 00:36:12.665 shouldn't be in the dashboard or at least the X portal.
00:36:13.165 --> 00:36:14.085 For what that's worth.
00:36:15.815 --> 00:36:16.995 That is fair point.
00:36:18.665 --> 00:36:20.775 Which would take us to and and honestly.
00:36:21.605 --> 00:36:22.715 That could be.
00:36:23.735 --> 00:36:26.804 The thing that Michael came back with in response as he could
00:36:26.804 --> 00:36:29.824 say? Ohh well yeah. Like you can make a user but what you're
00:36:29.824 --> 00:36:32.942 talking about what you're trying to do there. I just went into
00:36:32.942 --> 00:36:33.635 the wrong one.
00:36:35.095 --> 00:36:35.885 Is.
00:36:36.855 --> 00:36:40.948 Like, that's not where you would do that. Well, if that's the
00:36:40.948 --> 00:36:45.239 case, then he might redirect me here, just as Kyle mentioned. So
00:36:45.239 --> 00:36:48.275 we'll go into this and we'll see what we get.
00:36:50.915 --> 00:36:54.767 And one thing I wanna point out real quick cause Charlie was
00:36:54.767 --> 00:36:58.745 talking about exporting and I'm sure some people are like what
00:36:57.405 --> 00:36:57.785 Yeah.
00:36:58.745 --> 00:37:02.533 so it's it's really just it's just another website that the
00:37:02.533 --> 00:37:06.637 client needs for other users to be able to log in and do things.
00:37:06.637 --> 00:37:10.489 In this case affiliates are gonna log in and create auctions
00:37:10.489 --> 00:37:14.277 on one site and then users like any of us will log into the
00:37:14.277 --> 00:37:17.055 storefront and actually bid on those items.
00:37:18.715 --> 00:37:21.545 You can kind of think of it as a.
00:37:22.635 --> 00:37:27.375 A permission based dashboard so that they have admin access but
00:37:27.375 --> 00:37:32.188 not the keys to the Kingdom. So they're a slightly elevated role
00:37:32.188 --> 00:37:33.965 that has their own site.
00:37:37.695 --> 00:37:40.285 All right. And having done all of that.
00:37:44.285 --> 00:37:48.741 Custom this would not be valid data, but we're throwing
00:37:48.741 --> 00:37:53.753 something in here and it still won't let me, at least under my
00:37:52.985 --> 00:37:53.485 It's.
00:37:53.753 --> 00:37:57.095 permissions manipulate any of this which?
00:37:54.555 --> 00:37:55.405 Yeah, it.
00:37:56.125 --> 00:37:59.422 You might need to start at the account level because I think
00:37:59.422 --> 00:38:02.664 the account type is something that my control, that not the
00:38:02.664 --> 00:38:05.852 potentially not the user type. So if you go to new account
00:38:05.852 --> 00:38:09.257 it'll create a new user whenever you create a new account, 2nd
00:38:09.257 --> 00:38:12.553 row, third one over. Oh yeah, there you go. That's way to do
00:38:12.553 --> 00:38:12.715 it.
00:38:15.735 --> 00:38:18.294 But yeah, you might be able to go in there and create an
00:38:18.294 --> 00:38:21.076 account and then you have a type drop down where you can then
00:38:21.076 --> 00:38:23.365 select. I don't know if they have it in the types.
00:38:24.415 --> 00:38:26.405 Or in, uh, the roles.
00:38:28.225 --> 00:38:28.795 So.
00:38:37.125 --> 00:38:37.995 I was that busted.
00:38:39.535 --> 00:38:44.745 Well, it looks problematic. What this tells me is is.
00:38:47.025 --> 00:38:50.453 It didn't make it clearer. It meant I have more questions for
00:38:50.453 --> 00:38:50.895 Michael.
00:38:51.235 --> 00:38:51.695 Uh-huh.
00:38:52.165 --> 00:38:56.251 And ultimately like this is the point we frankly we are already
00:38:56.251 --> 00:39:00.274 past the point at which from a QA standpoint, I would have cut
00:39:00.274 --> 00:39:03.977 bait and said, hey, Michael, help me out, throw me a bone
00:39:03.977 --> 00:39:06.275 here. What do I need to do on this?
00:39:06.445 --> 00:39:06.805 Yep.
00:39:08.185 --> 00:39:12.991 And the smaller to Daniel's prior point about keeping the
00:39:12.991 --> 00:39:18.212 keeping the user stories small, the smaller the user story is,
00:39:18.212 --> 00:39:23.432 the more likely it's going to pass and I can push it along the
00:39:23.432 --> 00:39:28.404 process towards UAT, leaving smaller pieces hung up waiting
00:39:28.404 --> 00:39:33.459 for QA I if if I have a there's a user story floating around
00:39:33.459 --> 00:39:38.265 somewhere in the backlog that's got like 40 points in it.
00:39:38.375 --> 00:39:42.415 And I'm like, alright, I guarantee this is failing. I'm
00:39:42.415 --> 00:39:46.600 just I need to go through and find out why, but 90% of it
00:39:46.600 --> 00:39:51.073 works as designed and it's and so small user stories help you
00:39:48.365 --> 00:39:49.245 Exactly.
00:39:51.073 --> 00:39:55.401 focus. The other thing is that the bigger the user story is
00:39:55.401 --> 00:39:59.369 like the hours estimated increase in a linear fashion.
00:39:59.369 --> 00:40:03.265 But the error rate on those estimates is exponential.
00:40:02.235 --> 00:40:02.455 Yeah.
00:40:03.615 --> 00:40:04.085 Yes.
00:40:05.205 --> 00:40:09.075 Yeah. Yes. No, you're you're you're making me.
00:40:05.465 --> 00:40:08.375 Sorry, I'm gonna try and step off my soapbox, but that's.
00:40:09.845 --> 00:40:14.235 Snap over here in a good way. Snap my fingers, not my brain.
00:40:17.065 --> 00:40:18.615 Could go either way.
00:40:18.865 --> 00:40:22.325 So my next thing would be to say.
00:40:23.055 --> 00:40:28.306 Either, uh. Let's see. Copy link address during the work day, I'd
00:40:28.306 --> 00:40:33.238 flip over to teams, but at well Hell, it's sent central time.
00:40:33.238 --> 00:40:38.171 It's only 330. So my next thing would be to flip to teams and
00:40:38.171 --> 00:40:42.705 hit up Michael and say, what can you tell me about this?
00:40:43.495 --> 00:40:43.835 Mm-hmm.
00:40:45.665 --> 00:40:49.045 But I that's I'm not sharing that window, so you won't see
00:40:49.045 --> 00:40:49.675 that piece.
00:40:50.195 --> 00:40:52.775 Kudos. Kudos. Absolutely.
00:40:51.985 --> 00:40:56.279 Yeah. And I and I just, I just wanna add to that like in this
00:40:56.279 --> 00:41:00.642 instance, if I was Charlie, I would, I would ping Michael, but
00:41:00.642 --> 00:41:04.935 it would be an important ping. Can you please help on a call?
00:41:05.905 --> 00:41:08.957 And that's what I would do, because you're going to get to
00:41:08.957 --> 00:41:12.319 the bottom of this a lot quicker if you just hop on the call and
00:41:12.319 --> 00:41:15.422 actually talk to the person, I mean, pinging them on teams.
00:41:15.422 --> 00:41:18.629 Obviously, if you have other stuff going on or you have other
00:41:18.629 --> 00:41:21.215 meetings that you have to jump into is fine, but.
00:41:22.915 --> 00:41:25.645 Hopping on a call is gonna be the easiest way to resolve that.
00:41:26.725 --> 00:41:30.679 Yep, because then you can run through it together with the
00:41:30.679 --> 00:41:35.034 developer and show them what it is you're seeing, which is gonna
00:41:35.034 --> 00:41:38.988 spark all sorts of developer brain ideas and kind of guide
00:41:38.988 --> 00:41:43.344 them. And it it's also twofold, because it's gonna help get them
00:41:43.344 --> 00:41:46.895 into the mindset too, of being more proactive about.
00:41:47.835 --> 00:41:52.178 Validating the work that they're completing. So overall, while it
00:41:52.178 --> 00:41:56.521 may be a bit of a lift up front, this transition and this sort of
00:41:56.521 --> 00:42:00.732 shift in our mindsets and really getting more into the weeds on
00:42:00.732 --> 00:42:04.351 QA is going to have a net benefit win for you, for the
00:42:04.351 --> 00:42:08.628 developer and for the client so that everybody is playing on the
00:42:08.628 --> 00:42:12.642 same page. They're they don't want to have to jump on a call
00:42:12.642 --> 00:42:16.524 with you every couple of days because you're going through
00:42:16.524 --> 00:42:20.670 something. So they're going to start inspecting the work a lot
00:42:20.670 --> 00:42:21.525 more closely.
00:42:21.835 --> 00:42:24.927 So that those tickets when you go through and validate them,
00:42:24.927 --> 00:42:28.222 you can just say Yep that works and then it's going to be easier
00:42:28.222 --> 00:42:31.466 for you to create demos for your client, which is going to make
00:42:31.466 --> 00:42:34.558 them feel like they have more progress in front of them more
00:42:34.558 --> 00:42:37.599 frequently. And they're gonna be able to see those changes,
00:42:37.599 --> 00:42:40.893 Sprint over Sprint so that we're developing working software and
00:42:40.893 --> 00:42:43.985 giving them something to go and validate Sprint over Sprint.
00:42:47.285 --> 00:42:49.940 Ben, you have been characteristically quite
00:42:49.940 --> 00:42:53.801 uncharacteristically quiet. Do you have any additional examples
00:42:53.801 --> 00:42:57.602 of how you run through your QA process that you can share with
00:42:57.602 --> 00:42:58.145 the team?
00:42:58.895 --> 00:43:00.855 Yeah, absolutely. I'm so.
00:43:01.535 --> 00:43:06.338 A lot of kind of what you've gone over. Uh, really, you know,
00:43:06.338 --> 00:43:10.598 look to see what tickets are code complete that can be
00:43:10.598 --> 00:43:11.605 deployed and.
00:43:12.715 --> 00:43:17.122 Get them. Uh, you know, pushed up into the QA environment, and
00:43:17.122 --> 00:43:21.528 I'll either a depending on what the feature is. I I might have
00:43:21.528 --> 00:43:25.375 the developer in some instances demonstrate it for me.
00:43:26.955 --> 00:43:31.169 Not in in that seldom in most cases. I'm just gonna read the
00:43:31.169 --> 00:43:32.205 user story and.
00:43:33.605 --> 00:43:37.682 You know, try to, you know, identify like exactly what it's
00:43:37.682 --> 00:43:41.623 trying to do and go and I'll just go test against that. I
00:43:41.623 --> 00:43:45.836 mean, I'm sort of inspecting what I expect before I then, you
00:43:45.836 --> 00:43:46.175 know.
00:43:46.335 --> 00:43:49.744 That say, OK yeah, this is good. Push it up into stage so we can
00:43:49.744 --> 00:43:52.943 have the client approve it and then, you know, kind of rinse
00:43:52.943 --> 00:43:56.299 and repeat from there. But yeah, I mean that's that's the basic
00:43:56.299 --> 00:43:59.235 process. And even with Christian on the team, I always.
00:43:59.875 --> 00:44:00.595 Tested.
00:44:02.275 --> 00:44:04.195 My you know, a lot of my own stuff.
00:44:04.765 --> 00:44:07.687 Umm, because I you know, with your when you're dealing with
00:44:07.687 --> 00:44:10.705 the clients every day and you're in these meetings gathering.
00:44:11.815 --> 00:44:15.045 The details around their business requirements and what
00:44:15.045 --> 00:44:18.621 it is exactly that the client needs. There's really no one on
00:44:18.621 --> 00:44:21.966 the team at that point. Once you're, you know, full on in
00:44:21.966 --> 00:44:25.312 development that should end up, would know more about the
00:44:25.312 --> 00:44:28.945 project than than you about what these things should be doing.
00:44:30.845 --> 00:44:34.394 You know, and I say that because obviously during discovery you
00:44:34.394 --> 00:44:37.721 you should be intently, you know, sort of picking up on all
00:44:37.721 --> 00:44:41.103 of that. And I know it all kind of gets documented. But then
00:44:41.103 --> 00:44:44.652 once that that handoff is done and you're actually getting into
00:44:44.652 --> 00:44:47.923 the weeds of implementing and getting things developed and
00:44:47.923 --> 00:44:51.361 prototyping and all that fun stuff, you know that you're the.
00:44:51.361 --> 00:44:54.743 Yeah. I mean, the buck stops with you at clarity in terms of
00:44:54.743 --> 00:44:57.959 like, you should know exactly what each of these features
00:44:57.959 --> 00:45:01.175 should be doing. So you should know what to test against.
00:45:01.615 --> 00:45:05.015 Umm. And when you're making your tickets? Furthermore like this
00:45:05.015 --> 00:45:08.361 is just and I'll close with this because I'll talk a lot about
00:45:08.361 --> 00:45:10.485 this. But what I would do typically is.
00:45:12.105 --> 00:45:16.548 And and I I'm not 100% perfect at this, but I really try to on
00:45:16.548 --> 00:45:20.850 like my user stories add in sort of some acceptance criteria
00:45:20.850 --> 00:45:25.292 where it's just like in plain English. We're anyone could read
00:45:25.292 --> 00:45:29.665 it and understand what what the purpose of this user story is
00:45:29.665 --> 00:45:34.107 and how it sort of plays into the overall feature. And then if
00:45:34.107 --> 00:45:38.197 I can in my mind, if I can visualize the steps in my head
00:45:38.197 --> 00:45:39.255 as far as like.
00:45:39.855 --> 00:45:44.632 Uh, you know, step one login, Step 2, do this step three. OK,
00:45:44.632 --> 00:45:48.485 do this then. This should happen. Like I'll. I'll
00:45:48.485 --> 00:45:52.645 literally write that out in steps. Like as a sort of.
00:45:54.265 --> 00:45:57.777 Testing steps like and if you have that in there ahead of
00:45:57.777 --> 00:46:00.925 time, that's really helpful for developers because.
00:46:01.465 --> 00:46:04.959 Umm. Then they know that. OK, well, if I can do XY and Z uh,
00:46:04.959 --> 00:46:07.994 then then you know, they essentially have a a pretty
00:46:07.994 --> 00:46:11.544 solid definition of done there. And especially if you include
00:46:11.544 --> 00:46:14.809 sort of in plain English, you know, try to avoid in this
00:46:14.809 --> 00:46:18.417 particular statement, I always try to avoid jargon to the best
00:46:18.417 --> 00:46:21.910 of my ability. So that like literally anyone could just read
00:46:21.910 --> 00:46:24.315 it and understand what it's trying to do.
00:46:25.745 --> 00:46:29.684 Without, you know, using a lot of large words or or internal
00:46:29.684 --> 00:46:33.557 jargon, I think that's really helpful. So that's kind of my
00:46:33.557 --> 00:46:36.075 thought process and exactly what I do.
00:46:36.455 --> 00:46:41.786 Umm, in in those cases. So does anyone have any questions? Ohh
00:46:41.115 --> 00:46:41.725 Oh yes.
00:46:41.786 --> 00:46:43.055 Stephanie smam.
00:46:43.505 --> 00:46:45.415 So just to add a little.
00:46:47.115 --> 00:46:52.385 More info to the testing steps and the acceptance criteria.
00:46:54.225 --> 00:46:58.325 One of the things I would love to see is that as we're building
00:46:58.325 --> 00:47:02.297 a project out from the start, when we're importing everything
00:47:02.297 --> 00:47:06.077 into Azure and creating those user stories the first time,
00:47:06.077 --> 00:47:09.857 that's really the time frame where we should be, you know,
00:47:09.857 --> 00:47:13.701 putting in as much of that information as we can. Obviously
00:47:12.675 --> 00:47:13.155 Agreed.
00:47:13.701 --> 00:47:17.865 as we go through development and things shift and things change,
00:47:17.865 --> 00:47:22.093 we're gonna have to work through any new requirements. But one of
00:47:22.093 --> 00:47:24.335 the things that contend to happen.
00:47:24.395 --> 00:47:28.179 And you know, we all have a ton on our plate. There's a lot
00:47:28.179 --> 00:47:32.089 going on and there's a lot of moving parts and it's it can be
00:47:32.089 --> 00:47:35.810 very challenging, especially if you have like four or five
00:47:35.810 --> 00:47:39.467 projects that are in the discovery phase or just starting
00:47:39.467 --> 00:47:43.566 development all at the same time to keep everything straight. So
00:47:43.566 --> 00:47:47.476 the more work that you put in up front, the easier things are
00:47:47.476 --> 00:47:51.386 going to be for you down the road because you're not going to
00:47:51.386 --> 00:47:55.485 remember the acceptance criteria for a ticket that gets started.
00:47:55.695 --> 00:47:59.969 6 sprints from the project uh development cycle beginning so
00:47:59.969 --> 00:48:04.454 if you put that information in the beginning, you can basically
00:48:04.454 --> 00:48:08.868 write it down and forget about it till you need it rather than
00:48:08.868 --> 00:48:13.423 having to take the extra time to go back and think, OK, what are
00:48:13.423 --> 00:48:17.697 the steps? What do I need to do here? And it's also going to
00:48:17.697 --> 00:48:21.831 help you as things shift, OK, this is what this originally
00:48:21.831 --> 00:48:26.105 started out as, but I know that we've made some shifts here.
00:48:26.385 --> 00:48:30.115 So this acceptance criteria is no longer valid. I need to
00:48:30.115 --> 00:48:33.844 update that and move the project forward based on the new
00:48:33.844 --> 00:48:36.995 information that I have. So it's it's kind of a.
00:48:38.025 --> 00:48:41.905 It's helpful in that measure, twice cut once sort of.
00:48:42.515 --> 00:48:45.855 Philosophy. If you put the the heavy lift in at the beginning,
00:48:45.855 --> 00:48:49.037 it's going to be easier for you down the line to make those
00:48:49.037 --> 00:48:50.945 small adjustments and small shifts.
00:48:51.265 --> 00:48:55.231 Yep, the stitch in time saves 9 love that, saying goes goes hand
00:48:53.965 --> 00:48:54.325 Yep.
00:48:55.231 --> 00:48:56.695 and hand with that. Yep.
00:48:56.745 --> 00:48:59.873 And then additionally, one of the things I was kind of
00:48:59.873 --> 00:49:03.286 thinking about while Ben was talking about, you know, going
00:49:03.286 --> 00:49:04.935 through this with the client.
00:49:06.885 --> 00:49:08.185 I am sure that.
00:49:09.205 --> 00:49:13.253 The vast majority of us on the call, maybe with the exception
00:49:13.253 --> 00:49:17.039 of the newer folks, have had that moment where we're on a
00:49:17.039 --> 00:49:19.715 call with the client and we are doing a.
00:49:20.465 --> 00:49:24.045 Sort of live demo and ohhh my gosh, it's not working.
00:49:26.465 --> 00:49:30.355 Can any of you think of a time when that went smoothly?
00:49:32.615 --> 00:49:33.645 Not a single one.
00:49:35.805 --> 00:49:38.905 When I have an awesome developer on the line and they're like,
00:49:38.905 --> 00:49:41.415 I'll just fix it real quick, but that's like barn.
00:49:39.415 --> 00:49:45.419 I I I did actually have one instance where I messaged Sacco
00:49:42.485 --> 00:49:43.415 It's gonna say.
00:49:45.419 --> 00:49:51.524 outside the chat and he fixed it mid sentence and don't ever
00:49:51.524 --> 00:49:53.725 count on it it it was.
00:49:53.605 --> 00:49:54.205 Oh yeah.
00:49:54.425 --> 00:49:55.535 It was magic.
00:49:58.165 --> 00:50:01.867 I've rarely been able to pull that off and it's just it's.
00:50:00.475 --> 00:50:02.205 Yeah, yeah. I wasn't counting on it.
00:50:01.867 --> 00:50:05.255 It's not definitely not worth it. Yeah, I would best.
00:50:03.765 --> 00:50:04.065 Yep.
00:50:03.905 --> 00:50:07.022 I thought I was beating a hasty retreat and then he was like,
00:50:07.022 --> 00:50:07.625 you're good.
00:50:08.315 --> 00:50:11.828 I would I best thing to do, and this is this is something I have
00:50:11.828 --> 00:50:14.800 it I I kind of picked up from Chris's. I always have a
00:50:14.800 --> 00:50:18.043 recording on standby just in case. Should that happen. I've
00:50:18.043 --> 00:50:21.069 been caught too many times in a situation like that. So
00:50:21.069 --> 00:50:24.473 beforehand as I'm testing it at some point I'll just I'll just
00:50:24.473 --> 00:50:27.878 turn on my recorder record it real quick. I'll have the videos
00:50:27.878 --> 00:50:31.228 of backup. I don't necessarily always plan on using it unless
00:50:31.228 --> 00:50:34.417 there's a problem. But if you have that backup and you can
00:50:34.417 --> 00:50:37.227 sort of defer to that and explain it away, that's a
00:50:37.227 --> 00:50:37.605 really.
00:50:37.695 --> 00:50:41.223 Kind of a good way to recover a little bit, although it's not an
00:50:41.223 --> 00:50:44.425 ideal situation when you're trying to do a live demo. It's
00:50:44.425 --> 00:50:47.898 better than a complete flop, so just something to keep in mind.
00:50:46.025 --> 00:50:47.425 No, I like that a lot.
00:50:46.155 --> 00:50:49.695 100% so some.
00:50:47.898 --> 00:50:48.115 Yep.
00:50:48.765 --> 00:50:50.395 Redundancies are always nice.
00:50:50.655 --> 00:50:53.135 Somewhere in the archives of.
00:50:50.665 --> 00:50:51.035 Mm-hmm.
00:50:53.905 --> 00:50:58.152 Nuclino there is an inception video that I had created of
00:50:58.152 --> 00:51:02.837 recording. It's a recording of me recording a demo so it's it's
00:51:02.837 --> 00:51:03.935 demo inception.
00:51:04.805 --> 00:51:09.187 And I can find that for you guys, but there are some very
00:51:09.187 --> 00:51:13.795 specific steps cause one of the things that I want us to get
00:51:13.795 --> 00:51:18.026 more in the habit of is recording demos for clients and
00:51:18.026 --> 00:51:22.257 we kind of tried that with the asana task for doing the
00:51:22.257 --> 00:51:25.505 internal demo that didn't really take off.
00:51:27.765 --> 00:51:31.744 What I was working on CPA the client had asked that we do a
00:51:31.744 --> 00:51:35.988 demo for them every two weeks of the work that was completed in
00:51:35.988 --> 00:51:37.115 the Sprint prior.
00:51:38.305 --> 00:51:43.265 And that served so many functions at clarity.
00:51:44.325 --> 00:51:49.091 First off, it forced us. It was the never ending Project,
00:51:49.091 --> 00:51:54.103 Jessica for sure, that forced me and the development team to
00:51:54.103 --> 00:51:57.965 ensure that the work that I was assigning was.
00:51:59.285 --> 00:52:04.737 Completed Q aid and testable for client facing by the next
00:52:04.737 --> 00:52:10.189 Wednesday after a Sprint ended because I had to have those
00:52:10.189 --> 00:52:13.885 demos out for them every two weeks and.
00:52:14.865 --> 00:52:18.577 It got us to a point where we could literally go in and QA
00:52:18.577 --> 00:52:22.477 that Sprint in about an hours working session with me and the
00:52:22.477 --> 00:52:25.748 developers and fix any regressions or anything that
00:52:25.748 --> 00:52:29.586 came from that. Additionally, the client was so used to that
00:52:29.586 --> 00:52:33.297 that I didn't really. I mean most of the time I would play
00:52:33.297 --> 00:52:37.072 the demo for them in the call, but eventually it got to the
00:52:37.072 --> 00:52:40.909 point where our client calls and our client updates where 15
00:52:40.909 --> 00:52:44.621 minutes and I would be able to send that recording over to
00:52:44.621 --> 00:52:44.935 them.
00:52:45.385 --> 00:52:50.617 And send them the invoice for the new Sprint and just go about
00:52:50.617 --> 00:52:55.350 the day and we would have 15 minute client syncs so they
00:52:55.350 --> 00:52:55.765 were.
00:52:56.585 --> 00:53:01.055 Very used to a very specific cadence and that project was one
00:53:01.055 --> 00:53:05.742 where it was so predictable that I didn't really think about it,
00:53:05.742 --> 00:53:09.995 even though it was my largest project at the time because.
00:53:10.815 --> 00:53:14.994 I could I could dedicate my time to putting out other fires and
00:53:14.994 --> 00:53:19.108 the more we can get to a cadence with our clients where things
00:53:19.108 --> 00:53:22.960 are predictable, things happen on a regular schedule. They
00:53:22.960 --> 00:53:27.139 expect this. We expect this, we know what's going on, they know
00:53:27.139 --> 00:53:31.253 what's going on and the dev team knows what's going on. All of
00:53:31.253 --> 00:53:35.106 the fires and the stressful situations that we face on the
00:53:35.106 --> 00:53:39.023 regular are going to get so minimized and it really, really
00:53:39.023 --> 00:53:42.745 starts with us having a solid, solid foundation of what?
00:53:42.865 --> 00:53:46.601 Is expected on the project for the client. What are they? What
00:53:46.601 --> 00:53:50.336 problem are they trying to solve and how are we gonna solve it
00:53:50.336 --> 00:53:54.013 for them? We can boil it down to the simplest question and as
00:53:54.013 --> 00:53:57.689 long as we can answer that and know what criteria needs to go
00:53:57.689 --> 00:53:59.705 in the better off we're gonna be.
00:54:01.705 --> 00:54:02.695 Off myself box.
00:54:04.555 --> 00:54:09.292 So I'm assuming there's a good deal of some concern about this
00:54:09.292 --> 00:54:13.728 kind of shift in what we need to do for the projects. Does
00:54:13.728 --> 00:54:18.164 anybody have any immediate questions or anything regarding
00:54:18.164 --> 00:54:22.901 like timing and how to kind of start this process and go about
00:54:22.901 --> 00:54:26.435 it that we can kind of dive in on and dissect?
00:54:31.025 --> 00:54:34.363 Have a little question. Whenever you do find the user story
00:54:32.755 --> 00:54:33.175 Mm-hmm.
00:54:34.363 --> 00:54:37.923 you're going through it. Maybe you did do what Ben said and you
00:54:37.923 --> 00:54:40.871 wrote out your test steps perfectly and you're going
00:54:40.871 --> 00:54:44.097 through it and you do find a bug. How far down the rabbit
00:54:44.097 --> 00:54:47.490 hole or you guys going to go? Is it just like, oh, this step
00:54:47.490 --> 00:54:49.715 messed up and that's it? Or is it like?
00:54:47.595 --> 00:54:47.875 Yep.
00:54:49.125 --> 00:54:53.475 That's step messed up. Let's get a developer on the call. Let's
00:54:52.585 --> 00:54:53.655 They diagnosed.
00:54:53.475 --> 00:54:57.214 quick figure out if it's something and then if it goes
00:54:57.214 --> 00:55:01.632 beyond that, we need them to to take over because ultimately the
00:54:59.325 --> 00:55:00.195 Cool, cool.
00:54:59.855 --> 00:55:00.205 Yeah.
00:55:01.632 --> 00:55:05.914 project manager is not going to get too deep in the weeds into
00:55:05.914 --> 00:55:09.925 the code. Like I don't expect any of you guys to go in and
00:55:09.925 --> 00:55:13.935 validate the PR's and read the changes and the files that.
00:55:13.255 --> 00:55:13.635 So.
00:55:14.885 --> 00:55:18.429 Or like this through a 400 error and it's doing this because of
00:55:16.145 --> 00:55:16.865 We sniff.
00:55:18.429 --> 00:55:20.755 this on the back end, none of that stuff.
00:55:18.495 --> 00:55:18.995 Yet.
00:55:19.445 --> 00:55:20.205 We sniff.
00:55:19.695 --> 00:55:23.639 When yeah, and the the thing I wanna point out why I'm a big
00:55:20.855 --> 00:55:21.645 We're sniffers.
00:55:23.639 --> 00:55:27.518 fan of getting the developer on the call is because I would
00:55:27.518 --> 00:55:31.462 guess that seven out of 10 bugs are just one line of code or
00:55:31.462 --> 00:55:31.785 less.
00:55:33.435 --> 00:55:38.367 Yeah, it's usually like a, a misspelling or something like a
00:55:33.765 --> 00:55:37.793 Like they're literally between, right? Like 1 character like 1
00:55:37.793 --> 00:55:41.501 character and one line of code that it developer. Yeah, a
00:55:38.367 --> 00:55:39.175 typo. Hmm.
00:55:40.415 --> 00:55:41.485 Most common thing.
00:55:41.501 --> 00:55:45.464 developer can literally fix it faster than you can create the
00:55:45.464 --> 00:55:46.615 bug ticket for it.
00:55:46.935 --> 00:55:47.415 Mm-hmm.
00:55:47.625 --> 00:55:49.355 Probably 70% of the time.
00:55:50.435 --> 00:55:54.234 Yeah. So just keeping up with that and referencing back to the
00:55:54.234 --> 00:55:57.852 bid ticket we looked at, I went ahead and messaged Michael,
00:55:57.852 --> 00:56:01.591 since I wasn't gonna ditch this meeting to jump in a call and
00:56:01.591 --> 00:56:05.450 seven minutes after I messaged him, he came back with. Yeah, it
00:56:05.450 --> 00:56:09.430 looks like the PR was abandoned. For what? For. I'm not sure what
00:56:09.430 --> 00:56:13.108 reason I did the action on the same day I created the PR. By
00:56:13.108 --> 00:56:16.665 the look of the history. Not sure what happened there, but
00:56:16.665 --> 00:56:20.223 I'll get it going again and fix any merge changes that are
00:56:20.223 --> 00:56:20.645 needed.
00:56:20.995 --> 00:56:23.775 I'll have to give you an update Monday like great.
00:56:34.825 --> 00:56:35.235 Mm-hmm.
00:56:35.295 --> 00:56:38.972 But he may come back and say, yeah, this was five minutes and
00:56:38.972 --> 00:56:42.768 it was already captured and I'm not exactly sure what happened,
00:56:42.768 --> 00:56:45.615 but we're good to go. And one way or the other.
00:56:46.835 --> 00:56:48.825 We'll have a path forward coming out of that.
00:56:50.935 --> 00:56:51.515 Jessica.
00:56:52.955 --> 00:56:56.156 This might be a broad question that we can talk about and then
00:56:56.156 --> 00:56:59.154 like a shredded session or something, but earlier when you
00:56:59.154 --> 00:57:02.355 were going up your first ticket, when you were filling out the
00:57:02.095 --> 00:57:02.415 Umm.
00:57:02.355 --> 00:57:05.708 registration, you said that that was a bug. Is it more because of
00:57:05.708 --> 00:57:08.655 the aesthetic of it or because it should have been set up
00:57:08.655 --> 00:57:11.195 another way and it wasn't set up the correct way?
00:57:12.645 --> 00:57:13.125 Uh.
00:57:13.825 --> 00:57:18.355 Little of column A, a little of column BUM typically.
00:57:19.575 --> 00:57:24.605 With most projects you would have a a mark up or a mock up to
00:57:24.605 --> 00:57:28.905 go off of. With this registration form it was client
00:57:28.905 --> 00:57:33.692 request well after feature completion. So in this instance
00:57:33.692 --> 00:57:38.966 there was a markup to go off of. The reason I'm putting it in is
00:57:34.525 --> 00:57:35.535 And that's the key.
00:57:38.966 --> 00:57:44.077 a bug. Well actually I probably won't even put it in as a bug.
00:57:44.077 --> 00:57:48.701 I'll probably just put it in as another ticket under the
00:57:48.701 --> 00:57:50.405 registration feature.
00:57:50.455 --> 00:57:53.194 That that. Yeah, that that was my question. What was the
00:57:51.905 --> 00:57:53.895 Yep, Yep. Where does.
00:57:53.194 --> 00:57:56.220 difference between a bug and a change or a feature or wherever
00:57:55.905 --> 00:57:56.785 Can can.
00:57:56.035 --> 00:57:57.085 And where does it go?
00:57:56.220 --> 00:57:57.085 it falls in? Yeah.
00:57:57.855 --> 00:57:58.415 Yeah.
00:57:58.345 --> 00:58:03.073 Let me give the definition of a bug real quick. A bug is is a so
00:58:03.073 --> 00:58:06.927 like after a feature is completed or if it's past QA
00:58:06.927 --> 00:58:11.219 initially and then it's found like after the fact in doing
00:58:11.219 --> 00:58:15.655 some QA that that that is a bug. Otherwise it just fails QA.
00:58:16.945 --> 00:58:19.954 Right. And that's why I asked, Steph. Like she said it was
00:58:17.365 --> 00:58:17.775 Thank you.
00:58:19.435 --> 00:58:19.755 Yep.
00:58:19.954 --> 00:58:23.065 gonna go in as a bug. Is it because she had asked him to put
00:58:23.065 --> 00:58:26.074 it in there a certain way for aesthetic purposes, or is it
00:58:26.074 --> 00:58:29.338 just because she doesn't think it looks good? And no, this does
00:58:29.338 --> 00:58:32.704 not. It's not gonna work because the way that it came over in the
00:58:32.704 --> 00:58:36.018 e-mail, like her name was broken up where it was like, you know,
00:58:36.018 --> 00:58:39.078 her name and city state. And then her last name down to the
00:58:36.375 --> 00:58:36.815 Right.
00:58:39.078 --> 00:58:39.435 bottom.
00:58:39.675 --> 00:58:40.485 Umm.
00:58:40.755 --> 00:58:41.955 So yeah.
00:58:42.905 --> 00:58:48.575 So yeah. So with that like the the task itself passes because I
00:58:48.575 --> 00:58:54.068 I got the e-mail it I did the thing, but I'm just gonna put a
00:58:54.068 --> 00:58:59.472 new work item under the feature to clean up the registration
00:58:59.472 --> 00:58:59.915 form.
00:59:01.815 --> 00:59:01.955 Is.
00:59:02.035 --> 00:59:04.866 Something that we would also take back to the client. So hey,
00:59:04.866 --> 00:59:07.788 we're going to put another maybe like 30 minutes into this just
00:59:07.788 --> 00:59:10.071 to make it look more aesthetically pleasing or is
00:59:10.071 --> 00:59:11.715 that something that we just do and?
00:59:12.765 --> 00:59:14.215 Which do it and they trust us.
00:59:13.675 --> 00:59:13.995 It.
00:59:15.015 --> 00:59:20.252 It really depends on your client and on the project and sort of
00:59:18.005 --> 00:59:18.365 OK.
00:59:20.252 --> 00:59:25.161 everything that's happening there with that particular one.
00:59:22.395 --> 00:59:22.695 Got it.
00:59:25.161 --> 00:59:27.125 I know that that ticket.
00:59:27.925 --> 00:59:32.822 Exceeded my original estimation, so in that case, yes, I am 100%
00:59:32.822 --> 00:59:36.890 going to let the client know that I need to make some
00:59:36.890 --> 00:59:41.410 adjustments with that and with Max in particular, there are
00:59:41.410 --> 00:59:46.157 already aware because I demo for them pretty much every time I
00:59:46.157 --> 00:59:50.300 talk to them, so they're totally, totally aware of the
00:59:50.300 --> 00:59:55.272 hours, burn, the spend, and what needs to be adjusted on that. So
00:59:55.272 --> 00:59:58.135 it's really dependent on your client.
00:59:58.235 --> 01:00:01.870 If that original ticket was under and say I estimated 2
01:00:01.870 --> 01:00:05.700 hours and they cleared it, it you know one hour I would be
01:00:05.700 --> 01:00:09.789 comfortable going in and adding a ticket, adding an adjustment
01:00:09.789 --> 01:00:13.814 to that and just closing out the feature. If it goes over the
01:00:13.814 --> 01:00:17.644 estimation, you have to talk to your client every time. We
01:00:17.644 --> 01:00:21.798 always have to make sure that we are above board with the hours
01:00:21.798 --> 01:00:25.952 spend talking to the clients and letting them know what's going
01:00:25.952 --> 01:00:29.652 on so that there are no surprises and it makes our lives
01:00:29.652 --> 01:00:31.145 easier in the long run.
01:00:31.595 --> 01:00:33.965 Right. OK. Thank you for clearing that up.
01:00:34.225 --> 01:00:37.435 Yeah, 100%, we are. Ohh, go ahead.
01:00:37.525 --> 01:00:40.981 Everyone at? Yeah, I just. Uh, just for something that just
01:00:40.981 --> 01:00:44.378 happened cause I think it's a good a good example. Umm. So
01:00:44.378 --> 01:00:47.891 Charlie came back and said that my goal came back to him and
01:00:47.891 --> 01:00:51.462 said the PR was abandoned. Can anybody in this would probably
01:00:51.462 --> 01:00:55.205 be PM with more experience. So I suppose Daniel, Stephanie. Ben.
01:00:56.155 --> 01:00:57.385 Oh, I'm allowed to answer.
01:00:56.365 --> 01:01:01.381 But you are you are. When? When you heard Charlie say Michael
01:01:01.381 --> 01:01:06.315 said the PR was abandoned, what thought came into your head?
01:01:07.885 --> 01:01:08.455 So.
01:01:07.885 --> 01:01:08.595 My.
01:01:08.025 --> 01:01:08.555 Why?
01:01:10.225 --> 01:01:13.235 It's So what still need the work?
01:01:13.405 --> 01:01:17.535 Yeah. Well, the big thing would be white, like, you know.
01:01:13.535 --> 01:01:13.965 Yeah.
01:01:16.015 --> 01:01:19.910 Yes, Brandon, Brandon, Brandon, Brandon. That's what I want to
01:01:19.535 --> 01:01:23.242 Yeah. Can someone approve this PR? What's going on with this
01:01:19.910 --> 01:01:21.765 go through your guys's brains.
01:01:20.205 --> 01:01:20.525 Yep.
01:01:21.365 --> 01:01:21.855 OK.
01:01:23.242 --> 01:01:26.887 PR? Who? Why? Why did this get PR? Get abandoned? Who's not
01:01:23.635 --> 01:01:24.005 Yeah.
01:01:23.835 --> 01:01:24.155 Mm-hmm.
01:01:26.887 --> 01:01:28.345 paying attention to you?
01:01:26.915 --> 01:01:27.315 Yep.
01:01:28.355 --> 01:01:30.045 Some something has gone wrong.
01:01:31.215 --> 01:01:32.405 Someone being a mean.
01:01:31.285 --> 01:01:32.055 So please.
01:01:32.905 --> 01:01:35.075 Please let me into those situations.
01:01:37.245 --> 01:01:37.555 Alright.
01:01:38.615 --> 01:01:40.675 Why? Why, why, why, why, why, why, why, why?
01:01:38.745 --> 01:01:40.205 Yeah, yeah, yeah, absolutely.
01:01:41.445 --> 01:01:42.785 So kind of kind of.
01:01:44.745 --> 01:01:46.095 Feeding off of that.
01:01:44.935 --> 01:01:47.639 How do they get abandoned, Brandon, what happens? They
01:01:47.205 --> 01:01:51.091 So in so yeah. So in this case, I believe what happened was
01:01:47.639 --> 01:01:47.885 just.
01:01:51.091 --> 01:01:54.912 developers were using you can. There's a one of the little
01:01:54.912 --> 01:01:58.215 features of a PR is you could do do it as a draft.
01:01:59.515 --> 01:02:04.093 And the idea behind that is to get some feedback from like
01:02:04.093 --> 01:02:05.645 somebody like James.
01:02:07.735 --> 01:02:12.266 Sort of in the middle of a task so that you don't go too far
01:02:12.266 --> 01:02:16.573 down the wrong the wrong Rd. Azure of course doesn't know
01:02:14.655 --> 01:02:15.015 Umm.
01:02:16.573 --> 01:02:21.327 about clarity office hours, so people were were really misusing
01:02:21.327 --> 01:02:26.006 that feature and so I sent out a notice to every developer who
01:02:26.006 --> 01:02:27.565 had one and said hey.
01:02:28.325 --> 01:02:31.673 If you guys still have these PR's as drafts by this date,
01:02:31.673 --> 01:02:33.635 this PR is going to be abandoned.
01:02:35.455 --> 01:02:39.546 And I suppose that must be what happened in this case, so it
01:02:39.546 --> 01:02:43.502 wasn't actually ever PR. It was just a draft, so it wasn't
01:02:43.502 --> 01:02:44.105 actually.
01:02:45.445 --> 01:02:49.225 Ready to go in? And that's why I would need to get involved and
01:02:49.225 --> 01:02:51.765 address that situation with the developer.
01:02:55.215 --> 01:02:56.165 OK. Thank you.
01:02:56.585 --> 01:02:57.895 Checking you had a question.
01:02:58.435 --> 01:03:00.765 Uh, never mind that that kind of covered it.
01:03:01.255 --> 01:03:03.235 Does everybody know what a PR is?
01:03:06.955 --> 01:03:09.625 Yes, kind of. Uh.
01:03:09.125 --> 01:03:12.606 What I just heard from the group is no Chinese. I mean, if
01:03:09.575 --> 01:03:10.115 I know.
01:03:11.685 --> 01:03:14.255 Yeah, I went over with all y'all.
01:03:11.745 --> 01:03:15.920 Daniel Daniel. Like. Yeah. Daniel walked through what they
01:03:12.525 --> 01:03:14.755 Yeah, it's public, yeah.
01:03:12.606 --> 01:03:15.555 Trenton doesn't know, I don't know. I don't know.
01:03:15.585 --> 01:03:17.135 Public relations.
01:03:15.920 --> 01:03:19.175 are, I think I know what they are and enough.
01:03:17.005 --> 01:03:17.755 I do.
01:03:19.985 --> 01:03:20.455 Uh.
01:03:21.835 --> 01:03:25.628 But I wouldn't say that I like if somebody told me to describe
01:03:25.628 --> 01:03:29.421 what a PR is, I would be like it's I I don't know. I just know
01:03:29.421 --> 01:03:30.625 kinda what they are.
01:03:31.525 --> 01:03:33.615 Yes, please explain how I would love to know.
01:03:35.385 --> 01:03:37.485 I know, I know, it's a pull request, but.
01:03:38.325 --> 01:03:38.755 Umm.
01:03:38.715 --> 01:03:41.974 Yeah. So UMI can take this one. If you guys don't mind, it's
01:03:41.974 --> 01:03:44.485 gonna go longer than 4 minutes, I'm sure. But.
01:03:44.915 --> 01:03:49.605 Umm, so when we have a new like, is that everyone? Obviously
01:03:49.605 --> 01:03:54.065 here's about our products, right? And like corset and how
01:03:54.065 --> 01:03:58.678 Chris is talking about the progress we make, right? So Eric
01:03:58.678 --> 01:04:03.522 Weathers, our CTO is ultimately in charge of our products. And
01:04:03.522 --> 01:04:08.135 so he works with some PMS, some developers on getting work.
01:04:08.585 --> 01:04:11.976 Uh, you know, and adding features to uh Seth. And then
01:04:11.976 --> 01:04:15.428 when they're ready for a release, which is usually on a
01:04:15.428 --> 01:04:18.942 quarterly cadence. So we are about to, we've recently, I
01:04:18.942 --> 01:04:22.702 should say, executed a release that is like a new version of
01:04:22.702 --> 01:04:26.462 CEF. So new projects that come later are gonna branch off of
01:04:26.462 --> 01:04:27.695 that version of CEF.
01:04:28.465 --> 01:04:34.031 So a client branches created which basically just means that
01:04:34.031 --> 01:04:40.052 now we have a a version will say of CEF that we can customize for
01:04:40.052 --> 01:04:45.618 that client, right? So all of poor request is is basically a
01:04:45.618 --> 01:04:51.183 repo where that clients code exists and we obviously develop
01:04:51.183 --> 01:04:52.095 on locals.
01:04:53.315 --> 01:04:56.486 Because you don't want a developer to go in and break
01:04:56.486 --> 01:05:00.068 something on the QA site, right? Like if every developer was
01:05:00.068 --> 01:05:03.591 trying to develop against the QA site and this has happened
01:05:03.591 --> 01:05:05.705 before, things are gonna go poorly.
01:05:06.325 --> 01:05:09.722 Umm. And so because any developer can go onto the QA
01:05:09.722 --> 01:05:13.503 server and literally open the exact same file and model be
01:05:13.503 --> 01:05:16.195 modifying the same file at the same time.
01:05:18.005 --> 01:05:22.329 So we do the work on our locals and then we create a pull
01:05:22.329 --> 01:05:24.565 request and a poor request is.
01:05:25.025 --> 01:05:28.195 UM and I could share my screen here for a second.
01:05:30.365 --> 01:05:32.835 A poor if I can find the.
01:05:34.685 --> 01:05:35.275 Window.
01:05:36.895 --> 01:05:41.883 So this screen is is where you know me, James, Brendan, Jesse,
01:05:41.883 --> 01:05:46.949 Eric can come in and see all the active pool requests. And then
01:05:46.949 --> 01:05:51.620 here there's obviously, you know, standards and processes.
01:05:51.620 --> 01:05:54.945 So you'll see like the naming convention.
01:05:55.325 --> 01:05:59.302 Umm the the branch name. You'll see the client name in there,
01:05:59.302 --> 01:06:02.959 and they'll usually put the task number and then a brief
01:06:02.959 --> 01:06:06.615 description and say that they're merging it into bid QA.
01:06:07.075 --> 01:06:12.008 Umm so when we click on this all this is is it's. I mean it's Git
01:06:12.008 --> 01:06:14.175 the developers pushing it up.
01:06:15.005 --> 01:06:15.545 Umm.
01:06:16.305 --> 01:06:20.382 Into this, you know basically into this repo and they are and
01:06:20.382 --> 01:06:23.735 they're creating this poor request, for lack of a.
01:06:24.935 --> 01:06:28.687 More concrete way of explaining that process? Umm. But I think
01:06:27.265 --> 01:06:27.735 Umm.
01:06:28.687 --> 01:06:32.558 that gets point across. So then what we do is and by we I really
01:06:32.558 --> 01:06:36.131 mean James because he's the fastest at it. Although Brendan
01:06:36.131 --> 01:06:39.883 Lyon does it does it pretty well as well. He comes in here, he
01:06:39.883 --> 01:06:43.575 finds any issues and he'll put comments on a PR so like don't
01:06:43.575 --> 01:06:47.149 do this, don't do that change this this doesn't make sense.
01:06:47.149 --> 01:06:48.935 This is gonna break something.
01:06:49.585 --> 01:06:50.195 UM.
01:06:51.285 --> 01:06:55.002 And then it's up to the developer. So we just talked
01:06:55.002 --> 01:06:59.421 about Michael. So it's up to the developer then to come in and
01:06:59.421 --> 01:07:03.769 resolve these comments and the way that he's gonna do that is
01:07:03.769 --> 01:07:07.837 he has the code on his local, comes in, makes it changes,
01:07:07.837 --> 01:07:12.045 pushes it up and then someone will review it again. They'll
01:07:12.045 --> 01:07:15.972 click approve. Once it's approved, most not all not bid
01:07:15.972 --> 01:07:20.320 most of our projects are now on CI CD. So auto like pipelines
01:07:20.320 --> 01:07:22.915 where the deployments are automated.
01:07:23.435 --> 01:07:27.979 Umm. And a manual deployment is literally just a developer you
01:07:27.979 --> 01:07:32.450 know remote remoting into that to the box that the QA site is
01:07:32.450 --> 01:07:32.955 on and.
01:07:33.875 --> 01:07:37.659 Manually doing the deployment, building the code and all that.
01:07:37.659 --> 01:07:41.263 So basically a pull request is just a developer getting the
01:07:41.263 --> 01:07:43.365 code from their local into the QA.
01:07:44.135 --> 01:07:46.957 Server. I guess it's probably the most succinct way of
01:07:46.957 --> 01:07:47.675 explaining it.
01:07:48.045 --> 01:07:53.375 Umm, so if you don't see the pull request LinkedIn Azure.
01:07:54.915 --> 01:07:58.519 I would jump out and ask the devs if it's ready for you to
01:07:58.519 --> 01:08:02.429 test because it that ticket is now in code complete. You should
01:08:02.429 --> 01:08:06.033 be able to go in and validate it, but there are times when
01:08:06.033 --> 01:08:10.003 they'll move it to code complete prior to the pull request being
01:08:10.003 --> 01:08:13.730 approved and actually having that button clicked in the CCSD
01:08:13.730 --> 01:08:17.639 running the pipeline and pushing everything up. So that's why I
01:08:17.639 --> 01:08:21.671 kind of highlighted when Charlie was going through it to check to
01:08:21.671 --> 01:08:24.175 see if there's something LinkedIn there.
01:08:24.265 --> 01:08:27.386 If there's not, we need to reach out and figure out what's going
01:08:27.386 --> 01:08:30.363 on with that. If we're able to QA this particular item or not
01:08:30.363 --> 01:08:30.555 yet.
01:08:31.235 --> 01:08:35.442 And beyond that, from the PM side, if you are more curious
01:08:35.442 --> 01:08:39.649 and you want to kind of do a dive on how I do like a quick
01:08:39.649 --> 01:08:43.856 sniff test of checking the changed files just to make sure
01:08:43.856 --> 01:08:48.206 everything's cool. I'm happy to jump in with you, but that's
01:08:48.206 --> 01:08:50.345 more in the development realm.
01:08:50.835 --> 01:08:52.345 Oh, and if you?
01:08:51.675 --> 01:08:54.648 Brenda, did you? Did you cover? Did you cover how they can get
01:08:54.648 --> 01:08:57.526 to something like this through the tickets as well, like the
01:08:57.526 --> 01:09:00.546 ticket itself? You may already covered that. OK, cool. Sorry. I
01:08:58.325 --> 01:08:58.555 Yeah.
01:09:00.546 --> 01:09:03.424 just know he started at the PM or the pull request dashboard
01:09:03.424 --> 01:09:06.255 here. So I didn't know if you were going through. OK, cool.
01:09:04.925 --> 01:09:05.325 Yeah.
01:09:07.575 --> 01:09:10.844 And something. I mean if you guys want to get crazy with it
01:09:10.844 --> 01:09:14.168 at some point, just hit me up because I could show you how I
01:09:14.168 --> 01:09:17.437 kind of look at things with developers or specific projects
01:09:17.437 --> 01:09:20.870 with, you know, just changing these drop downs to filter. It's
01:09:20.870 --> 01:09:21.905 pretty fascinating.
01:09:22.365 --> 01:09:26.859 I will just go ahead and set that call up because I'd like to
01:09:26.859 --> 01:09:31.498 see that question would be how much time do you wanna set aside
01:09:31.498 --> 01:09:32.005 for it?
01:09:33.075 --> 01:09:36.268 Ohh man we could do. We could do at least at least 1/2 hour for
01:09:36.268 --> 01:09:37.265 sure. Maybe an hour.
01:09:38.855 --> 01:09:39.125 OK.
01:09:39.945 --> 01:09:40.755 Commune coach.
01:09:41.415 --> 01:09:41.785 Yeah.
01:09:43.405 --> 01:09:47.467 Because if I was a PM, I'll tell you guys right now. I would be
01:09:47.467 --> 01:09:51.275 doing this all the time because I'd be like, OK, so in this
01:09:47.865 --> 01:09:48.095 Yep.
01:09:51.275 --> 01:09:55.019 Sprint, what day is this? Sprint. OK, cool. So we've had X
01:09:55.019 --> 01:09:59.081 number of pull requests come in. You could see essentially what
01:09:59.081 --> 01:10:02.825 they're saying is complete here with the task numbers too.
01:10:03.365 --> 01:10:06.317 Umm, so I mean it's it's pretty interesting information that you
01:10:06.317 --> 01:10:07.225 can get out of this.
01:10:10.225 --> 01:10:10.775 Very cool.
01:10:11.795 --> 01:10:15.080 All right, we are a bit over and there's a ton of information
01:10:15.080 --> 01:10:18.258 that just came out. Everybody. How you feeling, doing OK? I
01:10:18.258 --> 01:10:20.695 won't make you go through and tell me you're.
01:10:21.435 --> 01:10:23.005 Happy moments of the week.
01:10:27.515 --> 01:10:32.192 It's just such a big part of what we do like. Yeah, we're
01:10:32.192 --> 01:10:37.272 over. But we've also like left out or skipped over so much. So
01:10:37.272 --> 01:10:41.707 I like, I I can't I the whole way through this. I keep
01:10:37.865 --> 01:10:38.205 Yep.
01:10:41.707 --> 01:10:46.626 thinking. Ohh God, I remember the first time I was trying to
01:10:46.626 --> 01:10:51.625 wrap my brain around a PR. And there's a lot to keep up with.
01:10:53.185 --> 01:10:57.219 And a lot left to do so. Like, don't be dispirited if you feel
01:10:57.219 --> 01:11:00.932 like you're sinking a little bit. Repetition, repetition,
01:11:00.932 --> 01:11:02.725 repetition, it'll get there.
01:11:07.085 --> 01:11:10.566 Alright, awesome. Oh, you guys are the best. I love you. OK,
01:11:10.566 --> 01:11:13.305 get out of here. Goodbye. Have a great weekend.
01:11:13.905 --> 01:11:18.615 I I think thanks team see you guys.
01:11:14.675 --> 01:11:16.405 By everybody have a good weekend.
01:11:14.785 --> 01:11:17.235 Have a great one. Have a good weekend. Bye.
01:11:14.865 --> 01:11:15.605 Thanks everyone.
01:11:16.495 --> 01:11:16.985 I.
01:11:17.025 --> 01:11:18.585 Do you everybody? Bye. Bye.
01:11:18.255 --> 01:11:21.804 I will be doing some work today, so I'm gonna take a little bit
01:11:21.804 --> 01:11:24.355 of a break and then if anybody wants to like.
01:11:25.415 --> 01:11:27.305 You know, work together or something, yeah.
01:11:25.775 --> 01:11:29.025 Shred and hang out, alright? Alright.
01:11:28.005 --> 01:11:28.315 Sure.
01:11:29.495 --> 01:11:32.746 I will be on later after my apartment, Jeff. I tried getting
01:11:29.785 --> 01:11:31.125 Ohh like that.
01:11:32.746 --> 01:11:36.050 Christian set up on one of your projects, but I can't add him
01:11:36.050 --> 01:11:38.715 because he has to be added to the entire project.
01:11:36.575 --> 01:11:36.965 Umm.
01:11:39.495 --> 01:11:42.965 No, no, Christians no longer with clarity so.
01:11:39.655 --> 01:11:40.205 Umm.
01:11:43.455 --> 01:11:46.286 OK, I didn't know if you wanted that line item to be logged or
01:11:46.286 --> 01:11:46.465 not.
01:11:46.705 --> 01:11:48.475 Ohh is it in needs reallocation.
01:11:49.135 --> 01:11:50.075 For PCs.
01:11:50.195 --> 01:11:52.055 Just leave it there for now. I'll take care of it.
01:11:52.475 --> 01:11:52.835 OK.
01:11:54.005 --> 01:11:57.875 OK, beautiful. Alrighty. Thanks everybody.
01:11:55.535 --> 01:11:56.525 You'll have a great weekend.
01:11:56.855 --> 01:11:58.315 Alright. Bye guys. See ya.
01:11:57.135 --> 01:11:58.945 Bye bye. See you everybody.
01:11:58.085 --> 01:11:58.605 Hi all.
01:11:58.845 --> 01:11:59.555 Good weekend y'all.
01:11:59.165 --> 01:11:59.525 Bye.
01:12:00.015 --> 01:12:00.715 Bye.
01:12:00.105 --> 01:12:00.395 Bye.