Why CONSTRAINTS are Good? MATT HARASYMCZUK / WHY CONSTRAINTS ARE GOOD? / SEP 23, 2014 MATT HARASYMCZUK MATTAGILE.com @MATTAGILE #careercon MATTAGILE.com @MATTAGILE #careercon MATTAGILE.com @MATTAGILE A Case Study of an Enterprise Agile Transformation
39
Embed
Why Constraints are Good? A Case Study of an Enterprise Agile Transformation
Agile transformation requires understanding 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?
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Why CONSTRAINTS are Good?
MATT HARASYMCZUK / WHY CONSTRAINTS ARE GOOD? / SEP 23, 2014
Individuals and interactions over processes and toolsWorking software over comprehensive documentationCustomer collaboration over contract negotiationResponding to change over following a plan
That is, while there is value in the items onthe right, we value the items on the left more.
Manifesto for AGILE Software Development
MATT HARASYMCZUK / WHY CONSTRAINTS ARE GOOD? / SEP 23, 2014
• Business Values orientation• Building trust and guidance• Scrum, Lean, Kanban as a communication framework• Project oriented organization• Software Development practices• Quality• Evolution not revolution
RECAP
@MATTAGILE
MATT HARASYMCZUK / WHY CONSTRAINTS ARE GOOD? / SEP 23, 2014