Roadmap Objectives

Program Increment XX Objectives

If your team plans in multi-month increments composed of multiple sprints, this is the spot to describe the overall objectives. Collectively, what does the organization plan to build or achieve during the next three months?

Desktop application

1. Objective 1

Mobile Application

2. Objective 2

Goals

This area lists the high level features or objectives. As each goal is met, the list is updated. If the team has identified stretch goals they can be listed here as well.  

Background

This is the overall objective of the entire initiative. It is the “north star” that all underlying work should support.

Sample:  Re-platform our core business’ operations, in a fiscally responsible manner (on time, on budget, fulfilling our commitments), with a solution that provides all necessary core functionality and provides a scalable modern platform that empowers the business to bring the seller and their customer together in the simplest possible way.​

Close-Out

In this section, summarize what was accomplished in the previous multi-sprint increment.  

Sample text:  Last program increment, we succeeded in launching the mobile application.

Alt Sample text:

• launched mobile app

        Sprint 1        

Accomplished

What did we accomplish overall this sprint?

This should be a tweet-sized synopsis, and can be a bulleted list. Remember, this is for you and your team to work from.  

CIKC Hub

Agency App

Who?

Who benefits from the work we did this sprint? Who was this for?

3. Customer Support Team
4. B2B Sellers

What?

What is changing? The example below assumes that you are moving from the “old” way of doing things to a “new” way of doing things.  How do they compare? 

Why?

Why is the work we did this sprint important? Who cares? Why do they care?

How?

Basic procedures for how to accomplish each task that was bult out.

In the example below, we see basic navigation steps for a user to choose a check as the payment method on a recurring payment schedule.

Use “check” Payment Method on a Payment Schedule

Navigate to Payment method

1. Choose check

1. Result: Payment schedule status = active (no stripe)

2. Create ps (payment schedule) line

1. Designation
2. Recurring amount

3. Save and close

1. Result:

1. no submit to stripe - record is saved

Auto update amount when payment schedule frequency changes

NOTE: this is pending Paritta review & Stripe integration

New fields are updated based as appropriate based on each scenario below:

5. If payment frequency is updated on payment schedule
6. Add new payment schedule line
7. Update payment schedule line
8. Deactivate payment schedule line

When?

What release is this functionality scheduled for?

When will it pass each “gate” - QA, User acceptance or Training, Production?  List it here if known, or link to the schedule where this information will be developed.

User Story List

Please find the recording to the session here: [Zoom link]

If you recorded the sprint demo, you can use clips to publish for users to review later.

Alternatively, use the “How” to build a how-to training video later.

Enter the specific requirements or user stories addressed here, along with hyperlinks to the location of the ticket in JIRA, Azure DevOps, or other ticketing system for easy access.

Use the time stamp to direct the viewer to to the relevant part of the sprint demo recording.