I started using “Solo Scrum” again. This means that I am playing the three roles all by myself.
What are the three roles?
1) Product Owner
2) Team Member
3) ScrumMaster.
After only one day (Thursday) of using this again, some big things jumped out at me as lessons learned.
Take a look at the video and please provide comments to what you see so far.
Is this kind of thing useful to you? Do you see similar mistakes?
I’ll see if I can make some improvements on Friday and share them with you.
Have an awesome weekend (or welcome to Monday!).
Thank you!
- mike vizdos
www.implementingscrum.com
www.michaelvizdos.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
Hi all,
Today is our first try at a new format (in addition to the cartoons) at www.implementingscrum.com.
It is called, “ImplementingScrum – UnScripted” and will feature audio and/or video in different formats along the way. By the time this goes out, it should be out on youtube and here is a link to the “.mov” format (uses quicktime and is just under 17MB — for some reason this is MUCH clearer — any recommendations???).
Using FeedBurner, it should also find it’s way out to iTunes as a podcast… let’s see together how it all works and continue to inspect and adapt.
Fair? (smile)
This first version of this is with a guy “Down Under” who had some spectacular patience with me this morning (in addition to the fifteen hour time difference!).
His name is James Brett and he maintains a site at www.scrummaster.com.au and recently (with a LOT of help with the people there!) published a survey, where you can see the results at www.scrummaster.com.au/Article.mvc/Detail/43 or download the PDF file from www.scrummaster.com.au/Content/download/ScrumSurveyResultsJan09.pdf.
The video of this is about eight minutes long and goes into the survey a bit and introduces the topic. It is not meant to be exhaustive — right now it is a test of the technology convergence(s) and as usual we want to keep these things short and to the point.
A few other references made in the video included a retrospective formats article and retrospective why.
You can also check out a few cartoons about retropectives on this site (there is a three part series here:
www.implementingscrum.com/2007/09/04/scary-team-retrospectives-part-one/
www.implementingscrum.com/2007/09/10/retrospectives-not-just-reading-a-book-part-two/
www.implementingscrum.com/2007/09/17/walk-into-the-light-retrospectives-part-3-of-3/
As usual, any errors anywhere on the video or my site — I accept that responsibility.
Take a look at the video and the links above for the survey and other stuff and PLEASE comment about it below.
Inspect and Adapt.
Let’s see where we go.
As usual!
Thank you.
www.implementingscrum.com
www.michaelvizdos.com
« Newer Articles
