June 1, 2021

Digital Platforms
PI4 Planning

Jussi Järvinen, Tuomas Oksanen and Product Owners

June 1, 2021
Our objective for
the next 3 days
• Work together as
‒ Digital Platforms
and Business stakeholders
• To produce plans
‒ For each DPL team (7)
‒ For PI4 (7.6. – 19.9.)
‒ As objectives with a
defined Business Owner
and business value
• Such that
‒ Businesses receive
maximum value
‒ Teams can commit to the
plans with given resources

June 1, 2021
Metso Outotec digital
opportunities and
priorities

June 1, 2021
Our purpose

Enabling
sustainable
modern life

June 1, 2021
Reshaping the
future

Our ambition is to be a
top-tier company, with a
high focus on digitalization

 We provide data and analytics to

help improve our customers'
equipment and processes

 We aim to offer a digital customer

journey for their entire equipment
lifecycle

June 1, 2021
Metso Outotec strategy
Digital opportunities and priorities

Customer engagement Connectivity, analytics Equipment & process Internal digital

& experience and remote support optimization efficiency

June 1, 2021
Digital opportunities and priorities

Customer engagement Connectivity, analytics Equipment & process Internal digital

& experience and remote support optimization efficiency

Develop customer engagement Collect, analyze and visualize Intelligent sensors and Automate and digitalize internal
across the board through a data of equipment and processes measurement systems, equipment processes e.g., fully digitalized field
common gateway, i.e., customer to improve their availability and and process automation, and service force to drive differentiated
portal, for all digital content with performance through process optimization to improve customer service and reduce cost.
increased use of eCommerce and performance-based services and process performance, recovery and Product data management
other online channels remote support efficiency improvements.

June 1, 2021
Update on Digital Platforms
team structure and vision
for PI4

June 1, 2021
Digital Platforms Teams

Intelligent Connected Modeling & Customer

Automation Analytics Simulation Experience

Automation and Modeling and

Information Systems Connected Analytics Customer Portal
Simulation
(PROSCON, Information (Metrics & Asset Analytics) (Pretium Portal, RSP, VeX)
(HSC Chemistry)
Management System)

Intelligent Sensors Virtual Plant

and Control Simulation Design System
(Ascent, ACT, Senses, OCS-4D,
(VPS & MPP)
Visio, Digital twin)

June 1, 2021
Digital Platforms Teams

Plant Intelligent Connected Modeling & Customer

Automation Automation Analytics Simulation Experience

Automation and Intelligent Sensors Modeling and

Information System and Control Connected Analytics Customer Portal
Simulation
(PROSCON, Information (Ascent, ACT, Senses, OCS- (Metrics & Asset Analytics) (Pretium Portal, RSP, VeX)
(HSC Chemistry)
Management System) 4D, Visio, Digital twin)

Virtual Plant
Simulation Design System
(VPS & MPP)

June 1, 2021
Digital Platforms Teams

Plant Intelligent Connected Modeling & Customer

Automation Automation Analytics Simulation Experience

Plant Automation Intelligent Automation Modeling and

Connected Analytics Customer Portal
(PROSCON, Information (Ascent, ACT, Senses, OCS- Simulation
(Metrics & Asset Analytics) (Pretium Portal, RSP, VeX)
Management System) 4D, Visio, Digital twin) (HSC Chemistry)

Virtual Plant
Simulation Design System
(VPS & MPP)

June 1, 2021
Digital Platforms – Use cases

Plant Intelligent Connected Modeling & Customer

Automation Automation Analytics Simulation Experience

Digitizing our process Providing great

Real-time and safe Real-time systems Connecting assets and
and equipment customer experiences
plant and equipment and tools ​that processes for storing,
knowhow using with a single secure
control and automatically​sense, analyzing and
chemistry and gateway to all digital
information systems think and optimize visualizing data and
metallurgy content
 the process insight
 
Safe and well  
Fit-for-purpose Harmonized user
managed plant Improved process Increased asset
process design end experience and
operations as a solid performance and availability and expert
simulation-based efficient design &
foundation efficiency support
services development

June 1, 2021
Digital Platforms – Development teams

Plant Intelligent Connected Modeling & Customer

Automation Automation Analytics Simulation Experience

The development teams in DPL value stream

