Our industry has a problem: We are not lacking software methodologies, programming languages, tools or frameworks but we need great software engineers.
Great software engineering teams build quality-in and deliver great software on a regular basis. The technical excellence of those engineers will help you escape the "Waterfall sandwich" and make your organization a little more agile, from the inception of an idea till they go live.
I will talk about my experiences from the last 15 years, including small software delivery teams until big financial institutions.
* Why would a company like to be "agile"?
* How can a company achieve that?
* How can you achieve Technical Excellence in your software teams?
* What developer skills are more important than languages, methods or frameworks?
----
What is the difference between Agile and Business Agility? I will use this as an intro exercise.
---
What is "Business Agility"? Why is Agility important? What is Software Craftsmanship?
What can we do to improve our Technical Excellence?
https://beyond-agility.com
What are the key points to focus on before starting to learn ETL Development....
You Cant Be Agile If Your Code Sucks (with 9 Tips For Dev Teams)
1. You Cant Be Agile If Your
Code Sucks
(with 9 Tips For Dev Teams)
Peter Gfader
twitter.com/peitor
2. Abstract
Our industry has a problem: We are not lacking software methodologies, programming languages, tools
or frameworks but we need great software engineers.
Great software engineering teams build quality-in and deliver great software on a regular basis. The
technical excellence of those engineers will help you escape the "Waterfall sandwich" and make your
organization a little more agile, from the inception of an idea till they go live.
I will talk about my experiences from the last 15 years, including small software delivery teams until big
financial institutions.
Why would a company like to be "agile"?
How can a company achieve that?
How can you achieve Technical Excellence in your software teams?
What developer skills are more important than languages, methods or frameworks?
----
What is the difference between Agile and Business Agility? I will use this as an intro exercise.
---
What is "Business Agility"?
Why is Agility important?
What are 4 essentials skills of Software Teams?
What is Software Craftmanship?
What can we do to improve our Technical Excellence?
https://beyond-agility.com
11. What is your current pain? What I heard...
• Lack of Innovation
• Operational issues
• Not working with My people
• No time for improving
• Too slow
• Late delivery
• Too little visibility
• Too many dependencies to manage
• Poor morale
• Too many issues in production
• Timelines not predictable
• Morale is low
• Problems discovered too late
• Hiring great people
• Competition
• Low Employee satisfaction
• People very busy certain time,
certain time team is over or understaffed
• They have the wrong Mindset
• Quality is low
• Feedback is very low and late
• Lack of know how
• Too many regulations, ISO, laws, compliance rules
27. Agile ... Why?
lt's not about doing more work in less time:
Agile is about working smarter, rather than harder.
lt's about generating more value with less work.
→ particularly more monetizable value with less work.
Steve Denning https://businessagility.institute
29. "Operational Agility"
How quick can we
deliver value
(in the form or a Product/Feature)
to changing
demands from the
market?
https://www.forbes.com/sites/stevedenning/2018/01/28/what-is-strategic-agility/#52f42dcda0b1
30. „Strategic Agility“
How quick can an
organisation
improve its competitive
position
& create opportunities
for growth.
https://www.forbes.com/sites/stevedenning/2018/01/28/what-is-strategic-agility/#52f42dcda0b1
36. “We are seeing more change in the next 15 years
than in the last 15 years.
The big question is always,
do we car manufacturers learn to become tech
companies more quickly than a tech company learns
to be an automotive player?”
Peter Schwarzenbauer – Aug 2017
BMW management board
https://www.nytimes.com/2017/02/08/business/germany-bmw-daimler-volkswagen-uber.html
37.
38. “We are seeing more change in the next 15 years than in the
last 15 years.
The big question is always,
do we car manufacturers learn to become tech companies
more quickly than a tech company learns to be an automotive
player?”
Peter Schwarzenbauer –
BMW management board
https://www.nytimes.com/2017/02/08/business/germany-bmw-daimler-volkswagen-uber.html
40. What is your current pain? What I heard...
Skills
• Lack of Innovation
• Operational issues
• No time for improving
• Too slow (Late delivery)
• Too many dependencies to manage
• Quality is low
• Lack of know how
People
• Poor morale
• Hiring great people
• People very busy certain time,
certain time team is over or understaffed
• Mindset problem? Tools & Know How is there
Competition
• Customer is gone
• Market share decreases
Self Awareness
• Too little visibility
• Problems discovered too late
• Lack of Innovation
• Feedback is very low and late
46. „Scrum says“
„This is not Agile“
„Let‘s do this in an agile way“
„XP recommends …“
„In the SAFe book its written“
„This is not Lean enough“
„You must be co-located for XP“
„Let’s make this transparent by
putting it in wall”
“We are iterative and adaptive”
„Customer“
„User“
„Risk“
„Market“
„Competition“
„Value“
„Produkt“
„Sponsor”
„Money”
#moreContent
Stop Start
https://beyond-agility.com/stop/
47. „How do we
become
agile?“
How can we
discover and
deliver Value
faster?
What is Value in our Organization? Product?
https://beyond-agility.com/stop/
71. #TODO: Review Code
• In your team
• With 1 peer
• Open source
• Brown bags – Lunch time discussion
72. #TODO: Better Code Reviews
• Code, !Person
• Constructively propose changes
→ Questions!
• Review not only code
o Tests
o Build process
o ..
→ Grow as a team
73. Instead of
“That ugly long method”
“I reviewed your code and
found 1,2,3 things to
change”
“If you don’t want to do it. I
do it”
“Why don’t you split that
method”
“Can you help me?”
“Can I help you with this? I
think we can improve it”
Say
#TODO
74. 3. Hypothesis For Bad Code
Nobody can write good code in 1 sit-in.
There is no “Right the 1st time”
75. 3. Hypothesis For Bad Code
Nobody can write good code in 1 sit-in
→ Refactoring
95. • Steve Denning 3 Laws of Business Agility
https://www.infoq.com/presentations/3-laws-business-agility
• Steve Denning – Why Agile
https://businessagility.institute
• Future Leadership Training
• Haier HBR – The end of bureaucracy
https://hbr.org/2018/11/the-end-of-bureaucracy
• Book: The Leader's Guide to Radical Management
http://www.stevedenning.com/Books/radical-management.aspx
References
96. References
• Pragmatics of Agile Development
http://www.agiledeveloper.com/presentations/pragmatics_of_agile_development.pdf
• Kanban VS Scrum
http://www.infoq.com/minibooks/kanban-scrum-minibook
• Agile Software Development
http://www.agiledeveloper.com/presentations/AgileSoftwareDevelopment.zip
• A Thinking Tool called Agile
https://sites.google.com/site/leanagileandscrum/lean-agile-scrum-conference-
2010/presentations-las-2010/00_Kniberg_Keynote.pdf?attredirects=0&d=1
• The Four Elements of Simple Design
http://www.jbrains.ca/permalink/the-four-elements-of-simple-design
• http://agilemanifesto.org/
• http://manifesto.softwarecraftsmanship.org/