{"id":176,"date":"2017-01-12T02:03:01","date_gmt":"2017-01-12T07:03:01","guid":{"rendered":"http:\/\/me.sites.mtu.edu\/meemscd\/?p=176"},"modified":"2022-10-09T17:31:57","modified_gmt":"2022-10-09T21:31:57","slug":"dg-pud-project-overview","status":"publish","type":"post","link":"https:\/\/me.sites.mtu.edu\/meemscd\/dg-pud-project-overview\/","title":{"rendered":"PUD Section 1 \u2014 Project Overview"},"content":{"rendered":"<p>This section should be no more than one (1) page in the format provided and including one graphic (NOT counting the stakeholder table if it is more than 5 rows; this is rare, but sometimes a well-thought-out table is longer than that).<\/p>\n<h2>1\u00a0\u00a0\u00a0\u00a0 Paragraph 1<\/h2>\n<p>This first paragraph will be written before the executive summary is written.\u00a0 However, given the content expected for the first paragraph of the executive summary, there is a risk that this paragraph could be very similar to it.\u00a0 This is often a potential pitfall in documents\u00a0\u2014 similarity in the executive summary and an introduction section of the main document.\u00a0 What is also common, and expected by the audience, is that the author has taken the time to <strong><em>not<\/em><\/strong> verbatim copy and paste from one to the other.\u00a0 They will often be read in immediate sequence.\u00a0 Reading the exact same thing again here after reading it in the executive summary would be, as you might imagine, pretty annoying.\u00a0 Don\u2019t do that to your audience.\u00a0 Don\u2019t do that to yourselves; that is, putting your audience in a less-than-favorable frame of mind at the outset.\u00a0 You want to put your best foot forward here (along with the executive summary), not set the stage with annoyance through laziness.<\/p>\n<p>As such, consider this first paragraph to include one sentence (per item) covering each of the following numbered items in the stated order:<\/p>\n<ol>\n<li>Identify the problem domain including reference to a <strong><em>relevant<\/em><\/strong> graphic, annotated to focus the reader\u2019s attention to the few important elements in the graphic. To help you place graphics in <em>Google Docs<\/em> with captions that remain attached, a link to a source having a figure+caption placeholder, a table+caption placeholder, and instructions for their use is linked via the comment on the cover page along with the link to this guidance.<\/li>\n<li><span style=\"font-size: 1rem\">Describe the \u201cpain\u201d or \u201cgain.\u201d You will expand upon this in the next subsections.<\/span><\/li>\n<li>Identify your customer and the general nature, or general idea, of the solution they are seeking.<\/li>\n<li>Identify the end-user(s) and how they will benefit from the solution.<\/li>\n<li>Identify your team by listing names of student members, your Primary Advisor, and your customer technical contact.<\/li>\n<\/ol>\n<p>Select \u201cSTART HERE-OVERVIEW1\u201d and begin typing.<\/p>\n<h2>2\u00a0\u00a0\u00a0\u00a0 Stakeholder List<\/h2>\n<p>After the first paragraph, the template provides a sentence \u201cThe project stakeholders are summarized as follows\u201d after which is a formatted two-column list.\u00a0 Keep the sentence as is then fill in the list.\u00a0 The first row is your customer.\u00a0 Provide a concise reason for their inclusion, that is, their \u201cinterest or concern\u201d in the project and its outcome.\u00a0 For each stakeholder, the \u201creason\u201d is not what they do, or their responsibilities; <strong>it is a description of why this matters to that individual or organization<\/strong>, how they will be affected by the outcome of the project.\u00a0 The final row is for \u201cyour business\u201d, that is, the ME-EM SCD Program.\u00a0 That has been entered for you.\u00a0 <strong>This must be the last row; other stakeholders are always higher priority<\/strong>, but still it is important to recognize \u201cyour business\u201d does have an interest and concern in the outcome of the project.<\/p>\n<p>The rows in between your customer and your business must include (second to your customer) end-user(s).\u00a0 If your customer has helped you identify more than one end-user (class), include them all.\u00a0 If not, don\u2019t; that is, don\u2019t make things up.\u00a0 But there is always at least one end-user (class).<\/p>\n<p>Beyond obvious end-users, this becomes an important thinking exercise to get you realizing this project is much more about others than yourselves, and who those others are and why it is important to them.\u00a0 There is likely one or more other personas\/parties significantly affected and, thus, having an interest or concern in the outcome of the project; note that they may not even be aware of the project.\u00a0 Be thoughtful; this is neither a hoop to jump through nor a place to write fluff.\u00a0 Recall from the book, there are various stakeholders, such as but not limited to those who manufacture, maintain, repair, and sell the product or process.<\/p>\n<p>Space has been provided for one stakeholder between your customer and the SCD Program.\u00a0 If you need more rows (and you generally will), select <strong>one of the middle rows <em>(not the title row, first row, or last row!)<\/em><\/strong> by clicking just to the left of the left column at that row, right-click, and select \u2018Insert\u00a0\u00a0\u00a0\u25ba\u2019, then \u2018Insert Rows Above\u2019 or \u2018Insert Rows Below\u2019.\u00a0 By following these instructions you will preserve the provided formatting.\u00a0 <strong><em>Finally<\/em><\/strong>, while you as individuals are indeed stakeholders, and\/or is your team as a combination of you as individuals, this is not a place to state that.\u00a0 <strong>The focus here is on others than the team and its members.<\/strong><\/p>\n<h2><a id=\"Paragraph2\"><\/a>3\u00a0\u00a0\u00a0\u00a0 Paragraph 2<\/h2>\n<p>Conclude this section with the two <strong><em>project<\/em><\/strong> constraints that are common to all projects, and the big-picture describing what defines success.\u00a0 Those two constraints are time and money.\u00a0 Thus, begin the paragraph with a single sentence stating (1) by when the project must be completed and (2) the monetary budget allocated.\u00a0 Follow that with how you define success at (1) the end of the first term and (2) at the end of the project; one sentence for each of the noted items.\u00a0 This should be one short focused paragraph of three sentences. \u00a0Select \u201cSTART HERE-OVERVIEW2\u201d and begin typing.<\/p>\n<p><strong>Give \u201csuccess\u201d some solid thought\u00a0\u2014<\/strong> <em>great<\/em>, well-thought-out success statements, versus so-so or even simply <em>good<\/em> success statements, goes a long way to establishing, from the start, (1) your credibility and (2) others\u2019 level of confidence in you.<\/p>\n<p>In regard to articulating it in written (or spoken) words, try to find a way to state it without explicitly using the word \u201cdefined.\u201d\u00a0 That is, avoid writing \u201cSuccess at the end of term-I is defined as\u2026\u201d\u00a0 Not only try to avoid the explicit use of the word \u201cdefine,\u201d but also try to frame it <strong><em>not<\/em><\/strong> in a status of your work, but in what you will have accomplished or will do\/execute.\u00a0 Use bold, definitive words\/phrases, not weak ones like \u201cwe wish to\u201d or \u201chope to.\u201d\u00a0\u00a0 Rather, \u201cwe will&#8230;\u201d\u00a0 For example, \u201cAt the end of Term-I we will\u2026\u201d then state the action like \u201cdeliver\u201d or the accomplishment like \u201chave completed.\u201d\u00a0 Go ahead here and use first person.\u00a0 First person should be used sparingly, and that actually makes it more powerful when used in a place like this.\u00a0 \u201cBy the end of the project we will deliver a tested, functioning prototype and all supporting documentation\u201d is way better than \u201cBy the end of the project a prototype should be complete along with a final report.\u201d\u00a0 There are differences both in person (first versus third) and voice (active versus passive) and definitiveness (will versus should).\u00a0 <strong>Note that this all applies to paragraph 5 of the Executive Summary when you get to writing that.<\/strong><\/p>\n<table>\n<tbody>\n<tr>\n<td>\u00a9 2017, William J. Endres<\/td>\n<td style=\"text-align: right\">Updated January 08, 2022<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"excerpt":{"rendered":"<p>This section should be no more than one (1) page in the format provided and including one graphic (NOT counting the stakeholder table if it is more than 5 rows; this is rare, but sometimes a well-thought-out table is longer than that). 1\u00a0\u00a0\u00a0\u00a0 Paragraph 1 This first paragraph will be written before the executive summary [&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,3,7],"tags":[],"_links":{"self":[{"href":"https:\/\/me.sites.mtu.edu\/meemscd\/wp-json\/wp\/v2\/posts\/176"}],"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=176"}],"version-history":[{"count":25,"href":"https:\/\/me.sites.mtu.edu\/meemscd\/wp-json\/wp\/v2\/posts\/176\/revisions"}],"predecessor-version":[{"id":2760,"href":"https:\/\/me.sites.mtu.edu\/meemscd\/wp-json\/wp\/v2\/posts\/176\/revisions\/2760"}],"wp:attachment":[{"href":"https:\/\/me.sites.mtu.edu\/meemscd\/wp-json\/wp\/v2\/media?parent=176"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/me.sites.mtu.edu\/meemscd\/wp-json\/wp\/v2\/categories?post=176"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/me.sites.mtu.edu\/meemscd\/wp-json\/wp\/v2\/tags?post=176"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}