Plant Automation Intelligent Automation Modeling and

Connected Analytics Customer Portal
(PROSCON, Information (Ascent, ACT, Senses, OCS- Simulation
(Metrics & Asset Analytics) (Pretium Portal, RSP, VeX)
Management System) 4D, Visio, Digital twin) (HSC Chemistry)

Virtual Plant
Simulation Design System
(VPS & MPP)

June 1, 2021
Digital Platforms – Vision for PI4

Consolidating the platforms by building new platforms based on legacy platforms, migrating
functionalities from one platform to another and merging platform components while assessing
the business needs and the most suited technologies and vendors.
Building new digital solutions especially for connected equipment to enable new business
opportunities and connectivity of all equipment. Maintain competitive capabilities in the more
established businesses like process control and instruments. Develop customer engagement
through a new customer portal and more adaptive design system for mobile design.

Plant Intelligent Connected Modeling & Customer

Automation Automation Analytics Simulation Experience

June 1, 2021
Overview of the
teams and their
visions for PI4

June 1, 2021
PA – Plant Automation
Planned highlights during PI4:
Vision for PI4
Plant automation enabler Mini-PROSCON - MVP release

Mini-PROSCON - 1st delivery project starting

Mini-PROSCON - Sales material

Team purpose and scope

PROSCON – new pricing tool release
• Realtime control systems for processes and
equipment's. Safety included.
• Collects operational and process data from DPL cyber security - architecture concept
control systems, analyzers, and other systems in a
DPL cyber security - SDL training & pilot plan
plant. Data is refined to useful information and
(SDL = Security Development Lifecycle)
KPIs and presented in reports and dashboards.
• Cyber security in DPL level DPL cyber security - open source concept

June 1, 2021
IA – Intelligent Automation

Vision for PI4

Accelerate our Ascent

Team purpose and scope

• Platform for process monitoring, control and
optimization (a.k.a. Ascent)
• Platform for intelligent instruments, based on
machine vision, 3D scanning, vibration, sound and
other senses
• Platform for simulator-based advisor and control
systems (a.k.a. Digital Twin)

June 1, 2021
CA – Connected Analytics

Vision for PI4

"Harder, better, faster, stronger"

Team purpose and scope

• A scalable platform and a set of features that support
BAs' use-cases for connecting assets and developing
analytics/intelligence to the equipment and services
• The purpose is to improve the availability
and performance of our customers' assets. Data
received from the connected assets can also be used
to drive internal efficiency within MO

June 1, 2021
MOSI – Modeling and Simulation

Vision for PI4

Towards integrated platform

Team purpose and scope

• HSC Chemistry as a core tool of process design in
mineral processing and metallurgical area
• HSC Sim as a calculation engine in digital twins
and process operation related digital products

June 1, 2021
VPS – Virtual Plant Simulation / My Plant Planner

Vision for PI4

Towards integrated platform and improving
MPP usability

Team purpose and scope

• VPS as an internal equipment sizing and selection
tool based on BL experts' knowledge (crushing,
grinding, separation)
• My Plant Planner as a free 3D online tool for
simulation based on VPS (crushing and screening
only)

June 1, 2021
CUPO – Customer Portal

Vision for PI4

Initiate the transfer of Customer Portal to
Salesforce Platform

Team purpose and scope

• Start transferring the existing Customer Portal
features to Salesforce
• Maintaining the current Customer Portal during the
platform transition

June 1, 2021
DESY – Design System

Vision for PI4

Introducing adaptive DSUI for mobile design

Team purpose and scope

• Metso Outotec Design System is a collection of
shared tools, assets, guidelines and working
principles providing digital teams all the necessary
elements to build consistent, usable and
meaningful digital products and services.

June 1, 2021
Program Increment and
PI Planning schedule

June 1, 2021
Where are we now in ITDD calendar?

June 1, 2021
Program Increments 2020-2021
(PI with 3-week sprints *)

Numbers are week numbers PI Planning

Sprint Sprint Sprint Innovation & Planning

Winter Break
Dec PI  Xmas Jan 2021 Feb (Finland) Mar

PI2 49 50 51 52 53 1 2 3 4 5 6 7 8 9 10
 Apr May Jun

PI3 10 11 12 13 14 15 16 17 18 19 20 21 22
Jun  Jul Summer Break Sep

