Cloud Innovate Build On Cloud Demand Profile v0.4

TM
Client Demand Profile Build on Cloud
Cloud Application Services

for Enterprise Digital Transformation
March 2017 Version 0.2
Copyright IBM Corporation 2017 | All rights reserved
Cloud InnovateTM our approach for Cloud Adoption
Client Demands
Cloud InnovateTM is End to Advise on Cloud Cloud InnovateTM ensures

Adoption
End
App Ops on Migrate to Consistency of experience from
Hybrid Cloud
Full lifecycle from strategy to Cloud Cloud IBM ensuring predictable
implementation outcomes
Vertically integrated solution Assimilation of best practices &
view Applications, experiences ensuring superior
Infrastructure, Operations etc. output quality
Addresses various stages in Modernize for Standard set of Tools
Hybrid cloud transformation Build on Cloud Cloud facilitating data capture,
journey analysis and reporting
Rationalize for Efficiency that increases speed
Cloud to value
Cloud InnovateTM Methodology brings the IBM way to address Hybrid Cloud
journey
2 Copyright IBM Corporation 2017 | IBM Internal

Client Demand Profile: Build on Cloud
IBM Bluemix Garage Method & Agile Program Management Practices are adapted with additional practices & assets to
develop Build on Cloud Client Demand Profile
Capability Patterns Build on Cloud
Agile Program Management & Governance Applied To
Hybrid Cloud
API Responsive Ux* Microservices Integrate Methods
Integration Hybrid Cloud Application
Refine Deliverables architecture
Systems Tools & Assets Cloud Native Application
Design Thinking* Hybrid Cloud Application Architecture
Management Integration Development
Design Thinking
Skill driven Talent
Model Agile Program Delivery
Cloud Platform Architecture Application optimization
Instantiate Common
MW
Business Business Solution Business Solution Technical Services
Solution Security & DevOps
Managed
Services
Integrated Method
Operations Compliance
Solution Design and Delivery
App Ops on Cloud
Guidance
Personalized Talent Model
Method Artifacts Common Technical Services
Practices
Toolchains
Assets & Accelerators
*In collaboration with iX Digital Strategy & Interactive Teams

3 Strategize / Mobilize Discovery & Analysis Design & Build Run Copyright IBM Corporation 2017 | IBM Internal
How to use this deck
A Demand Profile provides overall guidance on how to solution and

deliver client services in their Cloud Journey.
A Demand profile will contain
Client Scenario that motivates this profile
Integrated Method
Solution Design and Delivery Guidance
Common Technical Services

Integrated Method


End-to-End Delivery Approach Scenarios
Build on
Client Scenario Solution Driver Capabilities Business Results
Cloud
I need to rapidly bring an Rapid Proof of Concept Design Thinking Design Thinking enabled idea
S1
innovative idea to market Creation API development & minimum viable
Minimum Viable Rapid time to Market MicroServices product definition
Product using Cloud Low costs through cloud Cloud Application Architecture Rapid Delivery of PoC & MVP
Native Capabilities leverage using Platform as a Service &
Ideate, Innovate, Garage Method Practices
Implement
I have built an MVP; need Deliver cloud native Cloud Application Architecture Production Delivery with
S2
to deploy it in large-scale applications with full API Compliance
with full functional scope Cloud Native functional scope MicroServices Hybrid Cloud Platform Leverage
Application Additional rigor for Hybrid Cloud Integration (IBM / Non-IBM)
Development @ availability, disaster Agile Program Management &
Enterprise Scale recovery, security & data Governance
privacy
I need to re-write an Application Re-write to Cloud Application Architecture Large Scale Cloud Adoption
existing application using support User Experience, Hybrid Cloud Integration Enterprise Transformation
new architecture and Future Proofing AND/OR API New Operating Model
cloud native capabilities Cloud
S3 Native new revenue channels Microservices
I need to apply Cloud Transformation @ Assisted Transformation of Agile Program Management &
Native Transformation at Enterprise Scale Enterprise for cloud native Governance
Enterprise Scale to IT development
Landscape

