SpringboardThis topic is related to Springboard. | Form Builder | SMB DAO 1.4 This feature was updated in SMB DAO 1.4.
Here is a high level overview of the steps required for creating a base standard Springboard Implementation.
This topic covers the work required to build a Base Springboard implementation. It outlines the appropriate time to implement significant departures from the Base Springboard and references other related resources and documents throughout.
This page is intended for all project team members:
The following steps are commonly undertaken when creating a new Springboard implementation:
Team reviews project progress – goal of agreeing that Base Springboard implementation is complete
| Item | Description |
|---|---|
|
Who |
All resources. |
|
What |
Review Springboard Getting Started Guide. |
|
Why |
Everyone resources should start with understanding what the Springboard product is. The Getting Started Guide will give an overview of what Springboard is and the components it consists of. |
|
Where |
See Springboard overview. |
Team reviews project progress – goal of agreeing that Base Springboard implementation is complete
| Item | Description |
|---|---|
|
Who |
Project Manager, Business Analyst, Solution Architect, Technical Lead, Developers. |
|
What |
Review Customization Specification documents. |
|
Why |
The Customization Specification documents show what is available for customization in a Base Springboard project. |
|
Where |
|
| Item | Description |
|---|---|
|
Who |
Solution Architect, Technical Lead, Developers. |
|
What |
Review Developer Setup Guide. |
|
Why |
The Customization Specification documents show what is available for customization in a Base Springboard project. |
|
Where |
See link for Developer Setup Guide. |
| Item | Description |
|---|---|
|
Who |
Project Manager, Business Analyst. |
|
What |
Provide clients with a copy of Customization Specification documents to be filled by client. |
|
Why |
These documents must be filled to complete a Base Springboard implementation, the filled documents must be attached to certain stories in a later step in this guide. |
| Item | Description |
|---|---|
|
Who |
All Resources. |
|
What |
Review Base Springboard Sprints. |
|
Why |
The work that must be done to complete a Base Springboard implementation is covered in a pre-defined backlog. |
|
Where |
See backlog below. |
| Item | Description |
|---|---|
|
Who |
Project Manager, Business Analyst. |
|
What |
Gather and review Client’s reporting requirements. |
|
Why |
Set expectations and begin understanding the client’s reporting needs. |
| 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, include Springboard team if necessary. |
| 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 Customization Specification Docs from Client. |
|
Why |
Prior to starting development, review the Customization Specification documents provided by the client and add the appropriate documents to their associated tasks see Sprint 1 below). |
| Item | Description |
|---|---|
|
Who |
All Resources. |
|
What |
Kickoff Sprint. |
|
Why |
Start the project! |
Client Services are provided with a standard Jira sprint backlog to follow for each Springboard implementation.
Next, learn about SMB DAO sprint backlog.