1. Rapid Launch Workshop
©CC BY-SA

2. Strengths
Identify the items from the Rapid Launch Workshop that show where your company already excels.
Examples;
C-Level support and active engagement
API teams all reporting to same manager
Experienced product managers
Clearly defined scope for first launch
©CC BY-SA

3. Opportunities
Identify the items from the Rapid Launch Workshop that show where your company may be able to take advantage of an opportunity to go faster.
Examples:
Highly motivated product manager, Diane, who should drive first launch
Announcement of competitor for new mobile capabilities will help drive urgency for us to meet or pass them
Leverage our business impact to get more funding necessary to bring on two full time developers
Budget cycle approaching, so we should strategically fund the platform for three years
©CC BY-SA

4. Challenges <<add data>> Recommendation; TBD
Identify the items from the Rapid Launch Workshop that show where the core API team has challenges that need exec guidance and support. Include recommendations on how to address and discuss with your exec sponsor.
Examples;
Matrixed delivery team
High-level execution plan shows we will deliver past our intended go-live date. Need to cut scope
Product manager is not providing enough detail to deliver solutions
Existing governance model will add four weeks to our schedule
Getting past a consensus approach to empowered team members
©CC BY-SA

5. Concerns <<add data>> Recommendation TBD
Identify the items from the Rapid Launch Workshop that show where the core API team has concerns that need exec guidance and support. Include recommendations on how to address and discuss with your exec sponsor.
Examples:
Identified API team scrum master has no experience
Product owner / manager has only committed to working with us two days a week.
The process of hiring an architect for our team may take four weeks
We haven’t invested in training necessary for the team to use the platform efficiently
©CC BY-SA

6. First launch scope <<insert data>>
Key items to be delivered in 2 – 3 sprints.
©CC BY-SA

7. Success metrics <<insert data>>
Remember to include specific dates and metrics.
©CC BY-SA

8. Strategy alignment Corporate strategy TBD Digital strategy
Wording doesn’t need to be exact, but key concepts and alignment are needed.
©CC BY-SA

9. Enterprise architecture
Diagram showing where API management platform resides in overall architecture and other key systems needed for first launch.
©CC BY-SA

10. Security
Diagram and any context for security model to be implemented in the first launch.
©CC BY-SA

11. Implementation process
Provide implementation process and any other information to align with the exec sponsor.
©CC BY-SA

12. Implementation Tools User stories - Defect / issue mgmt -
Document management –
Source code management -
Test script builds –
Sanity / unit test –
Automated regression testing –
PEN testing –
Performance & load testing -
Build tools –
Continuous integration / continuous deployment -
Code analysis and coverage -
Monitoring –
Logging –
Companies should have tools for all these areas for CI/CD.
©CC BY-SA

13. Dependencies
Key items to take into consideration for first launch. This is input to the execution plan.
©CC BY-SA

14. Stakeholders
Internal, external (customers, partners, consulting partners, etc)
Compliance departments engaged?
Do you have stakeholders looking for this to fail?
Consider putting support rating next to each role / department.
Development of a communication plan with progress to goals
©CC BY-SA

15. API team
Executive sponsor - API evangelist – Product owner(s) – Principal architect - Developers – Test lead - Scrum master -
Other matrixed roles
Network / operations
Developer evangelist
Partner liaison
Release manager
©CC BY-SA

16. Guiding principles
Provide a list of principles the tactical team should reference when building the solution.
Examples Include;
Speed is more important than getting perfect with first iteration
Reusable assets
External consumption
App developer-centric
Build complexity over time
©CC BY-SA

17. Execution plan
High-level view of dates, activities, and milestones to reach first launch.
©CC BY-SA

18. Participants Workshop participants TBD
Additional exec review participants
TBD
Once information is input to this presentation, this should be reviewed and discussed with the exec sponsor for alignment.
©CC BY-SA