Handling projects and requirements towards
delivery
MAN Diesel & Turbo
Author
Current topic

00.00.2012
<
1
>
Agenda
•
•
•
•
•
General Company Presentation
Environment
Project Governance Model
Requriements Gathering Process
Development
MAN Diesel & Turbo
Author
Current topic

00.00.2012
<
2
>
Volkswagen Group
MAN Diesel & Turbo
Author
Current topic

00.00.2012
<
3
>
MAN Diesel & Turbo
Areas of Activity
•
2-stroke and 4-stroke engines for marine and stationary applications
•
Complete propulsion packages
•
Compressors and turbines for all industrial applications
•
Chemical reactors and apparatuses
•
Turnkey power plants
•
Operation and maintenance of power plants
•
After Sales Services like repair, spare part supply, retrofitting, recycling
and monitoring of all MAN large-bore engines and turbomachinery in
use across the world (MAN│PrimeServ)
MAN Diesel & Turbo
Author
Current topic

00.00.2012
<
4
>
Areas of Activity
MAN Diesel & Turbo in World Trade
50% of World Trade is Powered by MAN
Diesel Engines!
MAN Diesel & Turbo
Author
Current topic

00.00.2012
<
5
>
Sole Provider of a Diesel Engine
Programme from 450 kW to 87,000 kW
4-stroke engines 450 22.000 kW
Comparison
4
29
2-stroke engines 3.000 - 87.000 kW
214
845
(number VW
Golf TDI)
MAN Diesel & Turbo
Author
Current topic

00.00.2012
<
6
>
Areas of Activity
Applications and Market Segments
The product range covers almost all applications in the Upstream, Midstream, Downstream, Industrial
Gases, Power Generation as well as Marine Business.
2
6
4
8
1
5
3
5
7
4
21
10
13
16
9
12
13
19
17
21
21
14
18
22
15
MAN Diesel & Turbo
Author
Deep Sea / Subsea
2
FPSO-Ship
3
Offshore Platform
4
Marine Propulsion
5
Diesel / Gas-Electric
Propulsion
6
Marine Gen-Set
7
Waste-Heat-Recovery (WHR)
System
8
Floating Power Station
9
XTL Plant
(Very Large ASU)
10
LNG Liquefaction
11
Onshore Production
12
Gas Storage
13
Gas Transport
14
Refinery
15
Reactors
16
LNG ReGasification
17
Chemical / Petrochemical
18
Gasification
(Small and Medium ASU)
19
Power Generation
20
Enhanced Oil Recovery
21
CCS
22
Iron, Steel & Mining
20
11
5
1
Current topic

00.00.2012
<
7
>
Sites
Production Network
Frederikshavn
Changzhou
Copenhagen
Aurangabad
Hamburg
Berlin
Oberhausen
Velká Bíteš
Deggendorf
Augsburg
Saint Nazaire
Zürich
Diesel Plants
Turbo Plants
Diesel & Turbo Plant
MAN Diesel & Turbo
Author
Current topic

00.00.2012
<
8
>
Sites
Worldwide Locations (Service Centers/Hubs)
>100 global service centers/hubs in >50 countries
MAN Diesel & Turbo
Author
Current topic

00.00.2012
<
9
>
MDT Standard Technologies
•
•
•
•
SQL Server or Oracle Database
.NET ver. X.X
SharePoint 2007-2013
Various 3rd party frameworks within .NET
• Windows XP/7 OS
• Office 2007/2010
• IE8/IE9
MAN Diesel & Turbo
Author
Current topic

00.00.2012
<
10
>
MAN Diesel & Turbo
Key
Figures 2012
in € Mill.
Order intake
of which: Engines & Marine Systems
of which: Power Plants
of which: Turbomachinery
Revenue1
of which: Engines & Marine Systems
of which: Power Plants
of which: Turbomachinery
Employees2
2012
2011
Change
in %
3,510
3,692
-5
1,296
1,605
-19
668
640
4
1,5467
1,447
7
3,780
3,610
5
1,552
1,670
-7
773
647
19
1,455
1,293
12
14,863
14,039
6
€ Mio
Operating profit
437
460
-23
Of which: Engines & Marine Systems
319
359
-40
of which: Power Plants
-47
-22
-25
of which: Turbomachinery
165
123
42
11.6
12.7
-
ROS (%)
1)
2)
Including consolidation adjustments between the Engines & Marine Systems, Power Plants and Turbomachinery strategic business units.
Headcount (including subcontracted employees) as of December 31, 2012
MAN Diesel & Turbo
Author
Current topic