Build on Cloud: Circle of Life
Practices
Innovate
Culture Think Code Deliver
Agile Principles IBM Design Thinking Extreme Programming
Scaled Agile Framework (SAFe) Ideation Automated Testing Continuous delivery
Kanban and Scaled Agile Framework (SAFe) User Stories Database deployment automation Continuous delivery and iterative
development for Internet of
Building a culture and team User Experiments Performance Testing
Things projects
Fun Work Environment Sponsor Users TDD
Boot Camp Training Hills BDD Database deployment automation
Centre of Competency Envisioning the new user Refactoring
Building diverse teams experience Iterative Design Limited Blast Radius
Minimizing distractions Wireframe Sketches Refactoring to Microservices
Failing fast Playbacks Pair Programming Integrated globalization
Organizational Roles Rank ordered backlog
Inclusive design
Continuous Integration Delivery Pipeline Scale @ Demonstrate
Autonomous co-located squads BVT and Integration Verification Testing
Aligning development and operations for Iteration Planning Daily Standup Automated deployment Enterprise Proof of Value
success Value stream mapping Microservices
Evolving from waterfall to continous delivery Designing for mobile Integrated globalization
Failing fast for Internet of Things projects Mobile Development Planning Working in small batches
Retrospective Analysis The Build Measure Learn Loop Early risk mitigation
Social Coding Just Enough Architecture
Manage Run Learn

Circuit Breaker Pattern
Dark Launch and Feature toggles A/B Testing
Auto-scaling applications Implement
Incident Management
Auto scaling applications
Automated monitoring
Hypothesis driven development Minimum
Websphere migration to the cloud Fast recovery Viable Product
Resiliency
Chaotic Testing
HA
Operations Automation
Deliverables
API Minimum Service Level Responsive

Application DevOps Live Cloud
Management Viable ROI User Stories Agreements / User
Images for Scripts for Prototype Platform
Approach Product Objectives Experience
containers CI/CD/CT
Statement
Data Monitoring & MicroService

Application Operational Design Sprint
Data Model Synchronizati Management Code & Unit API Catalog App Catalog
Architecture Architecture Artifacts plan
on Approach Approach Tests

Integrated Method

Build on Cloud Practices : Culture
Building trust and alignment with better communication and transparency

Build on Cloud Practices : Think
Know your audience and meet their needs faster than your competition

Build on Cloud Practices : Code
Collaborate to create and continuously integrate high quality code

Build on Cloud Practices : Deliver
Continuously build, test and deploy code through an automated delivery pipeline

Build on Cloud Practices : Run
Harness the power of the cloud to quickly get your MVP to production

Build on Cloud Practices : Manage
Manage your applications to a high degree of quality and meet your SLAs

Build on Cloud Practices : Learn
Learn from your users as they interact with the application

Integrated Method

Build on Cloud Solution Entry Points
Proof of
Minimum Viable Solution @
Concept /
Product Scale
Technology
Market-ready Scope Scale from functional coverage as well as
Minimal Scope Focus on optimum business functionality coverage Production grade SLA/SLO coverage
Focus on idea proofing, rapid build Buildout in 4-6 months Buildout over multiple phases in 6-18
Internal Team consumption; production grade Production Release for limited users/groups months
not required Work Details
Work Details IBM Design Thinking Workshop
IBM Design Thinking Workshop UX and Visual Design
UX and Visual Design Build Prototypes on Bluemix
Build Prototypes on Bluemix User Testing
User Testing DevOps Setup & Application Development
Deliverables Knowledge Transfer & Go Live
Minimum Viable Product Statement Deliverables
Design Artifacts Production Quality code on Bluemix
Live Prototype on Bluemix Design Artifacts
User Testing outcome Project documentation
Duration : 4 -6 weeks User validation report
IBM Participants: Design Thinking SME, Test and delivery artifacts
Garage Solution Architect/Technical Lead, High Level Roadmap
UX/Visual Developer, Developer Operations Handbook
Client Participants: Business & IT Leaders, IBM Participants: Design Thinking SME, Garage
Product Managers/Delegate, Architect/Delegate, Solution Architect/Technical Lead, UX/Visual Developer,
Project Manager Developer
Client Participants: Business & IT Leaders, Product
Managers/Delegate, Architect/Delegate, Project
Manager
Staffing Customized solution ; T-Shirt sized solution can be used

Use Template + T-Shirt Size Guidance partially; will require additional considerations
Build on Cloud + App Ops On Cloud : Solution Component View
Business Solution Operations*
Build on Cloud
(Design +Build services)
GBS Middleware Mgmt

Services
Business
Solution Infra Mgmt / Managed PaaS SaaS GBS
Services Support
GBS
Security Business
& Solution Testing
Complian DevOps Services
ce IaaS
Private Public Local Dedicated Public

Hybrid Cloud Platform
*Integrated Ops might be required during design/build as well

Build on Cloud App Ops on Cloud GTS Collaboration IBM/ other Cloud Platform Components
Solution Component Guidance &Scenario Mapping
# Key Solution Components Guidance Summary Scenario / Approaches Entry point applicability
a) Cloud native solution reference a) Micro Services Application Proof of Minimum Solution @
Concept / Viable Product Scale
Cloud Native Application architecture b) API-enablement Technology
1
Design Build b) Standard t-shirt size solution c) Internet of Things Solution
(incl. Estimation, Delivery Squad ) d) Cloud native monolithic architecture solutions
Proof of
a) Standard t-shirt size solution for a) IBM Cloud used for Design build Concept /
Minimum Solution @
2 Application Delivery Platform Technology
Viable Product Scale
PaaS b) Non-IBM Cloud used for Design Build
a) Standard t-shirt size solution for