PI4 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37
 Oct Nov Dec

PI5 37 38 39 40 41 42 43 44 45 46 47 48 49

*) 2-week sprints possible. Up to team to decide.

June 1, 2021
Day 1, Tuesday agenda for PI4 planning
FIN-time
13:00 Piia Karhu, SVP, Business Development
• Next steps in our strategy
Kaisu Vesala, VP Applications
Opening words • xOT SAP is moving to Azure;
Info sharing about production break

Esko Harjama, Vice President, IT Architecture

• Architechtural guidance
Guidance for PI4 Planning
Jon von Weymarn, facilitator
• Goals of these 2,5 days
14:15 • Story: What happens in PI🦄 planning

14:30
CXD
Common digital STP SER Each value stream in separate
Field, Lifecycle, and
customer Standard Products
Performance DPL MS Teams sessions:
experience & and Parts
Solutions services Digital platforms
interface • Opening words
15:15 • What’s new
• Development vision
15:30 GRP ITE
Support services IT infrastructure
and corporate ETO and enterprise
functions Project business applications
and ETO
16:00
16:15

AMERICAS Teams Breakout 1 of 2

June 1, 2021
Links to join Teams sessions in Boulevard / IT & Digital Development / Events
Day 2, Wednesday agenda for PI4 planning
FIN-time
9:00
-
12:00

13:00

ETO
GRP Project business
Each train in separate MS
Support services and ETO ITE
13:50 and corporate IT infrastructure Teams sessions:
functions and enterprise
14:00 applications • Per team
14:15 • Risks and
STP impediments
14:45 SER Standard Products DPL
Field, Lifecycle, and
and Parts CXD • Draft plan,
Digital platforms
Common digital
Performance
Solutions services customer
highlighting
experience & dependencies
interface
15:30

Participants will be invited separately

AMERICAS Teams Breakout 2 of 2

June 1, 2021
Links to join Teams sessions in Boulevard / IT & Digital Development / Events
Day 3, Thursday agenda for PI4 planning
FIN-time
9:00
-
12:00

13:00

ETO Each VS in separate MS Teams sessions:

GRP Project business
and ETO • Per team
Support services ITE
13:50 and corporate
functions
IT infrastructure • Final plan...
and enterprise
14:00 applications • ...highlighting risks
14:15 • Review of VS shared risks
STP
14:45 • Confidence vote 👍👎🖖
SER Standard Products DPL
Field, Lifecycle, and
and Parts CXD Digital platforms
Performance Common digital
Solutions services customer
experience &
interface
15:30

Participants will be invited separately

*VS: Value stream

June 1, 2021
Links to join Teams sessions in Boulevard / IT & Digital Development / Events
What is inside a
team's PI plan?

June 1, 2021
PI plan contents

• Team vision
• Objectives
• Risks and dependencies
• Capacity
• Schedule
• Stakeholders and links

June 1, 2021
PI Objectives
• Objectives are one liners made of features that are from one portfolio epic. They
Make your objectives SMART:
are outputs of the Pi planning:
Specific – States the intended outcome concisely and
‒ Summarizes what you are planning to achieve with the planned to features explicitly as possible. (Hint: Try starting with an action
into simple business terms that can be understood by everyone, without losing verb.)
specificity. Measurable – It should be clear what a team needs to do to
achieve the objective. The measures may be descriptive,
‒ 1 PI Objective has 1 Business Owner that assigns Business value yes/no, quantitative, or provide a range.
• Business Owner should be asked if him/her want to be the business Achievable – Achieving the objective should be within the
owner team’s control and influence.
• The business owner should be the one giving the business value Realistic – Recognize factors that cannot be controlled.
(Hint: Avoid making ‘happy path’ assumptions.)
‒ Objectives are only for one program increment Time-bound – The time period for achievement must be
within the PI, and therefore all objectives must be scoped
‒ Not everything needs an objective to be inside your plan, e.g. support and
appropriately.
maintenance for production

• There are two kind of objectives: Business value:

‒ • Assigned to the objective by the business owner of the
Committed objectives:
objective
‒ Objectives that are planned to be achieved and that the team commits to • Ranges from 1-10
• 10 Business critical
‒ Uncommitted objectives: • 8 very important
‒ Are planned and capacity is reserved • 6 important
• 1-5 not so important
‒ Have dependencies or risks that make it impossible to know the outcome
of the objective
‒ Explain in the plan, why an objective is uncommitted

