Matt Harasymczuk
From MattAgile.com
Hi my name is Matt and I am a Agile Coach, Speaker and Pilot. I do believe in Agile philosophy as a people and interactions and culture based on trust.
I help solving problems with Agile Software Engineering and embracing Scrum, Kanban, Lean, XP, Gamification, DevOps processes: CI, CD, Quality, ChM, RM, BDD, TDD, Risk Management and GIT.
Blog: http://mattagile.com
Methodology & DevOps
Case Study: Agile @gov.pl
Agile transformation requires understanding of its rules by management. It is hard to leave status quo and change your way of thinking. It is especially hard when the previous model has been in use for many years. A frequent problem with Scrum / Kanban / Lean transformation is to go hard on deep water. Starting tommorow we're doing Scrum. Lack of understanding, communication chaos and rules distortion "just because daily is not working for us". What if take a different approach: slow and prudent? Let say iteratively. Gradually introduce another steps of chosen framework. However the question persists. How to effectively change our conservative organization into agile and constantly changing in response to business needs company?