<<Date>>

1. <<replace with Customer Logo>> Blueprint Kickoff <<Date>>

2. Introductions Customer Vision & Success Criteria Apigee Accelerator Overview Blueprint Schedule Roles & Responsibilities Communications Assumptions Risks

3. Introductions <<Customer Name>> • <<name>>, Executive Sponsor • <<name>>, Product Owner • <<name>>, Project Manager • <<name>>, Lead Architect • <<name>>, Network Engineering • <<name>>, Test Lead Apigee • <<name>>, Scrum Master • <<name>>, Global Architect • <<name>>, Principal Architect • <<name>>, Technology Specialist • <<name>>, Technology Specialist (Drupal)

4. Vision & Success Criteria <<customer Exec Sponsor presents this slide>> Vision <<vision statement of what is expected of program>> Success Criteria • <<list success criteria>>

5. Services: Mobile requires a new model • App cycle time demands extreme flexibility and speed • IT infrastructure demands stability • Digital programs connect these two worlds Digital Program Business Demand Time

6. Traditional deployment models don’t work • Demand increases over time in digital programs • Continuous optimization is required for best business results • Inefficiencies result from application of traditional methodologies Required Velocity Velocity Inability to Adapt to changing business priorities Insufficient User story gathering Initial higher velocity by “jumping in” Inefficient Sprint Management Actual Velocity Incomplete Delivery Infrastructure Time

7. Apigee Accelerator Continuous Deployment Extreme Sprints Enables Enables Blueprint Readiness Plan Plan Scoping Increment Increment Tuning & Hardening Sprints Feature Sprints Architecture & Design Retro Retro Operations & Support Review Review Delivery Framework Production Release

8. Blueprint • Readiness • Review and align on pre-blueprint deliverables • Customer & Apigee preparation for starting Scoping • Scoping • Define boundaries of implementation • Define user stories for initial sprints • Architecture & Design • Define infrastructure and data flow architecture • Create API Proxy design • Delivery Framework • Align on process and meetings for Extreme Sprints • Define key communication vehicles to keep team aligned • Operations Strategy • Review system monitoring strategy • Define support structure needed for the solution

9. Blueprint Deliverables • Readiness • Pre-Engagement Questionnaire • Project Success Criteria Definition • Detailed Blueprint Schedule • Blueprint Kick-off Presentation • Customer API Program Overview • JIRA & Confluence setup with acct access • Scoping • Project Executive Overview • Apigee Technical Overview • Functional & Non-functional Reqs Specs • User Story Backlog • Architecture & Design • API Specification • Solution Architecture • Developer Portal Design • API Platform Test Strategy • Functional, Performance & Unit Test Plan • Delivery Framework • RACI Matrix • Detailed Sprint Schedule • Project Milestone & Resource Plan • Budget Tracking Document • Standard Status Report • Source Code Mgmt Process • Githubsetup with account access • Maven deployment & Continuous Deployment Infrastructure setup • Customer Env Specification • Executive Review Presentation • Extreme Sprints SOW • Operation & Support • Monitoring and Operations Strategy Definition

10. Blueprint Activities • Readiness • Validate Customer Blueprint Readiness • Review pre-Blueprint deliverables • Blueprint Planning • Scoping • Project Scoping Discussions • Requirements Review Sessions • Apigee Technical Overview • Architecture & Design • Organization & Environment Architecture Discussions • Developer Portal Design Sessions • Testing Approach & Activities alignment • Delivery Framework • Project Delivery Methodology Best Practices Sessions • Development Infrastructure Design • Extreme Sprint Planning • Operation & Support • API Infrastructure Monitoring Strategy • API Platform Operations Strategies & Best Practices

11. Blueprint Schedule – Week 1

12. Blueprint Schedule – Week 2

13. Blueprint Schedule – Week 3

14. Blueprint – Apigee Roles & Responsibilities • Scrum Master • Main contact for project coordination activities • Leads daily stand-up meetings, oversees project schedule and coordinates with other organizations for testing and deployment activities • Accountable for reporting weekly status and budget information • Global Architect • Leads the creation of a infrastructure deliverable • Works closely with the Customer’s Technical Lead and/or Network Engineer to ensure Customer ownership of these deliverables once completed. • Principal Architect • Responsible for the software design deliverables • Leads customer requirements (user stories) sessions • Leads any design challenges that may arise • Technology Specialist • Implements the designs and requirements defined • Conducts unit tests • Resolves defects found during customer testing • Technology Specialist (Developer Portal) • Gathers developer portal requirements, designs, configures, unit tests and supports Customer-led functional testing

15. Blueprint – Customer Roles & Responsibilities • Executive Sponsor • Visible participant in the project and sets vision and guiding principles • Actively engaged in the Blueprint Executive Review session • Project Manager • Main contact for project coordination activities, working closely with the Apigee Scrum Master. • Ensures customer resources are available when needed • Coordinates the customer-led activities • Ensures an efficient process is in place to log defects and track to closure • Product Owner • Participates in all design and requirement sessions to provide input to what is needed to meet the business needs of the API program • Lead Architect • Participates in all design sessions and approves the solution design. • Participates in Functional and Performance Testing • Involved with the deployment of the solution to Production

16. Blueprint – Customer Roles & Responsibilities • Network Engineer • Sets-up all hardware necessary for the Apigee solution, including opening ports, setting up and modifying any firewall policies • Documents the Apigee installation procedures • Sets-up monitoring and ensures availability to the systems during the project • Test Lead • Defines the Testing Strategy for the program • Plans, develops and executes all necessary steps for executing Functional and Performance Testing. • Sets up a process and tools to track defects to closure

17. Communications Daily Standups Confluence Project Home Page Weekly Status Reports Monthly Executive Updates

18. Assumptions Enter details.

19. Risks Enter details.

20. Q&A

21. 2013