00.00.2012
<
11
>
SharePoint Environments
Intranet – SharePoint 2010
• Using almost all Services Application e.g. Project Server, Reporting, Access, Manage Metadata,
Performance Point
• Nintex Workflow
• Many customization ~120 solutions – no SharePoint Designer Customizations
Enterprise Search – SharePoint 2013 (under development)
Extranet – SharePoint 2007
• Out of the box
• Few customizations
• Custom admin module
MAN Diesel & Turbo
Author
Current topic

00.00.2012
<
12
>
Key highlights of IT PMM 2.0
Gate
0
Phases &
gates
Objective
Overall
criteria
Deliverable
Gate keeper
Project lifecycle
MAN Diesel & Turbo
Define
Strategic
alignment
Brief
Business
Idea
Application
committees
Plan
1
Project
Agreement
Solution
integration
Decision
foundation
Project
planned
Cost/benefit
approved
2
Application
committees
IT committee
Benefits
proven
3
Project Project
Evaluation
Closure
Updated
Project
Agreement
Building the plan
w. frontloading
Benefit
realisation
Integration is
evaluated
Steering
committees
Author
Gate
4
Finish
Execute
Business
anchoring
Benefits
defined
Gate
3
Gate
2
Gate
1
Steering
committees
Executing
the plan
Current topic
Application
committees
IT committee
Follow-up and plan for
the future

00.00.2012
<
13
>
Four questions need to be answered for all gate
deliverables
Document
creation
Why should we go through with
this project? (e.g. business case)
What are we implementing?
(e.g. deliverables )
How will we achieve this?
(e.g. project plan)
Why?
What?
Risk?
What risks are associated with the
project? (e.g. risk management)
How?
Document
approval
MAN Diesel & Turbo
Author
Current topic

00.00.2012
<
14
>
1. Project Governance
Governance structure and committee scope
Strategy
• Decides the overall strategic direction of MAN Diesel & Turbo and
allocates IT Budget
Executive Board
•
•
•
•
•
IT Committee (ITC)
Application Committees (AppC)
Governance
Committees
Supply Chain
Engineering
Web & Content
Project Steering Committee
Project Owner (chairman)
GI Team Members
BU Team Members
Overall Governance of IT Project Portfolio
Definition of frame for Application Committees
Responsible for IT projects above 500 K€
Approval at Gate 1 (Initial Project Agreement)
Follow-up on Benefit Realisation at Gate 4
• Prioritise project portfolio and recommend BBIs (at Gate 0)
• Responsible for IT projects between 50 K€ and 500 K€
• Approval at Gate 1 and 4
• Group to support realisation of project content
• Acts as Ambassador for the project
• Approval for Gates 2 and 3
• Owns and anchors a specific project in the organisation and is thereby
responsible for the overall success of the project
Project Team
Project
Management
GI Team Members
MAN Diesel & Turbo
• Leads the project organisation and carries out the project according to
the objectives and terms in Project Agreement
Project Manager
BU Team Members
Author
• Deliver defined tasks to achieve objective, scope and milestones
Current topic

00.00.2012
<
15
>
2. Portfolio Management
Project categories (ABCD)
Project category
A
Activity type &
governance group
Major strategic or
large change projects
Cost limit
Above
€500K
Gate 0 decision &
document
IT committee
Application
committee
review
Medium, tactical projects
BBI
Gate 1
decision &
document
Gate 2
decision & document
Gate 3
decision
ITC decision
Initial
Project Agreement
Gate 4
decision & document
ITC decision
Project Closure
StC decision
StC decision
Project Agreement
B
Application committee
Small projects
C
GI management
€50K 500K
€20K 50K
AppC decision
Initial
Project Agreement
GI management
decision
BBI
AppC decision
Project Closure
StC decision
StC Decision
Project charter & TPC
Project Closure
n/a
D
Tickets* &
maintenance**
Below
€20K
Ticket system
processes
n/a
n/a
n/a
CC managers
*
If tickets exceed €20K, the CC manager has to decide if they need to be redefined as projects. The nature of the work is more important for this determination than the cost. Tickets
above €50K must be designated as projects with the according governance.
MAN Diesel & Turbo
Author
Current topic