a) SOC services for end to end support
4 Business Solution Operations a system (S/M/L) Minimum
Viable Product
Solution @
Scale
b) SOC Services for platform only
b) Portfolio applications

a system (S/M/L)
b) Custom DevOps toolchain a) DevOps Minimum Solution @
5 Business Solution DevOps Viable Product Scale
(shared / dedicated) on Cloud b) SOC Services for platform only
c) Custom DevOps toolchain hosted
/ managed by IBM
Middleware Management Minimum Solution @

6 Standard rate-card based MW services baked into any solution context Viable Product Scale
Services

a) IBM takes end to end ownership of a portfolio / or a
Business Solution Security & a system Minimum Solution @
7 system. Viable Product Scale
Compliance b) Custom solution for portfolio of
b) IBM builds / transfer solution to client.
applications
a) Deployment model needs to be

analyzed for MSP solution Minimum Solution @
8 Managed Services Support a) MSP Support for IaaS and/or PaaS (Bluemix) together. Viable Product Scale
design. Bill of Material, NFR
including SLAs are needed.
19 Build on Cloud App Ops on Cloud Copyright IBM Corporation 2017 | IBM Internal
Build on Cloud : Overall Solution Flow (Primarily for MVP and Scale)
A Functional + Technical B Operational B Contractual
Initiate
1 Collect Volumetric Attributes
1 Determine Functional Scope/Attributes
Use App Ops
2 Select Platform T-Shirt Size on Cloud
2 Determine Technical Attributes guidance
GBS (incl. non functional)
Solution Define Application Architecture 3
N BAFO Price
Calculate Platform ROM Price Submission?
Architect 3 ( using Template + Guidance)
4 Select MW Management Size Y

4 Estimate Effort point using Guidance
Select Delivery Team T-Shirt Size 5 Select DevOps Services Size Tailor RACI Template
5 1
(based on Effort Points)
6 Select Security Services

6 Complete ITDA Reviews
Cloud
Platform 7 Provide Platform Firm Price 2 Agree on DOU / RACI
Seller
4
Create Addl Solution Artifacts
(as reqd by SIH/IOT)
GBS 7 Create Staffing Plan Solution @
(based on template) 8 Select Integrated Ops Size Complete SIH/IOT Reviews Scale
Solution 5
Manager Create Overall Delivery Plan
8 6 Finalize SoW / Proposal etc Minimum
Viable Product
Provide summarized cost inputs for

7 Pricing
Complete
Select Platform Management T-Shirt Size
Platform 9
Mgmt.
Provide Platform Management Price 3 Agree on DOU / RACI
Team(GTS) 10
A. Functional + Technical Areas
# Activity Step Guidance
1 Define / Adapt Technical Solution Determine Functional Scope / Attributes Identify Key Users, systems & Data Flow (adapt system
context)
Define MVP & End State Scope
Identify Channels & Key User Experiences
Define Technical Attributes Identify integration mechanisms & Frequency with upstream
channels & downstream SoRs
Determine persistence requirements (e.g. transactional,
analytical etc)
Identify Non Functional Requirements
Adapt Application Architecture Use Standard Templates and tailor wherever required
Finalize Architecture Decisions and Technology Selections
2 Select Application T-Shirt Size for Delivery Estimate Effort using Guidance Use Effort estimation t-Shirt Sizing to calculate Effort Points
5 Select T-shirt size for delivery Use Delivery Team T-shirt sizing and composition based on
Effort Points
3,4 Adapt Staffing Plan Use Delivery Guidance

Adapt Delivery Plan

Define/Adapt Technical Solution Non Functional Considerations
Non Considerations
Functional
Requirement
Availability Is there upfront, known affinity with on-premise applications & low response latency?
Network connectivity between on-premise apps and cloud may not be amenable to the response time requirements
Is this a mission critical application with aggressive availability / disaster recovery requirements ?
Check latest Terms of Use for PaaS availability
PaaS availability (for e.g. Bluemix) could depend on multi-region deployment. This in turn, could have an impact on cost
https://www-03.ibm.com/software/sla/sladb.nsf/sla/bm-6606-09
Disaster
Recovery Identify and document Recovery Time Objective (RTO) and Recovery Point Objective (RPO) for the application
Choose Persistence Options based on DR Requirements and SLA/SLO of services provided
Make additional considerations for Data Replication etc. if required
Security & Data Identify Authentication & Authorization Requirements
Privacy Authentication can be possible through Bluemix SSO, but that would require SAML / Oauth based authentication provider at customer
end. Consider Cloud Identity Services (CIS) as an alternative
User Credential Management is a key responsibility - This is best done by customer teams, its important that the responsibility here is
identified early and documented clearly
Identify additional requirements, specifically Intrusion Detection, Secure Communications etc
Identify specific requirements for Data Encryption in-flight and at-rest
Manageability

