| Topic | Presenter | Summary | Duration |
| ---------------- | --------- | --------------------------------------------------------------------- | -------- |
| PM: Re-Estimates | Kyle S. | This video is from a Friday training where Kyle covered Re-Estimates. | 37:17 |# Creating your Template## Find the Initial Estimates FileThe first thing you want to do is go into the Teams Channel and grab the Initial Estimations Spreadsheet from the Proposals Folder in Teams. (Files > General > Proposals > Sent)## Make a CopyMake a copy of the Initial Estimations Spreadsheet and rename to:* "[ProductInitials_ReEstimates_V1"## Prepare the Re-Estimates TemplatePut in new columns to the right of the existing columns for: * Original Est
- Rev Est
- Change (Hrs)
- Comments
- IIW Page Reference
- Orig $
- Rev $
- Change ($)Then fill in formulas in the first row for the new columns: * Orig Est: =[@[Hi Hrs.]]
- Rev Est: (Manual Entry)
- Change (Hrs): =[@[Rev Est]]-[@[Orig Est]]
- Comments: (Manual Entry)
- IIW Page Reference: (Manual Entry)
- Orig $: =IFERROR([@[Hi Hrs.]]*VLOOKUP([@Rate],'Configuration Table'!A:B,2,FALSE),0)
- Rev $: =IFERROR([@[Rev Est]]*VLOOKUP([@Rate],'Configuration Table'!A:B,2,FALSE),0)
- Change ($): =AF3-AE3
# Completing the Spreadsheet## Add User Stories and Hour EstimationsYou will want to start adding User Stories to the "Comments" Column, and the aggregate of their hour totals for all tasks to the "Rev Est" Column, for each correlating Line Item from the Initial Estimations Spreadsheet. ### Important Notes: * If the User Story does not have a correlating Line Item, you will need to add a new line item (in a specific section) to document Features that were ADDED during Discovery. - Be sure to break out Line Items into Front-End vs. Back-End Development Time. Sometimes, there will only be a front-end/back-end line item for the feature. If this happens, you will need to break out the line item into two separate line items (One for FE and one for BE estimates/rates)## Calculating TotalsOnce you have gone through the entire FSD, and all User Stories have been either added to their correlating line item, or to a unique line item for new features, you can start aggregating totals at the bottom of the table.
The formulas for the columns are: * Orig Est: =SUM([Orig Est]) - Rev Est: =SUM([Rev Est])
- Change: =Table1[[#Totals],[Rev Est]]-Table1[[#Totals],[Orig Est]]
- Comments: (N/A)
- IIW Page Reference: (N/A)
- Orig $: =SUM([Orig $])
- Rev $: =SUM([Rev $])
- Change ($): =Table1[[#Totals],[Rev $]]-Table1[[#Totals],[Orig $]]# ResultsOnce completed, the difference between the "Orig Est/Orig $" and the "Rev Est/Rev $" should indicate whether the Client's Re-Estimated Cost has increased or decreased from what was initially discussed during the Sales Process. # Video Transcript: 00:00:06.940 --> 00:00:08.638 The mean potatoes of today's training,00:00:08.640 --> 00:00:10.831 which I'm going to turn over to00:00:10.831 --> 00:00:13.163 Kyle and let him run with it is00:00:13.163 --> 00:00:15.270 going to be the RE estimates.00:00:15.270 --> 00:00:19.041 Uh, I'm going to make a couple of blanket00:00:19.041 --> 00:00:21.639 statements that are this must happen.00:00:21.640 --> 00:00:22.879 It's absolutely non-negotiable.00:00:22.879 --> 00:00:26.450 One before a client gets a re estimate,00:00:26.450 --> 00:00:31.498 you need an approval from myself or Chris.00:00:31.500 --> 00:00:33.732 The second thing is the 2nd00:00:33.732 --> 00:00:36.301 Kyle hands you the RE estimates00:00:36.301 --> 00:00:38.786 it is the PM's responsibility.00:00:38.790 --> 00:00:40.430 He's sending them to you.00:00:40.430 --> 00:00:42.392 You guys should be doing these00:00:42.392 --> 00:00:43.373 yourselves actually come,00:00:43.380 --> 00:00:45.336 but it is your responsibility to00:00:45.336 --> 00:00:47.366 validate that the discovery time and00:00:47.366 --> 00:00:49.046 everything done before delivery of00:00:49.046 --> 00:00:51.011 those re estimates has been updated00:00:51.011 --> 00:00:52.891 to have actuals, not re estimates.00:00:52.891 --> 00:00:54.526 So the Discovery line item,00:00:54.530 --> 00:00:56.498 a BS, is a great example.00:00:56.500 --> 00:00:58.894 We're going to have to credit00:00:58.894 --> 00:01:01.690 near 100 hours on that project.00:01:01.690 --> 00:01:03.495 Because the discovery time was00:01:03.495 --> 00:01:05.300 not updated in their estimates00:01:05.365 --> 00:01:06.995 and then re estimates ultimately00:01:06.995 --> 00:01:09.100 were never sent to the client.00:01:09.100 --> 00:01:11.123 So even the 50 hour difference we00:01:11.123 --> 00:01:13.209 should have been easily able to build00:01:13.209 --> 00:01:15.180 for we're having to fight for it.00:01:15.180 --> 00:01:16.426 So those two things are must haves,00:01:16.430 --> 00:01:17.926 but the call is going to go through00:01:17.926 --> 00:01:19.455 and show you guys how to handle00:01:19.455 --> 00:01:20.560 the RE estimates and creating00:01:20.611 --> 00:01:21.716 that document on your own.00:01:21.720 --> 00:01:24.450 And then please feel free00:01:24.450 --> 00:01:27.180 to throw out any feedback.00:01:27.180 --> 00:01:28.548 Or anything like that,00:01:28.548 --> 00:01:31.090 or if someone's got really, you know,00:01:31.090 --> 00:01:33.995 pretty Excel skills and they want to.00:01:34.000 --> 00:01:35.626 To clean it up, feel free.00:01:35.630 --> 00:01:37.172 This is actually not the the00:01:37.172 --> 00:01:38.620 template that I originally created,00:01:38.620 --> 00:01:41.098 so Kyle kind of modified the sales00:01:41.098 --> 00:01:44.410 template for it. So if we need to.00:01:44.410 --> 00:01:46.154 Update this change its.00:01:46.154 --> 00:01:48.334 Whatever we need to do,00:01:48.340 --> 00:01:50.108 let's make notes of it and get it00:01:50.108 --> 00:01:51.750 assigned to one of you guys, stone.00:01:51.750 --> 00:01:54.270 So I'm not owning all the things.00:01:54.270 --> 00:01:54.625 OK,00:01:54.625 --> 00:01:57.110 so starting out what is re estimates00:01:57.110 --> 00:01:59.282 Kevin kind of went into this00:01:59.282 --> 00:02:01.370 before but when sales first gets00:02:01.440 --> 00:02:03.654 the client they do an initial00:02:03.654 --> 00:02:05.770 estimation of what they think that00:02:05.770 --> 00:02:08.010 project is going to cost based on00:02:08.010 --> 00:02:10.199 their discussions with the client.00:02:10.200 --> 00:02:13.820 It's not in depth as I get with the client,00:02:13.820 --> 00:02:15.836 but it is an initial estimate00:02:15.836 --> 00:02:18.022 based on other projects that we've00:02:18.022 --> 00:02:19.967 done that are extremely similar,00:02:19.970 --> 00:02:22.658 so that's kind of what I use as00:02:22.658 --> 00:02:25.009 a starting point for discovery.00:02:25.010 --> 00:02:27.416 And I'd build on those initial00:02:27.416 --> 00:02:29.650 estimations for the clients project,00:02:29.650 --> 00:02:32.872 so where you can find these would be in00:02:32.872 --> 00:02:36.395 the proposals or the RE estimates folder.00:02:36.400 --> 00:02:39.354 I kind of move this one over,00:02:39.360 --> 00:02:41.898 but generally they'll be in the00:02:41.898 --> 00:02:44.000 proposals and worksheets folder here,00:02:44.000 --> 00:02:48.053 so once you pull that up it'll00:02:48.053 --> 00:02:50.490 look something like this.00:02:50.490 --> 00:02:52.828 Now this is a line by line00:02:52.828 --> 00:02:54.700 representation of what sales has00:02:54.700 --> 00:02:56.695 talked through with the client.00:02:56.700 --> 00:02:58.794 You'll see things in here for00:02:58.794 --> 00:03:00.710 each one of these lines,00:03:00.710 --> 00:03:03.630 so we have some stuff for CO301 redirects.00:03:03.630 --> 00:03:05.090 Building out the sitemap,00:03:05.090 --> 00:03:06.550 importing their static content.00:03:06.550 --> 00:03:08.740 You also see things like the00:03:08.740 --> 00:03:09.835 clarity e-commerce license,00:03:09.840 --> 00:03:12.680 so this is a really good representation of00:03:12.680 --> 00:03:15.679 of whether we charge them for the ecommerce.00:03:15.680 --> 00:03:18.536 If it's also going to be a00:03:18.536 --> 00:03:19.760 multicurrency multilingual platform.00:03:19.760 --> 00:03:22.720 And also if they are going to be a connect00:03:22.792 --> 00:03:25.397 project and integrating with anything00:03:25.397 --> 00:03:28.385 external from our e-commerce system. Uh,00:03:28.385 --> 00:03:31.760 so using this is kind of my starting point.00:03:31.760 --> 00:03:36.746 Now once I go through and create the IW.00:03:36.750 --> 00:03:38.275 I should have these builds00:03:38.275 --> 00:03:39.800 out in a feature parity.00:03:39.800 --> 00:03:42.040 I will note here that the features00:03:42.040 --> 00:03:43.915 will not probably align one to00:03:43.915 --> 00:03:45.896 one with what sales has come too,00:03:45.900 --> 00:03:47.902 so you might need to add a00:03:47.902 --> 00:03:49.260 few things in there.00:03:49.260 --> 00:03:50.175 It's totally fine,00:03:50.175 --> 00:03:51.700 it happens all the time,00:03:51.700 --> 00:03:53.434 so if you just don't see00:03:53.434 --> 00:03:54.590 something that's associated with00:03:54.645 --> 00:03:56.270 whatever feature I'm going over,00:03:56.270 --> 00:03:58.724 you would just add it in00:03:58.724 --> 00:04:00.980 as its own line item.00:04:00.980 --> 00:04:03.311 So the very first thing I do00:04:03.311 --> 00:04:05.361 whenever I whenever I get this00:04:05.361 --> 00:04:07.317 done so every single user story00:04:07.317 --> 00:04:09.656 here will have estimations on it.00:04:09.660 --> 00:04:11.390 I'll go through with the00:04:11.390 --> 00:04:12.774 developers and they'll say,00:04:12.780 --> 00:04:13.428 Oh yeah,00:04:13.428 --> 00:04:16.020 to change the UI of a product card00:04:16.097 --> 00:04:18.809 to match this for grid and list view00:04:18.809 --> 00:04:21.450 would be around two to four hours.00:04:21.450 --> 00:04:23.676 And that's applying the markup that00:04:23.676 --> 00:04:26.874 we get back from P2H or a markup team00:04:26.874 --> 00:04:29.090 and that's applying it to the UI.00:04:29.090 --> 00:04:30.870 So that's something that I00:04:30.870 --> 00:04:32.294 would come over here.00:04:32.300 --> 00:04:33.512 And put this,00:04:33.512 --> 00:04:36.996 modify the product card UI task and find00:04:36.996 --> 00:04:39.816 the corresponding feature over here.00:04:39.820 --> 00:04:43.528 So it would be under customized00:04:43.528 --> 00:04:46.622 HTML CSS template most likely00:04:46.622 --> 00:04:50.129 and I would put it in there.00:04:50.130 --> 00:04:52.738 So the first thing you want to do00:04:52.738 --> 00:04:55.617 is kind of get this document ready.00:04:55.620 --> 00:04:58.196 So basically what I would do and you00:04:58.196 --> 00:05:01.109 can use other projects as a reference,00:05:01.110 --> 00:05:03.306 so I usually use a BS.00:05:03.310 --> 00:05:05.410 So that's one of the ones00:05:05.410 --> 00:05:07.330 that Kevin was talking about.00:05:07.330 --> 00:05:09.885 I'll just use that as a reference.00:05:11.930 --> 00:05:12.560 Oh00:05:17.040 --> 00:05:18.420 it might actually be a little00:05:18.420 --> 00:05:20.480 bit different, I think.00:05:20.480 --> 00:05:22.090 Some changes have been made.00:05:26.000 --> 00:05:28.142 So the first thing I want to00:05:28.142 --> 00:05:30.458 do here so description is the00:05:30.458 --> 00:05:32.655 same column as this, whoops.00:05:32.655 --> 00:05:35.325 Is this description right over here?00:05:35.330 --> 00:05:37.618 So the first thing I'm going to do00:05:37.618 --> 00:05:39.971 is extend this out so that I can00:05:39.971 --> 00:05:41.882 start putting in what my estimations00:05:41.882 --> 00:05:43.988 were from the developers in with00:05:43.988 --> 00:05:47.090 all of the initial estimations here.00:05:47.090 --> 00:05:48.812 Uh, so the first thing I'll do00:05:48.812 --> 00:05:50.799 is I'll come in here and grab00:05:50.799 --> 00:05:52.581 original estimate all the way over.00:05:55.030 --> 00:05:55.680 Those.00:05:58.250 --> 00:06:01.242 Paste those in here. They should00:06:01.242 --> 00:06:02.697 all come over pretty nicely.00:06:05.290 --> 00:06:07.500 That's a clean this up, just a little bit.00:06:11.530 --> 00:06:13.112 And now I'm just going to go00:06:13.112 --> 00:06:14.649 through and plug in the formulas.00:06:14.650 --> 00:06:16.570 I've tried to do this in the past,00:06:16.570 --> 00:06:18.250 but it's kind of hard to do.00:06:18.250 --> 00:06:19.826 It'll want to reference.00:06:19.826 --> 00:06:22.545 The Excel document you have open if00:06:22.545 --> 00:06:24.817 you just try to paste it in there.00:06:24.820 --> 00:06:26.745 Uhm, so I usually come in here00:06:26.745 --> 00:06:28.936 and paste the actual formula into00:06:28.936 --> 00:06:31.096 where it's referencing for original00:06:31.096 --> 00:06:33.371 estimate here just so I can have00:06:33.371 --> 00:06:35.122 these right next to each other.00:06:35.122 --> 00:06:37.132 It's going to reference the00:06:37.132 --> 00:06:38.338 high hours column.00:06:38.340 --> 00:06:39.810 Which is this guy right here?00:06:39.810 --> 00:06:41.525 So we said on the high side.00:06:41.530 --> 00:06:45.346 This is what it was going to cost initially.00:06:45.350 --> 00:06:47.324 Uh, the revised estimate over here is00:06:47.324 --> 00:06:49.849 the one you are going to be filling out.00:06:49.850 --> 00:06:51.494 UM, that's whatever you know the00:06:51.494 --> 00:06:53.527 feature said so you can put multiple00:06:53.527 --> 00:06:55.592 of those user stories under one feature00:06:55.646 --> 00:06:57.487 and kind of build out whatever the00:06:57.487 --> 00:06:59.660 total for those user stories were00:06:59.660 --> 00:07:02.420 for that feature into this column.00:07:02.420 --> 00:07:05.180 Uhm, the change in hours would just be00:07:05.180 --> 00:07:09.460 this minus this, so I come over here.00:07:09.460 --> 00:07:11.548 And I want to reference those two columns.00:07:17.120 --> 00:07:18.530 Oops, I won.00:07:26.410 --> 00:07:28.730 So now as you fill things out here,00:07:28.730 --> 00:07:31.920 so if this was a wash and it was two hours,00:07:31.920 --> 00:07:34.152 it would zero that out if we went00:07:34.152 --> 00:07:36.214 any above that, it would show that00:07:36.214 --> 00:07:38.300 we had a positive change in hours.00:07:41.520 --> 00:07:44.330 But that works good, uhm?00:07:44.330 --> 00:07:45.955 Come over here the comments00:07:45.955 --> 00:07:47.580 and IW page reference columns.00:07:47.580 --> 00:07:49.210 This is for the client.00:07:49.210 --> 00:07:51.559 If they do want to go back and look00:07:51.559 --> 00:07:53.869 at exactly what was estimated for00:07:53.869 --> 00:07:56.488 this line item, they can do that.00:07:56.488 --> 00:07:59.033 I usually just reference the page there00:07:59.033 --> 00:08:01.665 so that they can go back and visually00:08:01.665 --> 00:08:04.587 see what that requirement was in detail.00:08:04.590 --> 00:08:07.497 Uhm, so these aren't going to have any uh,00:08:07.500 --> 00:08:10.700 formulas or anything in it.00:08:10.700 --> 00:08:13.248 And then these over here very simply,00:08:13.250 --> 00:08:16.092 just copying these over so this is00:08:16.092 --> 00:08:18.518 going to reference the high hours00:08:18.518 --> 00:08:21.143 and multiply it times the rate and00:08:21.229 --> 00:08:23.529 actually really quick while I.00:08:23.530 --> 00:08:26.434 Discussed that the rate here is00:08:26.434 --> 00:08:29.010 pulling from the rate table.00:08:29.010 --> 00:08:31.998 So sorry, the configuration table here.00:08:32.000 --> 00:08:34.420 So the configuration table00:08:34.420 --> 00:08:36.840 will have these codes.00:08:36.840 --> 00:08:40.445 Whoops, I'm still over here selecting stuff,00:08:40.450 --> 00:08:41.869 so those codes.00:08:41.869 --> 00:08:46.579 Are going to be in this rate column here.00:08:46.580 --> 00:08:49.324 So basically what this does is it00:08:49.324 --> 00:08:52.260 takes the value that is in this column00:08:52.260 --> 00:08:55.139 and it uses this ID for that rate.00:08:55.140 --> 00:08:58.380 It'll look up what that rate is on the00:08:58.380 --> 00:09:00.718 configuration table. Is it back end?00:09:00.718 --> 00:09:02.578 Is it front end development?00:09:02.580 --> 00:09:04.440 Is it a integration marketing?00:09:04.440 --> 00:09:07.072 It'll kind of tell you what rated is00:09:07.072 --> 00:09:09.637 here and what the percentages are.00:09:09.640 --> 00:09:12.244 I guess that's the high range percentage.00:09:12.250 --> 00:09:13.798 That's a different one,00:09:13.798 --> 00:09:16.889 but what the charge rate is for that.00:09:16.890 --> 00:09:18.430 Code.00:09:18.430 --> 00:09:22.948 And what this will do is it'll populate that.00:09:22.950 --> 00:09:24.230 Into this column here.00:09:24.230 --> 00:09:26.579 So here for designs I don't think00:09:26.579 --> 00:09:28.763 they had their own design company00:09:28.763 --> 00:09:30.440 coming into their designs,00:09:30.440 --> 00:09:32.096 so they didn't have anything here,00:09:32.100 --> 00:09:33.748 but if there was.00:09:33.748 --> 00:09:37.886 I could type in four here come the high00:09:37.886 --> 00:09:41.018 end would calculate using that 15%.00:09:41.020 --> 00:09:42.996 And it'll say that the high end would00:09:42.996 --> 00:09:45.313 be 5 and it will also calculate these00:09:45.313 --> 00:09:47.898 two things of the low cost and high cost.00:09:50.570 --> 00:09:54.610 So I'm using that same thing over here.00:09:54.610 --> 00:09:56.590 Uhm, so for the original and00:09:56.590 --> 00:09:59.200 then I'm kind of doing the exact00:09:59.200 --> 00:10:01.220 same thing here for revised,00:10:01.220 --> 00:10:04.340 and I'm using that same formula.00:10:04.340 --> 00:10:05.804 To get the revised.00:10:05.804 --> 00:10:08.542 So I basically just change it from00:10:08.542 --> 00:10:10.847 original to my revised estimate.00:10:10.850 --> 00:10:12.890 Here times the same rate,00:10:12.890 --> 00:10:16.537 and that'll give me the revised estimate.00:10:16.540 --> 00:10:20.518 How much cat will actually cost?00:10:20.520 --> 00:10:24.678 And then the last column here would just be.00:10:24.680 --> 00:10:27.020 The cost aspect of it.00:10:27.020 --> 00:10:27.950 The delta.00:10:30.120 --> 00:10:31.380 Do that in here.00:10:31.380 --> 00:10:34.740 So as you come and start filling things in.00:10:34.740 --> 00:10:37.356 You can see over here that you know00:10:37.356 --> 00:10:40.333 some will zero out if you go over it all.00:10:40.340 --> 00:10:41.890 It'll show as a positive,00:10:41.890 --> 00:10:44.378 so that will be over their initial estimate.00:10:44.380 --> 00:10:47.035 If we go down, it'll show that you know00:10:47.035 --> 00:10:49.758 it's not going to be that complex of a00:10:49.758 --> 00:10:52.156 project or that complex of a feature.00:10:54.620 --> 00:10:56.005 So that kind of gets00:10:56.005 --> 00:10:57.113 everything together over here.00:10:57.120 --> 00:10:59.298 I think the last thing I would kind of00:10:59.298 --> 00:11:01.850 do I really like the the formatting here.00:11:01.850 --> 00:11:03.789 I usually just use the format painter.00:11:03.790 --> 00:11:07.638 It's usually the easiest way to do it.00:11:07.640 --> 00:11:10.489 So that now all these do that.00:11:10.490 --> 00:11:13.066 Just to kind of say green is good,00:11:13.070 --> 00:11:14.036 we went down.00:11:14.036 --> 00:11:16.290 If you go over red is bad,00:11:16.290 --> 00:11:19.581 you went up. So very easy,00:11:19.581 --> 00:11:21.603 just a kind of visual representation00:11:21.603 --> 00:11:24.230 of exactly where your pain points are.00:11:24.230 --> 00:11:26.732 Anything that goes over that will00:11:26.732 --> 00:11:29.820 be a really good indicator of it.00:11:29.820 --> 00:11:32.578 Uhm, I think I also do that00:11:32.578 --> 00:11:34.539 for changing hours as well,00:11:34.540 --> 00:11:37.284 so let's bring that over here too.00:11:42.590 --> 00:11:46.896 That so that is all done here.00:11:46.900 --> 00:11:50.076 Uh, so you'll pretty much start going down.00:11:50.080 --> 00:11:52.065 Start finding which user stories00:11:52.065 --> 00:11:54.050 correlate to which line items.00:11:54.050 --> 00:11:56.829 If you do need to put anything,00:11:56.830 --> 00:12:01.037 that's just way out of left field.00:12:01.040 --> 00:12:02.930 You know, wasn't really discussed initially.00:12:02.930 --> 00:12:04.953 I usually kind of maybe put it00:12:04.953 --> 00:12:07.171 in one section down here is kind00:12:07.171 --> 00:12:09.097 of like a change request section00:12:09.166 --> 00:12:11.413 of you know this is stuff that00:12:11.413 --> 00:12:12.695 we uncovered during discovery.00:12:12.695 --> 00:12:14.270 We didn't initially scope it.00:12:14.270 --> 00:12:16.778 It's something that you know you00:12:16.778 --> 00:12:19.523 might not have mentioned Iran and I00:12:19.523 --> 00:12:21.833 would just kind of come down here.00:12:21.840 --> 00:12:25.248 Insert however many lines for the00:12:25.248 --> 00:12:27.950 features as you need to.00:12:27.950 --> 00:12:30.038 Fun, interesting shortcut for you guys.00:12:32.050 --> 00:12:35.040 After you do an insert, you can do00:12:35.040 --> 00:12:37.920 control Y to repeat the action.00:12:37.920 --> 00:12:44.278 But control Oh my gosh ran exploded.00:12:44.280 --> 00:12:46.880 My brain just exploded.00:12:48.950 --> 00:12:52.300 That is going to make my life so much easier.00:12:52.300 --> 00:12:53.748 Thank you for that.00:12:53.748 --> 00:12:55.899 When something ever did so, yeah,00:12:55.899 --> 00:12:58.611 you would come in here and put in00:12:58.611 --> 00:13:01.350 your new feature or whatever it is.00:13:01.350 --> 00:13:04.455 And if it's So what Ron usually does and00:13:04.455 --> 00:13:07.870 this kind of is a good representation of it.00:13:07.870 --> 00:13:10.285 He will have UI for the front00:13:10.285 --> 00:13:12.210 end aspect of a feature.00:13:12.210 --> 00:13:14.376 So product details page UI here.00:13:14.380 --> 00:13:16.984 He for anything that has UI on00:13:16.984 --> 00:13:19.869 it there is going to be a wire00:13:19.869 --> 00:13:22.439 up down here on the back end.00:13:22.440 --> 00:13:26.640 Side of it. So here.00:13:28.880 --> 00:13:30.210 Wire up so email notifications.00:13:30.210 --> 00:13:31.988 This would be like the front end00:13:31.988 --> 00:13:33.917 UI portion of it of the templates.00:13:33.920 --> 00:13:35.912 Then this would be the wire00:13:35.912 --> 00:13:37.240 up for the notifications.00:13:37.240 --> 00:13:39.676 Uhm, tried to find that down here,00:13:39.680 --> 00:13:41.540 but I think they were using00:13:41.540 --> 00:13:43.870 pretty much all of our attributes.00:13:43.870 --> 00:13:46.306 I don't think they had any major.00:13:46.310 --> 00:13:47.486 Oh yes they did.00:13:47.486 --> 00:13:49.760 So I remember we weren't planning on00:13:49.760 --> 00:13:51.548 product detail page customizations,00:13:51.550 --> 00:13:53.602 but I'm actually going to show00:13:53.602 --> 00:13:55.390 what that looked like after00:13:55.390 --> 00:13:57.478 everything is kind of all done.00:14:02.290 --> 00:14:03.030 Boom00:14:05.290 --> 00:14:07.130 so with this client, particularly,00:14:07.130 --> 00:14:09.618 UM, we kind of went a little bit00:14:09.618 --> 00:14:12.265 back and forth with the RE estimates00:14:12.265 --> 00:14:15.059 and so when I initially went through00:14:15.059 --> 00:14:17.393 it with them the first time,00:14:17.400 --> 00:14:20.968 we came back and it was really high.00:14:20.970 --> 00:14:23.715 And knowing that we went back and kind of00:14:23.715 --> 00:14:25.876 discussed a little bit more and said OK,00:14:25.880 --> 00:14:28.770 what can we actually do to get the cost down?00:14:28.770 --> 00:14:33.140 So I have a few of them here. Uhm?00:14:36.280 --> 00:14:38.092 And they went up a pretty00:14:38.092 --> 00:14:38.696 considerable amount.00:14:40.900 --> 00:14:43.872 But you can see here how I went in and put00:14:43.872 --> 00:14:47.112 all of the estimations in here. I'm like OK,00:14:47.112 --> 00:14:51.658 what's my actual totals? It was 31.00:14:51.660 --> 00:14:55.545 This is the page that referenced it.00:14:55.550 --> 00:14:57.899 And here you can kind of see the ones00:14:57.899 --> 00:15:00.155 that were pretty big deltas and red.00:15:02.260 --> 00:15:04.516 And, uh, like Kevin was saying,00:15:04.520 --> 00:15:09.080 up at the top, here is where you would have.00:15:09.080 --> 00:15:10.424 The discovery, technical specs,00:15:10.424 --> 00:15:12.105 and documentation. This is another00:15:12.105 --> 00:15:14.115 one where it got really complex.00:15:14.120 --> 00:15:16.563 There was a lot more discussion than00:15:16.563 --> 00:15:18.314 we originally anticipated having due00:15:18.314 --> 00:15:20.240 to their complexity of their designs00:15:20.240 --> 00:15:22.516 that came back from their third party,00:15:22.520 --> 00:15:24.536 so we had more meeting time,00:15:24.540 --> 00:15:26.430 and that's the stuff that we00:15:26.430 --> 00:15:28.570 had to go back and update.00:15:28.570 --> 00:15:30.580 Talk to them about and say,00:15:30.580 --> 00:15:33.051 you know it was more complex than00:15:33.051 --> 00:15:34.950 we originally thought it would be.00:15:34.950 --> 00:15:36.888 We had to have more discussions00:15:36.888 --> 00:15:38.959 on this stuff and really talk00:15:38.959 --> 00:15:41.834 through the details of it. So, uhm.00:15:41.834 --> 00:15:45.086 That's what we were talking about,00:15:45.090 --> 00:15:47.145 and updating the revised estimate00:15:47.145 --> 00:15:49.646 for these going into EP and00:15:49.646 --> 00:15:51.506 actually seeing what it is.00:15:51.510 --> 00:15:55.254 Uhm, the last thing I would say on this.00:15:55.260 --> 00:15:58.596 You know once you have gone through here,00:15:58.600 --> 00:16:02.344 you have all of your line items matching up.00:16:02.350 --> 00:16:04.852 Some of these here are kind00:16:04.852 --> 00:16:06.103 of blanket requirements,00:16:06.110 --> 00:16:08.606 so for like importing static content,00:16:08.610 --> 00:16:10.600 that's not something that's going00:16:10.600 --> 00:16:13.190 to fall under one specific feature.00:16:13.190 --> 00:16:14.858 It's really getting their00:16:14.858 --> 00:16:16.526 contents into the system.00:16:16.530 --> 00:16:19.866 It's kind of going to span multiple things.00:16:22.020 --> 00:16:24.508 And I accounted for those in other places,00:16:24.510 --> 00:16:26.370 so, uhm, I did this here.00:16:26.370 --> 00:16:27.558 This is definitely something00:16:27.558 --> 00:16:30.045 we can work on and do better on00:16:30.045 --> 00:16:31.655 instead of zeroing this out.00:16:31.660 --> 00:16:33.760 Actually, having them related directly to00:16:33.760 --> 00:16:36.018 the feature that they're going to be in.00:16:36.020 --> 00:16:39.010 That's what I did here.00:16:39.010 --> 00:16:41.794 So that was kind of my work around.00:16:41.800 --> 00:16:43.064 Anything that you know,00:16:43.064 --> 00:16:45.405 you're super not sure about or it's00:16:45.405 --> 00:16:47.310 been not mentioned whatsoever during00:16:47.310 --> 00:16:49.480 the project or anything like that.00:16:49.480 --> 00:16:51.230 You can zero it out.00:16:51.230 --> 00:16:54.366 Say, put a note in here of, you know,00:16:54.366 --> 00:16:55.758 not discussed during discovery,00:16:55.760 --> 00:16:58.210 and if that's something that comes up.00:16:58.210 --> 00:17:00.646 I usually ask about it during discovery.00:17:00.650 --> 00:17:01.282 Like hey,00:17:01.282 --> 00:17:03.494 there's this line item in your thing00:17:03.494 --> 00:17:06.226 here that we have not discussed whatsoever.00:17:06.230 --> 00:17:07.980 And they're like, Oh yeah,00:17:07.980 --> 00:17:09.970 I totally forgot to mention00:17:09.970 --> 00:17:11.960 that that's one thing that's.00:17:11.960 --> 00:17:13.330 Cut on our back burner,00:17:13.330 --> 00:17:15.778 but we still want to talk about or no,00:17:15.780 --> 00:17:16.872 that's an underlying thing00:17:16.872 --> 00:17:17.964 that we absolutely need.00:17:20.230 --> 00:17:23.575 But uhm, it's definitely00:17:23.575 --> 00:17:25.345 OK to 0 some things out.00:17:25.350 --> 00:17:27.126 If it's something that they just,00:17:27.130 --> 00:17:28.744 you know something that made it00:17:28.744 --> 00:17:30.210 into the estimations that they00:17:30.210 --> 00:17:31.570 don't necessarily want anymore.00:17:31.570 --> 00:17:34.090 Or it's just a nice to have a man they're00:17:34.160 --> 00:17:38.330 not really wanting it anymore, totally OK.00:17:38.330 --> 00:17:40.616 Uhm, so the last thing here.00:17:40.620 --> 00:17:43.427 What I would say would be re00:17:43.427 --> 00:17:45.189 calculating the amount of QA,00:17:45.190 --> 00:17:47.356 PM and meeting time that's going00:17:47.356 --> 00:17:49.759 to be needed for the project.00:17:49.760 --> 00:17:52.307 So this is going to be based on the00:17:52.307 --> 00:17:55.231 new RE estimated total for the project00:17:55.231 --> 00:17:58.297 and actually new cleaner does have a00:17:58.297 --> 00:18:00.427 really good representation of this.00:18:00.430 --> 00:18:01.627 The rates do,00:18:01.627 --> 00:18:04.420 I think change sometimes based on just00:18:04.505 --> 00:18:07.577 the size of the projects I know connect.00:18:07.580 --> 00:18:10.219 It's a little bit different from full00:18:10.219 --> 00:18:13.059 blown sev heavy customization projects.00:18:15.130 --> 00:18:17.566 But the QA is calculated by the00:18:17.566 --> 00:18:19.932 basically all of the revised estimates00:18:19.932 --> 00:18:22.416 and the entire column going all00:18:22.416 --> 00:18:25.010 the way up to the very first one.00:18:25.010 --> 00:18:30.026 Uhm, at 20% so times .2.00:18:30.030 --> 00:18:33.110 That's going to give you the estimation.00:18:33.110 --> 00:18:36.190 So we estimate QA to take 20%00:18:36.190 --> 00:18:40.080 of your total project hours.00:18:40.080 --> 00:18:42.300 So that's what you get here.00:18:42.300 --> 00:18:45.009 I kind of cheat a little bit and I00:18:45.009 --> 00:18:47.422 come over here and just get this00:18:47.422 --> 00:18:50.714 guy come and use that same thing to00:18:50.714 --> 00:18:53.029 go against the configuration table.00:18:53.030 --> 00:18:55.814 And what I do is just basically come00:18:55.814 --> 00:18:58.578 in here and I change the columns.00:18:58.580 --> 00:19:00.430 So instead of selecting this00:19:00.430 --> 00:19:02.280 column here for low hours,00:19:02.280 --> 00:19:05.208 I go over here and select this column00:19:05.208 --> 00:19:07.842 for revised hours and that'll give me00:19:07.842 --> 00:19:10.488 the right 20% based on the entire.00:19:10.488 --> 00:19:12.423 Column all the way up.00:19:14.630 --> 00:19:18.606 Uhm? Same with these,00:19:18.606 --> 00:19:21.630 but they work a little bit different00:19:21.714 --> 00:19:24.650 so I usually go one after the other.00:19:24.650 --> 00:19:27.506 So QA is the entire column here,00:19:27.510 --> 00:19:31.222 the next one down, which is I believe00:19:31.222 --> 00:19:34.864 meeting time that one is going to be00:19:34.864 --> 00:19:37.728 everything that was for QA plus QA.00:19:37.730 --> 00:19:40.684 Uhm, so it's going to be like00:19:40.684 --> 00:19:44.218 this full column. Times that rate.00:19:44.220 --> 00:19:46.638 Uhm, and then almost the same00:19:46.638 --> 00:19:48.690 for the project management time.00:19:48.690 --> 00:19:51.952 So it's going to be the QA00:19:51.952 --> 00:19:54.010 plus the meeting plus.00:19:54.010 --> 00:19:55.506 Everything else above that.00:19:55.506 --> 00:19:58.534 And that's how you get to your PM00:19:58.534 --> 00:20:01.005 budget for as the RE estimated value.00:20:01.010 --> 00:20:02.711 So based on this is how much00:20:02.711 --> 00:20:04.443 your project is going to cost00:20:04.443 --> 00:20:06.018 based on everything that we've00:20:06.018 --> 00:20:07.480 gone through and discovery.00:20:07.480 --> 00:20:09.865 And this is how much PM time we're going00:20:09.865 --> 00:20:12.175 to need for that re estimated cost.00:20:14.390 --> 00:20:18.020 Uhm? So I will stop there.00:20:18.020 --> 00:20:20.468 I know I've been talking like a madman,00:20:20.470 --> 00:20:22.622 uhm, and I know I might have lost00:20:22.622 --> 00:20:24.448 a couple of people possibly.00:20:24.450 --> 00:20:25.995 Does anyone have any questions00:20:25.995 --> 00:20:27.810 on anything I've covered so far?00:20:32.060 --> 00:20:34.125 Just a quick call out on a.00:20:34.130 --> 00:20:36.244 There's typically a line item for RE00:20:36.244 --> 00:20:38.278 estimates in most of the sales stuff,00:20:38.280 --> 00:20:40.368 and if we have to go back and00:20:40.368 --> 00:20:42.258 forth a couple of times that00:20:42.258 --> 00:20:44.490 needs to be updated as we go.00:20:46.560 --> 00:20:50.212 So the line items at the top? Uhm,00:20:50.212 --> 00:20:53.824 everything from RE estimates and above.00:20:53.830 --> 00:20:55.216 Before it goes to the client,00:20:55.220 --> 00:20:57.299 those need to be updated to be the actuals.00:20:59.470 --> 00:21:02.284 OK, so we're not talking like the00:21:02.284 --> 00:21:05.469 meeting if if we end up going back00:21:05.469 --> 00:21:07.870 to the client more than once,00:21:07.870 --> 00:21:11.134 and negotiating the re estimates whenever00:21:11.134 --> 00:21:14.190 that meeting whenever that gets sent.00:21:14.190 --> 00:21:15.320 We update all the actual.00:21:15.320 --> 00:21:16.912 So yeah, if you spend five or six00:21:16.912 --> 00:21:18.240 meetings on going over the estimates00:21:18.240 --> 00:21:20.113 and having to go back and circle back00:21:20.113 --> 00:21:21.863 then they re estimates line would grow.00:21:21.870 --> 00:21:23.678 So you need to update the actuals there.00:21:26.900 --> 00:21:29.726 And I guess that's a good call out though,00:21:29.730 --> 00:21:31.914 so my time is usually in discovery,00:21:31.920 --> 00:21:34.296 so my time I guess for for actually walking00:21:34.296 --> 00:21:36.442 the developers through that re estimation00:21:36.442 --> 00:21:38.830 process and figuring all of that out,00:21:38.830 --> 00:21:40.978 that's probably come out of my00:21:40.978 --> 00:21:42.998 discovery time versus your time is00:21:42.998 --> 00:21:45.102 going to come out of your PM time.00:21:45.110 --> 00:21:47.308 And Kevin correct me if I'm wrong,00:21:47.310 --> 00:21:48.900 if that's if that's where00:21:48.900 --> 00:21:50.760 our time is coming out of,00:21:50.760 --> 00:21:53.060 would this be the actual00:21:53.060 --> 00:21:54.900 developers going through it?00:21:54.900 --> 00:21:57.430 Like the time we need in their Sprint to grab00:21:57.488 --> 00:21:59.847 them and actually go through the document.00:21:59.850 --> 00:22:02.778 Yeah. Gotcha actually though the restaurant,00:22:02.780 --> 00:22:04.405 so that's that line item00:22:04.405 --> 00:22:06.030 specifically calls you out there.00:22:08.820 --> 00:22:10.880 Yeah, business analysts will reconcile00:22:10.880 --> 00:22:13.359 against three estimates. Yeah, it does.00:22:15.960 --> 00:22:18.664 So I don't know we might need to00:22:18.664 --> 00:22:21.154 change this because I mean I usually00:22:21.154 --> 00:22:23.841 just do all my stuff and I'll say00:22:23.841 --> 00:22:26.754 in my task or my time log that this00:22:26.754 --> 00:22:28.914 was specifically for re estimations.00:22:28.920 --> 00:22:32.440 Uhm? I personally just to show00:22:32.440 --> 00:22:34.769 it to the client what it means.00:22:34.770 --> 00:22:36.522 I've personally made a re estimate00:22:36.522 --> 00:22:38.724 line item if it didn't already exist00:22:38.724 --> 00:22:40.978 and then just add in whatever Kyle00:22:41.038 --> 00:22:42.853 the developers and depending on00:22:42.853 --> 00:22:45.000 the circumstances my own hours to00:22:45.000 --> 00:22:47.640 that so they can see it took us.00:22:47.640 --> 00:22:51.256 You know, six hours to do re estimates.00:22:51.260 --> 00:22:53.740 And the reason I prefer that is 'cause.00:22:53.740 --> 00:22:55.528 Otherwise if it just gets thrown00:22:55.528 --> 00:22:57.460 into PM or discovery or whatever,00:22:57.460 --> 00:22:59.630 it's more difficult to speak to than00:22:59.630 --> 00:23:01.800 just saying, yeah, we were on a,00:23:01.800 --> 00:23:03.760 you know, two hour call with four00:23:03.760 --> 00:23:05.520 of us for re estimates.00:23:08.780 --> 00:23:09.784 But that's just my00:23:09.784 --> 00:23:11.290 preference with how I do it.00:23:16.170 --> 00:23:17.780 That's a good call out.00:23:17.780 --> 00:23:18.484 No, definitely.00:23:18.484 --> 00:23:20.948 If there is anything in here that00:23:20.948 --> 00:23:23.224 you guys want to break up in EP.00:23:23.230 --> 00:23:25.477 I mean I'm always open to suggestions.00:23:25.480 --> 00:23:27.100 I always try to just keep00:23:27.100 --> 00:23:29.329 it to like a feature parity.00:23:29.330 --> 00:23:30.930 So specifically in here I00:23:30.930 --> 00:23:33.180 can see here and in my life.00:23:41.830 --> 00:23:43.950 Finding the right one here.00:23:43.950 --> 00:23:44.800 Yeah, interesting.00:23:46.810 --> 00:23:49.043 Uh, so like my persistent minicart widget00:23:49.043 --> 00:23:51.509 that was kind of like one feature here,00:23:51.510 --> 00:23:54.352 the front end and the back end00:23:54.352 --> 00:23:55.990 implement implementations of that.00:23:55.990 --> 00:23:59.234 Uhm? It was a lot.00:23:59.234 --> 00:24:01.489 Yeah, I mean it was a pretty detailed00:24:01.489 --> 00:24:03.903 task and I think that's what I had00:24:03.903 --> 00:24:06.480 here for the this year trailer status.00:24:06.480 --> 00:24:09.272 So this was a big guy here where00:24:09.272 --> 00:24:12.342 it was a building a status bar00:24:12.342 --> 00:24:14.622 into this whole thing here.00:24:14.630 --> 00:24:17.140 And we went through and.00:24:17.140 --> 00:24:20.420 Built out all of those.00:24:20.420 --> 00:24:22.676 Tasks, and that's kind of what went to,00:24:22.680 --> 00:24:24.626 so there are some things in here00:24:24.626 --> 00:24:26.617 that you will need to break out,00:24:26.620 --> 00:24:28.096 and this is something I try00:24:28.096 --> 00:24:29.730 to do during a discovery,00:24:29.730 --> 00:24:31.362 but whether this is a front00:24:31.362 --> 00:24:32.830 end or back end task,00:24:32.830 --> 00:24:34.498 I know that that's been something00:24:34.498 --> 00:24:36.238 that the PM's have struggled with00:24:36.238 --> 00:24:38.510 before and I've been trying to do that00:24:38.564 --> 00:24:40.440 as I go through these re estimates.00:24:40.440 --> 00:24:41.850 I think it's something new.00:24:41.850 --> 00:24:43.754 I've just been starting to do so that00:24:43.754 --> 00:24:45.562 you guys know which developers to00:24:45.562 --> 00:24:47.482 assign those two because you're like,00:24:47.490 --> 00:24:47.764 well,00:24:47.764 --> 00:24:49.956 I don't know if this is a front00:24:49.956 --> 00:24:52.050 end or back end task, what what?00:24:52.050 --> 00:24:53.575 Does it go to UM,00:24:53.580 --> 00:24:55.617 so that's something I've been trying to00:24:55.617 --> 00:24:59.730 get a little bit better about, UM, so.00:24:59.730 --> 00:25:01.980 Better things to come, yeah?00:25:04.060 --> 00:25:05.848 Uhm, but yeah, that's where those00:25:05.848 --> 00:25:08.202 would kind of go over to would be00:25:08.202 --> 00:25:10.350 these two line items here and that's00:25:10.350 --> 00:25:12.540 not something we discussed initially,00:25:12.540 --> 00:25:14.815 so they are not so pretty much.00:25:14.820 --> 00:25:18.436 All of these here or all of the00:25:18.436 --> 00:25:20.730 customizations on our home page.00:25:20.730 --> 00:25:22.774 The wire up for all of that.00:25:22.780 --> 00:25:24.538 Some of the stuff that they00:25:24.538 --> 00:25:25.710 wanted in their catalog.00:25:25.710 --> 00:25:27.175 All of those didn't have00:25:27.175 --> 00:25:28.054 initial estimations here,00:25:28.060 --> 00:25:29.750 'cause there's stuff that we00:25:29.750 --> 00:25:31.102 just uncovered during discussion00:25:31.102 --> 00:25:32.434 that we're actually gonna have00:25:32.434 --> 00:25:34.210 to go in and do that stuff.00:25:34.210 --> 00:25:36.546 So that's kind of what I have here.00:25:39.900 --> 00:25:42.133 And for some reason, I don't think00:25:42.133 --> 00:25:43.749 those other estimations they're in.00:25:43.750 --> 00:25:45.676 I think a more updated copy.00:25:45.680 --> 00:25:47.941 I think I'm pulling one that they00:25:47.941 --> 00:25:50.380 did not sign off on and you put00:25:50.380 --> 00:25:52.420 this into a new clean article.00:25:52.420 --> 00:25:54.667 Sorry, I thought I saw that again.00:25:54.670 --> 00:25:56.554 This was a new cleaner article00:25:56.554 --> 00:25:58.844 that was way back when we were00:25:58.844 --> 00:26:00.764 first kind of going through it.00:26:00.770 --> 00:26:03.330 It has a lot of really good information.00:26:03.330 --> 00:26:05.647 This all needs to change because it00:26:05.647 --> 00:26:08.197 was when this is not on my template.00:26:08.200 --> 00:26:09.950 Here, uh, this was just a template00:26:09.950 --> 00:26:11.499 that we were going through.00:26:11.500 --> 00:26:13.150 Like you see, Gary was like,00:26:13.150 --> 00:26:16.246 oh this is blank 'cause I guess it00:26:16.246 --> 00:26:19.180 needs to be cleaned up for sure.00:26:19.180 --> 00:26:22.042 'cause I kind of just did this based on.00:26:22.050 --> 00:26:23.970 Like you know I need to.00:26:23.970 --> 00:26:26.666 I need to show the difference and the00:26:26.666 --> 00:26:29.035 quickest and easiest way I saw to do00:26:29.035 --> 00:26:31.939 that was to just add these columns on here.00:26:31.940 --> 00:26:34.444 Use the formulas that are already in the00:26:34.444 --> 00:26:37.205 in the workbook and just start plugging00:26:37.205 --> 00:26:39.962 stuff in until I'm completely done and00:26:39.962 --> 00:26:42.516 see what my numbers come out too. Uhm,00:26:42.516 --> 00:26:45.900 so that's just the way I've been doing it.00:26:45.900 --> 00:26:47.780 I definitely need to write.00:26:47.780 --> 00:26:50.405 Kind of that down formula formally here,00:26:50.410 --> 00:26:54.170 but this is this is a good blurb up here.00:26:54.170 --> 00:26:56.426 I mean, this is definitely accurate.00:26:56.430 --> 00:26:59.670 Is that template still the same?00:26:59.670 --> 00:27:03.766 Or sorry and I miss this one here.00:27:03.770 --> 00:27:06.670 I don't think so.00:27:06.670 --> 00:27:08.600 That is a great question.00:27:08.600 --> 00:27:09.755 Let's find out.00:27:09.755 --> 00:27:10.910 No, this is.00:27:10.910 --> 00:27:11.352 It's.00:27:11.352 --> 00:27:12.236 It's similar,00:27:12.236 --> 00:27:16.170 but it is kind of broken out by like.00:27:16.170 --> 00:27:18.246 Here was the feature that was00:27:18.246 --> 00:27:19.630 in the initial estimation,00:27:19.630 --> 00:27:21.751 and here are all the tasks are00:27:21.751 --> 00:27:23.916 the users winnings that 'cause it00:27:23.916 --> 00:27:25.504 doesn't have the calculations?00:27:25.510 --> 00:27:26.894 I mean it does.00:27:26.894 --> 00:27:28.970 It has your revised estimate here,00:27:28.970 --> 00:27:31.738 just like mine does that change the comments?00:27:31.740 --> 00:27:33.124 The IW page reference,00:27:33.124 --> 00:27:33.816 the rate?00:27:33.820 --> 00:27:36.172 I don't have this because I literally00:27:36.172 --> 00:27:38.644 just grab that formula and it uses00:27:38.644 --> 00:27:40.738 the rate that's over here already.00:27:40.740 --> 00:27:43.288 That's why I wanted to use the00:27:43.288 --> 00:27:45.089 initial estimates 'cause I have00:27:45.089 --> 00:27:46.369 all of those original.00:27:46.370 --> 00:27:48.155 Estimations in the rate that00:27:48.155 --> 00:27:49.583 it was calculated already,00:27:49.590 --> 00:27:52.206 so that's why this one kind of fell00:27:52.206 --> 00:27:54.290 short because you would have to00:27:54.290 --> 00:27:56.330 go in and manually put everything00:27:56.403 --> 00:27:58.538 over or cross reference somehow.00:27:58.540 --> 00:28:00.292 What we initially estimated.00:28:00.292 --> 00:28:01.606 And that's hard.00:28:01.610 --> 00:28:02.970 That's hard to do.00:28:02.970 --> 00:28:05.420 That's would be these blue ones here.00:28:05.420 --> 00:28:07.280 Like this was the original feature00:28:07.280 --> 00:28:09.652 and these are the things that we got00:28:09.652 --> 00:28:11.680 at a re estimations and it would.00:28:11.680 --> 00:28:13.165 Basically this is the original00:28:13.165 --> 00:28:14.056 for the feature.00:28:14.060 --> 00:28:17.732 This was the revised based on all these guys.00:28:17.740 --> 00:28:19.756 And then this would be the00:28:19.756 --> 00:28:21.500 difference for that line item.00:28:21.500 --> 00:28:22.718 And then do all the reporting00:28:22.718 --> 00:28:23.530 over here with that.00:28:28.230 --> 00:28:30.606 For me that was just an extra step00:28:30.606 --> 00:28:32.918 trying to get all the initial stuff00:28:32.918 --> 00:28:35.519 in here and then trying to format it.00:28:35.520 --> 00:28:38.180 Yeah, I wouldn't do that.00:28:38.180 --> 00:28:38.982 Interesting though,00:28:38.982 --> 00:28:41.388 because there could be certain user00:28:41.388 --> 00:28:43.387 stories that are split among back00:28:43.387 --> 00:28:45.680 end and front end tasks and features,00:28:45.680 --> 00:28:48.884 so we may not be pulling the correct rate00:28:48.884 --> 00:28:52.605 if we're just going with the overall rate00:28:52.605 --> 00:28:56.035 that was originally set in the in the sales.00:28:56.040 --> 00:28:58.384 Exactly, so if there is a back end00:28:58.384 --> 00:29:00.994 aspect of that, if there's a UI,00:29:00.994 --> 00:29:02.618 something UI up here.00:29:02.620 --> 00:29:05.920 That did not have.00:29:05.920 --> 00:29:06.943 Of wire up,00:29:06.943 --> 00:29:09.330 I would literally just come in here.00:29:09.330 --> 00:29:13.188 Add this and dude wire up.00:29:13.190 --> 00:29:13.440 But00:29:15.870 --> 00:29:17.628 so I'm at the back end,00:29:17.630 --> 00:29:19.508 no initial because we didn't know00:29:19.508 --> 00:29:21.730 we were gonna have to do back end,00:29:21.730 --> 00:29:23.634 whatever for it and then come over00:29:23.634 --> 00:29:25.442 here and kind of specify whatever00:29:25.442 --> 00:29:27.296 that revised was and say hey,00:29:27.300 --> 00:29:29.052 we didn't know that this was00:29:29.052 --> 00:29:30.810 going to require back end work.00:29:30.810 --> 00:29:32.280 Here's the estimation for that.00:29:32.280 --> 00:29:34.324 It's going to be a $700.00 difference.00:29:37.360 --> 00:29:39.754 But that's how I would handle that.00:29:39.760 --> 00:29:41.674 At least. UM, definitely added in00:29:41.674 --> 00:29:44.156 if it's not in here already, uhm?00:29:44.156 --> 00:29:46.990 But if you don't see it on the back end,00:29:46.990 --> 00:29:48.095 I would just always make00:29:48.095 --> 00:29:49.500 sure that if you see a UI,00:29:49.500 --> 00:29:50.956 just go look for a wire up.00:29:50.960 --> 00:29:52.010 If there's not one there,00:29:52.010 --> 00:29:53.258 feel free to add it in.00:29:56.560 --> 00:29:58.648 But good question. Yeah, I I.00:29:58.650 --> 00:30:01.522 I showed that just because it has a00:30:01.522 --> 00:30:03.940 really good blurb down here 'cause00:30:03.940 --> 00:30:06.906 this is still pretty pretty on point00:30:06.906 --> 00:30:09.196 with how these are calculated.00:30:09.200 --> 00:30:10.640 These, like I said,00:30:10.640 --> 00:30:13.629 these do change and if those do change,00:30:13.630 --> 00:30:15.515 you'll probably see it in00:30:15.515 --> 00:30:17.023 this configuration table over00:30:17.023 --> 00:30:18.789 here 'cause it'll have QA,00:30:18.790 --> 00:30:20.270 PM and project management.00:30:20.270 --> 00:30:22.120 It'll have those over here.00:30:22.120 --> 00:30:24.808 So if you change those rates it00:30:24.808 --> 00:30:26.714 will dynamically change what those00:30:26.714 --> 00:30:28.754 actually get put in here as.00:30:31.330 --> 00:30:32.940 So for QA bug fixes,00:30:32.940 --> 00:30:34.550 if that's 56 right now,00:30:34.550 --> 00:30:38.537 if I came in here and did this to.00:30:38.540 --> 00:30:42.320 20% instead of 15.00:30:42.320 --> 00:30:46.485 Yep, I go from 56 up to.00:30:46.490 --> 00:30:49.950 Oh well, they're going to 59.00:30:49.950 --> 00:30:53.219 I don't know what it was before.00:30:53.220 --> 00:30:56.778 59 and originally it was 44.00:30:56.780 --> 00:30:59.612 So 44 to 59 is what it did00:30:59.612 --> 00:31:02.284 there and I think I put the00:31:02.284 --> 00:31:04.550 high end on it based on.00:31:04.550 --> 00:31:05.438 Did I do that?00:31:09.270 --> 00:31:11.100 Oh, that was the original, huh?00:31:14.060 --> 00:31:15.350 Yeah, that was mine here,00:31:15.350 --> 00:31:17.135 but it still uses that same rate.00:31:23.790 --> 00:31:24.780 Good questions though.00:31:27.880 --> 00:31:29.910 Oh, and something just to call out00:31:29.910 --> 00:31:31.595 something I've noticed on some of00:31:31.595 --> 00:31:34.649 the other projects. This does not.00:31:34.650 --> 00:31:37.780 Update I don't know why.00:31:37.780 --> 00:31:38.977 Kevin, maybe you?00:31:38.977 --> 00:31:43.360 Could help me figure this one out, uhm?00:31:43.360 --> 00:31:45.208 'cause I know we've sent this00:31:45.208 --> 00:31:47.190 before and this will not update.00:31:47.190 --> 00:31:49.276 I have not figured out how this00:31:49.276 --> 00:31:51.019 all just looks like static,00:31:51.020 --> 00:31:52.610 just no formulas or anything.00:31:52.610 --> 00:31:54.758 I wasn't really sure and sometimes00:31:54.758 --> 00:31:56.802 it just confuses the client to00:31:56.802 --> 00:31:58.986 no end of like what is all this.00:31:58.990 --> 00:32:01.534 I'm like, yeah we should really delete it,00:32:01.540 --> 00:32:04.423 yeah? And like this,00:32:04.423 --> 00:32:06.028 it's just the draw schedule.00:32:06.030 --> 00:32:07.630 An old trick confusing, yeah,00:32:07.630 --> 00:32:09.877 this stuff if you get into this.00:32:09.880 --> 00:32:12.022 I've looked at this quite a lot00:32:12.022 --> 00:32:14.001 and those are all tools for00:32:14.001 --> 00:32:15.656 run in the sales process.00:32:15.660 --> 00:32:15.968 Yeah,00:32:15.968 --> 00:32:18.124 this actually isn't the the RE estimate00:32:18.124 --> 00:32:20.149 template that I put together originally.00:32:20.150 --> 00:32:21.755 We've just started modifying the00:32:21.755 --> 00:32:23.504 sales estimates, which is fine,00:32:23.504 --> 00:32:26.080 but I think we need to know00:32:26.177 --> 00:32:28.457 that everyone has seen it.00:32:28.460 --> 00:32:30.068 But you guys brainstorm some ideas.00:32:30.070 --> 00:32:33.160 How did we could improve it?00:32:33.160 --> 00:32:34.090 100%.00:32:40.450 --> 00:32:43.334 And I think one thing that I00:32:43.334 --> 00:32:44.890 talked about originally is,00:32:44.890 --> 00:32:47.954 I mean I know you guys have kind00:32:47.954 --> 00:32:51.331 of seen how I make these iws feel00:32:51.331 --> 00:32:53.379 you have, where actually it's00:32:53.379 --> 00:32:55.394 in my view Navigation Pane.00:32:57.560 --> 00:32:59.820 Just collapse all of these.00:32:59.820 --> 00:33:02.590 So I tried to put it in a pretty good00:33:02.666 --> 00:33:05.114 feature parity, and generally I'll have.00:33:05.114 --> 00:33:06.769 This has a lot more,00:33:06.770 --> 00:33:09.082 I'll just point out the general ones that00:33:09.082 --> 00:33:11.738 I start with is just general requirements.00:33:11.740 --> 00:33:14.380 Just going to have the SSL 301 redirects,00:33:14.380 --> 00:33:16.328 just general requirement stuff00:33:16.328 --> 00:33:19.250 post their go live checklist stuff.00:33:19.250 --> 00:33:24.300 Home page I got home page. Uhm?00:33:24.300 --> 00:33:27.290 Catalog, UM, any catalog customizations?00:33:27.290 --> 00:33:30.270 I just go by modules,00:33:30.270 --> 00:33:32.658 so catalog product details,00:33:32.658 --> 00:33:34.449 page shopping cart,00:33:34.450 --> 00:33:38.482 going into check out, and then00:33:38.482 --> 00:33:43.249 ultimately going to a user dashboard.00:33:43.250 --> 00:33:46.238 And then automated email notifications and00:33:46.238 --> 00:33:49.100 then any integration stuff after that.00:33:49.100 --> 00:33:52.196 So I just kind of go by storefront module00:33:52.196 --> 00:33:55.069 and then I go for any notifications,00:33:55.070 --> 00:33:57.650 anything like that.00:33:57.650 --> 00:34:00.058 Actually, I think I've added in login and00:34:00.058 --> 00:34:02.016 authentication and a kind of setting up Seth.00:34:02.020 --> 00:34:04.060 So like setting up your development00:34:04.060 --> 00:34:06.061 environment and things like that would00:34:06.061 --> 00:34:08.112 be kind of like a general requirement.00:34:08.120 --> 00:34:11.135 Uhm, so that's kind of how I structured it.00:34:11.140 --> 00:34:13.317 Uhm, I know that that's kind of00:34:13.317 --> 00:34:15.488 hard when you're looking over here.00:34:15.490 --> 00:34:17.170 When I after you're done,00:34:17.170 --> 00:34:18.840 you're like well, where does?00:34:18.840 --> 00:34:20.520 Where does, uh, you know,00:34:20.520 --> 00:34:24.396 whatever you call it, go into.00:34:24.400 --> 00:34:28.408 A image rotator is probably a bad one.00:34:28.410 --> 00:34:30.026 But if you see stuff like set up00:34:30.026 --> 00:34:31.658 discounts and promotions and you're like,00:34:31.660 --> 00:34:34.864 well, what do I use this for? Uhm?00:34:34.864 --> 00:34:37.468 There might just be some things00:34:37.468 --> 00:34:38.770 that you're like.00:34:38.770 --> 00:34:39.285 Well,00:34:39.285 --> 00:34:42.890 that's not really how it's structured so.00:34:42.890 --> 00:34:43.793 I don't know.00:34:43.793 --> 00:34:46.477 I've had a long talk with Ron about it00:34:46.477 --> 00:34:48.979 and I want to see if we can possibly00:34:48.979 --> 00:34:51.870 get what he does in its initial00:34:51.870 --> 00:34:53.906 estimations closer to a feature00:34:53.906 --> 00:34:56.720 parity that's easy for you guys too.00:34:56.720 --> 00:34:57.129 Take.00:34:57.129 --> 00:34:59.583 And actually plug in my numbers00:34:59.583 --> 00:35:01.060 from the IW 2.00:35:03.700 --> 00:35:06.514 So I just think where we start00:35:06.514 --> 00:35:08.167 isn't necessarily where we00:35:08.167 --> 00:35:10.148 finish, if that makes sense.00:35:14.490 --> 00:35:16.667 Just an idea though, I'm just spitballing.00:35:20.570 --> 00:35:21.855 'cause we haven't yet really00:35:21.855 --> 00:35:22.883 confirmed anything on that.00:35:22.890 --> 00:35:25.203 It was just kind of a discussion one day.00:35:28.110 --> 00:35:32.115 On which park Co? On getting runs00:35:32.115 --> 00:35:33.660 initial estimation template,00:35:33.660 --> 00:35:39.717 just the feature parity for it and a more.00:35:39.720 --> 00:35:41.934 Kind of generic or more standard00:35:41.934 --> 00:35:44.387 format to where what I create is00:35:44.387 --> 00:35:46.487 the end game for my IW actually00:35:46.557 --> 00:35:48.717 matches his initial estimation.00:35:52.280 --> 00:35:54.254 Like a feature parity that's easy to00:35:54.254 --> 00:35:56.459 follow once you have an IW like Oh yeah,00:35:56.460 --> 00:35:58.540 this is where it goes in the estimation,00:35:58.540 --> 00:36:01.396 I see that Ron estimated it right here.00:36:01.400 --> 00:36:02.700 Sometimes it's not that easy00:36:02.700 --> 00:36:04.430 to go and find those things.00:36:04.430 --> 00:36:06.638 Yeah, it's something that I was hoping to00:36:06.638 --> 00:36:09.378 get to work on and haven't got around to it.00:36:09.380 --> 00:36:13.020 But I do think we need to kind of update.00:36:13.020 --> 00:36:15.453 This template summits.00:36:15.453 --> 00:36:18.697 A little dated uhm?00:36:18.700 --> 00:36:20.326 Because I could use some sprucing.00:36:22.360 --> 00:36:25.160 I do love sprucing.00:36:25.160 --> 00:36:27.650 Does that mean you just volunteered?00:36:27.650 --> 00:36:29.074 No, yes, I'd I'd.00:36:29.074 --> 00:36:30.498 I would use away.00:36:30.500 --> 00:36:32.033 Spruce awakens Sir.00:36:32.033 --> 00:36:35.610 I went and bugged round about it.00:36:35.610 --> 00:36:38.004 Yeah, come up with a come up00:36:38.004 --> 00:36:40.355 with a template for it and let's00:36:40.355 --> 00:36:43.000 let's take a look at it for sure.00:36:43.000 --> 00:36:44.680 Yeah, I started it kind00:36:44.680 --> 00:36:46.024 of actually re estimation.00:36:49.210 --> 00:36:54.540 I made one. At one time.00:36:54.540 --> 00:36:56.580 'cause I showed Ron I remember00:36:56.580 --> 00:36:58.829 I would have to go find it.00:37:01.280 --> 00:37:02.720 But so does that. Does that make sense00:37:02.720 --> 00:37:04.210 on the RE estimates for everybody?