Refocus on the agile developer

18/09/2020 #AgileTourSophia (par @AgileTourSophia) 1
Refocus On The Agile
Developer
Sandor DARGO
Agile Tour Sophia Antipolis
10ème édition – 18 septembre 2020

Merci aux Sponsors !

• Port du masque
obligatoire sur tout le
campus SophiaTech y
compris orateurs
– Intérieur (amphi, salles,
couloirs…)
– Extérieur (stands
sponsors…)

• Nettoyez vos mains
avec le gel hydro-
alcoolique en entrant
et en sortant de
chaque session
• Gardez vos affaires
avec vous
• Mettez vos déchets
dans la poubellePort du masque obligatoire

Developer
Sandor DARGO

Key points
Agile was made by developers for development
How we forgot about the developers
Recap on some agile developer practices

Agenda
The History of Agile
Agile Practices
What Practices Do We Use?
Some Technical Practices in Detail
Conclusion

Who am I?
Sándor DARGÓ
Software developer in Amadeus
Enthusiastic blogger
Creator of Daily C++ Interview
Curious home baker and cook
Happy father of two

The history of Agile
Made by developers for development

What brought us agile?
Application delivery lag
Met irrelevant requirements
Clearly unmet needs

Where does Agile come from?
Iterative development methods since 1957
Adaptive software development starting in the 70s
Lightweight methods emerging in the 90s
And then...

What do the numbers say?
2001/45/17/12/4
In 2001
In the 45th State of the USA
(Utah)
17 developers
Wrote the agile manifesto
with 12 principle
Around 4 values

The 4 values
Individuals and Interactions over processes and
tools
Working Software over comprehensive
documentation
Customer Collaboration over contract
negotiation
Responding to Change over following a plan

The 12 principles
Customer satisfaction by early and continuous delivery of valuable software.
Welcome changing requirements, even in late development.
Deliver working software frequently (weeks rather than months)
Close, daily cooperation between business people and developers
Projects are built around motivated individuals, who should be trusted
Face-to-face conversation is the best form of communication (co-location)
Working software is the primary measure of progress
Sustainable development, able to maintain a constant pace
Continuous attention to technical excellence and good design
Simplicity—the art of maximizing the amount of work not done—is essential
Best architectures, requirements, and designs emerge from self-organizing teams
Regularly, the team reflects on how to become more effective, and adjusts
accordingly

Agile practices

What Agile Practices Do You
Know?
Form groups
Collect the Agile Practices
Grouped into 3 categories
Project Management Tools
Development Practices
Other

Agile Project Management
Tools
Backlogs
Cross functional teams
Daily stand-ups
Planning poker
Retrospective
Scrum events
Timeboxing
User story
Velocity Tracking

Agile Development practices
ATDD
BDD
DDD
TDD
Iterative and incremental development
Specs by example
Pair programming
Refactoring
Timeboxing
Agile modelling
Agile testing
Story driven development

Other Agile Practices
CI/CD
Low-code development platform

What Practices Do We Use
Actually?

Let's collect them
Go back to groups and collect them

The result is...

What trainings do we usually
have?
Agile awareness
Agile Scrum
Agile Kanban
Agile and Scrum fundamentals
Agile project management
Agile Certified Product Owner
Agile Certified Scrum Master
...
But where is the Agile (Certified) Developer?

Some useful technical practices

Timeboxing
Can be used for processes and for development
Timeboxing as a process
Demo
Retrospective
Planning
Daily

How to timebox the daily standup?

The usual three questions
What did I do yesterday?
What will I do today?
Do I see any impediment?

The better three questions
What have you completed since the last
meeting?
What do you plan to complete by the next
meeting?
What is getting in your way?

The even better three questions
What did you achieve yesterday that helps us to
meet our Sprint Commitment?
What will you do today to help us meet the
Sprint Commitment?
Do you have any impediment/blocking point
that is preventing us from meeting our Sprint
Commitment?

Timeboxing
Timeboxing as a developer practice
Pomodoro technique
Give shorter deadlines to yourself as wanted
Set weekly goals
Track what you spend your time on
Use the time for the other activities

Pair (or mob) Programming
Social exercise
Awesome tool to level knowledge
Better focus
Less bugs
Does not slow down in the long run

Use it for tricky problems!
Timebox it!
Change roles frequently enough
(driver/navigator/mob)
Agree on the rules
Get a first thorough code review “for free”
Pair (or mob) Programming

Iterative and incremental
development
Don’t be afraid to overuse it!
The heart of agile
Deliver small vertical slices
That deliver value
And then start over

Conclusion
Agile was created by the developers for
development
From a framework, we created a pile of
processes
If the agile process transformation hasn't
worked without help, how could we expect that
with the agile development?

Call To Action
Introduce agile development practices in our
teams
Raise our voice when we need help
Use the help of our experts, our technical
mentors and even our agile coaches

Developer
Sandor DARGO

Refocus on the agile developer

Recommended

Recommended

More Related Content

Similar to Refocus on the agile developer

Similar to Refocus on the agile developer (20)

Recently uploaded

Recently uploaded (20)

Refocus on the agile developer