00:00:03.539 --> 00:00:07.249 It's so the number one first thing that a project is going to
00:00:07.249 --> 00:00:10.660 go through here at clarity is their sales and onboarding
00:00:10.660 --> 00:00:11.139 process.
00:00:11.279 --> 00:00:14.926 So the sales process itself and unfortunately we don't have Ron
00:00:14.926 --> 00:00:18.687 here to speak to us about how he works his magic, but it can be a
00:00:18.687 --> 00:00:22.335 very long process, a lot of our clients will speak to sales for
00:00:22.335 --> 00:00:25.697 years before they will actually move forward with having a
00:00:25.697 --> 00:00:26.609 project with us.
00:00:27.379 --> 00:00:30.357 But through the course of that, sales looks to gather as much
00:00:30.357 --> 00:00:33.240 information from the client as they can about what they are
00:00:33.240 --> 00:00:34.249 actually looking for.
00:00:35.229 --> 00:00:38.612 And at that point, when they have gathered that they will
00:00:38.612 --> 00:00:42.461 present a sales estimate to them and this is an initial estimate,
00:00:42.461 --> 00:00:46.077 very high level estimate for what they think the project that
00:00:46.077 --> 00:00:49.401 the client is asking for would look like financially and
00:00:49.401 --> 00:00:52.609 they'll hammer out an agreement, they'll be contracts.
00:00:52.709 --> 00:00:56.271 Sometimes they will have clauses in them, and that would probably
00:00:56.271 --> 00:00:59.402 be the first thing I would call out to all of our PM team
00:00:59.402 --> 00:01:02.478 members is whenever I project is coming out of the sales
00:01:02.478 --> 00:01:05.933 department, the number one thing we want to be paying attention
00:01:05.933 --> 00:01:09.495 for is anything special in their contract, any special agreements
00:01:09.495 --> 00:01:12.410 they've made any, you know, tweaks that have made our
00:01:12.410 --> 00:01:14.029 standard operating procedures.
00:01:14.239 --> 00:01:17.648 And I'm gonna give you a glimpse as to where you find all these
00:01:17.648 --> 00:01:19.139 fun things as we're talking.
00:01:19.479 --> 00:01:25.257 So we'll go ahead and share my screen, so I through the course
00:01:25.257 --> 00:01:30.943 of the sales process, we will get a contract and we will also
00:01:30.943 --> 00:01:32.869 get a sales estimate.
00:01:33.829 --> 00:01:35.953 And if I would Click to the right place, I could show you
00:01:35.953 --> 00:01:36.429 those things.
00:01:36.439 --> 00:01:40.536 So you will see all of those things in teams if you navigate
00:01:40.536 --> 00:01:44.701 to the teams channels and go to the project you were thinking
00:01:44.701 --> 00:01:48.530 about and you go to their general tab and then you go to
00:01:48.530 --> 00:01:52.426 files, you're gonna look under proposals and within there
00:01:52.426 --> 00:01:56.524 there's going to be worksheets and that is going to show you
00:01:56.524 --> 00:02:00.554 your sales estimate sheet and this is going to have all the
00:02:00.554 --> 00:02:04.854 numbers that sales put out for the client to let them know what
00:02:04.854 --> 00:02:09.153 they think the project is going to take and what features we're
00:02:09.153 --> 00:02:09.959 gonna build.
00:02:10.089 --> 00:02:13.722 And it's gonna boil down to a number number of customized
00:02:13.722 --> 00:02:15.539 hours and a financial number.
00:02:16.919 --> 00:02:19.990 And the second piece of the puzzle that's gonna come out of
00:02:19.990 --> 00:02:22.549 that is going to be their uh legal documentation.
00:02:22.919 --> 00:02:26.272 So you'll find that under legal and if there is a contract which
00:02:26.272 --> 00:02:29.109 they're most certainly will be, you will find it here.
00:02:29.179 --> 00:02:33.001 Sometimes it will be a statement of work, sometimes it will be
00:02:33.001 --> 00:02:36.520 named a different document, but no matter what it will be
00:02:36.520 --> 00:02:40.343 something that both their team and our team will sign and that
00:02:40.343 --> 00:02:42.709 will kind of lay out the expectations.
00:02:42.939 --> 00:02:46.648 So when a project comes from sales to us, the first thing
00:02:46.648 --> 00:02:50.228 you're gonna see is this beautiful ping right here from
00:02:50.228 --> 00:02:52.019 Brooke in the teams channel.
00:02:52.449 --> 00:02:55.024 And it is gonna outline everything she knows about the
00:02:55.024 --> 00:02:55.399 project.
00:02:56.929 --> 00:03:01.499 What we're building for them, what their invoicing plan is and
00:03:01.499 --> 00:03:04.909 most saliently, whether or not they have paid.
00:03:06.669 --> 00:03:10.943 Once the client has submitted payment the first time that PM's
00:03:10.943 --> 00:03:13.929 are going to touch, this entire process is.
00:03:13.939 --> 00:03:17.969 Once that has happened, and once that has happened, we are going
00:03:17.969 --> 00:03:21.690 to send out what we call the project kickoff email and that
00:03:21.690 --> 00:03:25.721 information on that can be found in nuclino like most everything
00:03:25.721 --> 00:03:29.503 here at clarity, there will be an article and you can follow
00:03:29.503 --> 00:03:33.348 this article to do the job that you're supposed to do at that
00:03:33.348 --> 00:03:37.192 point, which is to send your client this general intro letter
00:03:37.192 --> 00:03:40.293 introducing yourself and scheduling their kickoff
00:03:40.293 --> 00:03:40.789 meeting.
00:03:41.549 --> 00:03:44.921 And once you have scheduled their kickoff meeting, then we
00:03:44.921 --> 00:03:46.979 will do that kick off presentation.
00:03:47.369 --> 00:03:50.942 The agenda that you will create for said presentation is here in
00:03:50.942 --> 00:03:54.240 that team's in that Nuclino article as well, and that would
00:03:54.240 --> 00:03:56.109 be your template to do that work.
00:03:56.119 --> 00:04:00.411 Work so project comes in, they pay, we send them this injury
00:04:00.411 --> 00:04:04.704 letter and we work to get their kick off scheduled before we
00:04:04.704 --> 00:04:07.589 actually get into their kickoff meeting.
00:04:07.649 --> 00:04:10.233 The next most important thing we're gonna do is we're gonna
00:04:10.233 --> 00:04:10.879 meet with Kyle.
00:04:11.649 --> 00:04:15.359 And so I'm going to ask Kyle to jump in here and talk to us
00:04:15.359 --> 00:04:19.316 about what we're going to learn from Kyle in that sales handoff
00:04:19.316 --> 00:04:21.419 meeting, if you don't mind, Kyle.
00:04:22.129 --> 00:04:23.089 I I called guy.
00:04:23.099 --> 00:04:23.829 Gotta watch out for him.
00:04:24.469 --> 00:04:26.099 Umm yeah.
00:04:24.519 --> 00:04:24.899 Right.
00:04:26.109 --> 00:04:29.150 So the main stuff that we covered during that handoff is
00:04:29.150 --> 00:04:32.618 going to be first and foremost, who the client is and what we're
00:04:32.618 --> 00:04:33.419 doing for them.
00:04:33.469 --> 00:04:36.039 I mean, in a nutshell, that's what we're gonna be going over.
00:04:36.909 --> 00:04:40.910 So basically in the sales cycle, I will be aggregating different
00:04:40.910 --> 00:04:44.049 notes together requirements that they've provided.
00:04:45.089 --> 00:04:48.131 Pretty much everything that we've captured thus far during
00:04:48.131 --> 00:04:51.277 sales that hand off the main point of that is going to be to
00:04:51.277 --> 00:04:54.629 hand all of that information off to you guys to where we can hit
00:04:54.629 --> 00:04:55.609 the ground running.
00:04:56.229 --> 00:05:00.791 Uh, and I'll usually fill out my onboarding document to the one I
00:05:00.791 --> 00:05:05.284 post pretty much right after the the onboarding meeting is done,
00:05:05.284 --> 00:05:09.500 and that'll be kind of the main thing that the main, I guess
00:05:09.500 --> 00:05:13.716 artifact that we would be going over doing those handoffs is
00:05:13.716 --> 00:05:17.587 exactly what my or what our understanding is up to this
00:05:17.587 --> 00:05:19.039 point of the project.
00:05:20.739 --> 00:05:24.672 And sometimes they can bring new stuff up, so if they bring up
00:05:24.672 --> 00:05:28.356 anything new, or if there's anything specifically that you
00:05:28.356 --> 00:05:32.415 guys need to know coming into a project, that's the main goal of
00:05:32.415 --> 00:05:35.911 that meeting is to make sure I get you all every bit of
00:05:35.911 --> 00:05:39.657 information I can to make sure that handoff is seamless and
00:05:39.657 --> 00:05:40.719 easy as possible.
00:05:42.069 --> 00:05:42.729 The antastic.
00:05:42.739 --> 00:05:46.389 Thank you, Kyle and the attendees at that meeting are
00:05:46.389 --> 00:05:49.499 going to be Kyle Shelton and yourself the PM.
00:05:49.949 --> 00:05:52.598 And so you're gonna learn everything that you can from
00:05:52.598 --> 00:05:55.199 Kyle and from the onboarding document in that moment.
00:05:55.329 --> 00:05:58.798 And you're going to take that along with all the documentation
00:05:58.798 --> 00:06:02.213 that is available in teams and you are going to draw up their
00:06:02.213 --> 00:06:03.039 kickoff agenda.
00:06:03.169 --> 00:06:05.721 And I'm going to go ahead and reshare screen and show you what
00:06:05.721 --> 00:06:06.369 that looks like.
00:06:07.489 --> 00:06:09.379 We won't go through the whole thing cause it's long.
00:06:09.389 --> 00:06:10.419 It's a lot of talking.
00:06:10.629 --> 00:06:14.702 This is a meeting that will be presented by myself or another
00:06:14.702 --> 00:06:18.119 leader in the PM team, especially for our newer PM.
00:06:18.269 --> 00:06:20.459 This is not gonna be something you're gonna be expected to do
00:06:20.459 --> 00:06:21.519 on your own right off the bat.
00:06:21.529 --> 00:06:25.537 Because like I said, it's a lot of information, but the general
00:06:25.537 --> 00:06:28.919 idea of it is you're gonna introduce team and this is
00:06:28.919 --> 00:06:32.426 probably the number one most important slide within the
00:06:32.426 --> 00:06:36.059 document you were going to remind the client exactly what
00:06:36.059 --> 00:06:37.249 Kyle just told you.
00:06:37.259 --> 00:06:38.399 What are we building for that?
00:06:38.899 --> 00:06:40.994 And then you're gonna remind them about their budget
00:06:40.994 --> 00:06:41.469 estimations.
00:06:41.479 --> 00:06:42.749 This is what we're expecting.
00:06:42.999 --> 00:06:45.993 You're gonna give them some initial understandings about
00:06:45.993 --> 00:06:49.303 what timeline looks like, and then you're going to remind them
00:06:49.303 --> 00:06:51.509 about their billing or invoicing cadence.
00:06:52.259 --> 00:06:54.935 And this is going to be your number one goal is to
00:06:54.935 --> 00:06:57.769 communicate this information to them in that meeting.
00:06:58.019 --> 00:07:01.023 And then there's going to be a lot of talking about how
00:07:01.023 --> 00:07:03.812 projects work with us and all the, you know, rules,
00:07:03.812 --> 00:07:05.529 regulations, all that fun stuff.
00:07:05.539 --> 00:07:07.399 And my favorite tagline for this meeting.
00:07:07.409 --> 00:07:10.461 I always say to clients is is is kind of like you've gone to the
00:07:10.461 --> 00:07:13.467 amusement park, you're standing in line for that roller coaster
00:07:13.467 --> 00:07:16.472 that you're super excited about and you have to stand there for
00:07:16.472 --> 00:07:19.149 an hour and listen to the little, you know, radio squawk
00:07:19.149 --> 00:07:22.014 at you about how you need to keep your hands and feet in the
00:07:22.014 --> 00:07:22.859 cart at all times.
00:07:23.309 --> 00:07:24.259 That is this meeting.
00:07:24.269 --> 00:07:28.046 It is like an hour worth of terms and conditions and all the
00:07:28.046 --> 00:07:28.789 do not dues.
00:07:29.939 --> 00:07:31.049 It's a lot of talking.
00:07:31.159 --> 00:07:34.322 It's attiring meeting, but the most important things that we
00:07:34.322 --> 00:07:37.538 want to take the the client to take away from that meeting is
00:07:37.538 --> 00:07:40.442 how we work, what we're expecting to be able to deliver
00:07:40.442 --> 00:07:40.909 for them.
00:07:40.919 --> 00:07:45.115 And then the second piece of the puzzle is what we need from
00:07:45.115 --> 00:07:45.459 that.
00:07:46.079 --> 00:07:49.035 So you will work with Shelton directly to develop this list of
00:07:49.035 --> 00:07:51.569 action items, and sometimes it can be pretty lengthy.
00:07:51.579 --> 00:07:56.425 This this particular one had two slides worth of to DOS for the
00:07:56.425 --> 00:08:01.423 client and you know what we need from them in order to be able to
00:08:01.423 --> 00:08:05.891 push this project forward and then following that meeting,
00:08:05.891 --> 00:08:10.585 your next step is going to be inviting all of those wonderful
00:08:10.585 --> 00:08:14.599 people you just finished meeting with into Basecamp.
00:08:16.079 --> 00:08:18.996 So you're gonna go to base camp and I'll just give you an
00:08:18.996 --> 00:08:19.399 example.
00:08:19.409 --> 00:08:21.759 We'll use nationwide pharmaceuticals.
00:08:22.089 --> 00:08:24.909 You're gonna come to that new project space camp.
00:08:24.919 --> 00:08:28.906 You're gonna click set up people and you are gonna come down here
00:08:28.906 --> 00:08:32.349 and you are gonna add your client's gonna do so through.
00:08:32.389 --> 00:08:35.639 There's going to be a link down here which you won't see right
00:08:35.639 --> 00:08:38.890 now, cuz I already have client on this one, but that says like
00:08:38.890 --> 00:08:42.037 add people from your client, you're going to get your people
00:08:42.037 --> 00:08:45.442 in here and the very first thing you're going to post for them in
00:08:45.442 --> 00:08:48.590 Basecamp is going to be that PowerPoint presentation we just
00:08:48.590 --> 00:08:50.499 gave them the recording of the call.
00:08:50.509 --> 00:08:54.006 They just sat through where we gave them all those terms and
00:08:54.006 --> 00:08:57.445 conditions and you're going to take all of those todos, all
00:08:57.445 --> 00:08:58.649 those lovely, to DOS.
00:08:58.659 --> 00:09:02.229 You just showed them about what they need to do to drive their
00:09:02.229 --> 00:09:05.685 project to success, and you're going to come into your to-do
00:09:05.685 --> 00:09:09.199 section and you were going to write them all out and you were
00:09:09.199 --> 00:09:12.655 going to assign them to the client, and you're gonna set due
00:09:12.655 --> 00:09:16.055 dates and you're gonna do all the great things to make sure
00:09:16.055 --> 00:09:19.399 that the client knows what exactly we need when we need it
00:09:19.399 --> 00:09:22.629 from them and how important it is for them to get those.
00:09:22.769 --> 00:09:24.019 That's the that.
00:09:24.329 --> 00:09:24.899 Excuse me.
00:09:25.049 --> 00:09:28.609 Get us those pieces of information to drive the project
00:09:28.609 --> 00:09:32.487 towards success and at that point we will have completed the
00:09:32.487 --> 00:09:36.492 kickoff phase of the project and your next step is going to be
00:09:36.492 --> 00:09:40.242 scheduling your client some discovery meetings and at that
00:09:40.242 --> 00:09:42.849 point, we're gonna turn it over Shelton.
00:09:43.359 --> 00:09:46.801 And so I would love to invite Shelton to unmute now if he's
00:09:46.801 --> 00:09:50.359 willing and give us an idea of what the goal of discovery is.
00:09:52.659 --> 00:09:57.962 So the most important thing with discovery and something that's
00:09:57.962 --> 00:10:02.603 easily can be done by anyone, especially me, is kind of
00:10:02.603 --> 00:10:07.575 veering away from what the client originally discussed with
00:10:07.575 --> 00:10:11.719 sales and versus what you discussed in discovery.
00:10:12.309 --> 00:10:13.919 Umm, so a lot of times.
00:10:13.969 --> 00:10:16.729 Uh, you know, they'll go through on boarding with sales.
00:10:16.739 --> 00:10:21.031 They'll discuss certain things, and then by the time the project
00:10:21.031 --> 00:10:25.192 reaches discovery, they'll have new ideas that they've already
00:10:25.192 --> 00:10:29.088 discussed are throughout our discussions in Discovery, new
00:10:29.088 --> 00:10:32.918 features or requirements or revealed, and one of the most
00:10:32.918 --> 00:10:37.012 important things to do is to make sure that in that moment or
00:10:37.012 --> 00:10:41.173 either very quickly after that, any new items that are brought
00:10:41.173 --> 00:10:45.333 up in discovery that are deemed out of scope from the original
00:10:45.333 --> 00:10:49.625 estimates from the cells team is something that's called out and
00:10:49.625 --> 00:10:53.786 brought up with the client as well as with our leadership team
00:10:53.786 --> 00:10:55.899 and the project management team.
00:10:56.839 --> 00:11:00.954 Now it's not to say that clients cannot change a scope of their
00:11:00.954 --> 00:11:04.361 project or change their requirements, but we have to
00:11:04.361 --> 00:11:08.476 make it known to them that any changes that they request during
00:11:08.476 --> 00:11:12.141 discovery are is something that's gonna be an additional
00:11:12.141 --> 00:11:15.998 cost to the project and could impact budget and timeline as
00:11:15.998 --> 00:11:20.049 well as additional features that we were planning to build out
00:11:20.049 --> 00:11:22.299 from the original sales estimates.
00:11:24.529 --> 00:11:28.483 Umm, so that's just one of the biggest pieces of discovery to
00:11:28.483 --> 00:11:32.373 ensure that we're on top of and that's more of of a note for
00:11:32.373 --> 00:11:34.159 myself than you guys's PM's.
00:11:34.169 --> 00:11:38.564 But Mickey and Cassie, they do a very good job of jumping in and
00:11:38.564 --> 00:11:42.622 reminding me that, you know, this is out of scope or are we
00:11:42.622 --> 00:11:46.882 sure that this was an originals or this is different than what
00:11:46.882 --> 00:11:48.979 we had previously talked about?
00:11:48.989 --> 00:11:52.835 So I had to rely on you guys to keep me on track and help get
00:11:52.835 --> 00:11:54.759 the project on track with that.
00:11:55.329 --> 00:11:59.112 But essentially, the overall process of discovery, how it
00:11:59.112 --> 00:12:02.699 goes is we schedule our first meeting with the client.
00:12:03.779 --> 00:12:06.729 We have our original sales estimate line items.
00:12:06.739 --> 00:12:08.589 We present that document to them.
00:12:08.939 --> 00:12:09.329 Uh.
00:12:09.339 --> 00:12:13.144 During that, we go through each of the line items and we go over
00:12:13.144 --> 00:12:16.599 the overall scope or high level scope that they discussed.
00:12:16.609 --> 00:12:20.149 The cells make sure that we're on the right track and then
00:12:20.149 --> 00:12:23.689 essentially we progressed through the workflow of the site
00:12:23.689 --> 00:12:27.229 and discuss each of those different feature line items and
00:12:27.229 --> 00:12:28.669 gather the requirements.
00:12:29.159 --> 00:12:32.100 Make sure you know nothing's changed, or if things have
00:12:32.100 --> 00:12:34.149 changed, we document that accordingly.
00:12:36.009 --> 00:12:40.554 Another item that we've been looking to focus on a little bit
00:12:40.554 --> 00:12:43.779 earlier in the process is the integrations.
00:12:44.309 --> 00:12:48.968 So Jeremy Larose will typically be in addition to the call for
00:12:48.968 --> 00:12:53.257 projects that we'll have an integration, whether it be an
00:12:53.257 --> 00:12:57.621 integrated stuff project or a connect project that is just
00:12:57.621 --> 00:13:00.579 integration between to outside systems.
00:13:01.029 --> 00:13:03.719 So what we've been trying to do is get that integration
00:13:03.719 --> 00:13:05.689 discussion started a little bit earlier.
00:13:06.369 --> 00:13:09.012 Take a look at their the instance we're gonna be
00:13:09.012 --> 00:13:09.929 integrating with.
00:13:09.939 --> 00:13:14.475 Seeing what customizations may be needed, identifying those
00:13:14.475 --> 00:13:18.557 early in the process of discovery process rather than
00:13:18.557 --> 00:13:23.093 later because syncs can be somewhat of a pain to the entire
00:13:23.093 --> 00:13:24.529 process as a whole.
00:13:24.759 --> 00:13:28.690 You know, we may finish the self side of discovery or finish
00:13:28.690 --> 00:13:32.169 discovery and then realize you know there's all these
00:13:32.169 --> 00:13:36.294 additional pieces or this these areas that we run into with the
00:13:36.294 --> 00:13:40.225 syncs at a later date because we didn't spend enough initial
00:13:40.225 --> 00:13:42.029 time, uh on the integration.
00:13:42.039 --> 00:13:45.900 So that's something that we've been trying to improve upon and
00:13:45.900 --> 00:13:49.884 spend a little bit more time on and the discovery process is you
00:13:49.884 --> 00:13:53.684 know, it doesn't have to be the very first call, but within a
00:13:53.684 --> 00:13:57.239 typical week, we have two meetings with the client moving
00:13:57.239 --> 00:13:57.729 forward.
00:13:57.739 --> 00:14:01.053 It's going to be best if at least one of those meetings, if
00:14:01.053 --> 00:14:04.589 not both, are spent discussing the integration with the client.
00:14:07.049 --> 00:14:10.426 Once we, you know, start discovery, discuss integration,
00:14:10.426 --> 00:14:11.729 finalize requirements.
00:14:11.739 --> 00:14:13.039 Uh, with the client?
00:14:13.109 --> 00:14:16.725 What we do is we have a bird, a business requirement document
00:14:16.725 --> 00:14:20.225 where we capture all of the information from discovery, the
00:14:20.225 --> 00:14:22.909 project requirements and scope we would then.
00:14:25.099 --> 00:14:29.989 Finalize that and complete what we call project architecture.
00:14:30.579 --> 00:14:34.255 Project architecture is typically done with myself and
00:14:34.255 --> 00:14:34.589 Eric.
00:14:34.899 --> 00:14:38.510 Uh, sometimes other team members jump in to estimate some
00:14:38.510 --> 00:14:42.619 features, but during the project architecture phase of discovery,
00:14:42.619 --> 00:14:46.106 what Eric and myself will do will sit down, look at the
00:14:46.106 --> 00:14:49.966 requirements and determine, you know, kind of at a high level
00:14:49.966 --> 00:14:54.075 what it's gonna take to complete those features and the number of
00:14:54.075 --> 00:14:56.939 hours that each of the features will require.
00:14:58.689 --> 00:15:02.586 This is where we'll identify, post estimates, scope or scope
00:15:02.586 --> 00:15:06.164 that was determined to be outside of the original sales
00:15:06.164 --> 00:15:06.739 estimate.
00:15:06.969 --> 00:15:10.989 We typically divide the document into original scope versus post
00:15:10.989 --> 00:15:11.979 estimates scope.
00:15:12.249 --> 00:15:15.606 Once we have project architecture completed, what we
00:15:15.606 --> 00:15:19.660 do, what we call our reestimates process, this is where we take
00:15:19.660 --> 00:15:23.523 the original line items from the sales estimate spreadsheet,
00:15:23.523 --> 00:15:26.500 compare those against the numbers from project
00:15:26.500 --> 00:15:30.364 Architecture, see if there's been in the original line items
00:15:30.364 --> 00:15:34.165 that had further complexities throughout discovery that the
00:15:34.165 --> 00:15:37.712 hours required and increase sometimes the original line
00:15:37.712 --> 00:15:41.702 items would reduce, they would turned out to not be as complex
00:15:41.702 --> 00:15:42.589 as we thought.
00:15:42.599 --> 00:15:46.884 So there could be an hours reduction for an original line
00:15:46.884 --> 00:15:51.390 item and then similar to the BRD, we have our post estimates
00:15:51.390 --> 00:15:55.749 scope that is a separate section of the reestimates sheet.
00:15:55.839 --> 00:15:59.006 This is where we outline, you know, what new features, what
00:15:59.006 --> 00:16:02.225 new requirements came up during the discovery, the number of
00:16:02.225 --> 00:16:05.445 hours we estimate it's gonna take to build those out and all
00:16:05.445 --> 00:16:06.659 of that together would.
00:16:07.779 --> 00:16:11.331 So I'm up to our new RE estimated value for the project
00:16:11.331 --> 00:16:15.073 and this would be the final number of hours as well as the
00:16:15.073 --> 00:16:19.005 total cost for the final project that we would present to the
00:16:19.005 --> 00:16:19.449 client.
00:16:20.349 --> 00:16:20.979 And I will.
00:16:20.989 --> 00:16:23.815 I will step in there and interrupt you and add a word
00:16:23.815 --> 00:16:25.019 there, final estimated.
00:16:27.389 --> 00:16:27.699 Numbers.
00:16:28.419 --> 00:16:29.419 We don't guarantee you.
00:16:29.879 --> 00:16:33.499 Yeah, if you hear the word fixed, just run scare.
00:16:30.129 --> 00:16:30.839 Thank you, Kathy.
00:16:32.589 --> 00:16:38.369 Run and and get an adult on your way. Uh-huh.
00:16:33.029 --> 00:16:33.189 You.
00:16:35.419 --> 00:16:38.279 Yeah, yeah, yeah.
00:16:36.179 --> 00:16:40.409 Yeah, scream and fight pushback, yeah.
00:16:38.019 --> 00:16:39.019 And as the baby?
00:16:42.139 --> 00:16:43.189 Alright, thank you Shelton.
00:16:42.699 --> 00:16:45.979 I I ran and got Phil when I heard it, I said Phil help.
00:16:43.199 --> 00:16:44.039 I really appreciate that.
00:16:44.499 --> 00:16:45.299 Yeah, that's sorry.
00:16:45.309 --> 00:16:46.609 I feel like I ran long.
00:16:46.999 --> 00:16:48.149 No, no, that's perfect.
00:16:48.559 --> 00:16:49.019 Go ahead, Eric.
00:16:50.309 --> 00:16:52.529 I said I ran and got Phil when I heard it. So.
00:16:53.209 --> 00:16:54.999 See, you gotta get an adult.
00:16:55.319 --> 00:16:56.099 Alright.
00:16:56.109 --> 00:16:56.479 Thank you.
00:16:56.489 --> 00:16:56.789 Thank you.
00:16:56.799 --> 00:16:57.279 Thank you.
00:16:57.329 --> 00:17:01.679 That was perfect in terms of how the PM fits into that process.
00:17:02.149 --> 00:17:05.630 You're gonna be a scheduling the meetings for Shelton to meet
00:17:05.630 --> 00:17:06.529 with the client.
00:17:06.649 --> 00:17:10.113 You will sometimes attend them, hopefully, eventually we will
00:17:10.113 --> 00:17:13.689 get to the point where everybody is just attending on their own
00:17:13.689 --> 00:17:16.818 with Shelton, but in the meantime there I will be there
00:17:16.818 --> 00:17:20.171 to support you and that we may flex that as we move forward
00:17:20.171 --> 00:17:23.747 depending on how we think that's best architected and set up in
00:17:23.747 --> 00:17:25.759 terms of who attends what meetings.
00:17:26.139 --> 00:17:30.602 But for now you will be jumping in there wish outing and myself
00:17:30.602 --> 00:17:34.438 to attend all of those discovery meetings and then the
00:17:34.438 --> 00:17:38.344 presentation of the BRD and the REESTIMATES will be the
00:17:38.344 --> 00:17:39.669 conclusion of that.
00:17:40.019 --> 00:17:43.114 So you'll be scheduling meetings during that time, supporting
00:17:43.114 --> 00:17:46.209 Shelton in paying attention to the calls as you're there with
00:17:46.209 --> 00:17:46.409 him.
00:17:46.629 --> 00:17:50.444 I'm trying to make note of like he said, any red flags, anything
00:17:50.444 --> 00:17:53.907 that to you sounds not like something you read anywhere in
00:17:53.907 --> 00:17:57.604 the documentation that you've already seen for the project and
00:17:57.604 --> 00:18:01.360 just doing your best to support him and making sure we catch as
00:18:01.360 --> 00:18:02.769 many of those as we can.
00:18:04.309 --> 00:18:07.724 And then attending the scheduling first and then
00:18:07.724 --> 00:18:11.836 attending the RE estimates presentation once this document
00:18:11.836 --> 00:18:16.088 has been approved by management to go to the client, we will
00:18:16.088 --> 00:18:20.409 attend that meeting, present this information and then follow
00:18:20.409 --> 00:18:24.801 up with the client in Basecamp to get sign off on the bird and
00:18:24.801 --> 00:18:27.519 the reestimates document as presented.
00:18:27.609 --> 00:18:31.321 And you know, as we called out there and as Cassie said, these
00:18:31.321 --> 00:18:32.559 are never guarantees.
00:18:33.219 --> 00:18:34.969 Neither is there timeline.
00:18:35.219 --> 00:18:37.149 Uh, these are always just estimates.
00:18:37.619 --> 00:18:39.769 Unexpected complexities can come up.
00:18:40.059 --> 00:18:42.449 Things can get added to scope.
00:18:42.539 --> 00:18:45.754 There can be issues along the way, so nothing is ever
00:18:45.754 --> 00:18:46.409 guaranteed.
00:18:46.419 --> 00:18:47.549 Nothing is ever a promise.
00:18:47.559 --> 00:18:50.967 Everything is always an estimate and we are a time and materials
00:18:50.967 --> 00:18:51.439 business.
00:18:51.579 --> 00:18:57.019 So everybody's time costs money, right? Yes.
00:18:55.709 --> 00:18:56.209 I have a question.
00:18:57.579 --> 00:19:00.556 So for the when it comes to a meeting, you said catching red
00:19:00.556 --> 00:19:00.849 flags.
00:19:01.199 --> 00:19:03.039 Is that something we discussed after the meeting?
00:19:03.659 --> 00:19:03.959 Mm-hmm.
00:19:04.519 --> 00:19:05.279 OK, make sure.
00:19:05.589 --> 00:19:06.009 Yes.
00:19:06.309 --> 00:19:07.879 Now, when when you're.
00:19:07.929 --> 00:19:11.355 Uh, you know, Shelton and me and you've been here a while and you
00:19:11.355 --> 00:19:13.639 know you have good rapport with the client.
00:19:13.709 --> 00:19:17.693 You can absolutely speak up in a meeting, generally in terms of
00:19:15.869 --> 00:19:16.069 Yeah.
00:19:17.693 --> 00:19:20.059 how we will function, even ourselves.
00:19:20.489 --> 00:19:23.197 Very often we will ping each other on the side and a side
00:19:23.197 --> 00:19:26.139 chat that the client cannot see and say hey, that didn't sound
00:19:26.139 --> 00:19:26.699 right to me.
00:19:26.579 --> 00:19:27.439 Yeah. OK.
00:19:26.769 --> 00:19:29.991 Did you catch that and give us an opportunity to kind of
00:19:29.991 --> 00:19:33.214 confirm amongst ourselves before someone breaks into the
00:19:33.214 --> 00:19:36.663 conversation and says, hey, you know Joe, you just mentioned
00:19:36.663 --> 00:19:39.829 this feature, I'm not seeing that anywhere on the list.
00:19:39.839 --> 00:19:42.829 Uh, we're happy to spec that out, but I think that is outside
00:19:42.829 --> 00:19:45.579 of of scope a lot of times what we will do is we'll just
00:19:44.559 --> 00:19:44.829 OK.
00:19:45.579 --> 00:19:48.183 actually get some more information from them and then
00:19:48.183 --> 00:19:51.174 come back to them at the next meeting and say, hey, you know,
00:19:51.174 --> 00:19:53.923 we talked about this feature yesterday, we went back and
00:19:53.923 --> 00:19:55.949 checked and I'm not seeing that anywhere.
00:19:55.959 --> 00:19:59.203 Happy to build it, but that will be additional scope for the
00:19:59.203 --> 00:19:59.629 project.
00:19:59.679 --> 00:20:00.339 Something like that.
00:20:00.079 --> 00:20:01.059 Our purpose perfect.
00:20:01.619 --> 00:20:02.109 Yeah.
00:20:02.339 --> 00:20:06.139 And you will very frequently see me interrupt Shelton and call
00:20:06.139 --> 00:20:09.698 something out right in the moment if it's very urgent, you
00:20:09.698 --> 00:20:13.257 know, a client says something like the word fixed bid or I
00:20:13.257 --> 00:20:15.489 want this launched 2 weeks from now.
00:20:15.559 --> 00:20:15.839 Umm.
00:20:16.039 --> 00:20:16.969 I'm not gonna wait.
00:20:16.979 --> 00:20:18.229 I'm gonna raise my hand if you like.
00:20:18.239 --> 00:20:20.769 Hi no, in a very polite way.
00:20:19.209 --> 00:20:21.559 That might work, yeah.
00:20:23.419 --> 00:20:28.373 You know, so yes, but in terms of where we are now, definitely
00:20:28.373 --> 00:20:30.339 ping alongside if needed.
00:20:30.349 --> 00:20:31.569 Like I said, call it adult.
00:20:31.579 --> 00:20:33.629 Get Brandon, get me.
00:20:33.949 --> 00:20:36.882 Yell for help if you're hearing something that you're just like,
00:20:36.882 --> 00:20:37.469 that's wrong.
00:20:37.479 --> 00:20:38.179 That sounds bad.
00:20:39.159 --> 00:20:41.809 That, yeah, OK, cool.
00:20:40.069 --> 00:20:40.489 And perfect.
00:20:41.149 --> 00:20:41.559 Yeah.
00:20:41.199 --> 00:20:43.509 I will say really go ahead.
00:20:41.569 --> 00:20:42.519 Take let me take it.
00:20:42.529 --> 00:20:43.179 Oh, go ahead, Cassie.
00:20:43.519 --> 00:20:44.089 Sorry, Eric.
00:20:44.099 --> 00:20:44.339 Go ahead.
00:20:44.479 --> 00:20:45.119 No, no, no.
00:20:45.129 --> 00:20:45.429 You go ahead.
00:20:45.899 --> 00:20:50.259 Sorry, I will say that, you know, sometimes maybe during the
00:20:46.299 --> 00:20:47.439 You're you're the PM.
00:20:47.449 --> 00:20:47.899 Go for it.
00:20:50.259 --> 00:20:54.762 meeting as as I've been ramping up, you know, I'll ask Micki a
00:20:54.762 --> 00:20:59.336 question in teams like this, you know, this doesn't sound right
00:20:59.336 --> 00:21:01.409 to me or something like that.
00:21:01.479 --> 00:21:05.922 And she's she's always really great to take that conversation
00:21:05.922 --> 00:21:06.209 too.
00:21:06.219 --> 00:21:09.581 But I've I've gotten also comfortable in the last couple
00:21:09.581 --> 00:21:13.298 of weeks just to, you know, once she says, yeah, I acknowledge
00:21:13.298 --> 00:21:13.829 that too.
00:21:13.839 --> 00:21:17.206 Then I'll just say it as well, but it's always, you know,
00:21:17.206 --> 00:21:20.921 helpful to have those teammates on the side there to, you know,
00:21:20.921 --> 00:21:23.649 confirm your thoughts before talking about it.
00:21:24.699 --> 00:21:26.469 Absolutely, Eric.
00:21:27.179 --> 00:21:27.779 Uh, yeah.
00:21:27.799 --> 00:21:30.689 Man, I think you're as a as a really anybody.
00:21:30.699 --> 00:21:34.449 Developers PM BA anybody on a call with a with a client.
00:21:34.519 --> 00:21:35.909 Your your biggest weapon.
00:21:36.159 --> 00:21:37.970 You know, when you're when you get stuck is let me take that
00:21:37.970 --> 00:21:39.099 back to the team and get back to you.
00:21:39.709 --> 00:21:42.999 Pecchia is never, ever, ever a bad thing.
00:21:43.009 --> 00:21:45.199 To admit that you don't know the answer to something.
00:21:45.209 --> 00:21:48.968 If client asks the question or says a statement that you feel
00:21:45.429 --> 00:21:45.649 Yep.
00:21:48.968 --> 00:21:52.667 weird about, you know just being very calm and confident and
00:21:52.667 --> 00:21:53.759 being like, great.
00:21:53.769 --> 00:21:54.189 Thank you.
00:21:54.289 --> 00:21:56.893 You know, for that information, let me take that to the team and
00:21:56.893 --> 00:21:59.416 we'll talk about it internally and I'll get back with you with
00:21:59.416 --> 00:22:01.299 more information when I have it ready for you.
00:22:02.299 --> 00:22:05.779 It's actually one of your strongest and best tools.
00:22:07.709 --> 00:22:08.109 Here.
00:22:08.049 --> 00:22:08.679 Indeed.
00:22:08.119 --> 00:22:11.259 Here. Totally agree.
00:22:11.549 --> 00:22:14.619 Alright, so back to the project lifecycle.
00:22:14.709 --> 00:22:17.701 So while we are kind of in hand in hand with us doing the
00:22:17.701 --> 00:22:20.900 discovery and kind of already talked to this, but I'd like to
00:22:20.900 --> 00:22:23.945 invite Eric to give us a little bit more information on it
00:22:23.945 --> 00:22:25.699 happens the architecture process.
00:22:25.709 --> 00:22:29.149 So while we are meeting with the client regularly and gathering
00:22:29.149 --> 00:22:32.105 all their requirements and learning about what they're
00:22:32.105 --> 00:22:35.384 meeting this project to do, Shelton and Eric are on the side
00:22:35.384 --> 00:22:38.824 also working on building out the project level architecture and
00:22:38.824 --> 00:22:41.888 then that project level architecture will become feature
00:22:41.888 --> 00:22:44.629 level architecture and on and on down the process.
00:22:44.699 --> 00:22:47.330 So I'd love to invite Eric to tell us a little bit more about
00:22:47.330 --> 00:22:49.749 that phase and maybe how the PM can support him in that.
00:22:50.709 --> 00:22:51.179 Yeah.
00:22:51.189 --> 00:22:55.876 So a lot of times requirements come in and they they seem
00:22:55.876 --> 00:23:01.209 fairly straightforward and and a lot of times sometimes they are.
00:23:01.319 --> 00:23:04.933 But what Shelton I do in that is really just kind of breakdown
00:23:04.933 --> 00:23:08.491 the full requirement, make sure we have all the questions you
00:23:08.491 --> 00:23:11.876 know and then then ultimately and this is something that I
00:23:11.876 --> 00:23:15.433 need to work on, but there's a checklist checklist kind of in
00:23:15.433 --> 00:23:18.704 our minds of OK does this does integration, is there any
00:23:18.704 --> 00:23:22.318 integration factors that this where we're going to need to get
00:23:22.318 --> 00:23:25.818 data from one place or another push it one place to another,
00:23:25.818 --> 00:23:29.433 are there other what factors and what features on the site are
00:23:29.433 --> 00:23:32.990 are talked about here and you know can we can we reuse pieces
00:23:32.990 --> 00:23:36.547 or do we need to you know is this net new, what does it, what
00:23:36.547 --> 00:23:39.703 does it touch around it for example if you're touching
00:23:39.703 --> 00:23:43.432 something around the cart there is a lot that goes into the cart
00:23:43.432 --> 00:23:43.949 workflow.
00:23:43.959 --> 00:23:48.831 It's a very, very complicated and fragile workflow, and so we
00:23:48.831 --> 00:23:53.467 look at what are, what's going to be necessary to complete
00:23:53.467 --> 00:23:56.689 this, what are the risk areas with this?
00:23:56.899 --> 00:23:59.843 Is it going to be something that's high risk because we're
00:23:59.843 --> 00:24:03.087 dealing with the cart and we're doing a lot of customizations on
00:24:03.087 --> 00:24:06.130 the cart in terms of, you know, we're using like for forever
00:24:06.130 --> 00:24:09.374 stone, for example, we're doing a lot of static carts broken out
00:24:09.374 --> 00:24:11.969 by factories and there's a lot that goes into that.
00:24:11.979 --> 00:24:16.520 And so the best thing we can do is when we have questions in to
00:24:16.520 --> 00:24:21.060 DOS and I think you'll probably get to this shortly, Mickey, or
00:24:21.060 --> 00:24:25.246 if you haven't already, just posting those to Basecamp and
00:24:25.246 --> 00:24:26.169 following up.
00:24:26.559 --> 00:24:30.250 I try and do is the best I can about following up on emails
00:24:30.250 --> 00:24:33.879 with todo questions, but I admit that I'm not great at it.
00:24:34.169 --> 00:24:37.722 So if if you see questions coming in or answers the
00:24:37.722 --> 00:24:42.095 questions coming in, just saying hey, did you see this would be
00:24:42.095 --> 00:24:42.779 fantastic?
00:24:42.789 --> 00:24:44.899 I would love that and Shelton does a pretty good job of it.
00:24:45.109 --> 00:24:48.138 Keep me on track as well, but yeah, that's kind of our
00:24:48.138 --> 00:24:48.579 project.
00:24:48.589 --> 00:24:51.586 I don't know if Micki is there anything specific you wanted to
00:24:51.586 --> 00:24:53.299 talk about or what that looks like.
00:24:53.309 --> 00:24:55.139 If I need to expand on anything else.
00:24:55.679 --> 00:24:56.389 I I will.
00:24:56.399 --> 00:25:00.068 I will annoy you to expand a little bit further once I talk
00:25:00.068 --> 00:25:02.209 about Gantt charts, but thank you.
00:25:00.689 --> 00:25:02.759 Yeah, sure.
00:25:02.689 --> 00:25:05.533 Alright, so that brought up a really good point that I wanna
00:25:05.533 --> 00:25:06.559 hammer home right now.
00:25:07.059 --> 00:25:09.969 Never ever, ever feel like you are being annoying.
00:25:10.319 --> 00:25:14.823 That is 100% our role and the team is actually wanting that of
00:25:14.823 --> 00:25:15.109 you.
00:25:15.179 --> 00:25:18.838 OK, so if a document comes in to basecamp and you see it, there
00:25:18.838 --> 00:25:22.268 is absolutely no harm, no foul and pinging Shelton and just
00:25:22.268 --> 00:25:25.869 being like hey Shelton, did you see this document that came in
00:25:25.869 --> 00:25:28.099 because yeah, he probably already did.
00:25:28.109 --> 00:25:28.859 But you know what?
00:25:28.869 --> 00:25:31.169 In case he didn't, you just saved him.
00:25:31.219 --> 00:25:34.226 You just caught a problem before it happened, and the same thing
00:25:34.226 --> 00:25:34.689 with Eric.
00:25:34.789 --> 00:25:37.486 If you see something come in that you know Eric's been
00:25:37.486 --> 00:25:40.330 working on or looking for information or a document, just
00:25:40.330 --> 00:25:43.126 sending a pain and being like, hey, did you see this and
00:25:43.126 --> 00:25:46.019 linking him the doc or, you know, getting it right to him?
00:25:46.029 --> 00:25:49.039 Him none of that is ever annoying.
00:25:49.209 --> 00:25:50.399 That is your job.
00:25:50.549 --> 00:25:54.179 You are here to over communicate and I cannot stress that enough.
00:25:54.449 --> 00:25:56.859 I want to hear from you guys constantly.
00:25:56.869 --> 00:25:58.609 I want the team to hear from you constantly.
00:25:59.469 --> 00:26:00.359 That is our role.
00:26:00.369 --> 00:26:02.169 We are the communicators, dujour.
00:26:02.909 --> 00:26:03.279 Heard.
00:26:05.099 --> 00:26:08.859 Heard over communicators unite?
00:26:06.099 --> 00:26:06.839 Heard dunker.
00:26:06.359 --> 00:26:06.829 Your ear.
00:26:07.509 --> 00:26:09.679 Or for.
00:26:08.919 --> 00:26:09.259 Heard.
00:26:09.479 --> 00:26:10.449 Yes, ma'am.
00:26:11.299 --> 00:26:12.429 Alright, thank you.
00:26:12.719 --> 00:26:16.541 So we've now reached the point in the project in which we've
00:26:16.541 --> 00:26:20.364 developed those feature or the project level architecture we
00:26:20.364 --> 00:26:21.429 have estimations.
00:26:21.439 --> 00:26:22.589 We have a BRD.
00:26:22.599 --> 00:26:27.741 We've given it to the client and they say yes, Hazar, we're ready
00:26:27.741 --> 00:26:28.209 to go.
00:26:29.199 --> 00:26:32.682 And at this point this triggers a whole cascade of fun things
00:26:32.682 --> 00:26:33.749 that we have to do.
00:26:35.289 --> 00:26:38.798 Number one thing that's going to happen is Eric is gonna turn
00:26:38.798 --> 00:26:42.363 Daniel loose on the Miro board, and he's gonna turn everything
00:26:42.363 --> 00:26:43.099 into tickets.
00:26:43.389 --> 00:26:46.404 So Daniel, I'd love for you to pop in and just kind of talk
00:26:46.404 --> 00:26:47.309 about that moment.
00:26:49.369 --> 00:26:50.349 Yeah, certainly so.
00:26:49.399 --> 00:26:50.949 Can we get somebody to show a Miro board?
00:26:51.809 --> 00:26:56.620 I have one, but it's about HALA and it does not have a lot, so
00:26:55.019 --> 00:26:56.819 I would go repro or ever probably.
00:26:55.309 --> 00:26:55.979 No, I got it.
00:26:56.589 --> 00:26:58.439 That was it that I don't know where you joking, Eric?
00:26:56.620 --> 00:26:56.849 OK.
00:26:57.789 --> 00:26:58.029 I was.
00:27:00.499 --> 00:27:00.969 I have.
00:27:00.979 --> 00:27:02.339 I have one pulled up, that's.
00:27:01.179 --> 00:27:01.499 OK.
00:27:02.759 --> 00:27:03.709 No, I I yeah.
00:27:03.719 --> 00:27:06.269 I figured Daniel would be on it, but I didn't know if you had it
00:27:05.579 --> 00:27:05.819 Yeah.
00:27:05.689 --> 00:27:06.119 E perfect.
00:27:06.269 --> 00:27:08.505 queued or if we wanted somebody else's share it or yeah,
00:27:08.505 --> 00:27:09.329 alright, fair enough.
00:27:08.569 --> 00:27:14.079 I am looking at Miro roughly 6 of the 9 hours a day.
00:27:14.169 --> 00:27:19.965 OK so so Miro boards guys so kind of in part of that whole
00:27:14.819 --> 00:27:15.229 Like.
00:27:19.965 --> 00:27:26.155 workflow and Jordan and Julian have been seeing me share a lot
00:27:26.155 --> 00:27:27.629 of this lately.
00:27:28.179 --> 00:27:30.139 So let's just go full camera, OK.
00:27:33.269 --> 00:27:33.609 OK.
00:27:33.649 --> 00:27:37.290 So when it comes to the mural boards, this has been an ongoing
00:27:37.290 --> 00:27:40.873 structure and part of what I want to show you at that is kind
00:27:40.873 --> 00:27:42.549 of show you how it's evolved.
00:27:42.589 --> 00:27:44.715 Because I think that's part of what's interesting, and it's
00:27:44.715 --> 00:27:46.239 also part of kind of what makes it strong.
00:27:46.489 --> 00:27:49.137 So we're gonna go back to one that we don't really wanna talk
00:27:49.137 --> 00:27:50.419 about too much, but it's fine.
00:27:50.459 --> 00:27:51.239 It's a good one.
00:27:51.589 --> 00:27:55.962 Good enough as we go over here to like 10, the structure of it
00:27:55.962 --> 00:28:00.058 all is here all the same, where we have our features, user
00:28:00.058 --> 00:28:02.279 stories and the like broken out.
00:28:04.999 --> 00:28:06.189 And also I want you to see these.
00:28:06.199 --> 00:28:08.995 I want when you if you ever have to go to an older one, don't be
00:28:08.995 --> 00:28:11.534 scared because it's not in the same structure you have our
00:28:11.534 --> 00:28:13.169 features and user stories broken out.
00:28:13.179 --> 00:28:16.877 It's kind of this sort of more like like a creative person's
00:28:16.877 --> 00:28:17.969 mind space, right?
00:28:17.979 --> 00:28:19.469 It's kind of flowing through.
00:28:19.519 --> 00:28:20.849 We see where things are going.
00:28:20.859 --> 00:28:22.169 You can kind of follow a thing.
00:28:23.019 --> 00:28:27.103 Then we get to our kind of version two or three or four
00:28:27.103 --> 00:28:29.729 even would be like Craig and repro.
00:28:29.919 --> 00:28:31.489 We're kind of getting the pieces together.
00:28:31.779 --> 00:28:33.439 Things are a bit more succinct.
00:28:34.549 --> 00:28:37.998 Where we're getting the workflows more unified and
00:28:37.998 --> 00:28:39.689 everything else remember.
00:28:39.699 --> 00:28:44.850 And I was talking to Julian and John about this earlier is Miro
00:28:44.850 --> 00:28:46.379 boards are immense.
00:28:46.509 --> 00:28:49.941 You can make them as big as you possibly wanna possibly want,
00:28:49.941 --> 00:28:53.373 but they can be really big and you can waste a lot of time by
00:28:53.373 --> 00:28:54.259 making them big.
00:28:54.409 --> 00:28:57.146 So anytime you're going to Miro or making your own Miro, start
00:28:57.146 --> 00:28:58.319 small, small, small, small.
00:28:58.329 --> 00:29:01.574 Small, so let's zoom in on this one and we kind of see the
00:29:01.574 --> 00:29:02.069 workflow.
00:29:03.399 --> 00:29:07.167 So when we basically once we start discovery, we'll start up
00:29:07.167 --> 00:29:10.009 top here and put the original estimates here.
00:29:10.379 --> 00:29:13.475 This is intentional, just so everyone can kind of see and get
00:29:13.475 --> 00:29:16.521 an idea of what the project was at the very beginning of it,
00:29:16.521 --> 00:29:18.519 before the ball really started rolling.
00:29:20.129 --> 00:29:23.830 Then down here we have the original estimates for all of
00:29:23.830 --> 00:29:25.259 the original features.
00:29:25.689 --> 00:29:28.974 This is so that the folks who are working on it can take them
00:29:28.974 --> 00:29:31.729 and we can make sure that nothing gets left behind.
00:29:34.079 --> 00:29:36.724 Down here we only have the kind of broken out, so if
00:29:36.724 --> 00:29:39.769 configurations those are gonna be kind of like simple things
00:29:39.769 --> 00:29:42.864 that are working with our out of the box software integration
00:29:42.864 --> 00:29:45.859 pieces, we can create up to two different frames for these.
00:29:45.869 --> 00:29:48.080 If there's multiple integrations, we can always
00:29:48.080 --> 00:29:51.028 create more, but we do want to keep them separated, so anything
00:29:51.028 --> 00:29:53.930 that has to do with let's say CEF or in this case it was epic,
00:29:53.930 --> 00:29:56.832 we want to keep them separated so we can always kind of have a
00:29:56.832 --> 00:29:59.688 good mind on where things are and what they're doing and then
00:29:59.688 --> 00:30:02.590 new features, epics and these are going to be kind of anything
00:30:02.590 --> 00:30:04.939 that's completely different than what we're doing.
00:30:06.489 --> 00:30:09.670 Totally new functionality, even if we say, oh, we have a product
00:30:09.670 --> 00:30:12.754 Configurator on Project X, but we might want to use some of it
00:30:12.754 --> 00:30:12.999 here.
00:30:13.149 --> 00:30:14.019 It's a new feature.
00:30:14.109 --> 00:30:14.999 It's a whole new feature.
00:30:15.049 --> 00:30:17.774 We have familiarity with it, but each client's gonna use things a
00:30:17.774 --> 00:30:18.559 little differently.
00:30:19.199 --> 00:30:22.346 So once they're all in there, the architecture team will take
00:30:22.346 --> 00:30:25.290 those original estimates and turn them into what's called
00:30:25.290 --> 00:30:26.509 high level architecture.
00:30:26.839 --> 00:30:27.549 This is in the error.
00:30:27.559 --> 00:30:29.749 Can Shelton do where they go over the requirements?
00:30:30.099 --> 00:30:33.824 Take the original features and essentially break them out into
00:30:33.824 --> 00:30:34.829 smaller features.
00:30:34.919 --> 00:30:39.651 In this case, those four there turn into setting modifications
00:30:39.651 --> 00:30:43.633 and email templates, customizations, et cetera, down
00:30:43.633 --> 00:30:44.309 the line.
00:30:45.839 --> 00:30:51.460 Then even more important then that is these two big squares
00:30:51.460 --> 00:30:51.929 here.
00:30:52.339 --> 00:30:55.750 Now anytime something comes up in discovery and Shelton did
00:30:55.750 --> 00:30:59.332 mention this earlier, but just to reiterate on it and that any
00:30:59.332 --> 00:31:02.516 time anything comes up in discovery that did not have a
00:31:02.516 --> 00:31:05.415 bearing on the original estimates, meaning I never
00:31:05.415 --> 00:31:08.599 mentioned, I want a product Configurator in this case I
00:31:08.599 --> 00:31:09.509 never mentioned.
00:31:09.519 --> 00:31:11.569 I want an FAQ page, whatever it may be.
00:31:12.019 --> 00:31:15.573 If it has never been mentioned, it goes in this box because also
00:31:15.573 --> 00:31:19.072 part of the discovery in order to better call out these changes
00:31:19.072 --> 00:31:22.625 to the client early and rapidly if something goes into this box,
00:31:22.625 --> 00:31:24.539 we can ask them one of two things.
00:31:24.549 --> 00:31:26.319 One, do you want to talk about this right now?
00:31:26.329 --> 00:31:29.480 This will incur some overages on our discovery or we can talk
00:31:29.480 --> 00:31:32.631 about all of it at the end of it, I am not quite sure exactly
00:31:32.631 --> 00:31:35.934 how it's working with you right now, Shelton, but that's kind of
00:31:35.934 --> 00:31:36.849 the concept of it.
00:31:39.309 --> 00:31:41.499 Then over here we have our workflow.
00:31:41.789 --> 00:31:43.968 So the workflow will start always with the phase one stand
00:31:43.968 --> 00:31:44.079 up.
00:31:44.089 --> 00:31:48.420 This is something we're always gonna give to senior developer,
00:31:48.420 --> 00:31:51.239 most likely James, Justin, Brendan, Tim.
00:31:51.289 --> 00:31:55.393 Eric, maybe even where we're setting up the CEF out of the
00:31:55.393 --> 00:31:59.219 box with no changes whatsoever with their URLs for it.
00:31:59.329 --> 00:32:00.919 So that's all it's going to be.
00:32:01.049 --> 00:32:04.879 And the goal then is generally that happens before discovery.
00:32:05.049 --> 00:32:08.014 But Kyle can turn that over to them even during the onboarding
00:32:08.014 --> 00:32:09.709 phase so that they have their site.
00:32:10.039 --> 00:32:13.685 It works as our base product, so if there's anything they don't
00:32:13.685 --> 00:32:17.332 like while they're going through the discovery phase, they have
00:32:17.332 --> 00:32:20.750 complete power to go over it and we're giving them a ton of
00:32:20.750 --> 00:32:21.149 agency.
00:32:21.159 --> 00:32:22.929 We're giving them something right away that's theirs.
00:32:22.939 --> 00:32:23.709 So they can do what they want.
00:32:24.999 --> 00:32:28.747 Then you'll see that we grow out from there and we group each
00:32:28.747 --> 00:32:30.319 feature into its own epic.
00:32:31.469 --> 00:32:32.739 There's goes into our way.
00:32:32.749 --> 00:32:34.959 We practice our agile methodology.
00:32:35.869 --> 00:32:39.430 This can get pretty heady, so I won't go too into it, but an
00:32:39.430 --> 00:32:43.108 epic is essentially just gonna be a block of features that our
00:32:43.108 --> 00:32:44.859 developers will be working on.
00:32:44.959 --> 00:32:48.001 Hopefully all of those features within one Sprint, when all of
00:32:48.001 --> 00:32:50.995 those features are complete, we're again going to turn all of
00:32:50.995 --> 00:32:53.941 those features over to senior developer and they're going to
00:32:53.941 --> 00:32:56.645 put them up to stage once they're in stage, then we can
00:32:56.645 --> 00:32:59.640 turn those over to the client and they can take a look at all
00:32:59.640 --> 00:33:00.509 of those features.
00:33:00.969 --> 00:33:04.474 In the past, we were doing it just by feature and this is kind
00:33:04.474 --> 00:33:06.699 of like version two or three here Eric.
00:33:06.709 --> 00:33:07.709 Four, maybe six.
00:33:07.719 --> 00:33:08.119 Who knows?
00:33:08.129 --> 00:33:12.247 We kind of evolve every time we get a good hand on it, where all
00:33:12.247 --> 00:33:15.859 the books are grouped in, worked on, and then delivered.
00:33:17.279 --> 00:33:19.943 This will be kind of the backbone of your guys's Gantt
00:33:19.943 --> 00:33:22.849 charts, and I think Mickey said he was going to that later.
00:33:22.859 --> 00:33:23.879 I won't go deep into that right now.
00:33:25.069 --> 00:33:27.099 So you can see the workflows on these now.
00:33:27.109 --> 00:33:28.229 You'll see a whole lot of links.
00:33:28.239 --> 00:33:29.539 You see a whole lot of different things.
00:33:29.549 --> 00:33:32.656 Let's just zoom in on just the site setup in pre work epic
00:33:32.656 --> 00:33:32.919 here.
00:33:32.969 --> 00:33:35.592 So if we zoom in on this and it's something I'm going to
00:33:35.592 --> 00:33:38.492 start doing on all of them, I'm assigning the developer to the
00:33:38.492 --> 00:33:39.689 feature on the Miro board.
00:33:39.979 --> 00:33:42.845 This is trying to keep you guys out from having to do too much
00:33:42.845 --> 00:33:43.619 minutia in Azure.
00:33:43.629 --> 00:33:47.289 We make fun of Azure all the time for being slow, being kind
00:33:47.289 --> 00:33:47.949 of finicky.
00:33:48.059 --> 00:33:50.889 It's definitely more of a developer's plate where they
00:33:50.889 --> 00:33:54.132 have to use it for all of their code repos and everything like
00:33:54.132 --> 00:33:54.389 that.
00:33:54.459 --> 00:33:56.829 But at this, PMS don't need to spend too much time in there.
00:33:56.879 --> 00:33:59.511 So I'm trying to make it so it's easier for you guys to read from
00:33:59.511 --> 00:34:00.269 a Miro board level.
00:34:01.739 --> 00:34:04.446 With this we can see the interdependencies between the
00:34:04.446 --> 00:34:07.497 different features, so we know here that data creation can be
00:34:07.497 --> 00:34:10.253 done on its own, but because it's in this first sort of
00:34:10.253 --> 00:34:13.009 column of epics, we wanna make sure it gets done first.
00:34:13.779 --> 00:34:17.175 However, we do know that the site configuration must be done
00:34:17.175 --> 00:34:19.569 before the site styling modifications are.
00:34:19.879 --> 00:34:22.109 We see this by a solid arrow.
00:34:22.179 --> 00:34:25.120 We'll see a dotted arrow that leads up to these other items,
00:34:25.120 --> 00:34:27.917 and those are going to be essentially it would be best if
00:34:27.917 --> 00:34:31.099 we could get that work completed before we started on other work.
00:34:31.459 --> 00:34:33.139 But it's not necessarily necessary.
00:34:36.089 --> 00:34:39.993 We'll see these arrows on each one of these features if we
00:34:39.993 --> 00:34:44.029 click on that, it should go directly down to the feature and
00:34:44.029 --> 00:34:45.749 the included user stories.
00:34:45.759 --> 00:34:49.166 With it you can zoom out a little bit and we'll be able to
00:34:49.166 --> 00:34:50.379 see what we will see.
00:34:50.389 --> 00:34:55.755 All of those features that were in that one epic in this chunk
00:34:55.755 --> 00:34:59.929 over here, we have each one of the user stories.
00:34:59.939 --> 00:35:02.099 Those are always going to be these blue post, it notes.
00:35:02.849 --> 00:35:06.519 We have all the information that's inside of those user
00:35:06.519 --> 00:35:10.321 stories and essentially the order in which they should be
00:35:10.321 --> 00:35:11.829 done on that same line.
00:35:11.919 --> 00:35:17.839 We have this handy dandy little link which will open up that
00:35:17.839 --> 00:35:19.489 feature in Azure.
00:35:22.989 --> 00:35:23.239 Why?
00:35:23.249 --> 00:35:23.799 Why?
00:35:24.709 --> 00:35:27.664 Underneath that, you'll see every single one of those user
00:35:27.664 --> 00:35:30.619 stories as they relate, and we'll also see the successors.
00:35:30.629 --> 00:35:35.341 So this is all of the structure for this project is also entered
00:35:35.341 --> 00:35:36.139 into Azure.
00:35:36.209 --> 00:35:38.866 So all those dependencies are relayed back to the developer as
00:35:38.866 --> 00:35:41.059 long as they pay attention to the related work tab.
00:35:41.909 --> 00:35:45.457 Also within here we have a link that will go right back to this
00:35:45.457 --> 00:35:46.899 Miro to this feature link.
00:35:47.229 --> 00:35:50.485 So if a developer ever needs to see the work kind of in a larger
00:35:50.485 --> 00:35:52.239 scope, we link them right back in.
00:35:52.309 --> 00:35:53.549 We're sharing them back and forth.
00:35:53.959 --> 00:35:55.229 We're giving them the hall pass.
00:35:55.239 --> 00:35:55.949 Go back and forth.
00:35:55.959 --> 00:35:57.449 Have fun again.
00:35:57.459 --> 00:35:59.831 All that information from each one of those user stories is in
00:35:59.831 --> 00:36:00.019 here.
00:36:01.299 --> 00:36:04.650 This isn't a very verbose one that gets the story point story
00:36:04.650 --> 00:36:08.109 across the filter from the price ranges for the catalog filters
00:36:08.109 --> 00:36:11.460 we have the story point here, and then a task is created with
00:36:11.460 --> 00:36:14.649 the abstraction of those story points which is turned into
00:36:14.649 --> 00:36:16.109 hours onto the task itself.
00:36:17.699 --> 00:36:21.957 So you can see here how they all wipe out how we have all of the
00:36:21.957 --> 00:36:25.299 user stories related to features related to epics.
00:36:25.409 --> 00:36:29.214 They're all in blocks and they are all in the order of which
00:36:29.214 --> 00:36:30.649 that they are laid out.
00:36:30.659 --> 00:36:37.700 Here you see these Red X's and then down here be fully readded
00:36:37.700 --> 00:36:38.929 out frames.
00:36:39.419 --> 00:36:42.082 That is because the architecture has not been completed on these
00:36:42.082 --> 00:36:42.369 pieces.
00:36:42.519 --> 00:36:44.189 Now sometimes architecture won't be completed.
00:36:44.839 --> 00:36:49.646 Umm, just due to the order of operations and this case for
00:36:49.646 --> 00:36:54.453 Craig, I believe most of these are relating to the connect
00:36:54.453 --> 00:36:59.749 pieces which we are waiting for some information from the client
00:36:59.749 --> 00:37:01.379 on that as a as Amy.
00:37:01.429 --> 00:37:02.079 Amy's not here.
00:37:02.289 --> 00:37:03.719 She got a call or something.
00:37:02.599 --> 00:37:03.049 Did not know.
00:37:03.889 --> 00:37:04.339 OK.
00:37:04.349 --> 00:37:07.854 Well, as Amy had to deal with this week, we had to put out
00:37:07.854 --> 00:37:11.359 essentially a again, another kind of terms and conditions.
00:37:11.369 --> 00:37:13.899 Thing is, Mickey was talking about earlier to the client.
00:37:13.909 --> 00:37:16.957 That was, hey, we don't have all of your work architected because
00:37:16.957 --> 00:37:18.759 we're waiting on information from you.
00:37:18.769 --> 00:37:20.871 We're going to continue developing because that's what
00:37:20.871 --> 00:37:21.559 you want us to do.
00:37:22.209 --> 00:37:23.909 Everything is going to go over because of that.
00:37:24.579 --> 00:37:25.019 Umm.
00:37:26.309 --> 00:37:29.339 And they said OK and we said, OK, we'll keep working.
00:37:29.429 --> 00:37:31.309 Hopefully we're not trying to make it more difficult, but
00:37:31.309 --> 00:37:32.249 that's just kind of the case.
00:37:34.189 --> 00:37:34.479 OK.
00:37:34.489 --> 00:37:35.079 So that's it.
00:37:35.089 --> 00:37:38.123 In the short version, again, if you see these blue links, those
00:37:38.123 --> 00:37:40.209 will always link around Azure feature link.
00:37:40.219 --> 00:37:42.719 We can click on that and that will bring us back up to here.
00:37:42.729 --> 00:37:46.100 Which again was Eric's structure of kind of the three quote
00:37:46.100 --> 00:37:49.135 unquote phases of the implementation phase that could
00:37:49.135 --> 00:37:49.809 happen here.
00:37:51.949 --> 00:37:52.399 Yeah.
00:37:52.409 --> 00:37:55.662 Is there any questions about the architecture board, the Miro
00:37:55.662 --> 00:37:56.869 Board and how it works?
00:38:00.239 --> 00:38:03.447 No, but is there some way we can you show me how to access so we
00:38:03.447 --> 00:38:05.569 just could look at it whenever we want to?
00:38:05.129 --> 00:38:05.369 Yeah.
00:38:06.439 --> 00:38:11.885 Yeah, so every single Miro board when I create it has this bit
00:38:11.885 --> 00:38:14.479 where there Ohly shouldn't be.
00:38:14.489 --> 00:38:17.084 Anyone with link can edit, but I guess that's important to have
00:38:17.084 --> 00:38:19.557 enough licenses, but I'll drop you a link for this one right
00:38:19.557 --> 00:38:19.719 now.
00:38:21.239 --> 00:38:25.038 But and also every like I said, any feature from the past six
00:38:25.038 --> 00:38:27.979 months or so, we'll have a link directly to it.
00:38:32.179 --> 00:38:33.149 All right, cool.
00:38:33.359 --> 00:38:34.269 Thank you, Daniel.
00:38:34.519 --> 00:38:38.460 So I will go ahead and steal the screen again and and jump off of
00:38:35.069 --> 00:38:35.429 Of course.
00:38:38.460 --> 00:38:40.849 what Daniel referenced the Miro boards.
00:38:41.299 --> 00:38:45.849 So the sorry the Gantt charts based on the Miro board.
00:38:45.859 --> 00:38:51.063 So based on the information that Daniel just showed you, the next
00:38:51.063 --> 00:38:55.637 task that falls into the PM's plate following reestimates
00:38:55.637 --> 00:38:59.659 approval is creating a Gantt chart for the client.
00:38:59.739 --> 00:39:02.079 So we were looking at Craig in the mirror of Ward.
00:39:02.089 --> 00:39:06.521 So I pulled up Craig's Gantt chart and all of the information
00:39:06.521 --> 00:39:10.525 around the epics and what features we expect to work in
00:39:10.525 --> 00:39:14.743 what order is what is going to populate this entire purple
00:39:14.743 --> 00:39:18.389 section right here in the middle of this document.
00:39:18.479 --> 00:39:22.174 Every single one of these rows in the purple is one of the
00:39:22.174 --> 00:39:26.244 features of the project, so you are going to use that Miro board
00:39:26.244 --> 00:39:30.002 to say what order everything is gonna happen in in terms of
00:39:30.002 --> 00:39:33.571 getting all of the exact line items that's going to come
00:39:33.571 --> 00:39:36.139 directly from your reestimates document.
00:39:36.469 --> 00:39:41.251 So everything should be 1 to one match on features, so this also
00:39:41.251 --> 00:39:45.959 flows forward into EP, so that will be the next step you'll do.
00:39:45.969 --> 00:39:48.422 But first, you're going to create a Gantt chart for the
00:39:48.422 --> 00:39:48.729 client.
00:39:48.739 --> 00:39:52.027 You're gonna let them know what we expect to complete when I'm
00:39:52.027 --> 00:39:55.263 not going to go to in depth on this because there are lots of
00:39:55.263 --> 00:39:57.559 trainings available recorded on this topic.
00:39:57.569 --> 00:40:01.610 And I will also definitely do on live for you guys when you're
00:40:01.610 --> 00:40:05.396 ready for it, because this is a very hands on piece of the
00:40:05.396 --> 00:40:09.116 puzzle and there's a lot of little moving parts that will
00:40:09.116 --> 00:40:12.966 be, you know, easier to explain when we're using a concrete
00:40:12.966 --> 00:40:13.479 example.
00:40:13.549 --> 00:40:17.540 But the goal is to communicate to the client what we expect to
00:40:17.540 --> 00:40:21.341 do when and talk to them in advance about when we expect to
00:40:21.341 --> 00:40:23.369 be able to launch their project.
00:40:23.429 --> 00:40:26.533 So the the this whole document starts off with setting the
00:40:26.533 --> 00:40:29.952 project start date and that will kind of slow down into the rest
00:40:29.952 --> 00:40:33.372 of the document, though you will edit a lot of those dates as we
00:40:33.372 --> 00:40:36.476 go to match what actually is reflective of how the project
00:40:36.476 --> 00:40:36.739 went.
00:40:36.869 --> 00:40:40.696 This kind of pinky salmon color up here at the top is pretty
00:40:40.696 --> 00:40:44.335 much everything that's gonna happen in discovery and then
00:40:44.335 --> 00:40:47.159 initial environment setup here in the green.
00:40:47.249 --> 00:40:50.463 As I said, all of your feature line items here in the purple
00:40:50.463 --> 00:40:52.939 with all the dates we expect to get them done.
00:40:53.149 --> 00:40:56.611 Anything integration is pulled here into the orange and these
00:40:56.611 --> 00:40:59.069 will also come from the Miro board as well.
00:40:59.239 --> 00:41:02.474 And in terms of when we expect to be able to complete them and
00:41:02.474 --> 00:41:05.658 then this last section right here is kind of the probably the
00:41:05.658 --> 00:41:08.894 piece that the client is gonna be most interested in, which is
00:41:08.894 --> 00:41:11.359 knowing when we are going to get them to watch.
00:41:12.529 --> 00:41:15.951 So that is all going to be informed by all those epics and
00:41:15.951 --> 00:41:19.316 when we expect to be able to take the next one on and the
00:41:19.316 --> 00:41:22.738 next one which we will all estimate based on the number of
00:41:22.738 --> 00:41:25.639 hours that the project is going to take to build.
00:41:25.649 --> 00:41:27.671 So every project is going to be a little different, like it's
00:41:27.671 --> 00:41:27.769 in.
00:41:27.779 --> 00:41:31.163 This will be easier to kind of build out when you're working
00:41:31.163 --> 00:41:34.825 with a concrete example, but the end result is is we are going to
00:41:34.825 --> 00:41:38.375 tell the client what window we expect to be able to launch them
00:41:38.375 --> 00:41:41.982 in, and we're going to have that conversation now so that we can
00:41:41.982 --> 00:41:44.756 get them having solid expectations and reasonable
00:41:44.756 --> 00:41:48.029 expectations for when we might be able to accomplish that.
00:41:48.539 --> 00:41:51.090 So you will provide this document to your client in
00:41:51.090 --> 00:41:54.082 Basecamp once it is prepared, just like every other document
00:41:54.082 --> 00:41:55.799 that you're ever going to work on.
00:41:55.839 --> 00:41:58.462 That is client facing that goes up into Basecamp so that they
00:41:58.462 --> 00:41:59.309 have a record of it.
00:41:59.399 --> 00:42:01.799 We have a record of it and it can all be tracked.
00:42:03.759 --> 00:42:07.690 The next piece that you're going to work on at that point when re
00:42:07.690 --> 00:42:11.443 estimates have been approved is getting all of those same line
00:42:11.443 --> 00:42:13.469 items here in the purple into EP.
00:42:13.539 --> 00:42:16.169 And I know we did a whole training on that just this week.
00:42:16.419 --> 00:42:20.542 So we won't dig too deeply in there, but you do want to get
00:42:20.542 --> 00:42:25.078 all of those line items in there and have your appropriate people
00:42:25.078 --> 00:42:26.109 assigned to it.
00:42:26.239 --> 00:42:30.367 And I will confirm, Eric, the goal now is that we are gonna be
00:42:30.367 --> 00:42:34.430 putting all of our architecture team members on every feature
00:42:34.430 --> 00:42:36.069 when we put them into EP.
00:42:36.079 --> 00:42:39.276 So they can work on feature level architecture once that
00:42:39.276 --> 00:42:39.669 starts.
00:42:40.239 --> 00:42:40.549 Yeah.
00:42:40.559 --> 00:42:44.671 And then they'll they'll assign because what we had been doing
00:42:44.671 --> 00:42:48.717 is we've been putting the the feature level work that Tim and
00:42:48.717 --> 00:42:52.502 Justin primarily, but other people too have been doing is
00:42:52.502 --> 00:42:55.309 had been just logged towards architecture.
00:42:55.399 --> 00:42:58.625 Well, technically that's a Discovery line item that we're
00:42:58.625 --> 00:43:01.961 saying is done and what they're doing is just kind of a pre
00:43:01.961 --> 00:43:02.629 development.
00:43:02.799 --> 00:43:06.393 And so when they do feature level architecture, they'll log
00:43:06.393 --> 00:43:10.107 it directly to the feature so that you know it's because it's
00:43:10.107 --> 00:43:13.940 ultimately just figuring out how that feature is actually going
00:43:13.940 --> 00:43:14.659 to be built.
00:43:14.669 --> 00:43:18.798 So we're gonna gonna go ahead and mark it as part of that
00:43:18.798 --> 00:43:20.079 feature line item.
00:43:21.019 --> 00:43:23.777 So they'll need access to all of them so that they can log so
00:43:21.049 --> 00:43:21.469 Solutely.
00:43:23.777 --> 00:43:25.379 that they can log, log it that way.
00:43:26.639 --> 00:43:29.572 So when you are done, uh, entering all of your EP line
00:43:29.572 --> 00:43:32.985 items following the REESTIMATES approval, this is what your ERP
00:43:32.985 --> 00:43:34.799 for the project should look like.
00:43:34.879 --> 00:43:38.259 You should have everybody I.
00:43:38.269 --> 00:43:41.085 Well, everybody from architecture, both Justin and
00:43:41.085 --> 00:43:44.344 Tim, on every line of the project, you will also generally
00:43:44.344 --> 00:43:47.934 have whoever is going to do the phase one setup work and that'll
00:43:47.934 --> 00:43:51.468 be determined by management when we get to that point, a lot of
00:43:51.468 --> 00:43:54.727 times that will be Brendan, you'll get that person on that
00:43:54.727 --> 00:43:55.279 line item.
00:43:55.369 --> 00:43:58.324 You'll also make sure that the relevant people who might need
00:43:58.324 --> 00:44:01.279 to attend meetings so all the developers that are going to be
00:44:01.279 --> 00:44:04.187 shortly working on the project will get on the meetings line
00:44:04.187 --> 00:44:06.808 item and make sure your full PM team is on the project
00:44:06.808 --> 00:44:09.239 management line item and this should be your goal.
00:44:09.349 --> 00:44:13.239 And then as features close, you will be removing people.
00:44:13.389 --> 00:44:16.379 So right now looking at this one, onboarding is done.
00:44:16.429 --> 00:44:19.553 That line item should get closed and Kyle, myself and Shelton
00:44:19.553 --> 00:44:21.519 should be removed from that line item.
00:44:21.849 --> 00:44:25.333 So should discovery and architecture and design we have
00:44:25.333 --> 00:44:26.329 completed those?
00:44:26.339 --> 00:44:29.197 Those can be closed and you do want to make sure you are
00:44:29.197 --> 00:44:32.256 closing features as they are completed so that there are not
00:44:32.256 --> 00:44:33.309 hours billed to them.
00:44:33.319 --> 00:44:34.199 That shouldn't be.
00:44:34.389 --> 00:44:39.277 Then that'll save us some work down the line with any time log
00:44:39.277 --> 00:44:40.519 audits later on.
00:44:41.789 --> 00:44:45.039 So at this point, we are ready to enter full discovery.
00:44:45.249 --> 00:44:46.699 The client has seen their BRD.
00:44:46.709 --> 00:44:47.449 They've agreed to it.
00:44:47.459 --> 00:44:50.496 They've seen the reestimates they've agreed to it and we've
00:44:50.496 --> 00:44:53.634 told them what their estimated timeline looks like and we are
00:44:53.634 --> 00:44:56.923 ready both in Azure for the the developers to work their tickets
00:44:56.923 --> 00:44:59.859 and in EP for them to build their time for those tickets.
00:45:00.089 --> 00:45:03.851 So we introduce development and at this point the project fully
00:45:03.851 --> 00:45:05.379 comes home to the PM team.
00:45:05.909 --> 00:45:08.759 We are now going to be the primary source of contact.
00:45:08.769 --> 00:45:11.598 The main person that every one of these clients is going to be
00:45:11.598 --> 00:45:13.439 meeting with our meetings are scheduled.
00:45:14.029 --> 00:45:17.074 On average, the goal is biweekly, so once every two
00:45:17.074 --> 00:45:20.704 weeks kind of in cordance with our Sprint cadence, you should
00:45:20.704 --> 00:45:24.159 be meeting with your client every time you meet with them.
00:45:24.249 --> 00:45:27.369 You will be presenting them a financial health update on the
00:45:27.369 --> 00:45:30.233 project, a development status update on the project and
00:45:30.233 --> 00:45:33.302 alerting them to any pieces of information that they either
00:45:33.302 --> 00:45:36.269 know or any action items that they need to be working on.
00:45:37.269 --> 00:45:41.293 We've looked at those documents already, but I will pull up one
00:45:41.293 --> 00:45:45.129 here today just to get a refresh as to what that looks like.
00:45:47.329 --> 00:45:49.751 So every time you meet with the client, you should be
00:45:49.751 --> 00:45:50.559 representing them.
00:45:50.569 --> 00:45:54.006 Something that looks like this document that includes the
00:45:54.006 --> 00:45:55.429 development information.
00:45:56.749 --> 00:46:00.798 What their financials look like and hours balance what hours we
00:46:00.798 --> 00:46:04.846 plan to work, if there are any line item overages, those should
00:46:04.846 --> 00:46:08.768 be communicated both verbally and in writing in this document
00:46:08.768 --> 00:46:12.691 so that the client can never say that we didn't let them know
00:46:12.691 --> 00:46:14.209 that that was happening.
00:46:14.499 --> 00:46:17.863 You can include any other invoicing information if they
00:46:17.863 --> 00:46:21.468 have a set up invoice cadence that should be put there as a
00:46:21.468 --> 00:46:22.009 reminder.
00:46:22.239 --> 00:46:25.268 If there are risk areas which there are going to be, every
00:46:25.268 --> 00:46:26.449 project has risk areas.
00:46:26.679 --> 00:46:30.354 Those should be called out both verbally in the meeting and in
00:46:30.354 --> 00:46:33.795 writing in the document, and finally any action items that
00:46:33.795 --> 00:46:37.354 the client should be expected to take or that they should be
00:46:37.354 --> 00:46:38.579 expecting us to take.
00:46:39.989 --> 00:46:43.364 So this your PSR and your biweekly meeting recording
00:46:43.364 --> 00:46:47.375 should go up into Basecamp every single time you meet with the
00:46:47.375 --> 00:46:50.559 client, and I'm going to impose on somebody here.
00:46:50.729 --> 00:46:55.368 Elena, would you mind talking to us about just kind of keeping up
00:46:55.368 --> 00:46:57.829 on those kind of recurring things?
00:46:58.129 --> 00:47:01.043 Uh, any other things we should be paying attention to that we
00:47:01.043 --> 00:47:02.829 need to make sure we're always doing.
00:47:11.229 --> 00:47:12.199 Are you on mute?
00:47:12.369 --> 00:47:14.179 If you are talking, I think your headset might be muted.
00:47:15.929 --> 00:47:17.877 Is that for me at least, he broke up a little bit at the end
00:47:16.899 --> 00:47:17.519 Can you hear me now?
00:47:17.877 --> 00:47:18.069 there.
00:47:18.759 --> 00:47:19.299 Can you hear me?
00:47:19.019 --> 00:47:20.379 I can hear you now, yeah.
00:47:20.429 --> 00:47:21.649 I was double muted.
00:47:25.089 --> 00:47:30.343 For client communication we need to be double checking basecamp
00:47:30.343 --> 00:47:34.119 emails anytime there's anything communicated.
00:47:34.129 --> 00:47:38.583 Make sure you communicating it to your team that's working on
00:47:38.583 --> 00:47:43.036 it best practices and if you don't have an answer right away,
00:47:43.036 --> 00:47:47.275 just let them know that you'll get back to them as soon as
00:47:47.275 --> 00:47:48.999 possible with your team.
00:47:49.009 --> 00:47:51.460 It's always best practice to just do that if you don't have
00:47:51.460 --> 00:47:52.359 an answer immediately.
00:47:54.619 --> 00:47:55.609 Responding.
00:47:55.619 --> 00:47:56.509 That's always.
00:47:56.519 --> 00:47:57.329 That's what I do.
00:47:57.339 --> 00:48:00.709 If I don't have an answer, I'm just like hold please.
00:48:00.759 --> 00:48:05.829 I will get back to you and we'll get this figured out.
00:48:06.499 --> 00:48:08.629 Emailing as well.
00:48:09.679 --> 00:48:11.069 Keep an eye out for that.
00:48:11.079 --> 00:48:11.569 Always.
00:48:11.579 --> 00:48:15.788 Just make sure you're giving a response, umm quickly as
00:48:15.788 --> 00:48:20.449 possible and then getting back with them as soon as possible.
00:48:20.459 --> 00:48:23.837 When you have an answer back from your team, so that's at
00:48:23.837 --> 00:48:24.769 least what I do.
00:48:25.509 --> 00:48:26.919 Antastic perfect.
00:48:27.009 --> 00:48:29.999 And I would make I would add one thing just to that.
00:48:30.009 --> 00:48:33.025 Everybody is is aware of it and I know we've talked about this
00:48:33.025 --> 00:48:35.659 before, but just throw a reminder that while there are
00:48:35.659 --> 00:48:38.675 some clients that are going to want to function through email,
00:48:38.675 --> 00:48:41.548 we want to encourage as many clients as possible to utilize
00:48:41.548 --> 00:48:41.979 Basecamp.
00:48:42.049 --> 00:48:45.365 And if you do have clients that mostly use Basecamp, but
00:48:45.365 --> 00:48:48.798 occasionally will send an email, great practice is to just
00:48:48.798 --> 00:48:52.348 download a copy of that email and put it in Basecamp so that
00:48:52.348 --> 00:48:54.559 everything can be found in one place.
00:48:54.569 --> 00:48:55.449 If we ever need it.
00:48:57.639 --> 00:49:01.884 One little thing that I wanna say just if you can, if you can
00:48:57.669 --> 00:49:00.359 So word, yeah.
00:49:01.884 --> 00:49:06.129 get them to avoid using pings that only goes directly to you.
00:49:04.349 --> 00:49:04.609 Yes.
00:49:06.439 --> 00:49:10.942 I actually just experienced that from someone that had departed,
00:49:10.942 --> 00:49:15.237 not Clint, but where there was like a ping thread that he was
00:49:15.237 --> 00:49:19.532 expecting, he would be able to initiate with me and that it's
00:49:19.532 --> 00:49:23.134 not there because it's my account, not the previous
00:49:23.134 --> 00:49:23.619 person.
00:49:23.159 --> 00:49:23.409 Umm.
00:49:23.629 --> 00:49:25.929 So just.
00:49:25.939 --> 00:49:29.773 Yeah, I I just politely say hey, it is best practices for us
00:49:29.773 --> 00:49:32.099 because these pings only come to me.
00:49:32.109 --> 00:49:35.632 So if I'm ever out of office or sick for any reason, you know
00:49:35.632 --> 00:49:39.269 the rest of the team would not be notified if this information.
00:49:40.589 --> 00:49:42.039 As a fantastic call out.
00:49:42.049 --> 00:49:42.399 Thank you.
00:49:42.439 --> 00:49:42.569 Yeah.
00:49:44.699 --> 00:49:45.339 You're here.
00:49:45.949 --> 00:49:49.570 Alright, so that brings us to kind of the recurring tasks
00:49:49.570 --> 00:49:51.319 portion of the conversation.
00:49:51.449 --> 00:49:54.858 And so I would, you know, open the floor if anybody wants to
00:49:54.858 --> 00:49:58.546 weigh in on, you know, something that they want us to acknowledge
00:49:58.546 --> 00:50:01.229 as a, you know, recurring task for the PM team.
00:50:01.239 --> 00:50:02.629 I'm gonna go ahead and call out.
00:50:02.639 --> 00:50:06.639 What a couple right off the bat, all being in EP #1 being making
00:50:06.639 --> 00:50:10.577 sure we're looking at EP needs reallocation at least once a day
00:50:10.577 --> 00:50:13.469 and trying to clear our projects out of there.
00:50:14.059 --> 00:50:17.733 Second, being at the start of every Sprint, working through
00:50:17.733 --> 00:50:21.469 our EP resource allocation, meaning that we are checking the
00:50:21.469 --> 00:50:25.143 features and the tickets that are going to be worked in the
00:50:25.143 --> 00:50:29.063 current Sprint and we are making sure that those developers are
00:50:29.063 --> 00:50:33.043 assigned to those line items in EP so that they can successfully
00:50:33.043 --> 00:50:36.779 log their time to the proper place and the third piece being
00:50:36.779 --> 00:50:38.249 at the close of sprints.
00:50:38.309 --> 00:50:41.488 Especially making sure that we're closing any features that
00:50:41.488 --> 00:50:44.985 are done taking people off those line items, and if there are any
00:50:44.985 --> 00:50:48.217 change requests, updates that those numbers are getting back
00:50:48.217 --> 00:50:50.389 into EP to their appropriate line items.
00:50:51.579 --> 00:50:54.261 So I would open the floor to anyone else who wants to chime
00:50:54.261 --> 00:50:57.211 in with a recurring PM task that we need to be sure we're keeping
00:50:57.211 --> 00:50:57.569 eyes on.
00:51:06.669 --> 00:51:07.669 I will start calling on people.
00:51:11.229 --> 00:51:12.099 I'll just make a quick note.
00:51:12.109 --> 00:51:15.209 I'll make them make recurring task boards.
00:51:15.839 --> 00:51:20.297 Uh, micki, do you know off hand if Julian and Jordan have access
00:51:20.297 --> 00:51:21.189 to asana yet?
00:51:21.799 --> 00:51:22.319 I do not.
00:51:23.999 --> 00:51:26.049 I I think I have access to it and not think.
00:51:25.819 --> 00:51:28.279 I do have access to asana, yeah.
00:51:27.439 --> 00:51:29.459 Yeah, I think, yeah, I have access.
00:51:29.759 --> 00:51:31.969 And tastic I'll do those after this.
00:51:31.979 --> 00:51:33.849 Actually, I'll do just in a little bit here.
00:51:33.859 --> 00:51:34.809 We'll make those for you guys today.
00:51:34.819 --> 00:51:36.499 You can start messing around with them on Monday.
00:51:37.439 --> 00:51:37.579 Yeah.
00:51:37.469 --> 00:51:37.839 Great.
00:51:38.369 --> 00:51:38.769 Thank you.
00:51:39.389 --> 00:51:42.950 So that that right there is is gonna be one of your recurring
00:51:39.709 --> 00:51:40.009 Of course.
00:51:42.950 --> 00:51:46.684 tasks, keeping your asana board up to date, making sure that you
00:51:46.684 --> 00:51:50.189 are checking off items there as you do them so that you have
00:51:50.189 --> 00:51:53.635 those that information for yourself and that our leadership
00:51:53.635 --> 00:51:55.129 team can see that as well.
00:51:56.349 --> 00:51:56.729 Yeah.
00:51:56.739 --> 00:52:00.747 And we we talked about a little bit yesterday, Jordan, Julian,
00:52:00.747 --> 00:52:03.419 where it's just these very simple pieces.
00:52:03.609 --> 00:52:06.709 There's only a handful of them, and this goes for all you know.
00:52:06.719 --> 00:52:09.615 If I've had a good chat with you about this before, tell you what
00:52:09.615 --> 00:52:11.239 you need to do for each one of them.
00:52:12.699 --> 00:52:13.149 Umm.
00:52:13.199 --> 00:52:17.055 If it's something that has more complex pieces to it, there will
00:52:17.055 --> 00:52:20.732 be a link to new cleaner O in there that you can get right to
00:52:20.732 --> 00:52:24.469 and I'll give you the more in depth version of what it is, but
00:52:24.469 --> 00:52:27.969 then the biggest thing for all y'all I want to make sure I
00:52:27.969 --> 00:52:29.749 won't feels empowered by this.
00:52:30.019 --> 00:52:33.219 Create your own sections for your own projects.
00:52:33.229 --> 00:52:38.559 You know, if you know, I have to make a, you know, invoice follow
00:52:38.559 --> 00:52:43.567 up and then the details or you can even, you know link to it,
00:52:43.567 --> 00:52:48.735 link to a teams message, link to anything else like hey, I have
00:52:48.735 --> 00:52:53.339 to get that by Tuesday or whatever it might be use these
00:52:53.339 --> 00:52:54.389 for yourself.
00:52:54.459 --> 00:52:55.899 Organize them how you want.
00:52:55.909 --> 00:52:58.106 These will always be on repeating pingers because
00:52:58.106 --> 00:52:59.249 they're just these things.
00:52:59.299 --> 00:53:02.254 Little things that we forget little things like that, that we
00:53:02.254 --> 00:53:03.589 just need to remember to do.
00:53:03.979 --> 00:53:08.329 But these this is your guys's plate, as it were.
00:53:08.759 --> 00:53:12.025 So you guys can do a lot of great stuff with this,
00:53:12.025 --> 00:53:15.099 especially as you guys get a lot more projects.
00:53:15.109 --> 00:53:19.399 It's undoubtedly going to be a lot more things coming up for
00:53:19.399 --> 00:53:23.338 you and then just a fun thing you can do with the teams
00:53:23.338 --> 00:53:27.276 integration here is you can create an asana task from a
00:53:27.276 --> 00:53:27.839 message.
00:53:35.219 --> 00:53:37.499 Where you can put it in, let's say I just want to put in
00:53:37.499 --> 00:53:38.619 Mickey's thing just for fun.
00:53:46.629 --> 00:53:49.137 You can create that task right from here and it takes just a
00:53:49.137 --> 00:53:50.659 second and it'll go right into here.
00:53:50.729 --> 00:53:55.229 There it is already with a link back to that teams message.
00:53:56.519 --> 00:54:02.517 So when you open it there take just a second, it'll open it up,
00:54:02.517 --> 00:54:04.579 go right down to that.
00:54:04.589 --> 00:54:07.579 So you can any of those little things that developer asks you
00:54:07.579 --> 00:54:08.399 to do real quick.
00:54:08.609 --> 00:54:09.929 I don't have time for this right now.
00:54:09.939 --> 00:54:13.768 I don't yet yet that whatever it may be, you can just quickly
00:54:13.768 --> 00:54:15.559 make an asana task from that.
00:54:15.569 --> 00:54:19.641 So you can stay on task but also so you can give yourself kind of
00:54:19.641 --> 00:54:21.369 a reasonable follow through.
00:54:23.069 --> 00:54:23.979 That is fantastic.
00:54:23.989 --> 00:54:24.579 Thank you, Daniel.
00:54:25.309 --> 00:54:25.589 Umm.
00:54:26.739 --> 00:54:29.855 All right, Kathy, what's something you would contribute
00:54:29.855 --> 00:54:31.859 to the recurring task conversation?
00:54:33.099 --> 00:54:38.735 Our PSR S, which are so easy to do on it, gives you a live
00:54:38.735 --> 00:54:43.129 update of what's happening with your account.
00:54:43.779 --> 00:54:48.580 Preface to that is you just need to run the utility to make sure
00:54:48.580 --> 00:54:51.609 that it is updated and accurate from EP.
00:54:52.599 --> 00:54:53.509 Tell me to share one.
00:54:52.879 --> 00:54:53.549 Very good.
00:54:53.559 --> 00:54:54.669 Call out please.
00:54:58.579 --> 00:55:03.189 Mickey was so kindly helping me as I was a little behind today.
00:55:03.809 --> 00:55:04.379 Umm.
00:55:05.009 --> 00:55:08.419 With this project, Sprint planning piece actually.
00:55:08.429 --> 00:55:13.736 So basically on your cover page here, you'll come in and if you
00:55:13.736 --> 00:55:18.795 back it up a step it just you wanna pick 2023 project status
00:55:18.795 --> 00:55:23.439 report and then choose your project from the drop down.
00:55:24.049 --> 00:55:27.630 Not sure if you've might teams isn't probably sharing that,
00:55:27.630 --> 00:55:27.869 huh?
00:55:27.829 --> 00:55:30.499 Is that utility still necessary?
00:55:30.589 --> 00:55:32.509 Are you seeing that you're having to do that?
00:55:33.129 --> 00:55:33.289 Yes.
00:55:33.149 --> 00:55:37.356 I did actually the other day on Shelton or Clint had Marina
00:55:37.356 --> 00:55:38.899 report in the morning.
00:55:39.259 --> 00:55:43.389 I did some reallocation and I reran it and it, you know, it
00:55:43.389 --> 00:55:47.519 definitely was different from what he had from the morning.
00:55:47.609 --> 00:55:48.339 So yeah.
00:55:48.189 --> 00:55:50.239 Yeah, it's all about that reallocation, Eric.
00:55:48.479 --> 00:55:48.909 Well.
00:55:50.249 --> 00:55:53.046 So if it doesn't, if reallocation happens, like if
00:55:51.129 --> 00:55:51.309 Yeah.
00:55:53.046 --> 00:55:55.898 it's just Monday morning or whatever, you know, and
00:55:55.898 --> 00:55:59.079 everything is all cool and you run it, you don't need to.
00:55:59.249 --> 00:56:02.439 But let's say you run it and your numbers aren't sick.
00:56:02.809 --> 00:56:03.969 Then you gotta run it.
00:56:04.739 --> 00:56:06.689 Like I I almost always like.
00:56:06.919 --> 00:56:10.969 This is a reallocation and time logs here on EP.
00:56:11.339 --> 00:56:15.568 And whenever I'm gonna run one of those PSRS, it's probably
00:56:15.568 --> 00:56:19.797 best practice to check here first that there's nothing that
00:56:19.797 --> 00:56:21.489 needs to be reallocated.
00:56:21.919 --> 00:56:27.096 Last thing we wanna do is send a client a project status update
00:56:27.096 --> 00:56:31.869 that is inaccurate and not showing their correct balances.
00:56:31.879 --> 00:56:37.339 So and definitely as you can work on these the IT it it you
00:56:37.339 --> 00:56:42.890 know it is what it is we got to do it make it accurate don't
00:56:42.890 --> 00:56:47.349 don't don't stick your foot in your mouth there.
00:56:44.519 --> 00:56:45.079 Absolutely.
00:56:47.419 --> 00:56:50.469 So that is, uh.
00:56:49.349 --> 00:56:49.539 Yes.
00:56:50.479 --> 00:56:54.193 And then if you go down the line, you know it just gives you
00:56:54.193 --> 00:56:57.969 your line item consumption based on the whole entire project.
00:56:59.139 --> 00:57:00.329 I think you can't.
00:57:00.679 --> 00:57:00.919 Sorry.
00:57:02.429 --> 00:57:04.819 Uh, so yeah, this one is pretty big.
00:57:04.929 --> 00:57:09.622 Been going on for a while and then it also gives you cuz I had
00:57:09.622 --> 00:57:14.017 split out a range for this current Sprint that we're in so
00:57:14.017 --> 00:57:18.561 that gives them the usage that they have burned down in this
00:57:18.561 --> 00:57:19.679 last two weeks.
00:57:20.069 --> 00:57:24.101 And also what's really helpful because you're obviously going
00:57:24.101 --> 00:57:27.679 to be talking money during that project status update.
00:57:28.139 --> 00:57:31.342 You know, these are the up-to-date invoices, so you can
00:57:31.342 --> 00:57:32.029 click right?
00:57:32.129 --> 00:57:36.359 I'm here and see, you know specifically what that was.
00:57:37.609 --> 00:57:41.599 I haven't really dug into the graphical consumption too much
00:57:41.599 --> 00:57:45.327 here, but for time used graphics, but mostly these pages
00:57:45.327 --> 00:57:49.512 are really helpful and then we just go ahead and upload that to
00:57:49.512 --> 00:57:53.568 Basecamp as well, and then they they have it best practice to
00:57:53.568 --> 00:57:55.399 share it during the meeting.
00:57:55.409 --> 00:57:55.959 If you can too.
00:57:57.349 --> 00:57:57.869 Solutely.
00:57:58.799 --> 00:57:59.619 So that's all.
00:58:00.609 --> 00:58:02.769 In real quick this is not not at all being alright.
00:58:02.779 --> 00:58:06.530 I argumentative I just for the PSR 2023 Chris and I I believe
00:58:06.530 --> 00:58:10.160 any EP line items are actually pulling directly from the EP
00:58:10.160 --> 00:58:13.972 database now and that tool what it used to do is actually take
00:58:13.972 --> 00:58:17.723 the EP database and put it over in the CRM database, which is
00:58:17.723 --> 00:58:19.599 why that tool needed to be ran.
00:58:19.769 --> 00:58:25.515 I'd be curious if someone I'd be curious to test that run a PSR,
00:58:25.515 --> 00:58:30.819 see a line item go in and then see if the PSR auto updates.
00:58:31.379 --> 00:58:35.079 For what it's worth, Eric, earlier this afternoon I was
00:58:31.779 --> 00:58:32.059 OK.
00:58:35.079 --> 00:58:38.844 working on some EP cleanup for 10, and I did change some
00:58:37.399 --> 00:58:37.569 Uh.
00:58:38.844 --> 00:58:43.007 numbers like moved hours around within EP, and I needed to run
00:58:43.007 --> 00:58:47.169 the utility to get the PSR to reflect the changes that I made.
00:58:44.509 --> 00:58:44.719 Hmm.
00:58:47.799 --> 00:58:48.119 OK.
00:58:48.129 --> 00:58:51.249 And what and which in in on all screens?
00:58:48.249 --> 00:58:50.839 Now I was changing no.
00:58:53.419 --> 00:58:56.129 Uh, the line item consumption screen.
00:58:53.629 --> 00:58:53.979 Like on.
00:58:56.689 --> 00:58:59.189 OK, I'll take a look at it.
00:58:59.199 --> 00:59:02.319 And that was using that was using PSR 2023 right projects
00:59:02.319 --> 00:59:03.809 Yeah. Yes.
00:59:02.319 --> 00:59:03.449 that are sport 23 OK.
00:59:08.469 --> 00:59:10.629 Because like I said, I wasn't allocating time logs.
00:59:10.639 --> 00:59:15.068 I was actually changing like moving hours around, closing out
00:59:14.699 --> 00:59:15.399 Sure. Sure.
00:59:15.068 --> 00:59:16.569 line items and stuff.
00:59:15.479 --> 00:59:15.959 Yeah, that's fair.
00:59:17.449 --> 00:59:21.499 Yeah, I'll take a look at it and see what, see what we missed.
00:59:24.419 --> 00:59:24.699 Perfect.
00:59:25.689 --> 00:59:26.439 OK, cool.
00:59:27.069 --> 00:59:32.835 Alright, so anybody else have any recurring PM tasks that they
00:59:32.835 --> 00:59:34.299 wanna point out.
00:59:35.639 --> 00:59:38.289 And if Shelton doesn't point out one, I will do what?
00:59:38.299 --> 00:59:38.859 So for him.
00:59:41.409 --> 00:59:42.439 What was the question?
00:59:42.499 --> 00:59:43.959 Sorry or talk.
00:59:43.909 --> 00:59:47.339 Now any any recurring tasks for the PM team that you know about.
00:59:47.349 --> 00:59:50.533 And I have one in my mind that I would think you would shout out
00:59:50.533 --> 00:59:53.179 for us, but that's a lot of pressure to read my mind.
00:59:55.299 --> 00:59:58.279 Why and that I should know Ohly.
00:59:59.029 --> 00:59:59.999 I'll give you hints.
01:00:00.069 --> 01:00:02.729 We did it on repro and Craig this week.
01:00:04.489 --> 01:00:07.289 Ohh, the risk assessment document.
01:00:08.359 --> 01:00:09.379 Yeah, that's a good one over.
01:00:09.389 --> 01:00:10.409 And I didn't talk about that.
01:00:10.419 --> 01:00:11.539 So thank you for bringing that up.
01:00:11.549 --> 01:00:14.870 But no, I was just thinking if there's missing information if
01:00:14.870 --> 01:00:18.405 there are to do that we have not checked off yet information that
01:00:18.405 --> 01:00:21.565 we requested with Shelton and Discovery that we don't have
01:00:21.565 --> 01:00:21.779 yet.
01:00:21.869 --> 01:00:25.129 That is a recurring task annoy the client about it.
01:00:29.249 --> 01:00:31.159 But Shelton makes a good point.
01:00:29.559 --> 01:00:29.859 I have.
01:00:31.889 --> 01:00:33.899 So what quick talk about the risk assessments?
01:00:34.629 --> 01:00:37.139 So when we've entered development.
01:00:38.049 --> 01:00:38.739 Thank you, Cassie.
01:00:38.749 --> 01:00:39.939 I'll get to that one too.
01:00:40.359 --> 01:00:42.963 When we've entered development with the client, like I said,
01:00:42.963 --> 01:00:44.969 you're gonna have biweekly meetings with them.
01:00:45.019 --> 01:00:48.657 The very first one of those that you have is going to be talking
01:00:48.657 --> 01:00:49.329 about risks.
01:00:49.639 --> 01:00:51.969 So you are going to meet with them.
01:00:52.079 --> 01:00:54.114 You're gonna have met with Shelton before you go into that
01:00:54.114 --> 01:00:56.149 meeting and you're gonna have talked through with Shelton.
01:00:56.159 --> 01:00:59.411 Every single potential risk area on the project, and if that is
01:00:59.411 --> 01:01:01.799 every single feature on the project, so be it.
01:01:02.339 --> 01:01:03.879 You're going to talk to the client about that.
01:01:03.889 --> 01:01:06.909 You're going to let them know why those are potential risks?
01:01:07.479 --> 01:01:10.853 How serious of a risk they are and you're going to tell them
01:01:10.853 --> 01:01:14.392 what we're going to do to combat that, we're going to do to try
01:01:14.392 --> 01:01:16.439 to minimize the impact of that risk.
01:01:16.539 --> 01:01:20.075 A lot of times that answer is just going to be, hey, we're
01:01:20.075 --> 01:01:23.371 going to work on your integration as soon as we can so
01:01:23.371 --> 01:01:27.027 that we can make sure we're pulling over good data and allow
01:01:27.027 --> 01:01:30.742 that to help us mitigate any issues that are going to come in
01:01:30.742 --> 01:01:33.739 from that particular line item, things like that.
01:01:33.879 --> 01:01:37.053 So that'll be your first meeting with the client and then from
01:01:37.053 --> 01:01:39.926 there out you will keep those risk areas in your meeting
01:01:39.926 --> 01:01:40.329 agendas.
01:01:40.339 --> 01:01:46.369 And I let everyone see those on a recurring basis.
01:01:46.499 --> 01:01:49.994 And you know, if new ones come up, you're gonna remind them of
01:01:49.994 --> 01:01:50.549 those too.
01:01:50.679 --> 01:01:53.789 And obviously we need to be a little gentler with our clients
01:01:53.789 --> 01:01:56.949 than we necessarily do have to have to be with our colleagues.
01:01:56.999 --> 01:02:01.059 So you don't want to be too aggressive with the annoying?
01:02:01.449 --> 01:02:01.909 Umm.
01:02:02.549 --> 01:02:06.311 A nice polite annoyance when you're dealing with your clients
01:02:06.311 --> 01:02:10.194 and you know, obviously we can be polite with each other's too,
01:02:10.194 --> 01:02:13.288 but overcommunication I will bring us back to that
01:02:13.288 --> 01:02:15.169 overcommunication at all times.
01:02:15.539 --> 01:02:19.792 Alright, so final recurring PM task and this these are our
01:02:19.792 --> 01:02:20.729 Friday tasks.
01:02:20.859 --> 01:02:23.821 So I'm gonna remind you of them every Friday that we meet
01:02:23.821 --> 01:02:26.987 together, make sure that you do your invoice notes and I will
01:02:26.987 --> 01:02:28.519 show that document real quick.
01:02:30.219 --> 01:02:32.879 I can find it in any sort of timely manner.
01:02:38.809 --> 01:02:40.159 This is our invoice sheet.
01:02:40.169 --> 01:02:43.567 We meet every Monday morning with leadership to talk through
01:02:43.567 --> 01:02:46.129 where every client stands on their invoicing.
01:02:46.219 --> 01:02:49.607 So Friday, before you leave for the day, make sure that you are
01:02:49.607 --> 01:02:52.942 putting your notes into this PM notes column as to what you're
01:02:52.942 --> 01:02:55.960 understanding is for the invoicing plan for every single
01:02:55.960 --> 01:02:57.019 one of your clients.
01:02:57.369 --> 01:03:01.484 What you've talked to them about what they know, what we know as
01:03:01.484 --> 01:03:05.410 much data as you can possibly give the team so that they know
01:03:05.410 --> 01:03:08.639 what is what on the financial side of the project.
01:03:09.259 --> 01:03:14.223 So invoice notes, your number one Friday task time logs is
01:03:14.223 --> 01:03:16.579 your number two Friday task.
01:03:16.589 --> 01:03:19.551 That the daily task, but it's especially important on Friday
01:03:19.551 --> 01:03:22.756 afternoons to make sure that all of your time logs for the entire
01:03:22.756 --> 01:03:23.339 week are in.
01:03:23.529 --> 01:03:24.269 They're ready to go.
01:03:25.789 --> 01:03:28.820 That is number 2 and #3 is making sure that needs
01:03:28.820 --> 01:03:32.639 reallocation is clear so those are our big three to always try
01:03:31.539 --> 01:03:32.139 Umm.
01:03:32.639 --> 01:03:34.579 to get done by Friday afternoon.
01:03:35.429 --> 01:03:39.845 And I would say that is the conclusion of what I wanted to
01:03:39.845 --> 01:03:42.839 get everyone together about here today.
01:03:43.059 --> 01:03:45.819 Obviously there's lots more to learn about the PM role.
01:03:46.069 --> 01:03:49.361 You know lots of intricacies as we go through that development
01:03:49.361 --> 01:03:52.705 phase and especially as we get towards go live and all that fun
01:03:52.705 --> 01:03:53.019 stuff.
01:03:53.089 --> 01:03:56.263 So there's definitely still more to talk about, but I think we've
01:03:56.263 --> 01:03:59.148 done a great job today and I do want to leave some time for
01:03:59.148 --> 01:03:59.629 questions.
01:04:00.319 --> 01:04:03.420 If anyone has any, especially Jordan Julie and you guys, if
01:04:03.420 --> 01:04:06.520 there's anything we've talked about that you have questions
01:04:06.520 --> 01:04:07.399 about open floor.
01:04:10.989 --> 01:04:11.629 Real quick.
01:04:11.379 --> 01:04:11.729 I just want.
01:04:12.659 --> 01:04:16.177 I just wanna so PSR they you're saying you put put those on base
01:04:13.089 --> 01:04:13.279 Yeah.
01:04:16.177 --> 01:04:19.479 camp and you and you send them to client during the meeting?
01:04:20.319 --> 01:04:21.409 Yeah, I share.
01:04:20.579 --> 01:04:21.389 As somebody said that there.
01:04:21.739 --> 01:04:24.115 I share that with the client during the meeting and then
01:04:24.115 --> 01:04:26.699 after the meeting I upload that document to Basecamp as well.
01:04:27.429 --> 01:04:28.609 OK, just make it here, OK?
01:04:31.059 --> 01:04:31.549 Alaina.
01:04:32.259 --> 01:04:35.702 I was going to say don't forget to record your meetings and
01:04:35.609 --> 01:04:36.339 Oh yeah.
01:04:35.702 --> 01:04:39.316 don't forget to post your notes as well if you're able to take
01:04:39.316 --> 01:04:40.579 notes on your meeting.
01:04:41.379 --> 01:04:41.579 OK.
01:04:42.609 --> 01:04:42.829 Here.
01:04:43.389 --> 01:04:46.321 And this one's not required, but it's a good idea, especially if
01:04:43.639 --> 01:04:44.009 Thank you.
01:04:46.321 --> 01:04:49.253 you're recording either end the recording or end the meeting for
01:04:49.253 --> 01:04:49.659 everyone.
01:04:49.839 --> 01:04:53.681 Sometimes clients don't leave and they just sit there and
01:04:49.969 --> 01:04:50.379 Umm.
01:04:52.179 --> 01:04:52.519 Umm.
01:04:53.681 --> 01:04:55.669 extend the recording by hours.
01:04:56.349 --> 01:04:57.719 Yep, that is true.
01:04:57.059 --> 01:04:57.239 Yes.
01:04:57.259 --> 01:05:00.552 Or I'll do it in trainings just so you guys are aware too, I'll
01:05:00.552 --> 01:05:02.199 I'll not leave trainings and so.
01:05:02.009 --> 01:05:02.299 Uh.
01:05:06.489 --> 01:05:10.409 And just I'll let you guys forgive you for this in advance.
01:05:10.419 --> 01:05:14.171 Hopefully you won't do it nearly as many times as I've done it,
01:05:14.171 --> 01:05:17.688 but it is possible to call everyone and in chat thread into
01:05:17.688 --> 01:05:18.919 a meeting by mistake.
01:05:19.569 --> 01:05:20.839 So try not to do that.
01:05:19.819 --> 01:05:19.939 Yeah.
01:05:23.939 --> 01:05:24.899 Yeah, I've done that before.
01:05:24.459 --> 01:05:24.789 I wanted to.
01:05:24.909 --> 01:05:27.239 Work with Microsoft team, yeah.
01:05:27.649 --> 01:05:29.819 I was just going to say, like, how do you do that?
01:05:29.829 --> 01:05:33.579 That sounds like beyond teams capable.
01:05:29.999 --> 01:05:30.899 ID you know how.
01:05:31.149 --> 01:05:31.449 Alright.
01:05:31.459 --> 01:05:34.284 And the last time I did it, I was trying to type your name
01:05:34.284 --> 01:05:35.529 because it's like control.
01:05:35.539 --> 01:05:38.297 CI was trying to do capital C and I did control C and it
01:05:38.297 --> 01:05:40.959 called everyone in the meeting and I was like turn it.
01:05:41.279 --> 01:05:42.729 Yeah, it's it there.
01:05:42.739 --> 01:05:45.842 It's it's interesting because like on a on an actual teams
01:05:45.219 --> 01:05:45.819 Yeah.
01:05:45.842 --> 01:05:49.103 channel like a message there you can mark something as urgent
01:05:49.103 --> 01:05:51.049 with like it's like control shift U.
01:05:51.239 --> 01:05:54.078 But on an actual chat thread like, which is what we use the
01:05:54.078 --> 01:05:56.019 most of the time, there isn't an urgent.
01:05:56.029 --> 01:05:58.519 You only have important and control shift.
01:05:58.529 --> 01:06:02.419 You just calls everyone, so definitely doable.
01:06:00.729 --> 01:06:00.959 Oh.
01:06:03.299 --> 01:06:04.199 Yep, Yep.
01:06:03.789 --> 01:06:05.489 I wonder if that's what Wayne did today.
01:06:06.749 --> 01:06:07.149 Yeah.
01:06:06.759 --> 01:06:09.988 I think that he just was trying to call me and didn't think that
01:06:09.988 --> 01:06:11.429 I was gonna set up a meeting.
01:06:11.519 --> 01:06:12.589 I think there was cause he.
01:06:12.599 --> 01:06:15.316 He ended it right away and then joined the meeting that I sent
01:06:14.129 --> 01:06:16.469 Yeah, yeah.
01:06:14.329 --> 01:06:14.639 Umm.
01:06:15.316 --> 01:06:15.489 him.
01:06:15.499 --> 01:06:18.409 So yeah, interesting.
01:06:18.969 --> 01:06:23.501 Also I where can I complain to Microsoft that the league button
01:06:23.501 --> 01:06:25.979 is right next to the share button?
01:06:27.609 --> 01:06:28.589 Yeah, alright.
01:06:28.199 --> 01:06:29.369 All the time.
01:06:30.079 --> 01:06:33.169 Yeah, there's a long list of Microsoft complaints.
01:06:30.439 --> 01:06:30.589 Like.
01:06:33.179 --> 01:06:34.659 If there's something like that, we can get to.
01:06:35.379 --> 01:06:39.379 Team, can we just all write one large complaint to team?
01:06:37.599 --> 01:06:40.289 Just teams, yes.
01:06:40.229 --> 01:06:40.449 Yeah.
01:06:40.519 --> 01:06:43.279 Team. Yeah.
01:06:43.099 --> 01:06:43.779 For sure.
01:06:43.809 --> 01:06:46.049 Ohh alright.
01:06:45.539 --> 01:06:50.067 And then I guess the last one, this is just a for everybody, is
01:06:50.067 --> 01:06:54.029 there are chats that do use external chat with clients.
01:06:54.039 --> 01:06:57.590 So make sure that what you're typing is in a chat that's not
01:06:57.590 --> 01:07:01.200 external and is OK obviously you should be typing only things
01:07:01.200 --> 01:07:04.867 that are OK if you see anyway, but sometimes there's financial
01:07:04.469 --> 01:07:04.869 Well, that's.
01:07:04.867 --> 01:07:08.302 information or other things that clients shouldn't see, or
01:07:06.419 --> 01:07:06.709 Umm.
01:07:08.302 --> 01:07:09.059 probably not.
01:07:09.069 --> 01:07:11.142 Best for them to see that just make sure what you're typing
01:07:11.142 --> 01:07:12.109 where you typing it matters.
01:07:13.459 --> 01:07:16.814 Yeah, that that can get kind of tricky with the meeting chat and
01:07:16.814 --> 01:07:19.859 then our internal chat like sometimes they're kind of like
01:07:19.629 --> 01:07:20.189 Hmm.
01:07:19.859 --> 01:07:22.698 right next to each other, especially if you're like in
01:07:22.698 --> 01:07:23.679 that meeting, yeah.
01:07:24.019 --> 01:07:25.069 Advice for that?
01:07:24.359 --> 01:07:24.749 Yep.
01:07:25.079 --> 01:07:28.904 Umm, you can always make sure like internal in all bold is on
01:07:28.904 --> 01:07:29.459 the chat.
01:07:29.469 --> 01:07:30.469 That is acceptable.
01:07:30.699 --> 01:07:32.159 That does not have the client in it.
01:07:32.959 --> 01:07:33.639 Yeah.
01:07:33.859 --> 01:07:34.589 Yeah, they do.
01:07:33.919 --> 01:07:34.889 Ohh that's a good idea.
01:07:34.599 --> 01:07:35.409 They do have.
01:07:35.419 --> 01:07:36.329 Well, they do have.
01:07:36.379 --> 01:07:40.641 So obviously you have to check but external chats, not
01:07:40.641 --> 01:07:41.339 meetings.
01:07:41.349 --> 01:07:45.247 External chats do have the external word next to them, like
01:07:45.247 --> 01:07:49.471 they'll say external underneath the timestamp, and then anything
01:07:49.471 --> 01:07:53.044 that's a meeting chat has the calendar logo instead of
01:07:53.044 --> 01:07:54.019 people's faces.
01:07:57.159 --> 01:08:00.640 So just that can be a quick check, but if you're typing
01:07:59.559 --> 01:07:59.839 Umm.
01:08:00.640 --> 01:08:04.681 something that's maybe a little, just give it an extra look just
01:08:01.209 --> 01:08:01.899 Just pay attention.
01:08:03.759 --> 01:08:05.549 Just just pay attention.
01:08:04.681 --> 01:08:05.179 in case.
01:08:05.409 --> 01:08:06.369 Just pay attention.
01:08:06.309 --> 01:08:06.869 Definitely.
01:08:06.499 --> 01:08:07.429 Just pay attention.
01:08:08.309 --> 01:08:12.719 Also, your notifications too like I don't have notifications
01:08:12.719 --> 01:08:17.273 like come up on my screen cause you know you you may fall into
01:08:15.529 --> 01:08:15.749 Umm.
01:08:17.273 --> 01:08:21.539 that with if you're sharing screen right and notification.
01:08:20.569 --> 01:08:22.829 They do a good job of Microsoft Teams.
01:08:22.839 --> 01:08:25.554 Does a good job of hiding your note, not showing notifications
01:08:24.959 --> 01:08:25.119 Yeah.
01:08:25.554 --> 01:08:26.459 while you're sharing.
01:08:27.139 --> 01:08:27.459 Mm-hmm.
01:08:27.389 --> 01:08:31.215 Unless Brandon tells you to like, ignore the do not disturb
01:08:27.539 --> 01:08:28.459 Oh, that's good point.
01:08:31.109 --> 01:08:32.309 And specific person.
01:08:31.215 --> 01:08:32.809 for certain people, yeah.
01:08:32.409 --> 01:08:33.839 Boy did boy.
01:08:33.569 --> 01:08:33.869 Umm.
01:08:33.849 --> 01:08:35.929 Boy, did I need to walk that one back, huh?
01:08:36.689 --> 01:08:36.879 So.
01:08:36.909 --> 01:08:37.649 OHS.
01:08:38.389 --> 01:08:39.599 I still have that on for you.
01:08:40.569 --> 01:08:43.309 I appreciate that, man, Sprint.
01:08:42.229 --> 01:08:43.049 Hey, no problem.
01:08:48.339 --> 01:08:49.439 Any other questions?
01:08:51.239 --> 01:08:56.135 Oh, and a best practice is for Basecamp to pin your jobs that
01:08:51.359 --> 01:08:51.809 Ohh.
01:08:56.135 --> 01:08:59.689 you're working on to your little home front.
01:08:59.799 --> 01:09:04.968 It's easy to keep track of them that way, and your customer
01:09:02.589 --> 01:09:03.409 Very good call.
01:09:04.968 --> 01:09:10.308 conversations or your dev of chats and teams pin those so you
01:09:10.308 --> 01:09:14.099 can immediately find those where it's easy.
01:09:15.899 --> 01:09:17.679 Yeah, you get 15 pins in teams.
01:09:18.129 --> 01:09:21.439 Yes, only and it's frustrating, yes.
01:09:18.449 --> 01:09:18.799 Umm.
01:09:20.269 --> 01:09:20.839 Only, yeah.
01:09:22.799 --> 01:09:23.929 They should always have.
01:09:26.649 --> 01:09:27.329 Both pods.
01:09:28.839 --> 01:09:29.139 Umm.
01:09:29.489 --> 01:09:32.379 Our squads that PM Scrum chat.
01:09:35.819 --> 01:09:40.506 And the other ones, you guys are kind of musts, 8 needs keep that
01:09:37.599 --> 01:09:38.359 It needs.
01:09:38.989 --> 01:09:40.179 Yeah, it needs.
01:09:40.506 --> 01:09:41.429 one up there.
01:09:43.609 --> 01:09:44.539 And with that, PMS?
01:09:43.669 --> 01:09:44.709 Uh, Jordan and Julian.
01:09:44.299 --> 01:09:44.809 You have.
01:09:44.719 --> 01:09:46.219 Did you guys get added to it needs?
01:09:48.139 --> 01:09:49.409 Make sure I got it right.
01:09:48.279 --> 01:09:51.049 Uh, if not seen that one come up just yet.
01:09:49.419 --> 01:09:52.479 Now I'm on it already.
01:09:49.629 --> 01:09:49.839 It.
01:09:50.469 --> 01:09:50.689 OK.
01:09:52.189 --> 01:09:53.719 I everything that one either.
01:09:52.809 --> 01:09:53.349 I got you.
01:09:52.949 --> 01:09:53.229 OK.
01:09:53.039 --> 01:09:53.389 Like it?
01:09:56.809 --> 01:09:57.839 I definitely got the storm one.
01:09:56.869 --> 01:10:01.837 Fun fact too, uh Jordan and Juliane, you can actually add
01:10:01.837 --> 01:10:03.379 yourself to teams.
01:10:03.389 --> 01:10:06.149 I believe. Uh.
01:10:05.519 --> 01:10:06.099 Hmm.
01:10:05.839 --> 01:10:08.189 You get out yourself the tea to teams.
01:10:08.199 --> 01:10:10.569 You can't add yourself to chats, right?
01:10:08.669 --> 01:10:09.599 But not chats.
01:10:10.299 --> 01:10:10.559 OK.
01:10:10.319 --> 01:10:10.639 Umm.
01:10:10.579 --> 01:10:12.029 Correct, correct.
01:10:21.439 --> 01:10:24.617 Alright, Brandon, I you were the only person that I didn't give a
01:10:24.617 --> 01:10:25.869 full window to talk today.
01:10:25.879 --> 01:10:26.789 Is there anything?
01:10:26.799 --> 01:10:28.559 Any words of wisdom you'd like to share?
01:10:31.169 --> 01:10:33.499 No, I think I think this is really good.
01:10:33.509 --> 01:10:36.269 And I can imagine that it's probably overwhelming
01:10:36.269 --> 01:10:39.471 specifically for Jordan and Julian, if put myself in your
01:10:39.471 --> 01:10:40.189 guys's shoes.
01:10:40.199 --> 01:10:44.637 So I just wanted to say that we've all been there and it this
01:10:44.637 --> 01:10:49.004 uh obviously was recorded and would be a very valuable thing
01:10:49.004 --> 01:10:53.228 for you guys to kind of go back and reference at different
01:10:53.228 --> 01:10:53.729 points.
01:10:53.799 --> 01:10:54.359 Umm.
01:10:54.739 --> 01:10:57.734 But trust that as we're going through this, I definitely put
01:10:57.734 --> 01:10:59.109 myself in your guys's shoes.
01:10:59.119 --> 01:11:03.170 And I was like, whoo, yeah, I remember it's it's a lot, but
01:11:03.170 --> 01:11:05.669 super excited to have you guys here.
01:11:05.679 --> 01:11:09.993 And this group obviously in this this training was awesome, but
01:11:09.993 --> 01:11:14.375 this group is more than willing to answer any questions that you
01:11:14.375 --> 01:11:15.049 guys have.
01:11:15.059 --> 01:11:18.916 So just make sure that you're utilizing that resource and
01:11:18.916 --> 01:11:20.579 we'll get there for sure.
01:11:21.909 --> 01:11:22.369 Great.
01:11:21.999 --> 01:11:22.319 Thank you.
01:11:22.379 --> 01:11:23.049 Thank you.
01:11:23.839 --> 01:11:24.729 You're here.
01:11:25.479 --> 01:11:30.116 Alright, well then I will give everybody the last 15 minutes of
01:11:30.116 --> 01:11:32.869 our meeting to do those Friday tasks.
01:11:32.919 --> 01:11:36.409 So get your time logs in, get your invoice notes done.
01:11:36.719 --> 01:11:40.189 Make sure anything of yours and need your allocation is clear.
01:11:40.199 --> 01:11:43.762 Have a fantastic weekend and we will see you bright and early
01:11:43.762 --> 01:11:45.429 Monday morning to go get him.
01:11:46.929 --> 01:11:47.739 Thank you everyone.
01:11:47.189 --> 01:11:48.819 Thanks so much guys.
01:11:47.699 --> 01:11:48.519 Yeah, I'm gonna get.
01:11:48.489 --> 01:11:49.379 Thanks all.
01:11:48.829 --> 01:11:50.009 Take care.
01:11:49.009 --> 01:11:49.599 Have a good weekend.
01:11:49.729 --> 01:11:50.329 Thanks everyone.
01:11:50.109 --> 01:11:51.619 That's great weekend. Bye.
01:11:50.189 --> 01:11:50.349 Bye.
01:11:51.969 --> 01:11:53.249 Turn fine.