Embed Size (px)
Citation preview
10 AGILE STEPS FOR TECHNICAL EXCELLENCE AND BUILT-IN QUALITYOCTOBER 2019
NIKOLA BOGDANOV
2
TECHNICAL EXCELLENCE AND BUILT-IN QUALITY
3
AGILITY FROM TECH PERSPECTIVE
TECH FROM AGILE PERSPECTIVE
10 KEY POINTS
TO BRAINSTORM
WHAT’S THE PLAN?
4
INTERESTING ABOUT ME
5
SENIOR PROJECT MANAGER
AGILE COACH & TRAINER
TECH BACKGROUND
AGILE ENTHUSIAST AND THINKER
PHD, UNIVERSITY, CONFERENCES, TRAININGS
10+ YRS. IN IT
BORING PART ABOUT ME
6
THE TECHNICAL EXCELLENCE IN YOUR PROJECT?
7
8
WHO ARE THOSE PEOPLE?
9
AGILE IS FULL-STACK
10
AGILE IS FULL-STACK
11
PEOPLE NEED TO BE REMINDED, NOT INSTRUCTED
12
ACHIEVE GREATNESS
… in 10 steps
… as Craftsmen
13
1. WHOLE TEAM MENTALITY
THE PO, THE MANAGER, THE DEV
TEAM, THE CUSTOMER… EVERYONE!
HINT: LISTEN TO THE LANGUAGE
NO ONE CAN WIN THE GAME ALONE
14
2. BUILD ENVIRONMENT FOR LEARNING
PSYCHOLOGICAL SAFETY
CONTINUOUSLY LEARNING
15
WHY ARE WE STILL TALKING ABOUT SOFT-STUFF?
16
3. SYSTEM THINKING
Conway’s Law
“Any organization that designs a system will produce a design whose structure is a copy of the organization's communication structure.”
M. Conway
17
3. SYSTEM THINKING
COMMON SENSE DOES NOT WORK IN SYSTEMS
18
3.1. OOP AND AGILE TEAMS
Encapsulation, Loose
coupling, Strong CohesionSmall cross-functional
teams...
19
3.2. AGILE TEAMS AND MICROSERVICES
https://www.martinfowler.com/articles/microservices.html
20
3.3. BUILD ENVIRONMENT FOR LEARNING
PSYCHOLOGICAL SAFETY
CONTINUOUSLY LEARNING
YOUR SYSTEM WILL:
BE MEANT TO EVOLVE
BE RESILIENT
ACHIEVE TECH EXCELLENCE
21
4. TWO PIZZA TEAMS
22
23
THE COMPLEXITY
24
5. PROVIDE THE PRODUCT VISION
THE ESSENCE OF THE PRODUCT
BUSINESS GOALS
ENGAGES, INSPIRES & MOTIVATES
25
6. BUILD DOMAIN KNOWLEDGE
INVOLVE THE TEAM IN THE BUSINESS DOMAIN
USE THE DOMAIN LANGUAGE
MULTIFUNCTIONAL DOMAIN EXPERT TEAMS
DDD STRATEGIC AND TACTICAL LEVELS
26
7. OBJECT ORIENTED DESIGN
27
8. TACTICAL TECH AGILITY
28
8.1. EXTREME PROGRAMMING
29
8.2. MOB PROGRAMMING
30
8.3. FREQUENT RELEASES, DEVOPS CULTURE & TOOLING
31
9. THINK AGILE
32
9.1. THE TEAM OWNS THE CODE
EMPOWER YOUR TEAMS TO MAKE
DECISIONS FOR THE CODE & QUALITY
MAKE THEM TECH DEBT PRODUCT OWNERS
33
9.2. MAINTAIN A CONSTANT CODING PACE
CODING RHYTHM IS NEEDED
WORK ROUTINES HELP:
DAILY COMMITS, CODE REVIEWS, TDD, BDD, PO DEMOS, SCRUM CEREMONIES
34
WHICH WERE THE STEPS?
1. WHOLE TEAM
2. ENV. FOR LEARNING
3. SYSTEM THINKING
4. TWO PIZZA TEAMS
5. PRODUCT VISION
6. DOMAIN KNOWLEDGE
7. OBJECT ORIENTED DESIGN
8. TACTICAL TECH AGILITY
9. THINK AGILE
35
10. BE CRAFTSMEN
WORKING SOFTWARE IS NOT ENOUGH
BECOME PROUD OF YOUR CODE
36
37
BRAINSTORMING
