Welcome back to yet another week at www.implementingscrum.com.
OK.
This week may be the week that actually dates people reading this blog.
Tattoo. Not Toto.
Scary.
But true.
Admittedly I have had grey hair for a while (that is one of the reasons I keep it short short lol) and I know I am one of those people “in between” on the high and low-age readership of this group. Next year will be 20 years in the industry for me, so I do have some real life experience. And for you, a lot of this life is lived working with clients on Scrum Projects around the world.
And.
This may be one of my favorite cartoons Tony has done to date. This has been one that has been brewing and talked about for over a year with clients and class participants.
And as usual, Tony nailed it (got it right for the non-Americans — this is a good thing (smile)).
Maybe for tonight I just leave you with the cartoon.
An give you a little more about it as the week progresses.
I am on the road.
And wow do I have some ideas and opinions on this one.
See where this one cartoon strip can lead you?
First… see if you get the context of it!
Here is the cheater link if you have no clue (and THAT is OK!).
Please read part two here
Gotta run Please send comments, questions, criticisms, ideas, or whatever here.
You can also enter The Scrum Community to discuss this entry and other Scrum topics. Thank you!
May 27, 2008
Welcome back to yet another week at www.implementingscrum.com.
I am a bit worried about some of the things I am seeing out there.
Um.
The night before a Sprint Review meeting, I am seeing people stay late.
Uh.
Really late.
Like into the morning before the Sprint Review meeting.
Sometimes, it is minutes before.
Ug.
Oh no.
What does this remind you of?
What is wrong with that picture?
And what is right with the picture above?
Seriously folks.
Don’t kill Scrum this way.
Just go back to whatever you used to call it.
Really.
Or.
Look at what you are really doing.
Remember the objective of Scrum?
Working Software.
On one machine.
Real working software.
Not vaporware or conference-ware or some scripted bla bla bla.
Please.
Gotta run! Please send comments, questions, criticisms, ideas, or whatever here.
You can also enter The Scrum Community to discuss this entry and other Scrum topics. Thank you!
May 20, 2008
Welcome back to yet another week at www.implementingscrum.com.
[After you read this you may want to check out an updated posting to this cartoon at: http://www.implementingscrum.com/2012/01/04/scrummasters-feel-like-giving-up-sometimes/]
So.
A few weeks ago had someone in a class explain this. He was trained as an Antropologist — not a software developer.
Interesting dude. Really.
Let’s say your current organizational system is like a river flowing down stream.
How rough varies.
Introduce change.
Any change.
Just one.
Scrum for example (funny how that gets worked into this conversation, eh?).
Pretend that change is a boat (or canoe, as drawn!).
Insert a Chicken and Pig for some humor (smile).
Following along with me?
Now.
Paddle.
What happens when you stop paddling?
The river flushes you back down stream.
That’s the gist.
Easy brilliance.
Does this apply in your current situation?
If you are about to just embark on this journey, remember to always keep paddling!
Stop paddling and you have made a choice to give it up — and make room for something else to take its place.
Gotta run! Please send comments, questions, criticisms, ideas, or whatever here.
You can also enter The Scrum Community to discuss this entry and other Scrum topics. Thank you!
Originally Published:
April 21, 2008
[Updated posting to this cartoon at: http://www.implementingscrum.com/2012/01/04/scrummasters-feel-like-giving-up-sometimes/]
Welcome back to yet another week at www.implementingscrum.com.
Wahoo. We made it another week and did not wind up six feet under or having our ashes spread in some remote location of the world. In other words… yipee… we all made it another week to see another great cartoon and continue learning.
OK… so the title of this one is a little twisted. OK. A lot twisted. I guess I should have named it “The ScrumMaster Guide to Picking Up Filing Cabinets” but then who would really want to read about that?
This week I am writing about something that all people playing the role of ScrumMaster must be aware of.
Actually, I’d consider it important for the ScrumMaster on a team to help show the Team Members and Product Owner — through example — what to do when you are in over your head and really need help.
How many times have you been in a situation where you felt like you had to “wing it” or “fake” an answer?
We have learned that as a Product Owner, that can have dire consequences for the team.
Instead of “faking it” or “winging it” or “making up an answer” the Product Owner should feel safe enough to say to the team, “I do not know, but I will find out and get back to you in the agreed upon time.”
And then do that.
Guess what following through on promises helps build?
Trust.
Really.
The agreed upon time should be something that is ummm…. agreed upon by the team — maybe as one of the team norms that are posted on the wall of your team room.
You have those, don’t you?
Right next to the Burndown Chart and team Definition of Done, right (smile)?
So what can the ScrumMaster do to help show the team that they do not know everything (really… we do not!) and sometimes we need to bring in outside help.
Think about Retrospectives.
And.
What if the ScrumMaster is part of the problem in the current system?
You know the answer.
Get help.
Really.
Ask someone else to facilitate the Retrospective.
I have written about this in the past, but have been recently reminded how important this is for all roles of the Scrum Team.
Wow.
Something as simple as asking for help.
That simple.
But.
It does not get performed enough.
As a ScrumMaster, how can you make some simple changes on a daily basis to show the team how to become the best they possibly can?
Remember that the implementation of Scrum should sometimes be taken in small baby steps.
Which small baby step can you take today?
Please share them with us in the comments or on the forum.
Gotta run!.Please send comments, questions, criticisms, ideas, or whatever here.
You can also enter The Scrum Community to discuss this entry and other Scrum topics. Thank you!
April 1, 2008
Welcome back to yet another week at www.implementingscrum.com. We made it another seven or eight days on this earth — congratulations (smile).
So last week the post was a little long, and I put out some real life information that hit home hard for me. I received a ton of great feedback and people offering a lot of great advice. One thing I do want to make clear is that client was not my only client — something I have learned to not do in the past (depend on 1 client 100% of the time). As a consultant, this is a position you want to get yourself into. Really. Look at me as an example!
This week.
Um.
Where is our “old” ScrumMaster?
I kinda liked him. He was a little “off” at times; however, he started to grow on me and help with a lot of examples.
He seems to have disappeared last week.
Seems to have gotten himself whacked by some shady characters.
Oh no.
What has Tony done. What have I done?
At this point, there is now a [hot] ScrumMaster who has no problem saying, “Yes” to anything and everything asked of her.
Um.
Is this dangerous?
One word.
YES.
Notice the usage of capital letters above.
YES I AM YELLING THIS TO YOU THIS IS DANGEROUS.
I am trying to make a point (smile).
And, you may be asking yourself, “Mike… What point are you trying to make this week?”
Really?
You do not see it?
Look hard.
Read the comic strip above again, and again, and again.
Then, send me an e-mail (or write a comment on this blog entry) about what you think it means.
Really.
C’mon.
Take action and do it.
It will take you less than three minutes.
Please.
Gotta run!.Please send comments, questions, criticisms, ideas, or whatever here.
You can also enter The Scrum Community to discuss this entry and other Scrum topics. Thank you!
March 18, 2008
« Newer Articles — Older Articles »
