{"id":4764,"date":"2016-03-19T22:35:38","date_gmt":"2016-03-19T22:35:38","guid":{"rendered":"https:\/\/www.process.st\/templates\/scrum-project-management\/"},"modified":"2024-02-28T16:42:47","modified_gmt":"2024-02-28T16:42:47","slug":"scrum-project-management","status":"publish","type":"post","link":"https:\/\/www.process.st\/templates\/scrum-project-management\/","title":{"rendered":"Scrum Project Management"},"content":{"rendered":"<section id=\"introduction\">\n<h2> Introduction <\/h2>\n<div class=\"image-content\">\n<figure>\n   <a href=\"https:\/\/www.process.st\/templates\/wp-content\/uploads\/2024\/02\/oCNzSZRz4sDIVnISOZVBhQ.png\" alt=\"Introduction\" target=\"_blank\" rel=\"noopener\"> <img decoding=\"async\" loading=\"lazy\" src=\"https:\/\/www.process.st\/templates\/wp-content\/uploads\/2024\/02\/oCNzSZRz4sDIVnISOZVBhQ.png\" \/> <\/a><br \/>\n  <\/figure>\n<\/p><\/div>\n<div class=\"text-content\">\n<p>Although practices vary from company to company, having a regular process to follow during your scrum project management is crucial.<\/p>\n<p>The list of potential errors when not following set and recorded workflows is insane; even the <a href=\"http:\/\/arstechnica.com\/security\/2014\/11\/potentially-catastrophic-bug-bites-all-versions-of-windows-patch-now\/\" target=\"_blank\" rel=\"nofollow noopener\">big guys<\/a> sometimes get caught with their pants down after something in development goes awry.<\/p>\n<p>That's why we here at <a href=\"https:\/\/www.process.st\/\" target=\"_blank\" rel=\"nofollow noopener\">Process Street<\/a> have drummed up this scrum project management checklist, read-to-use and ready-to-kick-ass. By running this checklist before each sprint, you can ensure that your development, user story grooming, sprint planning and teasting all go as smooth as butter.<\/p>\n<p>So, what are you waiting for? Let's ace those Agile scrum projects!<\/p>\n<\/p><\/div>\n<\/section>\n<section id=\"presprint\">\n<h2> Pre-Sprint: <\/h2>\n<\/section>\n<section id=\"assess-your-software\">\n<h2> Assess your software <\/h2>\n<div class=\"text-content\">\n<p>You scrum project management is going to kick off before any sprint is actually started - with an <strong>assessment of your software<\/strong>. This does not have to be an exhaustive&nbsp;procedure that practically turns your software inside-out, but instead a series of <strong>thoughts on how to improve<\/strong> the product.<\/p>\n<p><strong>Note these thoughts<\/strong>, along with <strong>basic information<\/strong> <strong>about your software<\/strong>, in the <strong>form fields<\/strong> below for safe keeping.<\/p>\n<\/p><\/div>\n<div class=\"text-field-content form-field-content\">\n<div class=\"form-group\">\n   <label> Scrum Project Manager <\/label><br \/>\n   <input type=\"text\" placeholder=\"Something will be typed here...\" disabled=\"disabled\" class=\"form-control\" \/>\n  <\/div>\n<\/p><\/div>\n<div class=\"text-field-content form-field-content\">\n<div class=\"form-group\">\n   <label> Software Name <\/label><br \/>\n   <input type=\"text\" placeholder=\"Something will be typed here...\" disabled=\"disabled\" class=\"form-control\" \/>\n  <\/div>\n<\/p><\/div>\n<div class=\"text-field-content form-field-content\">\n<div class=\"form-group\">\n   <label> Software Version <\/label><br \/>\n   <input type=\"text\" placeholder=\"Something will be typed here...\" disabled=\"disabled\" class=\"form-control\" \/>\n  <\/div>\n<\/p><\/div>\n<div class=\"textarea-field-content form-field-content\">\n<div class=\"form-group\">\n   <label> Potential Improvements <\/label><br \/>\n   <textarea placeholder=\"Something will be typed here...\" rows=\"3\" disabled=\"disabled\" class=\"form-control\"><\/textarea>\n  <\/div>\n<\/p><\/div>\n<div class=\"text-content\">\n<p>Think of<strong> features<\/strong> which could be improved,<strong> bugs<\/strong> you have noticed, etc, and <strong>jot them all down<\/strong> in your favourite note taking software (we'd recommend <a href=\"https:\/\/workflowy.com\/\" rel=\"nofollow noopener\" target=\"_blank\">Workflowy<\/a> for that little bit more organization&nbsp;in your thoughts) and the above <strong>form fields<\/strong>. Remember, these thoughts do not have to be exhaustive, but go for as much detail as you can easily gather about the topic.<\/p>\n<\/p><\/div>\n<\/section>\n<section id=\"write-up-your-assessments-as-user-stories\">\n<h2> Write up your assessments as user stories <\/h2>\n<div class=\"image-content\">\n<figure>\n   <a href=\"https:\/\/www.process.st\/templates\/wp-content\/uploads\/2024\/02\/matYY_JVbA0UEymiGuVKow.png\" alt=\"Write up your assessments as user stories\" target=\"_blank\" rel=\"noopener\"> <img decoding=\"async\" loading=\"lazy\" src=\"https:\/\/www.process.st\/templates\/wp-content\/uploads\/2024\/02\/matYY_JVbA0UEymiGuVKow.png\" \/> <\/a><br \/>\n  <\/figure>\n<\/p><\/div>\n<div class=\"text-content\">\n<p>Now that you have your<strong> general improvements<\/strong> and<strong> fixes<\/strong> written down, it's time to put them into your project management software as <strong>user stories<\/strong>! <strong>Record<\/strong> the <strong>links<\/strong> to these new user stories and your project management software account in the<strong> form fields<\/strong> below.<\/p>\n<\/p><\/div>\n<div class=\"text-field-content form-field-content\">\n<div class=\"form-group\">\n   <label> Project Management Software Dashboard <\/label><br \/>\n   <input type=\"text\" placeholder=\"Something will be typed here...\" disabled=\"disabled\" class=\"form-control\" \/>\n  <\/div>\n<\/p><\/div>\n<div class=\"text-field-content form-field-content\">\n<div class=\"form-group\">\n   <label> User Story 1 <\/label><br \/>\n   <input type=\"text\" placeholder=\"Something will be typed here...\" disabled=\"disabled\" class=\"form-control\" \/>\n  <\/div>\n<\/p><\/div>\n<div class=\"text-field-content form-field-content\">\n<div class=\"form-group\">\n   <label> User Story 2 <\/label><br \/>\n   <input type=\"text\" placeholder=\"Something will be typed here...\" disabled=\"disabled\" class=\"form-control\" \/>\n  <\/div>\n<\/p><\/div>\n<div class=\"text-field-content form-field-content\">\n<div class=\"form-group\">\n   <label> User Story 3 <\/label><br \/>\n   <input type=\"text\" placeholder=\"Something will be typed here...\" disabled=\"disabled\" class=\"form-control\" \/>\n  <\/div>\n<\/p><\/div>\n<div class=\"text-field-content form-field-content\">\n<div class=\"form-group\">\n   <label> User Story 4 <\/label><br \/>\n   <input type=\"text\" placeholder=\"Something will be typed here...\" disabled=\"disabled\" class=\"form-control\" \/>\n  <\/div>\n<\/p><\/div>\n<div class=\"text-field-content form-field-content\">\n<div class=\"form-group\">\n   <label> User Story 5 <\/label><br \/>\n   <input type=\"text\" placeholder=\"Something will be typed here...\" disabled=\"disabled\" class=\"form-control\" \/>\n  <\/div>\n<\/p><\/div>\n<div class=\"text-content\">\n<p>Don't worry too much about putting them in a standardized format, but try to include all of the necessary information as concisely as possible.<\/p>\n<p>Note that, before writing up any of these issues you should <strong>first check for existing user tickets which cover the topic<\/strong>; it doesn't matter if you have a <em>similar<\/em> user story, just be certain that you're not duplicating a known issue. Also, be sure to<strong> put them into your grooming queue<\/strong>, so that they can be later sorted and assigned correctly.<\/p>\n<\/p><\/div>\n<\/section>\n<section id=\"ensure-that-your-user-stories-being-groomed\">\n<h2> Ensure that your user stories being groomed <\/h2>\n<div class=\"text-content\">\n<p>Whilst you're in your project management software, it is highly advisable that you <strong>check your project's backlog<\/strong> (production queue). If your <strong>user stories are regularly being groomed<\/strong> into a consistent format, then go ahead and check this task off.<\/p>\n<p>If you find that your stories are not being groomed at all or are standardized badly, refer the engineering team to your <strong><a href=\"https:\/\/www.process.st\/templates\/user-story-template\/\" target=\"_blank\" rel=\"nofollow noopener\">user story template<\/a><\/strong>.<\/p>\n<\/p><\/div>\n<\/section>\n<section id=\"check-up-on-your-sprint-planning\">\n<h2> Check up on your sprint planning <\/h2>\n<div class=\"text-content\">\n<p>To follow up on your user stories being groomed, you should also <strong>check that your sprint planning is going smoothly<\/strong> whilst you're in the correct software. This shouldn't be an in-depth analysis, but more of a<strong> quick assessment<\/strong>, after which you need to <strong>note the number of points<\/strong> you expect to tackle and the <strong>start date<\/strong> of your next sprint in the<strong> form fields<\/strong> below.<\/p>\n<\/p><\/div>\n<div class=\"text-field-content form-field-content\">\n<div class=\"form-group\">\n   <label> Target Points To Tackle <\/label><br \/>\n   <input type=\"text\" placeholder=\"Something will be typed here...\" disabled=\"disabled\" class=\"form-control\" \/>\n  <\/div>\n<\/p><\/div>\n<div class=\"date-field-content form-field-content\">\n<div class=\"form-group\">\n   <label> Sprint Start Date <\/label> <\/p>\n<div class=\"date-container\">\n    <button type=\"button\" disabled=\"disabled\" class=\"btn btn-default\"> <i class=\"fa fa-calendar btn-icon\"><\/i> Date will be set here <\/button>\n   <\/div>\n<\/p><\/div>\n<\/p><\/div>\n<div class=\"text-content\">\n<p>Check that a<strong> consistent number of points<\/strong> are being tackled in each sprint, along with each developer getting the same number of points to tackle. This is <strong>vital<\/strong> in your scrum project management, as deviating from these principles will only lead to unrealistic goals and unhappy developers.<\/p>\n<p>Once again, if this is not happening, refer the team to your <strong><a href=\"https:\/\/www.process.st\/templates\/sprint-planning\/\" rel=\"nofollow noopener\" target=\"_blank\">sprint planning template<\/a><\/strong> and enquire as to why this is happening.<\/p>\n<\/p><\/div>\n<\/section>\n<section id=\"during-the-sprint\">\n<h2> During the Sprint: <\/h2>\n<\/section>\n<section id=\"maintain-a-solid-testing-process\">\n<h2> Maintain a solid testing process <\/h2>\n<div class=\"image-content\">\n<figure>\n   <a href=\"https:\/\/www.process.st\/templates\/wp-content\/uploads\/2024\/02\/mbVTkj1hpiWBJ-ZLuEJNjA.png\" alt=\"Maintain a solid testing process\" target=\"_blank\" rel=\"noopener\"> <img decoding=\"async\" loading=\"lazy\" src=\"https:\/\/www.process.st\/templates\/wp-content\/uploads\/2024\/02\/mbVTkj1hpiWBJ-ZLuEJNjA.png\" \/> <\/a><br \/>\n  <\/figure>\n<\/p><\/div>\n<div class=\"text-content\">\n<p>During your regular sprints, it is imperative that <strong>any changes<\/strong> made to your software are <strong>checked and double-checked before being set live<\/strong>. To this end, you must ensure that during the sprint a rock solid <strong>testing process<\/strong> is carried out for each alteration.<\/p>\n<p>If you need a little help in setting up a steady test procedure, we have a handy <strong><a href=\"https:\/\/www.process.st\/templates\/software-testing-tutorial\/\" target=\"_blank\" rel=\"nofollow noopener\">software testing tutorial<\/a><\/strong>&nbsp;to get you going.<\/p>\n<p>Remember that, even if you are not doing these tests yourself, you should be checking that the testing process is carried out for each new piece of code and that the tests are up to scratch.<\/p>\n<\/p><\/div>\n<\/section>\n<section id=\"postsprint\">\n<h2> Post-Sprint: <\/h2>\n<\/section>\n<section id=\"ensure-that-your-issues-are-dealt-with\">\n<h2> Ensure that your issues are dealt with <\/h2>\n<div class=\"text-content\">\n<p>After your sprint has concluded it's time to pick up with your scrum project management once again! The next step is to <strong>check that the issues set out in the last sprint have either been dealt with or broken down<\/strong> into appropriate smaller issues. <strong>Record your progress<\/strong> using the <strong>form fields<\/strong> below.<\/p>\n<\/p><\/div>\n<div class=\"select-field-content form-field-content\">\n<div class=\"form-group\">\n   <label> Were All Issues Dealt With? <\/label><br \/>\n   <select disabled=\"disabled\" class=\"form-control\"><option value=\"An option will be selected here\">An option will be selected here<\/option><\/select>\n  <\/div>\n<\/p><\/div>\n<div class=\"textarea-field-content form-field-content\">\n<div class=\"form-group\">\n   <label> Unsolved Issues <\/label><br \/>\n   <textarea placeholder=\"Something will be typed here...\" rows=\"3\" disabled=\"disabled\" class=\"form-control\"><\/textarea>\n  <\/div>\n<\/p><\/div>\n<div class=\"textarea-field-content form-field-content\">\n<div class=\"form-group\">\n   <label> Responsible Developers <\/label><br \/>\n   <textarea placeholder=\"Something will be typed here...\" rows=\"3\" disabled=\"disabled\" class=\"form-control\"><\/textarea>\n  <\/div>\n<\/p><\/div>\n<div class=\"text-content\">\n<p>Go back to your<strong> sprint board<\/strong> and <strong>check<\/strong> that <strong>each assigned user story<\/strong> has been completed, or at least documented and partially completed (eg, if unforeseen difficulties arose).<strong> If a project has not been completed, contact the developer<\/strong> and ask for an explanation.<\/p>\n<p>There will always be issues which turn out to be more complicated than first anticipated, and so it's <strong>not always the dev's fault<\/strong> if a user story has not been resolved. However, this is a <strong>good opportunity to monitor the progress<\/strong> <strong>of your developers<\/strong> and pick up on any lax procedures.<\/p>\n<\/p><\/div>\n<\/section>\n<section id=\"double-check-your-softwares-security\">\n<h2> Double check your software's security <\/h2>\n<div class=\"image-content\">\n<figure>\n   <a href=\"https:\/\/www.process.st\/templates\/wp-content\/uploads\/2024\/02\/lkL264AxNBQeu8hwGb9ICA.png\" alt=\"Double check your software's security\" target=\"_blank\" rel=\"noopener\"> <img decoding=\"async\" loading=\"lazy\" src=\"https:\/\/www.process.st\/templates\/wp-content\/uploads\/2024\/02\/lkL264AxNBQeu8hwGb9ICA.png\" \/> <\/a><br \/>\n  <\/figure>\n<\/p><\/div>\n<div class=\"text-content\">\n<p>The final step in your scrum project management is to <strong>check up on your software's security<\/strong>. Whilst this should generally be a separate process which is carried out regularly, security is certainly no laughing matter; check that the process is being followed regularly and is up to scratch.<\/p>\n<p><strong>Monitor your progress<\/strong> with the <strong>sub-checklist<\/strong> below; feel free to <strong>add items<\/strong> to cater to <strong>your requirements<\/strong>!<\/p>\n<\/p><\/div>\n<div class=\"multi-select-content form-field-content\">\n<ul class=\"items\">\n<li class=\"item\">\n<div class=\"step-number-container\">\n<div class=\"step-number\">\n       1\n     <\/div>\n<\/p><\/div>\n<div class=\"step-checkbox-container\">\n<div class=\"step-checkbox\"><\/div>\n<\/p><\/div>\n<div class=\"item-name-static\">\n      Any areas which have been affected by the update\n    <\/div>\n<\/li>\n<li class=\"item\">\n<div class=\"step-number-container\">\n<div class=\"step-number\">\n       2\n     <\/div>\n<\/p><\/div>\n<div class=\"step-checkbox-container\">\n<div class=\"step-checkbox\"><\/div>\n<\/p><\/div>\n<div class=\"item-name-static\">\n      Basic security measures, such as user password entry forms\n    <\/div>\n<\/li>\n<li class=\"item\">\n<div class=\"step-number-container\">\n<div class=\"step-number\">\n       3\n     <\/div>\n<\/p><\/div>\n<div class=\"step-checkbox-container\">\n<div class=\"step-checkbox\"><\/div>\n<\/p><\/div>\n<div class=\"item-name-static\">\n      New error messages (ensure that no extra information is being given out)\n    <\/div>\n<\/li>\n<\/ul><\/div>\n<div class=\"text-content\">\n<p>Congratulations! You're <strong>all done<\/strong> with this stint of scrum project management; huzzah! Now it's time to <strong>start the whole thing again in preparation for your next sprint<\/strong> - there's no rest for the wicked, but every completion brings you closer to success!<\/p>\n<\/p><\/div>\n<\/section>\n<section id=\"sources\">\n<h2> Sources: <\/h2>\n<div class=\"text-content\">\n<p><a href=\"https:\/\/twitter.com\/dangoodin001\" target=\"_blank\" rel=\"nofollow noopener\">Dan Goodin<\/a> -&nbsp;<a href=\"http:\/\/arstechnica.com\/security\/2014\/11\/potentially-catastrophic-bug-bites-all-versions-of-windows-patch-now\/\" target=\"_blank\" rel=\"nofollow noopener\">Potentially Catastrophic Bug Bites All Versions of Windows. Patch Now<\/a><\/p>\n<p><a href=\"https:\/\/www.scrumalliance.org\/community\/profile\/rkidambi\" target=\"_blank\" rel=\"nofollow noopener\">Raju K<\/a> -&nbsp;<a href=\"https:\/\/www.scrumalliance.org\/community\/articles\/2014\/march\/the-importance-of-pre-project-sprints\" target=\"_blank\" rel=\"nofollow noopener\">The Importance of Pre-Project Sprints<\/a><\/p>\n<p><a href=\"https:\/\/www.linkedin.com\/in\/ksvikash?trk=pulse-det-athr_prof-art_hdr\" target=\"_blank\" rel=\"nofollow noopener\">Vikash Krumar<\/a> -&nbsp;<a href=\"https:\/\/www.linkedin.com\/pulse\/importance-scrum-project-management-vikash-kumar\" target=\"_blank\" rel=\"nofollow noopener\">Importance of Scrum in Project Management<\/a><\/p>\n<\/p><\/div>\n<\/section>\n<section id=\"relevant-checklists\">\n<h2> Relevant Checklists: <\/h2>\n<div class=\"text-content\">\n<p><a href=\"https:\/\/www.process.st\/templates\/git-workflow\/\" target=\"_blank\" rel=\"nofollow noopener\">Git Workflow<\/a><\/p>\n<p><a href=\"https:\/\/www.process.st\/templates\/user-story-template\/\" target=\"_blank\" rel=\"nofollow noopener\">User Story Template<\/a><\/p>\n<p><a href=\"https:\/\/www.process.st\/templates\/sprint-planning\/\" target=\"_blank\" rel=\"nofollow noopener\">Sprint Planning<\/a><\/p>\n<p><a href=\"https:\/\/www.process.st\/templates\/software-deployment\/\" target=\"_blank\" rel=\"nofollow noopener\">Software Deployment<\/a><\/p>\n<p><a href=\"https:\/\/www.process.st\/templates\/software-testing-tutorial\/\" target=\"_blank\" rel=\"nofollow noopener\">Software Testing Tutorial<\/a><\/p>\n<p><a href=\"https:\/\/www.process.st\/templates\/software-debugging-process\/\" target=\"_blank\" rel=\"nofollow noopener\">Software Debugging Process<\/a><\/p>\n<\/p><\/div>\n<\/section>\n","protected":false},"excerpt":{"rendered":"<p>Introduction Although practices vary from company to company, having a regular process to follow during your scrum project management is crucial. The list of potential errors when not following set and recorded workflows is insane; even the big guys sometimes get caught with their pants down after something in development goes awry. That's why we [&hellip;]<\/p>\n","protected":false},"author":3,"featured_media":4765,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"ep_exclude_from_search":false,"cover_icon_emoji":"","cover_icon_url":"","tasks_count":"13","template_description":"Run this checklist for every sprint you undertake.","template_id":"rOwfs5uiU_KcuqlLPldLyw","task_0":"Introduction","task_slug_0":"introduction","task_1":"Pre-Sprint:","task_slug_1":"presprint","task_2":"Assess your software","task_slug_2":"assess-your-software","task_3":"Write up your assessments as user stories","task_slug_3":"write-up-your-assessments-as-user-stories","task_4":"Ensure that your user stories being groomed","task_slug_4":"ensure-that-your-user-stories-being-groomed","task_5":"Check up on your sprint planning","task_slug_5":"check-up-on-your-sprint-planning","task_6":"During the Sprint:","task_slug_6":"during-the-sprint","task_7":"Maintain a solid testing process","task_slug_7":"maintain-a-solid-testing-process","task_8":"Post-Sprint:","task_slug_8":"postsprint","task_9":"Ensure that your issues are dealt with","task_slug_9":"ensure-that-your-issues-are-dealt-with","task_10":"Double check your software's security","task_slug_10":"double-check-your-softwares-security","task_11":"Sources:","task_slug_11":"sources","task_12":"Relevant Checklists:","task_slug_12":"relevant-checklists","task_13":"","task_slug_13":"","task_14":"","task_slug_14":"","task_15":"","task_slug_15":"","task_16":"","task_slug_16":"","task_17":"","task_slug_17":"","task_18":"","task_slug_18":"","task_19":"","task_slug_19":"","task_20":"","task_slug_20":"","task_21":"","task_slug_21":"","task_22":"","task_slug_22":"","task_23":"","task_slug_23":"","task_24":"","task_slug_24":"","task_25":"","task_slug_25":"","task_26":"","task_slug_26":"","task_27":"","task_slug_27":"","task_28":"","task_slug_28":"","task_29":"","task_slug_29":"","task_30":"","task_slug_30":"","task_31":"","task_slug_31":"","task_32":"","task_slug_32":"","task_33":"","task_slug_33":"","task_34":"","task_slug_34":"","task_35":"","task_slug_35":"","task_36":"","task_slug_36":"","task_37":"","task_slug_37":"","task_38":"","task_slug_38":"","task_39":"","task_slug_39":"","task_40":"","task_slug_40":"","task_41":"","task_slug_41":"","task_42":"","task_slug_42":"","task_43":"","task_slug_43":"","task_44":"","task_slug_44":"","task_45":"","task_slug_45":"","task_46":"","task_slug_46":"","task_47":"","task_slug_47":"","task_48":"","task_slug_48":"","task_49":"","task_slug_49":"","task_50":"","task_slug_50":"","task_51":"","task_slug_51":"","task_52":"","task_slug_52":"","task_53":"","task_slug_53":"","task_54":"","task_slug_54":"","task_55":"","task_slug_55":"","task_56":"","task_slug_56":"","task_57":"","task_slug_57":"","task_58":"","task_slug_58":"","task_59":"","task_slug_59":"","task_60":"","task_slug_60":"","task_61":"","task_slug_61":"","task_62":"","task_slug_62":"","task_63":"","task_slug_63":"","task_64":"","task_slug_64":"","task_65":"","task_slug_65":"","task_66":"","task_slug_66":"","task_67":"","task_slug_67":"","task_68":"","task_slug_68":"","task_69":"","task_slug_69":"","task_70":"","task_slug_70":"","task_71":"","task_slug_71":"","task_72":"","task_slug_72":"","task_73":"","task_slug_73":"","task_74":"","task_slug_74":"","task_75":"","task_slug_75":"","task_76":"","task_slug_76":"","task_77":"","task_slug_77":"","task_78":"","task_slug_78":"","task_79":"","task_slug_79":"","task_80":"","task_slug_80":"","task_81":"","task_slug_81":"","task_82":"","task_slug_82":"","task_83":"","task_slug_83":"","task_84":"","task_slug_84":"","task_85":"","task_slug_85":"","task_86":"","task_slug_86":"","task_87":"","task_slug_87":"","task_88":"","task_slug_88":"","task_89":"","task_slug_89":"","task_90":"","task_slug_90":"","task_91":"","task_slug_91":"","task_92":"","task_slug_92":"","task_93":"","task_slug_93":"","task_94":"","task_slug_94":"","task_95":"","task_slug_95":"","task_96":"","task_slug_96":"","task_97":"","task_slug_97":"","task_98":"","task_slug_98":"","task_99":"","task_slug_99":"","footnotes":""},"categories":[5,7,16,31],"tags":[],"class_list":["post-4764","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-featured","category-miscellaneous","category-quality-assurance","category-software"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/posts\/4764","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/comments?post=4764"}],"version-history":[{"count":0,"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/posts\/4764\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/media\/4765"}],"wp:attachment":[{"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/media?parent=4764"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/categories?post=4764"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/tags?post=4764"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}