Re: [scrumdevelopment] Scrum Principle: Cross-Functional Team
- I'm confused by your email.Your two "If a team..." paragraphs seem to agree with the quoted paragraph. Then you posit that the quoted paragraph is contrary to the Agile Manifesto. So you support the quote but then find it troubling.
And, if one is going to "blame" a method or framework for failure, wouldn't one need to have followed the method before blame can be attributed?I think I'm still something missing in your statements. Are you in favor of cross-functional teams? Why or why not?AlanOn Tue, Aug 3, 2010 at 4:02 PM, Geoffrey <geoffrey_slinker@...> wrote:
"From the Agile viewpoint, what we have here is a fundamental violation of the Scrum principle that the software must be done by a cross-functional team: a team that has all the skills needed to do the project. This team doesn't have the design skills to do the project … and therefore they are not an Agile team at all!"
If a team has all of the skills needed to do a project then any process management methodology and any software development methodology would most likely be successful.
If a team does not have the skills needed to do a project then any process management methodology and any software development methodology will fail.
I find the quote at the beginning to be troubling in its implications. Is it saying, "Hey, you can't blame Agile because YOU didn't have a properly skilled team."
Is this Scrum principle in conflict with "people before process"?
- I think also team based organizations do need leaders and there should be a succession plan for CTO and the like.
I read this book years ago before starting with scrum and it deals with some of your concerns.
M.On Fri, Aug 6, 2010 at 3:24 PM, Satish Thatte <smthatte@...> wrote:
From my own experience (in a role of traditional project manager in my past industry experience), project plans elaborated with Gnatt charts, etc., do not work well for software projects, unless the project requirements/scope is very stable, technology platform is very stable, there are very low risks, and it’s a simple, small, short duration project… and that is a rare occurrence indeed.
CEO, New Synergy Group
Hello, Satish. On Thursday, August 5, 2010, at 7:40:49 PM, you
> In traditional project management, project managers still prepare elaborate
> project plans (with Gantt charts, etc.) and tell each project members their
> tasks, start and due dates, task dependencies, etc., and then try to track
> or manage them.
How's that working for them? :)
The opinions expressed here /are/ necessarily those of XProgramming.com.
But I might change my mind.
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 9.0.851 / Virus Database: 271.1.1/3050 - Release Date: 08/06/10 03:37:00
I keep six honest serving-men (They taught me all I knew); Their names are What and Why and When And How and Where and Who.