Win a copy of Classic Computer Science Problems in Swift this week in the iOS forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Head First Agile: is Agile a misunderstood paradigm?  RSS feed

Ranch Hand
Posts: 183
Java Python Ruby
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Dear Authors,

My understanding is ,Do Scrum, or Kanban, or XP, or anything. Learn it, practice it, and most importantly, understand why these agile practices work the way they do.
Only then can you step back and say "OK, I get this, lets run a small test and tweak X or Y for two weeks and see what happens" - but you can't do that until you have a
solid baseline and a good working knowledge of why things work the way they do. But if you mix things up, don't call it what it's not.

At the end of the day, you can do whatever you like. Just understand every decision you make will have a positive (your goal) and negative (your unintended result) action.
For example, lets say that we condense the daily Scrum to a weekly meeting. We save 15 minutes, so now we have "fewer, shorter meetings" (your goal). The negative pattern you
introduced, however, is that the team now has one opportunity per week to sync up and identify impediments, issues, challenges, etc, that would have otherwise surfaced in a
daily meeting.

So we have essentially delayed the smaller loops into longer loops......

I would appriciate your take on this.

Thanks and Regards

It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!