API Development : Complexity and T-shirt size selection steps
Delivery Squads will

Calculate Effort Point primarily provide Design,
using Guidance Coding & Unit Test
Services
Architecture & Service

Discovery will be provided
Determine number of by a common arch +
Delivery + Support
Squads design team
System Testing, UAT

Squads need to be
selected separately
Determine Application T-
Shirt Size for Delivery

Calculate Effort Point API Development
Integrated Operations # Component Type Description Effort Point Calculation

Guidance
Securi Integr API Gateway
ty ation
b 1 API a. API Implementation with a. API Effort Point
Implementation business logic; business rules Calculation
b c Self Service Portal b. API endpoint exposure ; API
b security; throttling; version
management
API Management b c. Integration (composition,
orchestration ) with external
systems using existing
Implementation a services
Testing DevOps
Management & Monitoring

API Effort Point Calculation
1. Identify APIs and their Operations.
2. For Each factor, select the applicable complexity level (e.g. it is possible to have an API to have Complex # of endpoints and Simple Operations)
3. Award effort points per factor based on the last column. It is either same as the # for the factor or is a weight based on the applicable complexity
4. Total Effort points will be required to identify number of delivery squads
Factors Simple Medium Complex Effort Point per Parameter

Same as number of
Number of endpoints/Services Invoked 1 2 3 to 5
endpoints
No. of API Entities (e.g. Customer, Account) 1 2 3-5 1,2,3
No. of API Operations (e.g. Get/Put/Post/Delete) 1-4 5-8 9-20 1,2,3
API Data Models (Total no. of attributes) <20 20 to 40 40-100 1,2,3
2
3 to 5
1 (Aggregation of Same as number of
Data mapping complexity (Aggregation of 1-3 Proxy &
(Simple Proxy) 1 Proxy & 1 new aggregations
1-2 new API assembly)
assembly)
Validation None Mandatory fields >10 fields 1,3
Error Handling Standard Error codes Custom Error codes Framework 1,2,3
Rules None Simple Complex 2,3
Basic
Security None Custom/header based/OAuth 2,3
(Client id/Secret)
Publishing APIs 3 4-6 6-10 1,2,3
Basic plan Up to 3 Plans with rate >3 plans with rate limiting
Subscription/Usage Management 1,2,3
(<5 users) limiting (<10 users) (>10 users)

API Development : Delivery Squad Roles
API Designer Scrum Master
How do I assemble APIs? Remove impediments
How do I manage security? Communications Management
Will the infrastructure scale? Conflict Management
How do I measure performance? Maintain Velocity
API Developer
Create and configure APIs
Reuse assets & apply
patterns
Technical implementation of
APIs
Unit Test
Operations Lead DevOps Lead

How do I manage all the API DevOps & Automation Evangelist
Environments that are being requested? Release Strategy?
How can I scale each environment? Configuration Management
How can I easily find and fix issues?
Functional Tester Automation Tester

What test cases will be required for core What level of automation can be achieved
functional testing? considering the functionality ?
What are the different scenarios that need How to implement and integrate with
to be covered ? DevOps ?

API Development: Determine number of Delivery & Support Squads*
Lead Designer
Common IBM Architect Lead Business LeadLead
Designer API Product
Analyst** Test Lead*
Arch + Designer** Manager**
Design
Use App Ops On Cloud Guidance
Delivery Squad Infra Management Squad Ops Squad

(for IaaS components only)
Offshore +
Analysis
Onshore
System Engineers Operations Lead
Designers
Offshore
Scrum Master
Design
Build
Landed Offshore
Infra Mgmt Lead DevOps Lead
Designer Developer / Tester Onshore
Offshore Offshore
Developer Automation Functional DevOps SME Developer
Developer
Tester Tester
1 Analysis + Design Build Squad can deliver 80 points / month ( 1800 hrs of *Test Squads would need to be added separately
Design+Code+Unit Test Effort ) **Not required for POC/POV, Need based for MVP,
This roughly equals 2 Simple, 2 Medium, 1 Complex APIs Must have for Enterprise Scale
27 2016 IBM Corporation
API Development : Determine Delivery Team T-Shirt Size
Calculate Effort Points for API Solutions
Select number of Delivery Squads based on Effort Points and Delivery Timeframe ( 80 Effort points / month / Squad metric)
Choose Application T-Shirt Size based on the number of delivery squads required to get the total dedicated team size
Use Staffing Plan templates and tailor based on delivery & support timelines
Small Medium Large For additional squads ; always

consider a full squad partial
# of API Delivery Squads 1 2-4 5-7 squads should not be added
Common Arch + Design 3 4 5
Overall Governance Team Size 1 2 2
Total Dedicated Team Size 10-14 25-50 60-100
Shared Teams
# of Infra Management Squads 1 1 2-3

(Shared)
# of Ops Squads (Shared) 1 1 2
Shared Team Size 8 8 16-20
28 2016 IBM Corporation

MicroService Applications Complexity and T-shirt size selection steps
Delivery Squads will

Select microservice primarily provide Design,
application complexity
using t-Shirt Size Coding & Unit Test
Services
Architecture & Service

Discovery will be provided
Determine number of by a common arch +
Delivery + Support
Squads design team
System Testing, UAT

Squads need to be
selected separately
Determine Delivery
Team T-Shirt Size

MicroService Application
MicroService Architecture based solutions require multiple components to be considered for estimation, which are summarized
in the table below
Solution T-Shirt Size should be selected based on the combination of complexity factors of these components
Integrated Operations # Component Type Description
Security IPC API Gateway 1 1 API Gateway a. Effort for API Endpoint Exposure, Management,
3.c Authentication, Key Management
1 Proxy 1 Circuit Breaker 1
BFFs 2 2 BFF a. Effort for building a user experience specific

API composition and orchestration layer
3 MicroService Application a. Effort for building a micro-service application

MicroService Business API
3.a including Persistence Representation &
Persistence retrieval logic as well as business logic, rules
per bounded context
ETL 3.b b. Effort required for loading/synching data
between microservice persistance & external /
MicroService Application SOR persistence
c. Effort required for IPC
Testing DevOps
Management & Monitoring

MicroServices Application T-Shirt Size Selection
Components Simple Medium Complex
API Gateway , 1-2 Endpoints 3-5 Endpoints 6-10 Endpoints

Proxy, Circuit Synchronous Invocation only Synchronous OR Asynch Invocation Synchronous AND Asynch Invocation
Breaker Basic Management Plan (<5 Users) Upto 3 Plans with Rate Limiting (<=10 users) >3 Plans with Rate Limiting
BFF Proxy Exposure
Proxy Standard Load Balancing Load Balancing + Canary Testing Load Balancing + Canary Testing
Circuit Breaker Not used, self-sufficient app; Circuit breaker services for 1-2 external Services Circuit breaker services for 3-6
external services
Security Basic Platform Security ; does not require user Cliend ID / Secret Oauth, Customer header based, SSO
credential validation
BFF 1-2 BFFs 3-5 BFFs 3-5 BFFs

<=2 operations/BFF 2-3 Operations/BFF 3-4 Operations/BFF
<= 2 API Compositions Orchestration across upto 2 Business APIs Orchestration across 3-5 Business
APIs
Microservice API & Persistence Logic API & Persistence Logic API & Persistence Logic
Application : <= 2 Entities <= 4 Entities <= 6 Entities
Business API & <= 20 Fields / Entity <= 20-40 Fields / Entity <= 50-100 Fields / Entity
Persistence <=4 operations <=8 operations <=9-20 API operations
Standard Error Codes Standard + Custom Error Codes Error Mgmt Framework
REST Exposure Simple Business Logic Complex Business Logic
Microservice One to One Mapping for 2 Entities, upto 20 One-Many OR Many-One mapping for 4 entities, Combination of One-One, One-Many
Application : ETL fields / Entity 20-40 fields/entity > 10 Fields validation
No Validation Validation for Mandatory fields only
Microservice No external integrations <= 2 external integrations 3-6 external integrations

Application: IPC Synch OR Asynch communication Synch AND Asynch communication
REST or SOAP REST+SOAP + Other protocol
combination
Upto 2800 hrs of DCUT Effort 5700 - 8640 hrs DCUT effort 8600-11500 hrs. DCUT Effort
MicroService Applications : Delivery Squad Roles
BFF Designer /Developer MicroService Designer Scrum Master
What are the channel specific API What is the bounded context? Remove impediments
Requirements What is/are the core functions Communications
What API endpoints and operations exposed by MicroService App? Management
need to be consumed ? What is the business logic Conflict Management
What is the orchestration / required for implementation ? Maintain Velocity
consumption logic required ?
MicroService ETL Developer MicroService Data Modeler MicroService Business API Developer
What is the mapping required for What entities should be Create and Configure APIs
microservice data included? Implement Business Logic
How frequently does the data Which fields do I need per Implement Persistence Retrieval
need to be synched entity? Logic
/transformed? Implement IPC/ Failure Mgmt.
Operations Lead
DevOps Lead
How do I manage all the API
DevOps & Automation Evangelist
Environments that are being
Release Strategy?
requested?
Configuration Management
How can I scale each environment?


MicroService applications: Determine number of Delivery & Support Squads*
Lead Designer
Common IBM Architect Lead Business LeadLead
Designer
Analyst* Test Lead
Arch + Designer**
Design
Use App Ops On Cloud Guidance
Delivery Squad Infra Management Squad Ops Squad

(for IaaS components only)
Offshore +
Analysis
Onshore
System Engineers Operations Lead
MicroService Designer
Offshore
Scrum Master
Design
Build
Landed Offshore
Infra Mgmt Lead DevOps Lead
MicroServices BFF Designer Onshore
Designer
Offshore Offshore
DevOps SME Developer
Developer
BFF Biz API ETL Data Automatio Functional
Developer Developers Dev Modelern Tester Tester
Test Squads would need to be added separately for System, Integration & User Acceptance Testing
33 **Not applicable for Small Size, Optional for Medium, must for Large 2016 IBM Corporation
*Only required during Learn / Identification Phase
MicroService Applications - Determine Delivery Team T-Shirt Size
Identify number of MicroService Applications and Complexity based on T-Shirt Size guidance
Select number of Delivery Squads based on Effort Points and Delivery Timeframe ( 80 Effort points / month / Squad metric)
Choose Delivery Team T-Shirt Size based on the number of delivery squads required to get the total dedicated team size
Use Staffing Plan templates and tailor based on delivery & support timelines
Small Medium Large For additional squads ; always

consider a full squad partial
# of Microservice Delivery 1-2 2-4 5 squads should not be added
Squads
Common Arch + Design 3 4 5
Overall Governance Team Size 1 2 2
Total Dedicated Team Size 12-24 25-40 50-100
Shared Teams
# of Infra Management Squads 1 1 2-3

(Shared)
# of Ops Squads (Shared) 1 1 2
Shared Team Size 8 8 16-20

Build for Cloud: Factory delivery model overview
Cloud technologies like platform-as-a-service, evolution in software defined environments, and tooling frameworks have given rise to true realization of
the Cloud Native applications and primarily leveraging microservices architectural style. Build on Cloud encompasses methods and processes to build
cloud native applications for clients. The primary method of delivery is the IBM Bluemix Garage ++ Method
Delivery Lifecycle
1
1. Design 2. Develop 3. Develop 3. Scale (Continuous
Thinking POC MVP enhancements)
Minimal Scope Market-ready Scope
Focus on idea proofing Focus on optimum business Scale from functional coverage as well
Rapid PoC (4-6 weeks) functionality coverage as Production grade SLA/SLO coverage
Internal Team consumption; Buildout in 4-6 months Buildout over multiple phases in 6-18
production grade not required Production Release for limited months
users/groups
Delivery methodology Components
Method & Templates Talent Model & Team Tool Based Delivery Service Delivery Foundation
IBM Garage Method ++ based with Team composition roles, band mix DevOps toolchain driven model. Foundation Technical Services
hybrid cloud scenario extensions guidance, responsibilities, skill sets Continuous planning, development, configured for Solution Pattern -
Deliverables and templates Agile Squad based delivery model integration, delivery and monitoring , Agile & DevOps, Security,
Project Management Guide different types of squads (co-located Code discovery tooling for Testing, Solution Operations
Normative guidance, Estimation and remote squads) modernization Center*
templates/tools
35 Copyright
* OptionalIBM Corporation 2017 | IBM Internal
services
Methods and Templates
Innovation Workshop POC Sprint Analysis & Macro MVP Sprints & Playbacks(12- Architecture Refinement & Enterprise Scale Sprints &
(1 Week) (4-6 Weeks) Design(4-6 weeks) 16 weeks) Analysis for Scale Playbacks
WEEK |
Proposed schedule
1 2 3 4 5 6 .. .. 16
MVP Sprint 1.N Enterprise Scale Sprint 1 - N
Design Workshops
Architecture
On Paper
Review Playbacks MVP
High Level Design

Frameworks Demo
Arch Refine ment for Scale
Stories/Ta Demo Stories/Ta

Stories/Ta Demo
sks sks
sks
Iterate
&
Stories/Ta
Deliver Stories/Ta Demo
Stories/Ta Demo
sks
sks sks
Demo Demo
Stories/T Demo Stories/T
asks asks Project
Project Playback
Playback
Continuous Backlog Refinement Continuous Backlog Refinement Continuous Backlog Refinement

= Deliverable
Activities Activities Activities
Activities Activities Activities Activities
Development Space Setup Define Operational Architecture Production and Test Space Setup
Conduct Introductory Identify & Agree Hills Apply Scale Considerations Production and Test Space Update
Implementation Define Application Architecture Implementation
Workshops Define Priority Refine Operational Architecture Implementation
Daily Scrum Calls Volumetrics Daily Scrum Calls
Confirm Sponsor Identify Skills Refine Application Architecture Daily Scrum Calls
Conduct Playbacks API Identification Conduct Playbacks
Users and Personas Update API and MicroService Conduct Playbacks
Backlog Refinement & MicroService Identification Backlog Refinement &
Confirm Key catalog Backlog Refinement &
Reprioritization Reprioritization
Challenges Reprioritization
Conduct Design
Thinking Workshop
Candidate Solutions
Deliverables Deliverables Deliverables Deliverables
Deliverables Deliverables Deliverables
Personas, Sponsor Minimum Viable Design Hills / Features Design Hills / Features
Application Architecture Application Architecture Design Hills / Features
Users Product Statement Executables Code, Unit Tests Executables Code, Unit Tests
Operational Architecture Operational Architecture Executables Code, Unit Tests
POC Candidates Live Prototype Apps / Deployables Apps / Deployables
API and Microservices Catalog API and Microservices Catalog Apps / Deployables

Build on Cloud : Dev Tooling Framework
Requirements Cloud Native Code Trigger Test the Deploy to Proactive

Grooming Development Check-in Build Build Production Monitoring
All the stakeholders Developers leverage Developers check-in their Before the code gets The code is then Fully tested and verified The Continuous
collaboratively identify Bluemix PaaS and other code to the Git committed, it is promoted to the test applications are then Monitoring tools help pro-
& prioritize the Product Cloud services to Repository on Bluemix automatically built, environment, where promoted to the pre-prod actively monitor the
Backlog Items develop at least once a day analyzed and tested for end-to-end testing is environment for UAT, deployed application
Cloud native sanity done and then to production
applications
Bluemix Track & Plan Build Orchestration

Used for capturing Tools for pro-active and
tool responsible for automated monitoring
requirements, project Continuous Integration
planning & reporting
Collaboration
Git & its variations Repository Tools for automated deployments, &
Management tool Static Code Analyzer Test tools that enables
Source Code Repository provisioning environments
automated testing

Build on Cloud : Ops Tooling Framework
Dashboards & Reporting

Service Level Management Reports Grafana/Freeboard
Runbooks
Custom monitoring IBM Runbook Automation
alerts
Monitoring
NewRelic Collaboration
Dynatrace Tealeaf Slack
Nagios AICS MW Tools Mural.ly

Operate Event
Bluemix Notification
Trend Micro AV Management
TSM Monitoring/A PagerDuty
Runscope nalytics Netcool Omnibus
Bluemix Key Impact (NOI) Incident
Management
Protect
IBM Control
Bluemix
Logging Desk
Autoscaling
Splunk QRadar
38 Manage Analyze Copyright IBM Corporation 2017 | IBM Internal

Monitor
Integrated Method

Build on Cloud Delivery Roles & Staffing
Roles Staffing

API Development : Delivery Squad Roles
API Designer
How do I assemble APIs?
How do I manage security?
Will the infrastructure scale?
How do I measure performance?
API Developer
Create and configure APIs
Reuse assets & apply
patterns
Technical implementation of
APIs
Unit Test
Operations Lead Scrum Master

How do I manage all the API Remove impediments
Environments that are being requested? Communications Management
How can I scale each environment? Conflict Management
How can I easily find and fix issues? Maintain Velocity
DevOps Lead
Release Strategy?


MicroService Applications : Delivery Squad Roles
BFF Designer /Developer MicroService Designer Scrum Master
What are the channel specific API What is the bounded context? Remove impediments
Requirements What is/are the core functions Communications
What API endpoints and operations exposed by MicroService App? Management
need to be consumed ? What is the business logic Conflict Management
What is the orchestration / required for implementation ? Maintain Velocity
consumption logic required ?
MicroService ETL Developer MicroService Data Modeler MicroService Business API Developer
What is the mapping required for What entities should be Create and Configure APIs
microservice data included? Implement Business Logic
How frequently does the data Which fields do I need per Implement Persistence Retrieval
need to be synched entity? Logic
/transformed? Implement IPC/ Failure Mgmt.
Operations Lead
DevOps Lead
How do I manage all the API
Environments that are being
Release Strategy?
requested?
How can I scale each environment?


Integrated Method

B. Operational Areas
# Step Guidance
1 Collect Volumetric Attributes Identify key parameters that impact application performance and infrastructure sizing
Identify base values and assumptions
Get a view of volume increase over 3-5 years to create a view of current and future volumes
Typical Parameters considered

Number of Users (for each type of user e.g. Employee, customer )
Number of Concurrent users
Average Message Load / Transaction
Total Transactions
Number of access locations
Number of Devices
Data stored / user / transaction

App Ops : Hybrid Platform Service Selection for Build on Cloud
No
No PaaS service
available?
GBS Hybrid Cloud &
(i.e. Management
functional Services
/ operational fit)
Yes SaaS
Solution Operation Center
Container service No
available?
available?(i.e. Migration Factory/ GBS DST
(i.e.
functional functional (SW product management)
/ operational fit) / operational fit)
Where applicable due to
GTS IMI
Client needs, non-IBM Yes
PaaS can also be
(OS, Network, Storage
considered mgmt.)
Assumption: SaaS
is fully managed IaaS (IBM, Non-IBM)
For Build on Cloud Solution For Cloud only
Service
- Run / Manage /
Composition / Operate
Service Service Service
Integration
- Integrated Service
Management from SOC
App Ops : Most common scenarios for Service Selection
DevOps Services Integrated Ops Services Security Services
For Most Cloud Native Consider Scenarios Custom Service

Applications the SOC Support of Selection based on
scenario DevOps for a One System compliance to
system one solution SOC Support Customer
for all components should for Portfolio Specific Policies
be used T-Shirt Size can be Data Privacy
T-Shirt Size can be selected based on App Requirements
selected based on App Ops Guidance further Budget
Ops Guidance further
T-Shirt Sizing and Pricing for selected scenarios is available as part of App Ops on Cloud Demand
Profile

Cloud Innovate Build On Cloud Demand Profile v0.4

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Cloud Innovate Build On Cloud Demand Profile v0.4

Diunggah oleh

Hak Cipta:

Format Tersedia

TM

Client Demand Profile Build on Cloud

Cloud Application Services

Cloud InnovateTM is End to Advise on Cloud Cloud InnovateTM ensures

2 Copyright IBM Corporation 2017 | IBM Internal

Agile Program Management & Governance Applied To

*In collaboration with iX Digital Strategy & Interactive Teams

A Demand Profile provides overall guidance on how to solution and

Common Technical Services

4 Copyright IBM Corporation 2017 | IBM Internal

Solution Design and Delivery Guidance

Personalized Talent Model

5 Copyright IBM Corporation 2017 | IBM Internal

6 Copyright IBM Corporation 2017 | IBM Internal

Manage Run Learn

API Minimum Service Level Responsive

Data Monitoring & MicroService

7 Copyright IBM Corporation 2017 | IBM Internal

Common Technical Services

8 Copyright IBM Corporation 2017 | IBM Internal

9 Copyright IBM Corporation 2017 | IBM Internal

10 Copyright IBM Corporation 2017 | IBM Internal

11 Copyright IBM Corporation 2017 | IBM Internal

12 Copyright IBM Corporation 2017 | IBM Internal

13 Copyright IBM Corporation 2017 | IBM Internal

14 Copyright IBM Corporation 2017 | IBM Internal

15 Copyright IBM Corporation 2017 | IBM Internal

Common Technical Services

16 Copyright IBM Corporation 2017 | IBM Internal

Staffing Customized solution ; T-Shirt sized solution can be used

Business Solution Operations*

GBS Middleware Mgmt

Private Public Local Dedicated Public

*Integrated Ops might be required during design/build as well

a) Standard t-shirt size solution for

