Scrum is only a tool and you must make sure to double check your processes before ploting the backlogs in the scrum board. Unprepared Project Managing makes your plan fail.
I have seen PMs creates their own rules. Some I've seen was:
DoneDone, When I asked what they meant by this the Scrummaster replied:
When the programmer declares that a backlog is finnished, when it has been approved by the product-owner. And in the real life no product. manager/owner/Customer knows exactly, whant she/he wants before the feature is released and then they find out something is missing.
This is part of your planning. and if the Product-manager (customer) did not do his job properly or if you are sure that he is not able to come up with the whole feature discription, You must have it in your paln. Here is a tip how you can handle this scenario.
Suppose your project plan has a 10 sprint, sprint 1 to sprint 10 and experince has shown you that your customers (product-owner) always come up with the last change in the last min.
So in this case you must create your ms project as following:
Sprint 1 and here is the work is 300 hours.
Add a Sprint 1 Follow up that has between 10% to 20% of the total Sprint 1 work.
and add another 20% for test and bug fix.
so here is the result:
Sprint 1 : 300h
Sprint 1 Follow up: 30h (10%)
Sprint 1 Error Fix: 60h (20% of 330 hours)
Total of the S1 : 390h
I hope this will help you to approve your projects.
Please add your questions and comments to the blog or
send and email to bobby.saeidi@adept.dk
Regards
Bobby Saeidi
I have seen PMs creates their own rules. Some I've seen was:
DoneDone, When I asked what they meant by this the Scrummaster replied:
When the programmer declares that a backlog is finnished, when it has been approved by the product-owner. And in the real life no product. manager/owner/Customer knows exactly, whant she/he wants before the feature is released and then they find out something is missing.
This is part of your planning. and if the Product-manager (customer) did not do his job properly or if you are sure that he is not able to come up with the whole feature discription, You must have it in your paln. Here is a tip how you can handle this scenario.
Suppose your project plan has a 10 sprint, sprint 1 to sprint 10 and experince has shown you that your customers (product-owner) always come up with the last change in the last min.
So in this case you must create your ms project as following:
Sprint 1 and here is the work is 300 hours.
Add a Sprint 1 Follow up that has between 10% to 20% of the total Sprint 1 work.
and add another 20% for test and bug fix.
so here is the result:
Sprint 1 : 300h
Sprint 1 Follow up: 30h (10%)
Sprint 1 Error Fix: 60h (20% of 330 hours)
Total of the S1 : 390h
I hope this will help you to approve your projects.
Please add your questions and comments to the blog or
send and email to bobby.saeidi@adept.dk
Regards
Bobby Saeidi
5 comments:
Looks like you are an expert in this field, good articles and keep up the great work, my friend recommended me it.
My blog:
regroupement de credit et Rachat de credits
You got great points there, that's why I always love checking out your blog.
My blog:
Meilleur Taux aussi Rachat de credit rachatdecredit.net
I think this is one of the most important information for me. And i am glad reading your article. But should remark on few general things, The website style is perfect, the articles is really nice
I have been reading your article for the second time ..and i feel yours make a lot of sense and i have adviced all my subordinates to read this article.Thanks a lot for the painstaking job you have been doing but i feel that you are some information about time sheet that would made yours a complete one ..
Waу cool! Some very valid pοints! I appгеcіate уou penning this
write-up рluѕ the rest of the site is аlso verу good.
Also visit my blog post - Gutschein Dezember 13
Post a Comment