{"id":2156,"date":"2017-01-12T08:02:58","date_gmt":"2017-01-12T13:02:58","guid":{"rendered":"http:\/\/me.sites.mtu.edu\/meemscd\/?p=2156"},"modified":"2023-02-11T16:05:53","modified_gmt":"2023-02-11T21:05:53","slug":"dg-ptr-pre-meeting-briefing","status":"publish","type":"post","link":"https:\/\/me.sites.mtu.edu\/meemscd\/dg-ptr-pre-meeting-briefing\/","title":{"rendered":"Prototyping and Testing Review (PTR) \u2014 Pre-meeting Briefing"},"content":{"rendered":"<p>This one sheet serves three purposes:<\/p>\n<ul>\n<li>brief\/quick preparation for your audience prior to the meeting (\u201cpre-meeting briefing\u201d);<\/li>\n<li>a guide for the PTR meeting, for you and your audience members; and<\/li>\n<li>a take-away for your audience.<\/li>\n<\/ul>\n<h2>1\u00a0\u00a0\u00a0\u00a0 Organization and Formatting<\/h2>\n<ul style=\"list-style-type: disc\">\n<li>There are four (4) sections that progress according to the numbers in their respective headings.<\/li>\n<li>There are two layouts from which you can choose based on how you think apportioning the space between sections 2 and 3 works best for you:\n<ol>\n<li>The first goes from top-left <strong>down<\/strong> to bottom-left then <strong>over and up<\/strong> to top-right and <strong>down<\/strong> to bottom-right (top-to-bottom then left-to-right, or \u201cTBLR\u201d).<\/li>\n<li>The second goes from top-left <strong>over<\/strong> to top-right then <strong>back over and down<\/strong> to bottom-left and <strong>over<\/strong> to bottom-right (left-to-right then top-to-bottom, or \u201cLRTB\u201d).<\/li>\n<\/ol>\n<\/li>\n<li>Each section on the sheet has, below its heading, a text field with a prompt for a short sentence to provide context (replace that prompt with yours) followed by a bullet-list starter \u201cXxxxx\u201d.<\/li>\n<li>The top headings (left- and right-columns) are on the respective master layout (named \u201cPMB-TBLR\u201d or \u201cPMB-LRTB\u201d) and should not be moved. The other two headings may be moved up or down (hold the shift key down to maintain vertical alignment) to redistribute space as it better serves you. \u00a0<strong>Do <em>NOT<\/em> change the wording of any of the headings.<\/strong><\/li>\n<li><span style=\"font-size: 1rem\">Remember, like previous (PUR and CSR) PMBs, this is highlights, what will prep your audience before the meeting and that you will use to lead the discussion at the start of the meeting.<\/span><\/li>\n<li>\n<ul style=\"list-style-type: circle\">\n<li>It need not be jam packed; you are allowed\/encouraged to have relevant TAD pages with you to reference for details as needed.<\/li>\n<li>The content should be <strong>graphics-rich with minimal text<\/strong>. Aim for (<strong><em>minimum<\/em><\/strong>) 75% of the space consumed by graphics (with the exception of the next-steps section which will likely, though not necessarily, be mainly text).<\/li>\n<li>But do not try to include all of your graphics relevant to the respective section. Be <strong><em>thoughtfully<\/em><\/strong> selective; you can have select TAD pages to reference as noted, and the graphics on the PMB must be large enough to see any important feature on the graphic.<\/li>\n<li>Think of each of the four sections as a \u201cslide\u201d dominated by graphics with some bullet points to complement the graphics.<\/li>\n<\/ul>\n<\/li>\n<li>Regarding graphics:\n<ul style=\"list-style-type: circle\">\n<li>Graphics include <strong><em>annotated<\/em><\/strong> CAD, illustrations, plots, and photos as well as tables. Yes, annotate plots as needed (often but not all of the time) to point out what is of particular interest.<\/li>\n<li>Graphics used here are copied and pasted from your other docs.<\/li>\n<li>Choose graphical elements of substance, not just present as a token non-textual element that is otherwise useless.<\/li>\n<li>Be sure to have figure and table numbers so your audience can follow you as you talk them through it.<\/li>\n<li><strong>Did you see \u201c<em>annotated<\/em>\u201d above?!<\/strong><\/li>\n<\/ul>\n<\/li>\n<li>Regarding text:\n<ul style=\"list-style-type: circle\">\n<li>The bullet points serve three purposes:\n<ul style=\"list-style-type: square\">\n<li>guidance for your audience, leading them through the storyline and graphics both during the meeting and for <strong><em>quick<\/em><\/strong> pre-meeting preparation,<\/li>\n<li>cues for you during the meeting, reminding you not what specifically to say (use your spoken words for that), but what generally to talk about, and<\/li>\n<li>refreshers for your audience, reminding them afterwards what you talked about and jogging their memory about some of the details of what they heard you say (your spoken words).<\/li>\n<\/ul>\n<\/li>\n<li>These bullet points are short, to-the-point, not copied from your TAD since they are to be very limited and short compared to your more extensive bullet points in the TAD. Each should be no more than a <strong><em>single short<\/em><\/strong> sentence or phrase.<\/li>\n<li>The bullet points, at this stage, should just come to you naturally, like was described for the RPU, that you just know the project work well enough you can just talk about it (i.e., you can just write some bullet points about it).<\/li>\n<li><strong>Again\u2026 more graphics, less text!<\/strong><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h2>2\u00a0\u00a0\u00a0\u00a0 Content Presentation<\/h2>\n<ul style=\"list-style-type: disc\">\n<li>Leading into each bullet-point list should be one short, complete sentence providing context for the list\/section.<\/li>\n<li>There are four areas of your work-product you are covering <strong>(in this order)<\/strong>:\n<ol>\n<li>Problem understanding (and definition in engineering terms; i.e., engineering requirements)<\/li>\n<li>Overall solution concept from a system-level view (largely graphical)<\/li>\n<li>Design details (expressed in terms of functionality and exciting\/cool design features)<\/li>\n<li>Next steps (basically your status on prototyping and testing plans)<\/li>\n<\/ol>\n<\/li>\n<li>Some additional guidance follows:\n<ul style=\"list-style-type: circle\">\n<li>Section 1 is a few key bullet points on what your project is, and perhaps what it isn\u2019t, then defined in engineering terms (your engineering requirements tables).<\/li>\n<li>The meat of this is Section 2, showing one (or more as appropriate) graphical views of your final solution from a system-level viewpoint. Annotate main subsystems or interesting elements of focus (i.e., ones you are particular proud of in how they serve the needs\/function to be met).<\/li>\n<li>Section 3 is <strong><em>not<\/em><\/strong> your function-structure diagram; the FSD is too much detail to be shown\/readable here. And Section 3, at this stage, is <strong><em>not<\/em><\/strong> your main system function table or morph chart.\u00a0 Section 3 should include graphical views zoomed in on function-level <strong><em>details<\/em><\/strong> not as discernable in the wider, zoomed-out view(s) of Section 2. \u00a0Complement the graphics with a few bullet points describing the features of your design (again, some of the things you feel are interesting in how it meets the needs, or even special design decisions related to material or COTS components chosen).\u00a0 Being zoom-in graphics of details, the layout with Section 3 at the top-right is often chosen as this provides more space for Section 3.<\/li>\n<li>Section 4 is <strong><em>not<\/em><\/strong> your verification plan tables; those tables are too much detail to be shown\/readable here.\u00a0 It is a few bullet points on the status of prototyping and plans for testing, the latter being much of your next steps (along with completing the prototyping activities, and <strong>with special emphasis on your (hopefully initiated about now) subsystem\/function-level testing<\/strong> that happens before full system-level testing).\u00a0 This is also the place to note whether or not you think a project title change\/tweak would make sense (or not)\u00a0\u2014 <strong>enter information here for <em>BOTH<\/em> red-background prompts.<\/strong><strong><a href=\"#_ftn1\" name=\"_ftnref1\"><sup>[1]<\/sup><\/a><\/strong><\/li>\n<\/ul>\n<\/li>\n<li>This is not \u201cnew documentation,\u201d it is just a quick compilation of highlights pulled from other places in your documentation <strong>to prep others<\/strong> for the meeting and, furthermore, assist you in leading the meeting before getting into the details of discussion.<\/li>\n<\/ul>\n<h2>3\u00a0\u00a0\u00a0\u00a0 Examples of Great Work<\/h2>\n<h3><a href=\"https:\/\/drive.google.com\/file\/d\/1cZ2QrwCwg6sTjJqFNIpUon6LdrN1DKP9\/view?usp=sharing\">Example 1<\/a><\/h3>\n<h3><a href=\"https:\/\/drive.google.com\/file\/d\/12X8p720Y02TtfZ79yedaI3b_rp2yQIrp\/view?usp=sharing\">Example2<\/a><\/h3>\n<hr \/>\n<p><sup><a href=\"#_ftnref1\" name=\"_ftn1\">[1]<\/a><\/sup>\u00a0 Some projects evolve into something a little different than what we think they will be when we bring them in and get started.\u00a0 To avoid confusion in the broader audience of your FRV and\/or FRP, it may be helpful to adjust the title of some projects to reflect these changes in scope and\/or project\/problem understanding that may have occurred over the course of the project.\u00a0 We are asking now so this can be discussed with your PA this week and as needed at the PTR and a decision made before you begin working on your FRV and\/or FRP content.\u00a0 You will <strong><em><b>NOT<\/b><\/em><\/strong><strong> change<\/strong> your various templates\/documents as this is more a matter of clarity for your broader audiences (FRV and FRP).\u00a0 Any suggested change (or the word \u201cnone\u201d) should be entered in the field after the red-background prompt at the bottom-right corner of the PMB.\u00a0 Also there, you should enter your current customer contact(s) info (which sometimes changes over the course of a project; we need to be sure to send FRP invites to the right people).<\/p>\n<table>\n<tbody>\n<tr>\n<td>\u00a9 2017, William J. Endres<\/td>\n<td style=\"text-align: right\">Updated February 11, 2023<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"excerpt":{"rendered":"<p>This one sheet serves three purposes: brief\/quick preparation for your audience prior to the meeting (\u201cpre-meeting briefing\u201d); a guide for the PTR meeting, for you and your audience members; and a take-away for your audience. 1\u00a0\u00a0\u00a0\u00a0 Organization and Formatting There are four (4) sections that progress according to the numbers in their respective headings. There [&hellip;]<\/p>\n","protected":false},"author":35,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[17,10],"tags":[],"_links":{"self":[{"href":"https:\/\/me.sites.mtu.edu\/meemscd\/wp-json\/wp\/v2\/posts\/2156"}],"collection":[{"href":"https:\/\/me.sites.mtu.edu\/meemscd\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/me.sites.mtu.edu\/meemscd\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/me.sites.mtu.edu\/meemscd\/wp-json\/wp\/v2\/users\/35"}],"replies":[{"embeddable":true,"href":"https:\/\/me.sites.mtu.edu\/meemscd\/wp-json\/wp\/v2\/comments?post=2156"}],"version-history":[{"count":30,"href":"https:\/\/me.sites.mtu.edu\/meemscd\/wp-json\/wp\/v2\/posts\/2156\/revisions"}],"predecessor-version":[{"id":2780,"href":"https:\/\/me.sites.mtu.edu\/meemscd\/wp-json\/wp\/v2\/posts\/2156\/revisions\/2780"}],"wp:attachment":[{"href":"https:\/\/me.sites.mtu.edu\/meemscd\/wp-json\/wp\/v2\/media?parent=2156"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/me.sites.mtu.edu\/meemscd\/wp-json\/wp\/v2\/categories?post=2156"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/me.sites.mtu.edu\/meemscd\/wp-json\/wp\/v2\/tags?post=2156"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}