Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Truly agile company

1,421 views

Published on

We talk a lot about managing an agile team, agile transformations and about Scrum, Kanban, TDD, CI, small nimble companies about building positive motivation.

It's all a set of beautiful buzzwords. A lot of people make living coaching and helping to make transformations. But as it comes to real work in the companies - reality rarely resembles beautiful stories from trainings. Why?

An attempt to answer this question is model "Truly Agile Company", which is trying to catch the complexity of the transformation of the company. An attempt to capture the key roles and aspects often overlooked by the "Dogmatic Agile."

Let's try to think about:
• What is the "Pragmatic agile"?
• How to work effectively with all key aspects of Agile transformation?
• How not to get lost?
• How to work with people and build on their potential for change?

Published in: Technology
  • Be the first to comment

Truly agile company

  1. 1. Truly Agile Company @marekkirejczyk
  2. 2. Challenge ● Growth ○ From 30+ to over 100 in a year ○ From 60 to almost 200 in a year ● Almost 20 initiatives ● Wide technological landscape ○ Web development (ruby on rails) ○ Python ○ Data science ○ Mobile: iOs, Android
  3. 3. Pragmatic vs. dogmatic
  4. 4. 5 key aspects of Agile/Lean management Team Technical Product Management People
  5. 5. Team
  6. 6. Team - general problem ● Who is working on what? ● When will we deliver? ● What is the progress? ● Slow
  7. 7. Team - Malpractice ● Process “mastrubation” ● Management destroys our process
  8. 8. Team - tools ● Scrum shock therapy as a start then Minialistic Viable process ● Communication to management and reporting
  9. 9. Technical
  10. 10. Technical - problem ● Low quality code ● Technical debt ● Slow development
  11. 11. Technical - malpractice ● Hype driven development ● Over engineering ● Over design
  12. 12. Technical - tools ● TDD ● CI ● Devops ● Feature flags
  13. 13. Technical - tools ● Pair programming ● Spikes ● Hackathons ● Tech meetings
  14. 14. Pair programming
  15. 15. Hackathons ● Product in a day ● Feature hackathon ● Technology ● Hardware ● Lego Storm wars
  16. 16. Learning ceremonies ● DoJo’s ● Retreat’s (CodeWars) ● Hackathons ● Trainings ● Tech talks
  17. 17. Software craftsmanship vs. lean startuper
  18. 18. Example
  19. 19. Product
  20. 20. Product Skill
  21. 21. Corporate vs. Lean PO
  22. 22. Corporate vs. Lean PO
  23. 23. Example
  24. 24. Management
  25. 25. Management ● Goals setting ● Control ● Alignment ● Decision making
  26. 26. Management ● V2MOMs ● 1 on 1s ● Feature teams
  27. 27. People
  28. 28. People problems ● Low motivation ● Lost in ○ Process ○ Direction ○ Purpose ● Lack of ○ Skill development ○ Appreciation ○ Finance satisfaction
  29. 29. People tools ● Pink’s 4 pillars ● Brainwashing ● 1 on 1s ● Tribal Leadership ● Team building ● On boarding and exit interview ● Recruitment and Employer branding
  30. 30. Brainwashing ● Process ● Philosophy ● Values
  31. 31. Agile company
  32. 32. Questions? @marekkirejczyk

×