{"id":7,"date":"2021-10-05T00:20:55","date_gmt":"2021-10-05T00:20:55","guid":{"rendered":"https:\/\/blogs.oregonstate.edu\/pichettl\/?p=7"},"modified":"2021-10-05T00:20:56","modified_gmt":"2021-10-05T00:20:56","slug":"development-workflow","status":"publish","type":"post","link":"https:\/\/blogs.oregonstate.edu\/pichettl\/2021\/10\/05\/development-workflow\/","title":{"rendered":"Development Workflow"},"content":{"rendered":"\n<p>In the beginning of the project, everyone will be working together to create deliverables that fall under the following categories:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li><strong>Minor<\/strong>: A task that should take less than 2 hours.<\/li><li><strong>Major<\/strong>: A task that should take less than 8 hours.<\/li><li><strong>Epic<\/strong>: A task that should take less than 40 hours.<\/li><\/ul>\n\n\n\n<p>In addition to this, these tasks should have tags added to them. Tags will be more solidly established during this beginning-process, but some foundational ones are:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>Progress Halted<\/li><li>To-Do<\/li><li>In-Progress<\/li><li>Completed<\/li><\/ul>\n\n\n\n<p>Lastly, tasks should have categories. Categories will exist depending upon if someone exists in the team to support a particular category (if there aren&#8217;t any website designers, there&#8217;s no need for that category). Here are what they may look like:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>Back-end<\/li><li>Front-end<\/li><li>Design<\/li><li>SA<\/li><\/ul>\n\n\n\n<p><\/p>\n\n\n\n<p>An example ticket, visible on Notion, may look like:<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"651\" src=\"https:\/\/osu-wams-blogs-uploads.s3.amazonaws.com\/blogs.dir\/4682\/files\/2021\/10\/Screenshot-2021-10-04-171234-1024x651.png\" alt=\"\" class=\"wp-image-8\" srcset=\"https:\/\/osu-wams-blogs-uploads.s3.amazonaws.com\/blogs.dir\/4682\/files\/2021\/10\/Screenshot-2021-10-04-171234-1024x651.png 1024w, https:\/\/osu-wams-blogs-uploads.s3.amazonaws.com\/blogs.dir\/4682\/files\/2021\/10\/Screenshot-2021-10-04-171234-300x191.png 300w, https:\/\/osu-wams-blogs-uploads.s3.amazonaws.com\/blogs.dir\/4682\/files\/2021\/10\/Screenshot-2021-10-04-171234-768x488.png 768w, https:\/\/osu-wams-blogs-uploads.s3.amazonaws.com\/blogs.dir\/4682\/files\/2021\/10\/Screenshot-2021-10-04-171234.png 1228w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p><\/p>\n\n\n\n<p>You can in the ticket title: there&#8217;s some information regarding what should be done, and there&#8217;s the ticket-id. Since this is a style-based ticket, this would be created by a website designer (if we get one), or by a front-end developer. You assign yourself tickets as you can, but by the end of the project, the development effort should be evenly spread. This identification is necessary, even if it&#8217;s not created yet. If you take on this ticket, but don&#8217;t want to start development immediately, copy the ticket id and paste it in as a comment where it would be created in the project. This is critical for speeding up development and issue-fixing.<\/p>\n\n\n\n<p><\/p>\n\n\n\n<p><strong>There is a ticket-id naming scheme<\/strong>. It goes as follows (and must be followed): [yourInitials-functionOrElementName:filename]. I chose [lp-div.resourceWrapper:resource.css], as:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>lp: my initials<\/li><li>-div: the element name<\/li><li>.resourceWrapper: optional additional information about the function or element<\/li><li>:resource.css: the name of the file. If there are multiple files this needs to be done for, or multiple elements, then use a semi-colon. For example: [lp-p;span;a.animatedUnderline:resource.css;survey.css]<\/li><\/ul>\n","protected":false},"excerpt":{"rendered":"<p>In the beginning of the project, everyone will be working together to create deliverables that fall under the following categories: Minor: A task that should take less than 2 hours. Major: A task that should take less than 8 hours. Epic: A task that should take less than 40 hours. In addition to this, these &hellip; <a href=\"https:\/\/blogs.oregonstate.edu\/pichettl\/2021\/10\/05\/development-workflow\/\" class=\"more-link\">Continue reading <span class=\"screen-reader-text\">Development Workflow<\/span><\/a><\/p>\n","protected":false},"author":11546,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-7","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/blogs.oregonstate.edu\/pichettl\/wp-json\/wp\/v2\/posts\/7","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.oregonstate.edu\/pichettl\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.oregonstate.edu\/pichettl\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/pichettl\/wp-json\/wp\/v2\/users\/11546"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/pichettl\/wp-json\/wp\/v2\/comments?post=7"}],"version-history":[{"count":1,"href":"https:\/\/blogs.oregonstate.edu\/pichettl\/wp-json\/wp\/v2\/posts\/7\/revisions"}],"predecessor-version":[{"id":9,"href":"https:\/\/blogs.oregonstate.edu\/pichettl\/wp-json\/wp\/v2\/posts\/7\/revisions\/9"}],"wp:attachment":[{"href":"https:\/\/blogs.oregonstate.edu\/pichettl\/wp-json\/wp\/v2\/media?parent=7"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/pichettl\/wp-json\/wp\/v2\/categories?post=7"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/pichettl\/wp-json\/wp\/v2\/tags?post=7"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}