SpringboardThis topic is related to Springboard. | Form Builder | Retail DAO 4.0 This feature was updated in Retail DAO 4.0.
Here is a high level overview of the steps required for creating a Standard Springboard Implementation.
This topic covers the work required to build a Standard Springboard implementation. It outlines the appropriate time to implement significant departures from the Standard Springboard and references other related resources and documents throughout.
This document is intended for all project team members:
The following steps are commonly undertaken when creating a new Springboard implementation:
| Item | Description |
|---|---|
|
Who |
All resources. |
|
What |
Review Springboard Getting Started Guide. Resources should start with understanding Springboard and its components. |
|
Why |
Getting Started Guide will give an overview of Springboard and its components. |
|
Where |
See Springboard overview. |
| Item | Description |
|---|---|
|
Who |
Project Manager, Business Analyst, Solution Architect, Technical Lead, Developers. |
|
What |
Review Specification documents. |
|
Why |
The Specification documents show what is available for configuration and customization in a Standard Springboard project. |
|
Where |
|
| Item | Description |
|---|---|
|
Who |
Solution Architect, Technical Lead, Developers. |
|
What |
Review Developer Setup Guide. |
|
Why |
The Specification documents show what is available for configuration and customization in a Standard Springboard project. |
|
Where |
Available from your implementation team. |
| Item | Description |
|---|---|
|
Who |
Project Manager, Business Analyst. |
|
What |
Provide clients with a copy of the Specification documents to be completed by the client. |
|
Why |
These documents must be completed for any Springboard implementation for the implementation team to configure Springboard. |
|
Where |
Available from your implementation team. |
| Item | Description |
|---|---|
|
Who |
All Resources. |
|
What |
Review Standard Springboard Sprints. |
|
Why |
The work that must be done to complete a Standard Springboard implementation is covered in a pre-defined backlog. |
|
Where |
Available from your implementation team. |
| Item | Description |
|---|---|
|
Who |
Project Manager, Business Analyst. |
|
What |
Gather and review Client’s reporting requirements. |
|
Why |
Set expectations and begin understanding the reporting needs. |
| Where | Available from your implementation team. |
| Item | Description |
|---|---|
|
Who |
Project Manager, Business Analyst, Solution Architect, Springboard Team (if necessary). |
|
What |
Review client’s use case for gaps. |
|
Why |
Review the client’s complete use case with a focus on finding any missed functionality or gaps. |
| Item | Description |
|---|---|
|
Who |
Solution Architect, Technical Lead, Developers, QA Team. |
|
What |
Agree on development process. |
|
Why |
Prior to starting development, the team should agree on the process and workflow for making changes to the Maestro and Journey Manager projects. |
| Item | Description |
|---|---|
|
Who |
All Resources. |
|
What |
Review Specification documents from client. |
|
Why |
Prior to starting development, review the Specification documents provided by the client and add the appropriate documents to their associated tasks. |
Next, learn about standard Springboard sprint backlog.