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).
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.
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.”
Is there a difference?
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?
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.”
What a paradigm shift in the way you are working today.
Or is it?
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?
I see this.
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?
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 Scrum Community to discuss this entry and other Scrum topics. Thank you!
February 11, 2008