CAPO™ method optimizes IT development and improves the quality of the end product. It can be utilized by any organization operating, designing or developing IT products, capabilities or end user services. CAPO™ completes current and the most common agile methods e.g. Scrum, SAFe.

1. CAPOTM way of working
CONCEPTING – ARCHITECTURE – PROTOTYPING – OPERATIONS
Talent Base Oy

2. CAPO™ method optimizes IT development
and improves the quality of the end product.

3. Introduction
• CAPO is a way of working model and it can be utilized by
any organization operating, designing or developing IT
products, capabilities or end user services
• CAPO completes the existing, most common agile
methods e.g. Scrum, SAFe
• CAPO method provides tools and best practices from
portfolio management level to development team level
and enables organizations to get the best out of IT
development

4. Key benefits
• Crystallizes product vision and the “big picture” to everybody
• Makes the process from business need to implementation more agile
• Provides a clear model how business needs are transformed to actual
functionality
• Improves work efficiency, communication and commitment
• Improves transparency and predictability and ensures that stakeholder
expectations are in line with implementation
• Optimizes business value:
– Doing the rights things in the right order
– Minimizing waste
• Improves quality of the end product
– All relevant aspects are considered for every requirement

5. CAPOTM way of working
PORTFOLIO LEVEL
Business Stakeholders provide the needs/requirements to
the program level. The portfolio level could also leverage the
CAPO way of working (not in the picture).
PROGRAM LEVEL
All requirements pass through the program level. The
program level refines the needs to concrete requirements
and also plans the releases.
• Product owner steers the CAPO team
• Business stakeholders accept the concepts and help in
prioritization
TEAM/IMPLEMENTATION LEVEL
Development team refines and implements the
requirements/concepts provided by the program level. The
concepts are refined to actual solutions.

6. CAPOTM aspects
Concept and Solution Design
• Business needs are transformed
to concrete requirements
• Different aspects are aligned
(UI&UX/Operations/Architecture..)
• Dependencies between teams &
projects are coordinated
• Communication with all parties
Architecture
• Technical solution design is
aligned with the company
architecture and infrastructure
Prototype / Proof of Concept
• Verifies concept eligibility with
working prototype
• The prototype can be e.g. process
simulation or HTML prototype
that uses real content
• Visualizes/Concretizes the end
product
• Important tool to concretize UI/
UX and validates the technical
solution
Operational optimization
• Operational/maintenance aspect
• Alignment with business processes
• Deployment impact
• Optimize the operational efficiency
(automation in key parts)
• Content and operational needs
communicated
• Service Lifecycle
• Training needs
C A
P O

7. More information:
Nino Ilveskero, Partner
+ 358 40 511 8935
nino.ilveskero(at) talentbase.fi