Implementing an end-to-end application lifecycle management (ALM) solution is a challenge. Some people think that it is impossible, but they are wrong. IBM and Premium Technologies did it successfully for Poland's Ministry of Finance. Premium Technologies implemented a comprehensive application development platform based on the IBM collaborative lifecycle management (CLM) platform, modeling, development and testing solutions, and determined how to enhance internal IT processes to improve time to market, quality and innovation. The result is a unique solution for documenting the Ministry's SDLC processes, which is based on IBM Method Composer (for process definition) and IBM CLM.

1. About Us
• Premium Technology Poland is a group
of business practitioners with many years
of international experience. We combine
practice with the latest business
knowledge, which we are continually
updating and enriching with real
experience stemming from the ventures
and projects we’ve participated in. This is
how we produce innovative solutions in
the form of deployment solutions, advice
and consulting, training and specialized
coaching
1
• Business Partner Lead Model
• Value Advantage Plus
• Authorized Managed Service Provider CEEMA
• Gold Services Provider CEEMA
• ITBM Business Partner Advisory Group Member
• Software Engineering
• Project and Portfolio Management

2. Case ZPWO – Ministry of Finance in Poland
2

3. • Modernized Software Development Process (ZPWO) is a
practical and working process that standardizes the way:
– Software development by teams of the Ministry of Finance
– Cooperation and communication with external suppliers, building
software for the Ministry of Finance
– Verification of ordered software with needs and requirements
for different project stakeholders
• This process is supported by
friendly tool environment,
that simplifies and automates everyday
work in IT projects
What is it ZPWO?

4. Key business requirements for ZPWO project
4
Improving cooperation between the Ministry of Finance with software vendors:
• Improving and standardizing communication between the contractors and the Ministry of
Finance through the implementation of a uniform software development process.
• Support the internal flow of information in the field of gathering requirements, creating
architecture, designing, implementing, testing and acceptance of information systems.
ZPWO variants (how Ministry of Finance is delivering projects):
• Development of a new system or a new system release (internal supplier)
• Development of a new system or a new system release (external supplier)
• Development of a new system or a new system release - SOA Architecture (internal supplier)
• Development of a new system or a new system release - SOA Architecture (external supplier)
• Purchase of software such as COTS
• Implementation of ad-hoc changes (fast track)

5. Customer expectations for the project
5
The expected outcome of the project in accordance with the Modernized Software Development
Process (ZPWO) is readiness for implementation in the Ministry of Finance software that:
• Implements business needs defined by future users and other stakeholders
• Will be purchased (COTS software) or designed and manufactured by the realization team of the
Ministry of Finance or external supplier,
• Is consistent with the defined acceptance criteria and the quality criteria of all stakeholders (including
system users, administrators, support department and those responsible for information security),
which has been confirmed by appropriate tests.
• Has been documented in a way that allows the installation, configuration, and make it available for
final users,
• Has been documented in a way that allows its care and development (if allowed by the license
conditions).
Modernized Software Development Process (ZPWO) assumes to create or acquire any specialized
products, which are necessary to achieve listed objectives.

6. ZPWO - Overview
Agreed scope
Defined architecture
Completed
functionality
Ready for
production
Satisfied
stakeholders
Persuaded
objectives
Business
Needs
Requirements
System release
Management process
(planning, monitoring, management)
ZPWO
Inception TransitionConstruction (development / purchase )
Execution
formula
High level
architecture /
standards
Team (entry)
Project documents
(optional)
Development
Environment
System release
(ready for acceptance tests)
Specialized products
(depending on the variant)
Software
development
plan

7. ZPWO – Standards and software dev methodologies in MF
ITIL
Architecture and
system design
documentation
Business process description,
requirements specification
Iteration plan
(development,
quality assurance,
Deployment itd.)
Service descirption
Enterprise Architecture (TOGAF)
Program Management / Portoflio Management
Project Management (PRINCE2)
Information about
velocity,
available resources
and project health
Deployment
and
exploatation
documentation
Architecture standards
and recommendations
(incl. SOA)
Transition
Exploatation and maintanace
ConstructionElaboration
Report
(project status) System release
Project
plan
Software Development (ZPWO)
Initative
Business needs/
Change request or
defect

8. Process Portal – all You need in one place
ZPWO Home Page
Disciplines
perspective
Roles
perspective
Tools
perspective

9. From process to execution
9
Process Execution
Feedback
Execution

10. Deployment Architecture
10

11. Customer feedback and business results
• The progressive integration of projects and initiatives
• Standardization of agreements with suppliers on compliance with the process ZPWO
• Positive control of the project by the Supreme Chamber of Control
• First completed project – „Tax advisor”
• Documenting already existing system Trezor ($82 mln)
• The aim of TREZOR 3.0 is to improve the exchange of information between
administrators of budget funds and the Ministry of Finance in the execution of the
following budget processes:
– planning the state budget, which aims to develop the budget bill and financial plan,
– executing the state budget, involving the transfer of funds for spending, state budget liquidity management and accounting management
of the state budget,
– budget reporting, which is drafted and submitted periodic reports of budget funds from the state budget execution,
– preparing reports for the management, including generation of all reports on the planning and execution of the state budget.
11

12. Project statistics
• 10 software development disciplines
• 6 variants of software development process (ZPWO)
• 200 detailed process activities
• 23 software developemnt roles
• 53 developed arttifacts, document templates, listy kontrolne
• 130 tools guidelines (in Polish)
• Integration of ZPWO with 6 currently in force standards
• ZPWO currently contains more than 3300 HTML pages, 5500 files and
it requires more than 100 MB of storage.
12

13. Questions and answers
13
Piotr Kowalski
Vice Chairman Of The Board Premium
Technology Polska
pkowalski@PremiumTechnology.pl
Linkedin:
https://pl.linkedin.com/in/kpiotr
Bartosz Chrabski
WW Competitive Team – DevOps
Leader
bartosz.chrabski@pl.ibm.com
Linkedin:
https://www.linkedin.com/in/bchrabski
Twitter: @bchrabski

14. Thank You
Your Feedback is Important!
Access the InterConnect 2016 Conference Attendee
Portal to complete your session surveys from your
smartphone,
laptop or conference kiosk.