Using PMBOK and Agile approaches to gain the best effectiveness in IT projects.

1. IT PROJECT:
COMBINING PMBOK® AND AGILE
Danil Dintsis
Ph. D., PMP®, EXIN® accredited trainer
consult@Dintsis.org
info@i-mokymas.com
dinzis@specialist.ru

2. BRIEF ABOUT THE PRESENTER
 Ph. D. in System Analysis (Doctorate degree)
 Ph.D. in Technical management
 Portfolio manager and IT consultant, teacher and coach for 15+
years with the following certifications:
 PMP®
 EXIN accredited trainer for ITIL®, MOF®, Cloud computing, Operation
services and Analysis (OSA®)

3. EXTENDING PM FOR IT PROJECTS

4. WHAT IS THE GOAL OF THE PRESENTATION
How ITSM
may help us?
How should we
Work together
What shall I do
with my IT people
What are our
common goals

5. IT PROJECT AS
A PART OF IT SERVICE LIFECYCE
Measurable targets
for IT
IT supports
Main business
IT as a Service
Business-IT
alignment

6. HIERARCHICAL MODEL

7. MSF EXAMPLE OF AGILE PROCESS MODEL
Project plan
approved
Out of
Developme
nt
Release Readiness
Review
Deployment
Milestone
Vision approved
Build

8. Time
Functionality
Agile may be integrated to minimize threats
Release 1
Release 2
Release 3
ADAPTIVE MODEL

9. INTEGRATED PROJECT LIFECYCLE MODEL

10. STEP1. ALIGN BUSINESS AND IT PORTFOLIO

11. WHAT IS IT INFLUENCE
ON MAIN BUSINESS PROCESSES
 Does your company have IT services with direct impact on sales, productivity, etc?
 Are there any business services critically dependent on IT?

12. CREATE VISION – DEVELOP A PROJECT CHARTER
 Business Case
 Project Charter
 Project Stakeholder Register and Analysis Matrix

13. STEP 2. IT SERVICE REQUIREMENTS

14. FEASIBILITY RESEARCH
 Goals
 Research sources (2-3)
 Share responsibility amongst core team members
 Provide research. Fix results
 Discuss results, create united feasibility plan
 Decide go/no go

15. FEASIBILITY PLAN
 Executive Summary – brief for CxOs
 Product Scope
 Technical constraints
 Organizational constraints
 Audience Impact (Users, Customers, business processes)
 Financial obligations (-15 - +25%)
 Recommended actions
 Go
 Additional research
 Non-IT decision
www.i-mokymas.com

16. INTEGRATE ADAPTIVE CYCLE
www.i-mokymas.com

17. INTERNAL ADAPTIVE CYCLE
www.i-mokymas.com

18. ITERATION ATTRIBUTES

19. ADAPTIVE MODELS
 Increment planning for 1 – 30 day period
 Customer representatives and team members mutual
involvement
 Small teams for each package (no more than 10 members)
 Project teams are built as a set of such small teams
 Each team member involves only in a single project during a
single iteration
 Each small team includes both general and specialized
experts

20. WBS AMMENDMENTS

21. CUMULATIVE DIAGRAMS (CFD)
http://i-mokymas.com

22. ADDITIONAL ADAPTIVE TOOLS
 Release and iteration plans
 Information radiators
 Team productivity
 Historical productivity
 Team on-line collaboration tools
http://i-mokymas.com

23. SCRUM BOARD AS
AN INFORMATION RADIATOR

24. THANK YOU!
 .
 www.i-mokymas.com
 info@i-mokymas.com
 https://www.facebook.com/ismanusism
 https://www.researchgate.net/profile/Danil_Dintsis

LET’S STAY IN TOUCH