June 1, 2021 RESTRICTED 32

Risks and dependencies

• All plans have risks and dependencies of some kind of

‒ Make them visible in the plan
• Risks ROAM the risks
• Resolved – The teams agree that the risk is
‒ Things and circumstances that might have an impact
no longer a concern.
on your plan • Owned – Someone on the train takes
ownership of the risk since it cannot be
‒ Identify and write out your risks resolved during PI planning.
‒ ROAM the risks to make your plan more reliable • Accepted – Some risks are just facts or
potential problems that must be understood
and accepted.
• Dependencies • Mitigated – Teams identify a plan to reduce
‒ Features might be dependent on something or the impact of the risk
someone that is outside your team
‒ Identify the dependency and who to contact to clarify
it
‒ Agree with the source of the dependency on how
to handle it
June 1, 2021
Capacity
• You can't complete all the Epics, Features and Stories in
your backlog in this PI.

• Knowing your team's capacity is the cornerstone to be able

to plan what you can achieve in the PI
‒ Take the following into account
‒ Allocations: Is some team member only partly
allocated to your team?
‒ Vacations: Most of us will have 4 weeks off during
PI4
‒ Other absences: Parental leave etc.
Innovation and Planning Iteration:
• When you know your team's capacity for the whole PI
• The last 3 weeks of the PI
consider these: • Are used for:
‒ Don't plan development work for IP iteration – Preparing for the next PI planning
(preplanning, epic & feature refinement)
‒ Reserve time for maintenance, bugs and supporting – Innovation and training
production if you are not able to plan it – Refactoring, doing PoCs, hactathons

‒ Reduce your capacity by for example 20%

June 1, 2021
Schedule

• You need two things to be able to plan and schedule the

development of features for the PI:
‒ Capacity of the team for the PI
‒ Good to know on at least sprint level
‒ Estimates about feature sizes or story sizes
‒ Can be story point estimations or t-shirt estimations
‒ The more refined the features are, easier they are to
break down to story level or to estimate
‒ Use the tools available to help you visualize your schedule
‒ Advanced roadmaps / Plan view in Jira
‒ Miro
‒ Table in confluence

June 1, 2021
Stakeholders and links

• List the stakeholders and business people who participated in the PI

planning to make it visible
‒ Can be used later for communications and to find out who from
business were involved in the planning
• Links to material and tools that support your plan
‒ Excels, word documents
‒ Other confluence pages
‒ Miro boards

June 1, 2021
PI Planning tips and practicalities

• If a team needs major efforts from regional IT, Salesforce, SAP, Dynamics, etc... remember to communicate actively with
them

• Vacation period:
‒ Remember to rest!
‒ Maybe not major production changes here... buuuuut you teams know best. We trust you

• If you encounter a problem and need help with the planning:

‒ Teams message/call and ask to join your team breakout session (or a phone call)
‒ Tuomas Oksanen, Release Train Engineer (+358 50 548 2739)
‒ Jussi Järvinen, Value Stream Lead (+358 40 831 2762)
‒ Qaiser Siddique, Agile Coach (+358 45 136 1177)
‒ Scrum Masters: Kristiina, Aino, Matti, Sarita
‒ Line managers: Juha Karttunen, Peter Blanz, Olli Luukkonen, Antti Roine, Janne Lampinen

• If you have cross value stream dependencies, join the breakout or contact the PO of that team.
‒ Let Tuomas and Jussi know about the risks and dependencies between value streams

June 1, 2021
After the planning

• Answer the feedback survey about the PI Planning: Feedback Survey

• Take part in DPL PI4 planning retrospective:
‒ Star by answering mentimeter surveys:
‒ Team and Technical Agility assesment: https://www.menti.com/tbtfkht9b9
‒ PI4 planning retro: link shared on PI planning day 3
• Take a breather and admire the magnificent plan you have made.
• Add PI Objectives to Jira
• Start preparing for iterations with, decomposing features to stories and refining the
team backlog
• Start the first iteration with sprint planning

June 1, 2021
Time to plan!

June 1, 2021
June 1, 2021

8.9.2020

mogroup.com