a) Standard t-shirt size solution for

Middleware Management Minimum Solution @

a) Standard t-shirt size solution for

a) Deployment model needs to be

4 Select MW Management Size Y

6 Select Security Services

Provide summarized cost inputs for

3,4 Adapt Staffing Plan Use Delivery Guidance

21 Copyright IBM Corporation 2017 | IBM Internal

22 Copyright IBM Corporation 2017 | IBM Internal

Delivery Squads will

Architecture & Service

System Testing, UAT

23 Copyright IBM Corporation 2017 | IBM Internal

Integrated Operations # Component Type Description Effort Point Calculation

Management & Monitoring

Hybrid Cloud Platform

24 Copyright IBM Corporation 2017 | IBM Internal

Factors Simple Medium Complex Effort Point per Parameter

No. of API Operations (e.g. Get/Put/Post/Delete) 1-4 5-8 9-20 1,2,3

API Data Models (Total no. of attributes) <20 20 to 40 40-100 1,2,3

25 Copyright IBM Corporation 2017 | IBM Internal

Operations Lead DevOps Lead

Functional Tester Automation Tester

26 Copyright IBM Corporation 2017 | IBM Internal

Delivery Squad Infra Management Squad Ops Squad

Small Medium Large For additional squads ; always

Overall Governance Team Size 1 2 2