Agile scrum Project Management

[abcd]

I recently read about Scrum and ScrumMaster. Are these new Principles
available from MS Project. Is Scrum really helpful for the productivity. To
me it looked waste of time in the first reading. (I may be wrong as I am
novice in that topic). I know that software development is complex process
and developers, testers, QA, business analysts are involved. Is it really
feasible to involve customer in each sprint. Does the customer really know
what he want and how he wants. They may be unsure about their requirements
too....

thanks

 

[Rod Gill]

On the other hand how could you not involve the customer?!! If a project is
deemed successful because of a happy customer, then the customer must be
involved. Typically the biggest failures come when the customer says "go
away and develop a solution for me". Methods agile like scrum are typically
showing better results for up to 30% less resource work and cost.

Project is fine for scrum: you just need an overall schedule for however
many sprints you expect to have, then a detailed schedule for each scrum
once you have agreed (with the customer) what is in and locked for this
scrum.

--

Rod Gill
Project MVP

Project VBA Book, for details visit:
http://www.projectvbabook.com

NEW!! Web based VBA training course delivered by me. For details visit:
http://projectservertraining.com/learning/index.aspx

 

[davegb]

On the other hand how could you not involve the customer?!! If a project is
deemed successful because of a happy customer, then the customer must be
involved. Typically the biggest failures come when the customer says "go
away and develop a solution for me". Methods agile like scrum are typically
showing better results for up to 30% less resource work and cost.

Project is fine for scrum: you just need an overall schedule for however
many sprints you expect to have, then a detailed schedule for each scrum
once you have agreed (with the customer) what is in and locked for this
scrum.

--

Rod Gill
Project MVP

Project VBA Book, for details visit:
http://www.projectvbabook.com

NEW!! Web based VBA training course delivered by me. For details visit:
http://projectservertraining.com/learning/index.aspx

---------------------------------------------------------------------------­-------------------------







- Show quoted text -

I can't remember how many times I've read that the number one reason
for software development projects failing is that the the customer was
not involved early enough and often enough. Particularly not involving
the lowly end-user, who knows nothing about software development. Of
course, they know better than anyone else, including the developer and
their own management, how they do their jobs. Software designed from
"on-high" is usually a disaster. Sounds to me like the people who
designed the system you're talking about, though I have no knowledge
of it at all, were as many of these people are, on the right track.
But often some "smart" Project Manager or staff manager will decide
that consulting with the customer is a waste of precious time! Save a
few weeks in the schedule by eliminating the customer from the process
as much as possible, and create a useless end product as a result.

I think I'd stick with the process designer's process as is,
particularly if it involves getting the customer/end-user involved.

Hope this helps in your world.

 

[jesspinto00]

I recently read about Scrum and ScrumMaster. Are these new Principles
available from MS Project. Is Scrum really helpful for the productivity. To
me it looked waste of time in the first reading. (I may be wrong as I am
novice in that topic). I know that software development is complex process
and developers, testers, QA, business analysts are involved. Is it really
feasible to involve customer in each sprint. Does the customer really know
what he want and how he wants. They may be unsure about their requirements
too....

thanks

Agreed and agile software development ( http://www.agiledistributed.com/testingDistributedAgile.html ) process enables the involvement and co- ordination of the customer, development team and the testing team. It is done in certain phases so that the developer doesn't have to start from scratch if something may have gone wrong.