Agile Manifesto signatories' reunion to celebrate its 10th anniversary was... Educational?
It was encouraging to hear them saying that they won;t change anything in the Manifesto, 10 years later.
Not too many cultural artifacts can boast of retaining their relevance for so long.
But it was even more thought-provoking to hear what they think we've done wrong during these years.
And for me, one of the most important lessons was that the Agile methodologies like Scrum or Kanban define rhythms and processes, but not craftsmanship techniques.
That is to say, the team may have backlogs, sprints and reviews, as mandated by Scrum definitions - but they'll never be truly Agile, nor will they be professional craftsmen if they don't follow the XP techniques (CI, TDD, clean code).
So, my tiny epiphany on this subject was that these parameters (methodology and techniques) are orthogonal.
Next time I'm asked what is it we're doing, my answer will be: Scrumban with XP.
It was encouraging to hear them saying that they won;t change anything in the Manifesto, 10 years later.
Not too many cultural artifacts can boast of retaining their relevance for so long.
But it was even more thought-provoking to hear what they think we've done wrong during these years.
And for me, one of the most important lessons was that the Agile methodologies like Scrum or Kanban define rhythms and processes, but not craftsmanship techniques.
That is to say, the team may have backlogs, sprints and reviews, as mandated by Scrum definitions - but they'll never be truly Agile, nor will they be professional craftsmen if they don't follow the XP techniques (CI, TDD, clean code).
So, my tiny epiphany on this subject was that these parameters (methodology and techniques) are orthogonal.
Next time I'm asked what is it we're doing, my answer will be: Scrumban with XP.
No comments:
Post a Comment