Overview of Dependencies

Let this overview of requirements and/or dependencies guide you on the timeline for each task's completion, their potential barriers, and which ones to expect or request for updates from first.

Since everything is intricately tied together on our platform, this overview should provide a deeper understanding of how certain tasks depend on other tasks in order to be published, done or completed.

COURSE dependencies upon going live:

• Content must be ready for users

CATALOG PAGE update:

• Product (must be published)

PRODUCT dependencies upon going live:

• Sales Page (must be published - custom field association needed)

• Course (must be published - Woocommerce course product association needed)

"ADD TO CART" link dependencies:

• Product (must be published)

PRODUCT "ADD-ONS" OR CHECKOUT RECOMMENDATION requirements:

• Specifications of 2 (or more) products: X product(s) being purchased to recommend add-on Y product(s), and is it vice versa or just one way?

• Both Products must be published (X and Y)

SALES PAGE / sales page link dependencies:

• Course (screenshots needed from the course in order to complete sales page content)

• Product (must be published - page will not display a Purchase button if product custom field association is not set)

CERTIFICATION INFORMATION PAGE upon going live:

• Content (text & images) must be updated and relevant to the certification

• Sales Pages (must be published for permalink)

SAMPLE EXAM PAGE dependencies upon going live:

• LMS Sample Exam (must be published)

• Sales Page : Practice Exams (must be published for button permalink to be working)

FORUM requirements:

• Course - Practice Exams (must be published, for course association)

SITE MENU changes:

• Certification Information page (must be published)

HOMEPAGE updates (footer links & course grid):

• Sales Pages (must be published)

• Catalog page (must already be updated & contain the products, for course grid to redirect correctly)

IMPORTANT NOTE

If any changes to this process is made (e.g. replacing a checkout button with a "coming soon" label to publish a page earlier than its dependency), please document these tasks as soon as assigning these tasks, in order to accurately keep tabs on which pages we need to go back to later to update as soon as their dependencies go live.

HOW TO GET ANY DEVELOPER-DEPENDENT TASK STARTED

Please contact the team's scrum master, Eddie, to have your tasks added to our Product Backlog Trello board to be placed in queue and up for consideration for the next sprint(s) to come.