---Presenter: Kevin KramerSubject: Architecture ReviewDetails: What are architecture reviews, and what are the expectations?Duration: 00:09:37---00:00:00.030 --> 00:00:04.359 - So we have a jam packed uhm agenda today along with a couple 00:00:04.359 --> 00:00:08.355 - of exercises were going to go through and a couple of places 00:00:08.355 --> 00:00:12.018 - where we're going to discuss, but for the most part everyone 00:00:12.018 --> 00:00:16.014 - should buy this point in time. Have had a chance to review. 00:00:16.590 --> 00:00:19.390 - Uh, the architecture document and what the architecture 00:00:19.390 --> 00:00:22.540 - reviews are an what our expectations are. So last 00:00:22.540 --> 00:00:26.040 - weekend and Monday I worked on a comprehensive document that 00:00:26.040 --> 00:00:30.240 - calls out the process based on kind of all of our discussion 00:00:30.240 --> 00:00:34.090 - and back and forth. So we had something documented and had 00:00:34.090 --> 00:00:35.140 - clear expectations set. 00:00:35.710 --> 00:00:39.389 - Uh, so has everyone had a chance to review that? Are there any 00:00:39.389 --> 00:00:40.521 - sections specifically that we 00:00:40.521 --> 00:00:42.770 - want to cover? Um? 00:00:43.350 --> 00:00:44.390 - I have reviewed it. 00:00:45.120 --> 00:00:49.560 - I have reviewed it awesome so it should be relatively quick to 00:00:49.560 --> 00:00:52.730 - get through. We're going to talk through a little bit of the 00:00:52.730 --> 00:00:54.908 - change request process. What does it change? How we 00:00:54.908 --> 00:00:57.570 - documented and I have put together a new template that I 00:00:57.570 --> 00:00:59.990 - think looks more professional and has a little bit more 00:00:59.990 --> 00:01:02.168 - information that should help. You guys manage expectations a 00:01:02.168 --> 00:01:06.450 - little bit clearly. So we're going to cover that. 00:01:06.450 --> 00:01:09.466 - I'm going to ask that we hold all comments till I get through 00:01:09.466 --> 00:01:12.250 - the section on that one because I literally have a section to 00:01:12.250 --> 00:01:16.710 - discuss it. Um and take any feedback and we can make any 00:01:16.710 --> 00:01:18.098 - adjustments in that time. 00:01:18.220 --> 00:01:21.570 - And then we're going to talk through some Azure DevOps 00:01:21.570 --> 00:01:25.590 - backlog management. Little bit of how to and then kind of go 00:01:25.590 --> 00:01:28.605 - through some ticket examples. What's good, what's bad, what's 00:01:28.605 --> 00:01:31.955 - ugly, and we have a little game to play so. 00:01:31.990 --> 00:01:38.486 - But You you won't. Oh there are no winners. 00:01:39.410 --> 00:01:41.930 - Alright, so architecture review. 00:01:42.830 --> 00:01:45.650 - So essentially I've broken down the document into the slides 00:01:45.650 --> 00:01:49.880 - here just so we can kind of have it to reference if we need to, 00:01:49.880 --> 00:01:52.700 - but ultimately the architecture review is going to generate what 00:01:52.700 --> 00:01:55.520 - is needed to have an effective work breakdown structure and 00:01:55.520 --> 00:01:57.212 - kind of hours estimation on the 00:01:57.212 --> 00:02:02.455 - task. Um? The process currently, since we're not, we don't have 00:02:02.455 --> 00:02:05.605 - any projects in the pipeline that have had this estimated. 00:02:05.605 --> 00:02:09.385 - It'll probably be a little bit before that happens. Is that for 00:02:09.385 --> 00:02:12.220 - every 100 hours on your projects, original estimates, 2 00:02:12.220 --> 00:02:15.685 - hours of credit is available to make sure that this meeting 00:02:15.685 --> 00:02:19.150 - happens. At the outputs are put together, so if you're working 00:02:19.150 --> 00:02:22.930 - on 1000 hour project, you know that gives you 20 hours of 00:02:22.930 --> 00:02:25.450 - credit available towards the architecture review and stuff 00:02:25.450 --> 00:02:28.285 - like that. Now the documentation discovery hours should cover 00:02:28.285 --> 00:02:30.805 - some of this as well, so we only 00:02:30.805 --> 00:02:34.824 - need. So we need to use that if we need to, but it is there 00:02:34.824 --> 00:02:37.695 - an pre approved by management. You don't need to worry about 00:02:37.695 --> 00:02:40.566 - asking for those hours to be credited. That is, there is 00:02:40.566 --> 00:02:42.915 - kind of your safety net for the architecture review. 00:02:44.280 --> 00:02:48.050 - So, uhm, the meeting should consist of the business analyst. 00:02:48.050 --> 00:02:52.951 - In this case Kyle, and for the short term until we nail down 00:02:52.951 --> 00:02:57.475 - the process of making sure we're hitting on all cylinders, I will 00:02:57.475 --> 00:03:02.376 - need to be invited. All of those as well. The project manager, a 00:03:02.376 --> 00:03:06.900 - senior front end developer which has been defined as I believe CB 00:03:06.900 --> 00:03:11.020 - or Jesse. For the time being, a senior back end developer which 00:03:11.020 --> 00:03:15.028 - would be James or Eric if it's a self project, I strongly 00:03:15.028 --> 00:03:18.034 - encourage the team to make sure James is present. 00:03:18.620 --> 00:03:22.974 - Um, and if he's not then user 'cause it back up there. If it's 00:03:22.974 --> 00:03:26.395 - a yeah any set project, James right not even showing courage 00:03:26.395 --> 00:03:29.194 - just like mandatory. Think Eric will even say that. 00:03:29.730 --> 00:03:32.394 - Yep, uhm, but there are situations where James will 00:03:32.394 --> 00:03:35.946 - be on vacation, so I don't want to make it limiting. and 00:03:35.946 --> 00:03:39.202 - I definitely don't want to just say it's going to be 00:03:39.202 --> 00:03:39.794 - James forever. 00:03:40.880 --> 00:03:44.620 - So roles in the 00:03:44.620 --> 00:03:48.288 - architecture review. This is essentially just kind of 00:03:48.288 --> 00:03:51.068 - outlining what each person's role will be. There was some 00:03:51.068 --> 00:03:54.126 - back and forth between Chris and I about what the business 00:03:54.126 --> 00:03:57.462 - analyst role should be. He and I chatted over the weekend and 00:03:57.462 --> 00:04:00.798 - came to a compromise that we do indeed want the developers to 00:04:00.798 --> 00:04:03.022 - write the technical documentation, but we want that 00:04:03.022 --> 00:04:06.636 - to happen in that meeting in the teams chat for that meeting so 00:04:06.636 --> 00:04:09.972 - that Kyle can copy and paste and make sure that it's transferred 00:04:09.972 --> 00:04:12.752 - into a readable format taking anything but the basic technical 00:04:12.752 --> 00:04:15.254 - documentation of the developers plate and where he's still 00:04:15.254 --> 00:04:18.312 - putting that information into the IW where it needs to go. 00:04:19.000 --> 00:04:23.800 - Um, so the PM's role in that meeting is just capture any 00:04:23.800 --> 00:04:27.400 - overall concerns. Help keep the meeting on track, uhm? 00:04:28.150 --> 00:04:31.234 - And make sure that if Kyle starts to flounder, we get him 00:04:31.234 --> 00:04:34.832 - back on track. Or if I start to flounder we get me back on 00:04:34.832 --> 00:04:38.430 - track. We all know that I have a bad tendency of doing that so 00:04:38.430 --> 00:04:41.257 - just making sure that you guys are facilitating the meeting and 00:04:41.257 --> 00:04:43.827 - that you're taking the overall notes in those meetings. Kyle, 00:04:43.827 --> 00:04:47.168 - if he's taking that output and trying to put into the IW in 00:04:47.168 --> 00:04:50.252 - real time, we're kind of making notes of his own about the 00:04:50.252 --> 00:04:52.822 - technical functionality. He's not going to be able to catch 00:04:52.822 --> 00:04:55.649 - the side conversations that are no doubt going to be happening 00:04:55.649 --> 00:04:58.733 - in that meeting, so make sure you guys are still ready and 00:04:58.733 --> 00:04:59.761 - able to take notes. 00:05:01.020 --> 00:05:04.543 - And we kind of covered with the developers role is I am planning 00:05:04.543 --> 00:05:07.253 - on reviewing this with the development team next week. Um, 00:05:07.253 --> 00:05:10.524 - so. I believe I will be relinquishing training back over 00:05:10.524 --> 00:05:13.982 - to Daniel for the entire T of next weeks meeting while I go 00:05:13.982 --> 00:05:15.844 - kind of cover some things in the 00:05:15.844 --> 00:05:19.684 - developer training. So just as a quick high level there. 00:05:20.410 --> 00:05:25.287 - Uh. And then what are the outputs so? 00:05:26.350 --> 00:05:30.230 - The opportunist meeting should have everything we need to get 00:05:30.230 --> 00:05:31.394 - to start development. 00:05:31.990 --> 00:05:36.046 - And kind of just a couple examples I have here that we 00:05:36.046 --> 00:05:39.088 - would document any items we needed from the client. 00:05:39.730 --> 00:05:42.821 - And then for what development needs to happen for a particular 00:05:42.821 --> 00:05:45.631 - feature, user story could be things like we need to 00:05:45.631 --> 00:05:47.317 - validatethelatestauthorize.net packages, make sure it's codes 00:05:47.317 --> 00:05:49.846 - up-to-date, making sure we're updating all the apps settings 00:05:49.846 --> 00:05:52.656 - related to the payment provider to make sure that's working. 00:05:52.656 --> 00:05:55.185 - Validate the credit card payments are going through and 00:05:55.185 --> 00:05:56.309 - then make any adjustments. 00:05:57.010 --> 00:05:59.990 - Um, in the actual document I provided some examples that 00:05:59.990 --> 00:06:03.268 - Andrew has put together from the Digitek document just to give 00:06:03.268 --> 00:06:07.142 - people an idea, I do believe the formats going to evolve, and I 00:06:07.142 --> 00:06:11.016 - don't want to quite dictate that yet until we go through a couple 00:06:11.016 --> 00:06:14.146 - of these. We call you have a plan on how you're planning to 00:06:14.146 --> 00:06:15.728 - document that we want to see how 00:06:15.728 --> 00:06:18.030 - that turns out. It. 00:06:18.730 --> 00:06:21.500 - Uh, so. 00:06:24.240 --> 00:06:27.866 - Just kind of the high level there as far as we are in the 00:06:27.866 --> 00:06:30.715 - process. Does it occur? I'm adding a new section. You can 00:06:30.715 --> 00:06:33.305 - kind of see it there in the background, highlighted green 00:06:33.305 --> 00:06:36.413 - and covered up because my design skills are not that great today. 00:06:37.440 --> 00:06:41.873 - We're going to add a new section to the SDLC, so after discovery 00:06:41.873 --> 00:06:45.624 - will have post discovery now. Although I have this called out 00:06:45.624 --> 00:06:48.693 - that this happens in post discovery, there's no reason 00:06:48.693 --> 00:06:52.103 - that for her super complex projects that pieces of this 00:06:52.103 --> 00:06:56.536 - can't be done while the rest of discovery is still going on to 00:06:56.536 --> 00:06:59.605 - make sure we capture those different components from those 00:06:59.605 --> 00:07:03.015 - meetings. Ultimately, Chris and I have very different schools of 00:07:03.015 --> 00:07:07.107 - thought on this one. Daniel can attest to the Fight Club that 00:07:07.107 --> 00:07:10.518 - ensued. Uhm, but ultimately, if it's something that we're pretty 00:07:10.518 --> 00:07:14.170 - certain it's not going to change, feel free to go ahead 00:07:14.170 --> 00:07:18.154 - and do that in discovery, but Even so, in post discovery that 00:07:18.154 --> 00:07:20.478 - needs to be recapped in case any 00:07:20.478 --> 00:07:24.224 - things have changed. Uh, just to make sure that we have. 00:07:24.840 --> 00:07:27.090 - The latest information is we're kind of moving forward. 00:07:27.090 --> 00:07:30.090 - Um, and the reason for that is, of course we're still in 00:07:30.090 --> 00:07:32.340 - business. We still have to focus on revenue, and 00:07:32.340 --> 00:07:35.090 - sometimes things may have to move a little bit faster than 00:07:35.090 --> 00:07:35.590 - others so. 00:07:37.140 --> 00:07:40.070 - Does that all make sense? 00:07:41.520 --> 00:07:47.986 - Yep. Sweet. All is well. Um, measures of 00:07:47.986 --> 00:07:52.232 - success. The architecture review is going to be measured on the 00:07:52.232 --> 00:07:55.320 - following things. Once the project kicks off, so. 00:07:56.640 --> 00:07:59.410 - Each user story should have should be bulleted out into 00:07:59.410 --> 00:08:02.457 - rough task that can be refined in the work breakdown structure 00:08:02.457 --> 00:08:03.565 - meetings and receive proper 00:08:03.565 --> 00:08:08.528 - estimates. Um? Any development risk need to be called out under 00:08:08.528 --> 00:08:11.300 - each user. Stories to those can be addressed in the work 00:08:11.300 --> 00:08:13.568 - Breakdown Structure meeting or with the client after the 00:08:13.568 --> 00:08:16.995 - architecture review. Uh, the wording of each broken down 00:08:16.995 --> 00:08:19.830 - requirements should be easily understandable by a newer junior 00:08:19.830 --> 00:08:23.420 - developer. Um? So if. 00:08:24.610 --> 00:08:27.770 - Kyle can't understand it, and the PM can't understand it. 00:08:27.770 --> 00:08:28.718 - It's probably not. 00:08:29.930 --> 00:08:32.702 - Written where it needs to be written. So just keep that in 00:08:32.702 --> 00:08:35.012 - mind. So if you guys don't understand what the developments 00:08:35.012 --> 00:08:37.553 - going to be, that's probably written at a 2 technical level. 00:08:38.390 --> 00:08:41.415 - Hum, that should also help with you guys translating what has 00:08:41.415 --> 00:08:44.165 - happening, what is happening to your clients at the end. 00:08:44.810 --> 00:08:47.816 - Um, specifics on any task. Relevant documentation should be 00:08:47.816 --> 00:08:51.490 - linked with each of the user stories and features that we're 00:08:51.490 --> 00:08:55.263 - talking about. So that would be things like if we know there's a 00:08:55.263 --> 00:08:58.059 - new cleaner article on how to do something specific that we make. 00:08:58.059 --> 00:09:00.855 - Sure you get that documented so that there's less back and forth 00:09:00.855 --> 00:09:04.673 - going into development. Uh, and then ultimately, once the work 00:09:04.673 --> 00:09:07.724 - Breakdown Structure is done after this meeting, Kyle will 00:09:07.724 --> 00:09:11.792 - facilitate the import of all of the task and user stories with 00:09:11.792 --> 00:09:12.809 - the necessary detail. 00:09:13.370 --> 00:09:17.275 - Um, at least that's our hope and understanding of what we're 00:09:17.275 --> 00:09:21.771 - expecting. So with that said, any questions, comments, 00:09:21.771 --> 00:09:24.640 - concerns. Feedback to the process or anything that's 00:09:24.640 --> 00:09:27.240 - not in alignment with what the rest of the team 00:09:27.240 --> 00:09:28.020 - discussed last Friday. 00:09:30.610 --> 00:09:31.270 - Looks good. 00:09:33.420 --> 00:09:33.990 - Good. 00:09:36.000 --> 00:09:37.460 - Sweet.