Євген Лабунський: agile in enterprise. how do we do it
TRANSCRIPT
Agile in EnterpriseHow do we do it?
About
10 years in IT7 years on a management position5 years of Agile experience
Who we are?
What is Enterprise?
• High Level of Development Complexity• Architecture Planning• Risk Management• Integration, integration, integration• Complex Deployment• Complicated Communications• Bureaucracy & Politics
Traditional Project Management
XP Technics
Development by Iteration
Lean
1994 1996 1998 2000 2004 2006 2009 2011 2012 2013 2014 20150%
5%
10%
15%
20%
25%
30%
35%
40%
16%
27%26%
28%29%
35%
32%
29%
27%
31%
28%29%
Agile is the mindset. We use Scrum as tool, as well as XP technics, Lean practices and Traditional Management approach
We name it Adaptive
Project Lifecycle
PreparationHow do we kick-off development
Project Initiation
Business Idea Project Charter Approval
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
Release Planning - Overview
Release Planning - Phases
Architectural Planning
High Project Complexity
Development Final Testing Deploy
2 Weeks SprintContinuous TestingContinuous Integration
IntegrationPerformanceLoadFailover
CI/CD
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
Working with Requirements
Product Owner:• Writing up Features• Verify Stories Description• Prioritize Defects• Work with Business
Team:• Creates Stories• Provide Estimation• Groom Defects/Stories
Working with Requirements - Levels
Levels:• Feature – full functionality is going to be developed• Story – small part of Feature• Task – low level Dev/QC work
Development Lifecycle
Life in Sprint - Lifecycle
Sprint Planning – Estimations
User Storiesin Story Points
Tasksin Ideal Hours
Sprint Planning – Work Load
Sprint Execution
Burndown
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
Automation and Testing in Sprint
Unit Tests
Integration Tests
UI Automation
Manual Run
Automation Run & Quality Gate
Unit Test Smoke+ + SonarQube
Production Delivery
Testing Types in Delivery
• UI Automation: Smoke, Functional, Integration• Performance Testing• Stress Testing• Failover testing• Manual Regression
Continuous Delivery (?)
Now the process contains a lot of approval steps
Next Steps
Production Delivery Every Sprint in 3 monthsFeature-by-Feature Production Delivery in 6 monthsCompany Agile Transformation - SAFe
Thank you!
