Two sport fishermen had a successful weekend of remote fishing. When the bush pilot arrived to retrieve them, he soon notified them that with the added weight of the fish they had caught and all their gear, he would have to make a return trip. Not wanting the extra trip, the sportsmen convinced the pilot to pack everything in tight and offered him extra cash. Reluctantly he agreed.
As the plane took off the weight was too much for the plane to handle and they crashed beyond the end of the lake. No one was seriously injured and as they came to, one of the fisherman asked, “What happened?” To which the other responded, “We crashed . . . . . about 100 meters further up than last year.”
Scrum as an agile framework isn’t just about being agile enough to be able to create great software products but also allows Product Owners, Scrum Masters, and developers as individuals and as a team to learn, grow and adapt.
Scrum provides us the Sprint Retrospective at the end of each sprint providing each team member to share their perspective on such things as:
What worked really well for us as a team?
What could we change that might make the team better?
Can we make the processes more enjoyable?
How can we adapt our definition of "Done" to improve quality?
But simply meeting, providing answers to these questions, and having them recorded isn’t enough. Teams are only a sum of each individual member. So for a team to adapt for the better, each individual must take it upon themselves to improve. Otherwise, whether one or all, and thereby the team (where we go one, we go all), will continue to be at risk to fail or to become stagnant.
If your team has chosen Scrum as its development framework and with it the Sprint Retrospective. Embrace it, learn it and be an active participate. Else, I guess we’ll see you again next year . . . crashed just beyond the lake.
Cheers.
As the plane took off the weight was too much for the plane to handle and they crashed beyond the end of the lake. No one was seriously injured and as they came to, one of the fisherman asked, “What happened?” To which the other responded, “We crashed . . . . . about 100 meters further up than last year.”
Scrum as an agile framework isn’t just about being agile enough to be able to create great software products but also allows Product Owners, Scrum Masters, and developers as individuals and as a team to learn, grow and adapt.
Scrum provides us the Sprint Retrospective at the end of each sprint providing each team member to share their perspective on such things as:
What worked really well for us as a team?
What could we change that might make the team better?
Can we make the processes more enjoyable?
How can we adapt our definition of "Done" to improve quality?
But simply meeting, providing answers to these questions, and having them recorded isn’t enough. Teams are only a sum of each individual member. So for a team to adapt for the better, each individual must take it upon themselves to improve. Otherwise, whether one or all, and thereby the team (where we go one, we go all), will continue to be at risk to fail or to become stagnant.
If your team has chosen Scrum as its development framework and with it the Sprint Retrospective. Embrace it, learn it and be an active participate. Else, I guess we’ll see you again next year . . . crashed just beyond the lake.
Cheers.
RSS Feed
