… in order to help *everyone* in our community, I’d like to ask for the following people to please contact me off-line from the blog:
1) If you are currently looking for a Scrum type job. What role? What experience level? Tell me what you can about *you* and *your needs*.
2) If you are working in a company and know you have OPEN REAL positions for people who are in the first position above (LOOKING for work).
3) If you know people in your circle of friends PLEASE PLEASE PLEASE forward this email or call them today and have them contact me directly.
In the past six months or so I have been informally connecting these three groups of people together and have promised myself to take it up a notch and see if we can get our community working together to solve some of these things.
I know all three types of you are out there.
Time to speak up!
I am going to try a *small* experiment.
And see where it goes.
Fair?
Let’s go!
Let me know.
And.
As usual.
Thank you.
- mike vizdos (mvizdos@gmail.com)
Good day.
This is another version of the “UnScripted” blog entry on the site implementingscrum.com.
Today I’d actually like to post a question from one of my readers that I’d like to get feedback from you — the community — via answers in the comments of this blog. I’ll plan on doing a follow-up to this but as usual, I want to show the community we can all learn from each other…
I have an opinion. Of course!
—————————–
Hello Mike,
I took your class last year and I am a CSM now. I have not had the chance to be Scrum Master on a project yet, but it is in the near future.
Currently I am on a project that has 2 week sprints and on a team of 8.
The question came up yesterday during our Retrospective that during out last sprint there were a lot of chickens on the scrum calls.
How do we handle this?
I know that if you don’t have any tasks to complete or you have completed your tasks you should be reporting yourself as “chicken”, but with stakeholders on the call everyday hearing 2 people report tasks and the rest of the team reporting “chicken” every day for almost 2 weeks…doesn’t that appear to the stakeholders that only 2 people are working?
IS there another way to still follow the Pig/Chicken rule without appearing to the stakeholders that there are a lot of people not working?
Please advise.
This was a discussion that was placed on the action item list due to too many conflicts between team members.
Have you seen this before?
How was it handled in other teams/projects?
Comments Please!
- mike vizdos
www.implementingscrum.com
www.michaelvizdos.com
Thanks for reading the latest blog entry at www.implementingscrum.com.
One of the things I hear a lot about (both inside and outside of our little industry in the world) is the differences between coaches, consultants, and mentors.
Which brought me back to a discussion I had a few years ago with John Snuggs (shout out!) who used to poke me about wearing my “Captain Obvious” hat.
Which then lead to the super-hero-wearing-ScrumMaster in the comic strip above.
And.
Then the elephant.
Huh?
What does that elephant represent?
In America, we talk about this thing called, “An elephant in the room” which is something reallllllllllly uncomfortable that everyone knows is there but is afraid to bring it up. Make sense?
Sooo… besides being the elephant in the room… what does Captain Obvious need to teach us about Scrum “Coaches” versus “Consultants” versus “Mentors”?
This could be one of those epic postings with me talking about the ins-and-outs of the three words and how they not only sound different — but in the real world ARE different.
So.
Question to you… and I will talk and post more about this… in the comments section write more about the good, the bad, and the ugly about the differences you see in either the people you hire, work with, or ARE.
Elephant recognized.
Let’s hear more about what this means to you. And your teams. And your organizations.
And of course… this is leading somewhere. It always does.
And it usually surprises even me (heh).
Time for Captain Obvious. Pointing out the elephant in the room.
- mike vizdos
www.michaelvizdos.com
www.implementingscrum.com
Hi all,
Wow. I was going to post the comic strip tonight but wanted to wait just one more day because a few interesting things went on today…
I got a TON of feedback from people on both sides of the fence on this one.
Now, as a consultant/coach/mentor myself, I do not want to seem to have a totally skewed view about this.
Got something to say about the good, the bad, and the ugly about your use of coaches/mentors/consultants in the past?
Scrum related would be great since well, this is about Scrum 
.
Thank you!
- mike vizdos
Hi all,
The cartoon this week (coming out tomorrow) will examine why the heck almost 100% of the teams implementing scrum today should be using some sort of consulting / coaching / mentoring support.
Of course this is written from the point of view of me — who in reality is a consultant, coach, and mentor — who also sees the worst of the worst implementations of Scrum trying to get better.
Tomorrow I will post the actual cartoon. If anyone has to say anything BEFORE the cartoon gets published, please feel free to comment or send me an email.
Thank you.
- mike vizdos
Older Articles »
