Blueprint
Design. Speed. Quality.
Accelerate your transition into the digital world
As part of the overall Accelerator Methodology, Blueprint defines the API program’s design and processes to be used in building solutions. This foundation sets standards that enables teams to focus on their customer’s requirements to meet the ever-increasing demands in the digital economy. Our techniques are built on experience and enable your digital journey from concept to reality in a structured path to ensure stability and reliability.
See also Kicking off your API Program - Where to start
The overall framework is based on three key ideas
- Design
e.g. API Specifications, Solution Architecture, Delivery Approach - Speed
e.g. Design first API approach, iterative development cycles to adapt to business needs, development best practices to drive a right first time culture - Quality
e.g. Checkpoints for API Design and Development, Continuous Integration, Test driven and behaviour driven development
How it Works
Our Blueprint offering is broken into 5 logical segments;
- Accelerator Planning
- Scoping
- Architecture & Design
- Operations & Support
- Delivery Approach
The Apigee team works a series of activities and facilitated sessions with the customer to design an API Program that will continually evolve and mature over time.
Delivery Approach
We have simplified the delivery into a consecutive 3-week process, which includes one week on-site working directly with the Customer’s team. Included is a quality framework process of having a cross sectional group of experienced consulting resources ensuring the design incorporates the latest functionality and utilises the product capabilities to maximize the performance and maintainability of the delivered solution.
Activities
Outputs
Accelerator Planning
This phase confirms the alignment and readiness of all parties for the Blueprint including confirmation of:
- Collaboration and communication tools
- Team Directory
- API Program Overview
- Blueprint Kick Off presentation
Scoping
This phase defines the process for capturing and managing the requirements backlog and also start to build the backlog for the initial 3 - 6 Sprints
Architecture and Design
This phase defines the high level solution architecture and low level design of the APIs to be delivered in the first 3 - 6 Sprints
See also
Best practices for defining an API Specification
Developer portal quick starter guide
Coordinating API and App Development cycles
Operations and Support
This phase outlines the different components of the Apigee product and defines the teams and processes required to successfully maintain and support the platform
See also Forming an API Monitoring Stategy - Where to start
Delivery Approach
This phase defines the best practices around API Development including
- Sprint Planning
See also Best Practices for running effective Sprints - API Testing Strategy
See also Forming an API Test Strategy - Where to start - Source Code Management
- API Deployment
- Continuous Integration
For customers just starting the Agile journey we also offer advice for moving from a Waterfall to a more Agile approach e.g. Advice for starting out on the Agile journey
Summary
The Blueprint is summarized in an Executive Presentation which captures the key details and outputs which merit stakeholder alignment to move forward. The other purpose is to facilitate Blueprint closure, designed as a gate that leads into subsequent Sprint phases.
The summary includes a review of key items identified and completed during the Blueprint, including;
- Objectives and achievements
- Deliverables completed
- Key decisions and recommendations
- Highlighted risks and mitigation plan
- Final retrospective and remarks