Académique Documents
Professionnel Documents
Culture Documents
Cloud InnovateTM Methodology brings the IBM way to address Hybrid Cloud
journey
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
Integrated Method
Solution Design and Delivery Guidance
Personalized Talent Model
Integrated Method
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
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
Deliverables
Integrated Method
Solution Design and Delivery Guidance
Personalized Talent Model
Integrated Method
Solution Design and Delivery Guidance
Personalized Talent Model
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
Build on Cloud
(Design +Build services)
# 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
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)
Select Delivery Team T-Shirt Size 5 Select DevOps Services Size Tailor RACI Template
5 1
(based on Effort Points)
Complete
Select Platform Management T-Shirt Size
Platform 9
Mgmt.
Provide Platform Management Price 3 Agree on DOU / RACI
Team(GTS) 10
20 Copyright IBM Corporation 2017 | IBM Internal
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
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
Testing DevOps
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 Developer
Create and configure APIs
Reuse assets & apply
patterns
Technical implementation of
APIs
Unit Test
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
Shared Teams
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
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
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 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?
How can I easily find and fix issues?
Lead Designer
Common IBM Architect Lead Business LeadLead
Designer
Analyst* Test Lead
Arch + Designer**
Design
Use App Ops On Cloud Guidance
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
Shared Teams
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
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
Demo Demo
Stories/T Demo Stories/T
asks asks Project
Project Playback
Playback
Runbooks
Custom monitoring IBM Runbook Automation
alerts
Monitoring
NewRelic Collaboration
Integrated Method
Solution Design and Delivery Guidance
Personalized Talent Model
Roles Staffing
API Developer
Create and configure APIs
Reuse assets & apply
patterns
Technical implementation of
APIs
Unit Test
DevOps Lead
DevOps & Automation Evangelist
Release Strategy?
Configuration Management
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?
How can I easily find and fix issues?
Integrated Method
Solution Design and Delivery Guidance
Personalized Talent Model
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
Service
- Run / Manage /
Composition / Operate
Service Service Service
Integration
- Integrated Service
Management from SOC
45 Copyright IBM Corporation 2017 | IBM Internal
App Ops : Most common scenarios for Service Selection
T-Shirt Sizing and Pricing for selected scenarios is available as part of App Ops on Cloud Demand
Profile