00.00.2012
<
16
>
Execute – Build Information Architecture
What is our process?
Analysis
Design
User Research
Know your users - Who are the user profiles internal or
external or both? How do they use the application (own
PC, mobile device, kiosk?), what drives the use etc.
Paper or sketch prototype
Give a visual overview of the future solution. To assure
a consistent look-and-feel and optimal visual use of the
application e.g. App or Web
Information Architecture
User Profiles
Kick off workshop
Graphical Design
Interviews
Scenarios
Usability Test
Visual Identity
MAN Diesel & Turbo
Survey
Author
Current topic

00.00.2012
< < 17
17 > >
Tools to help initial workshops
MAN Diesel & Turbo
Author
Current topic

00.00.2012
<
18
>
Business Analysis
What is our process?
April 2010
July 2010
Information architecture
Business analysis – “as is”
Business analysis – ”to be”
Process: Interview &
Workshops
Process: Interviews and input
from Information architecture
Process: Interviews &
Workshops
Iterations
MAN Diesel & Turbo
Author
Current topic

00.00.2012
<
19
>
What happens after Business Analysis
July 2010
Business
Requirements Breakdown
Process: Interview & Workshops
October 2010
Functional & Non Functional
Requirements Breakdown
Technical System
Requirements Breakdown
Process: Workshops based on
prototypes, workflow scenarios or user
stories
Process: Developers Analysis,
Workshops
Iterations and Change control
MAN Diesel & Turbo
Author
Current topic

00.00.2012
< < 20
20
>>
Hands on Experiences
• Going from Photoshop design to real functionality req. description can be very time consuming
• Make Evaluation about how much of the box SharePoint can be utilized:
• Should it developed as standard .NET or inside SharePoint foundation (why and why not)
1. E.g. system with a lot of non document data - outside SharePoint
2. Use of workflow - inside
3. Document centric - inside
• Focus on using the given technologies optimal instead of adding 3rd solutions e.g. know
differences between foundation and enterprise
• Make generic and reusable components
 E.g. download zip applications make one
• Layout changes is a killer and time consuming
MAN Diesel & Turbo
Author
Current topic

00.00.2012
<
21
>
Development Approach
Requirements and packages
All business and functional requirements should be grouped and prioritized by the LoB and Architects
Technical Requirements should be grouped in a packages and overall estimated
Iterative Development Approach
Often done as a combination of classic waterfall and agile development
One approach could be start with Two iterations with demo for the customer and defect handling
Development Iteration 1
Defects
Development Iteration 2
Demo
Process
Delivery Package handed to developer -> Developer estimate (incl. unit test) package and update on a project
site -> Progress on development (remaining hours)
If an estimate exceeds expected hours then it is important to flag it up front
MAN Diesel & Turbo
Author
Current topic

00.00.2012
<
22
>
Development Environment how is our?
•
•
•
•
Developer Machine
Deployment /Test Server
Pre Prod Server
Production Server
How do we ensure all are in sync?
Where do we stored code and which standard are we using?
MAN Diesel & Turbo
Author
Current topic

00.00.2012
<
23
>
Defects, Change and Test Management
Defects/Change Request
TestTrackPro or SharePoint lists
Test cases
Simple test cases developed
MAN Diesel & Turbo
Author
Current topic

00.00.2012
<
24
>
Development Environment optimal
MAN Diesel & Turbo
Author
Current topic

00.00.2012
<
25
>
Do you have any more questions?
Peter Stern
[Contact details]
MAN Diesel & Turbo
Niels Garde
[Contact details]
Author
Current topic

00.00.2012
<
26
>