NANBAN Agile practice
This blog is about a sample organization called Agile-Lean Organization XYZ and its agile transformation and agile adoption...
One day a Team Manager was having a discussion with one of his Development Team Member and found that he has developed an Agile Practice called as "NANBAN" which the Manager and Developer currently discussing...
Part1: Gradual adoption of agile practices
"Manager": Why do you want to create another agile practice?
"Developer": I see that we are missing the importance of agile values and principles and a practice that inherits existing framework/practice like Scrum, XP, Lean, Lean/kanban attributes and helps to build a practice that is best suited for our team in a gradual and customized transformation!
"Manager": Seems interesting, but I am not fully understanding still, why you would need another practice? I feel there are enough practices and practices related confusion about following and not following or selecting only one practice and ignoring other practices..
"Developer": That's exactly correct! So, let me ask you a question, Do You think my team has understood the agile values and principles and they have fully utilized Scrum Framework?
"Manager": No, I don't think so, in both questions.. neither values and principles nor Scrum utilization. But, don't you think they are a new team and all are having different experience level, and not a pure development team! Huh! I think I am able to connect some dots here and there, but I would like you to explain me more about your thought process, and be ready for a detailed feedback of mine!
"Developer": Yes, you are absolutely right and we are nearing to a good discussion and connecting the dots. The problem with agile practices adoption and agile transformation is not about selecting practices, training, coaching and managing.. it is more about the team's ownership to time-to-market and business-value delivered by their own team-level practices inheriting what they can fully understand themselves by combining all the required practices for their team without leaving any elements of (agility) the practices like Scrum, XP, Lean/kanban, DSDM, FDD, DevOps and more, in a gradual step-by-step approach rather than big-bang approach with organization level impediments. Most of our team members would like to get a process first than a practice, they are not clear to follow the agile practices or not ready with the mindset change and they don't even have time to look at the agile values and principles, various practices and their purpose, not focused to experiment and apply some of the fundamental concepts to their day-to-day work!
"Manager": Sorry, I am really Sorry about that! Yes, please explain more about this "NANBAN" practice!
"Developer": That's ok. Sure, let us have coffee first :)
To be continued...