|
|
Hi,
I am announcing another test (remember — inspect and adapt) on our site at implementingscrum.com.
Know what a Product Backlog is?
I am opening the Product Backlog to you — the reader — for input.
Is it the perfect tool for this? Maybe not.
However.
Let’s see if we can get some things started on here.
You can read more about it (see the product backlog and be able to enter your ideas into the product backlog) here.
Thank you.
- mike vizdos
www.michaelvizdos.com
www.implementingscrum.com
 |
 |
Interested in becoming a Certified Scrum Master?
Come to my next workshop!
Today I am addressing something that has been bothering me — and others in the industry too — and maybe even you, my great reader!
Scrum talks about having having working software at the end of every Sprint (or iteration).
Wow.
Not a Requirements Document. Working Software.
Not a Design Specification. Working Software.
Not a great Architecture PowerPoint Presentation. Working Software.
Not Compiled Code. Working Software.
Not an incredible Test Plan with Automated Testing and complete coverage. Working Software.
Yikes.
Get the point here?
Not too preachy I hope (smile).
That is awesome, right?
“Working Software” then became recast or known a, “Potentially Shippable Product.”
Huh?
Is there a difference?
Yes.
There is a difference.
Think about it.
In your Scrum Teams today, do you have someone from your Production and Support areas involved with your Sprint on a daily basis? How about the Daily Scrum (or Daily Stand-up meeting)? What about in your Sprint Planning? Planning Poker?
Any planning?
At all?
Hmmm.
Now OK.
We may have different definitions of Production and Support people. You can look at them as one separate team, two separate teams, or actually part of your Scrum Team.
In Agile and Scrum, I’d argue that the Production and Support people should be an integral part of the Scrum Team.
In the end, it is the Scrum Team agreeing on the definition of, “Done” for the Sprint (or iteration).
And where does Working Software actually spend most of its usable life?
Say it with me now… “In Production and Support.”
Wow.
What a paradigm shift in the way you are working today.
Or is it?
And.
Think about this.
If your Scrum Team does not include the Production and Support people into your Scrum Team, you may be creating more “Working Software” than the rest of organization can handle.
What? You may be asking yourself?
Are you kidding me?
Nope.
I see this.
Often.
And.
One way I advise clients about handling this situation is to include the Production and Support people into the Scrum Team.
Do they always listen?
Nah.
And then they have a big dump truck full of stuff (waste…. work in process…. inventory….).
What does this cost an organization?
What is this costing your organization today?
Do you care?
Gotta run….Please send comments, questions, criticisms, ideas, or whatever here.
You can also enter The Forum to discuss this entry and other Scrum topics. Thank you!
February 11, 2008
|
|
Interested in becoming a Certified Scrum Master?
Come to my next workshop!
Please note:
Tomorrow will most likely be the last comic strip for the end of 2007. Tony (our artist!) is planning on taking a two week hiatus between now and the new year. This is good stuff and shows he works on having a life (something we talk about a lot on here). While he is gone, I may do a little refactoring on the site and add some additional material and ideas.
If you have any ideas about the content for the remainder of this year, please contact me anytime and we can chat, email, or meet face-to-face.
I have a lot of great plans to be unveiled for 2008.
For those of you who are “stuck” doing the work thing over the upcoming holidays — spend some time surfing the net — specifically at this site and learn more about your craft and how to get better at it. Find something you like? Pass it on to your friends (they do not even need to be geeks!).
So… Tomorrow we will introduce the last comic strip of 2007.
Hope you enjoy it!
Gotta run….Please send comments, questions, criticisms, ideas, or whatever here.
You can also enter The Forum to discuss this entry and other Scrum topics. Thank you!
December 16, 2007
|
|
Hi,
Thanks for continuing to read the series this week about the ImplementingScrum Forum and the entries I’d like to highlight for you. Hopefully also you take the time to register as a member - it is FREE and I do not sell or rent your name or email address to anyone!
Good day.
The topic today is “Done” and what that means on a Scrum Team.
For those of you practicing Scrum today, think about how important this is.
For those of you who are not yet practicing Scrum today, remember when you start that it is a very important topic to discuss with each of your Scrum Teams.
Today we continue examining some of the postings and related comments at www.implementingscrum.com and the forum.
This entry is going to ask you to look at the topic, “Developer Done, or all done?“. Go ahead and take a look at it.
Any new ideas or comments you’d like to add to this topic?
You may also want to check out the following blog postings and comments related to this:
Done. Really?
Who’s Your Product Owner?
Welcome to Oz.
Thanks for continuing to read this — or welcome new people reading and subscribing to this forum!
- mike vizdos
Have a great day and thank you for your time.
- mike vizdos
www.implementingscrum.com
www.michaelvizdos.com
PS –> Want to join the Forum? Click here!
|
|
Hi,
Thanks for the positive feedback I have received so far on the idea for this week. It is good to hear and see that people are interested and some are learning about the forum for the first time!
One of the most viewed threads on this forum is called, “Understanding Velocity“. It has some great information and questions / answers that help clear up (I think) the usage of story points for measuring velocity within a Sprint and for Product Backlog Planning purposes.
You may also want to check out the following blog postings and comments related to this topic:
Whiskey Tango Foxtrot. Over.
Scrum = Communication.
Ya Got to Know When to Fold ‘Em.
Burn Baby Burn.
Hope this is helpful and please feel free to add to this or other threads located at the forum.
Get involved!
Have a great day and thank you for your time.
- mike vizdos
www.implementingscrum.com
www.michaelvizdos.com
PS –> Want to join the Forum? Click here!
Request for Feedback. Please. 
I have been receiving a lot of requests from people asking if they can print tee-shirts or mugs (or whatever) for use either internally at their company or for sale. At this time, it is strictly prohibited to use the cartoons or characters for anything that is of commercial interest (read: makes you money off our brand!).
We have a LOT of comic strips (I think we are are approaching 50!) and of course our characters. At this point, all the artwork on the site is “optimized” for the web viewing (meaning if you try to print them they are not “book” quality). This will take time to do.
So.
Instead of me rushing to convert all the artwork and creating a lot of products and an online store (bla bla bla)… I figured I’d ask YOU and see if there is any interest in merchandise for you and your teams. Am thinking T-Shirts, Mugs, and whatever cool stuff you can think of doing.
That’s where YOU come in.
Please let me know if there is any interest in merchandise from the site.
It is not a commitment to order, but rather actually me talking to my customers before trying to deliver something. Wow. How Agile 
.
If you can, please take a few moments and send me your thoughts.
I’d really appreciate the feedback!
And also don’t forget to tell your teams and friends about the site (thank you).
Gotta run….
Please send comments, questions, criticisms, ideas, or whatever here.
You can also enter The Forum to discuss this entry and other Scrum topics. Thank you!
August 9, 2007
Drink. Out of a Fire Hose.
*** Interested in becoming a Certified Scrum Master? Come to my next workshop! ***
Today, I discuss ways in which the Product Owner interacts outside the team — with what I call, “The Noise.”
First, please remember that each Scrum Team should have ONE Product Owner.
ONE.
Not two.
Not three.
Not a committee.
ONE.
Comprende?
This is a super important concept to understand and make sure you are actually following on your Scrum Team. It is a major point of failure when implementing Scrum if your team is being run by a committee of Product Owners. If you are in this situation, I think you know this in your heart; and, you probably feel the pain on a daily basis.
For the reminder of this discussion, lets assume that you have one Product Owner.
Ahhh. Nice (smile).
This Product Owner is actively involved on a daily basis with the team. In fact, as a team member, you feel like the Product Owner IS a part of team. This person attends the daily stand-up meetings, is actively involved in your Scrum Team Room (collocated of course), and has the answers and is empowered by his or her peers and bosses to make the call on direction. If there are any questions, this person knows how to navigate “the system” outside of the room, and is able to get the Scrum Team a definitive “yes” or “no” (or answer) in a timely fashion.
Sounds easy, right?
Here is what could be happening outside the room. And this is where the Product Owner really needs to shine for the team.
On the “outside” world (away from your Scrum Team), the Product Owner is actively defending people from coming into your Scrum Team Room and asking for new things to be added. You know… those pesky Vice Presidents who have “friends” on the team that can do “favors” for them. An effective Product Owner — in conjunction with the Scrum Master — works to ensure this actually stops happening.
This is part of shielding the team from “The Noise” on the outside world.
In addition to being a shield for that, the Product Owner has the distinct opportunity to help all the outside stakeholders shape and form the Product Backlog (remember… there is a difference between a Product Backlog and Sprint Backlog ). At the end of every day (or minute, depending on how your organization looks and reacts), ultimately it is the Product Owner who is the single wringable neck (a term, by the way, which I hate to see used gulp). This person has the responsibility of making sure the priorities are negotiated and are correctly identifying the highest risks to the organization today.
This can be tough.
The Product Owner must negotiate with his or her peers and up the chain of command in an organization (even if it is an organization where there is only one more person with an opinion above the Product Owner).
And remember, like you (o Scrum Team Member), this person cannot just make stuff up in a vacuum. If that happens, I can pretty much guarantee career suicide for that person. I have, unfortunately, seen that happen.
So.
If you are on a Scrum Team today and things look rosy and things are going smooth, be thankful.
If your Product Owner makes it look easy to the team, you are lucky.
Hmmm…
If you are not in the happy happy situation as described above, maybe it is time to chat with your Scrum Master, Product Owner, and Team (maybe a Retrospective Topic???) about what can be done. Call in someone from the outside if needed (shameless plug for me if you take it that way!).
If you are in the happy happy situation as described above, then give your Product Owner a hug (or at least a sincere “Thank You” if it is inappropriate) right this moment. Allow that person to continue shielding you from “The Noise.”
And, continue making your team even higher performing than it started today.
Good luck!
Gotta run…
Please send comments, questions, criticisms, ideas, or whatever here.
You can also enter The Forum to discuss this entry and other Scrum topics. Thank you!
April 16, 2007