The document discusses how to implement agile practices in an enterprise setting. It describes using a combination of Scrum, XP techniques, lean practices, and traditional project management adapted to the enterprise context called "Adaptive". Key aspects include architectural planning, risk management, integration testing, continuous delivery, and working with complex requirements and stakeholder needs across multiple releases. The goal is to deliver working software in short iterations while managing the increased complexity of enterprise projects.

1. Agile in Enterprise
How do we do it?

2. About
10 years in IT
7 years on a management
position
5 years of Agile experience

3. Who we are?

4. What is Enterprise?
• High Level of Development Complexity
• Architecture Planning
• Risk Management
• Integration, integration, integration
• Complex Deployment
• Complicated Communications
• Bureaucracy & Politics

5. Traditional Project Management
XP Technics
Development by Iteration
Lean

7. 16%
27%
26%
28%
29%
35%
32%
29%
27%
31%
28%
29%
0%
5%
10%
15%
20%
25%
30%
35%
40%
1994 1996 1998 2000 2004 2006 2009 2011 2012 2013 2014 2015

9. Agile is the mindset.
We use Scrum as tool, as well as XP technics,
Lean practices and Traditional Management approach
We name it Adaptive

10. Project Lifecycle

11. Preparation
How do we kick-off development

12. Project Initiation
Business Idea Project Charter Approval

13. Project High Level Planning
Initial Plan Includes:
• Identify Project Steps (Releases)
• Identify Goals for Steps
• Set Approximate Dates
The Goal is to get from Business when they would like to see each step

14. Release Planning - Overview

15. Release Planning - Phases
Architectural Planning
High Project Complexity
Development Final Testing Deploy
2 Weeks Sprint
Continuous Testing
Continuous Integration
Integration
Performance
Load
Failover
CI/CD

16. Architectural
Planning
Proof-of-Concept Approach
• Gather with Team
• Agree Approach
• Make it as much
independent as possible
• Approve approach
• Make PoC and prove it
works

17. Working with
Requirements
Product Owner:
• Writing up Features
• Verify Stories Description
• Prioritize Defects
• Work with Business
Team:
• Creates Stories
• Provide Estimation
• Groom Defects/Stories

18. Working with Requirements - Levels
Levels:
• Feature – full functionality is going to be developed
• Story – small part of Feature
• Task – low level Dev/QC work

19. Development Lifecycle

20. Life in Sprint - Lifecycle

21. Sprint Planning – Estimations
User Stories
in Story Points
Tasks
in Ideal Hours

22. Sprint Planning – Work Load

23. Sprint Execution
Burndown

24. Development Rules
• Everything possible need to be covered by Unit Test
• All defects need to be automated
• Main Flows should be covered by Integration Tests and Automation
• Test cases need to be written together with Requirements testing
• Development in Feature Branch
• Quality Control on merge

25. Automation and Testing in Sprint
Unit Tests
Integration Tests
UI Automation
Manual Run

26. Automation Run & Quality Gate
Unit Test Smoke+ + SonarQube

27. Production Delivery

28. Testing Types in Delivery
• UI Automation: Smoke, Functional, Integration
• Performance Testing
• Stress Testing
• Failover testing
• Manual Regression

29. Continuous Delivery (?)
Now the process contains a lot of approval steps

30. Next Steps

31. Production Delivery Every Sprint in 3 months
Feature-by-Feature Production Delivery in 6 months
Company Agile Transformation - SAFe

32. Thank you!

33. Lets be in touch!
IN: ua.linkedin.com/in/labunskiy
Mail: labunskiy@outlook.com
FB: facebook.com/labunskiy