You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Using the "Agile Adventurer" challenge as an excuse to say "Hello", I thought I'd also throw in a little humor to see what conversation it may spark.
So, what is an example of something you have heard referred to claim "agile" that either isn't, isn't enough, or can run counter to? And what advice would you offer?
For example, estimation. Many claim the use of story points as helping them be agile. How so? And given that there is no reference in the manifesto, how does estimation or pointing map back to one of the values or principles?
I have the pleasure of working with one of the original manifesto authors and have followed others for most of my career. None advocate estimation or pointing, and rather recommend spending any such time on other value-add activities.
What do you think? Please share your thoughts.