What is an Agile Mindset, and how can it help you? Why are we still 19 years after Agile Manifesto still focusing on frameworks instead of the mindset? An example on how the agile mindset helped SSAB (Swedish Steel manufacturer), and the steps made for creating lots of value instead of focusing on frameworks, estimates and time plans

1. An Agile Mindset
Established great value for SSAB
Peter Sandberg, Agile Coach
LearningWell
peter.sandberg@learningwell.se

3. Scrum’s roles, events, artifacts, and rules are immutable and
although implementing only parts of Scrum is possible
The result is NOT Scrum

4. Scaled Agile Framework (SAFe)

5. Do not treat frameworks as the holy bible!

7. Agile Manifesto
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
Why the huge focus on
frameworks?
Why are we looking for
a Scrum Master
Why do we call it
”Scrum Teams”

8. Communicate and Collaborate
Deliver Value
Embrace changes
Continuous Improvments
Failure opportunity to learn

9. Protect your mindset.
Not your framework or process

10. An Agile Mindset helped

12. Replace old process monitoring systems with
new architecture technique in an agile
context

15. Everbody can do everything
Minimize handovers
Strengthen eachothers competence
Create pleasent environment
Colocated
Create a super sharp TEAM

16. Introduce Continuous Delivery
Push
Build
Unit
Test
Package
Deploy
Test
System
Test
Deploy?

17. 10 teams
Monolith
250 000 lines of code
Amounts of manual tests
Cultural changes
Introducing Continuous Delivery
1 team
0 lines of code
New team = No defined culture

18. Corner-stones in Continuous Delivery
Unit Tests
System Tests
Installations
Database-scripts

19. Top-prio
How do we feel?
Helicopter view
Plan when empty!
No sprint-plannings
Visualize flow and status

20. Visualize Pipeline and Production
Error in Pipeline
Error in production

21. Continuous Improvements

22. Trust – A success story

23. We need
feature X.
Can you
assist?
Of course!
We solve it
together!

24. Traditional
Functionality
Time Resources Value for user
ResourcesTime
Agile
Fixed
Flexible

25. Product X
Product Y
Product Z

26. ToDo Ongoing Done
Backlog

27. ”Double”-implementation
Forgot to write tests!
Production-crashes
Missinterpretet customer and
delivered wrong feature

28. We forgot to Communicate and Collaborate!

29. So we have not
1 Implemented any framework
2 Had any Product Owner
3 Done any Estimates

30. The result
1 Live within budget and deadline
2 Happy customer that wants more!
3 Dedicated team handling more products!

31. Agile Mindset
Dedicated team
Trust
Continuous Delivery
Close to Business
Success factors!