4 replies
by dc_guy
Your description is a little vague. A "plan" documents what you intend to do in the future. Assuming you're using a software tool like MS Project, you simply load it with the number of human resources you have, allow some slack time while they learn how to get things done in a new company, estimate the speed at which they can perform their assignments (without the leadership of a QA Lead and probably having to perform some of the QA Lead's work), and let the tool calculate how much they will be able to get done.
If you're already in the middle of a plan, then you should already be experiencing large variances because of the missing staff member. You will still have to go through all of the above steps and produce a revised plan to reflect your new reality.
If you're not using a software tool, you still have to do all of these same things manually, it just takes longer and gives you a bigger headache.
Notice that the other managers' guesses about how much time they think you have lost don't figure into this process. This is the reason you have plans, so you don't have to rely on guesswork.
Please don't tell me your organization doesn't do formal planning. Most companies measure productivity and ignore quality. I'd be really surprised to learn of one that had the opposite problem. ^_^
by manmohan74
Their are couple of pointers to be considered for any project as thumb rule:
1. Objective
2. What you will achieve at the end of it
3. What else can be achieved even after the set mile stone
4. What it takes to achieve the mile stone
5. What are the resources available
6. What is the actual plan/ contingency plan
Needless to say your own knowledge, how much of rework it takes if something needs to be fixed at a later stage, how much time it takes to get the resources speed up in correct direction
factor in the JAD resources availability/approval process for each step.
your work plan should reflect based on about pointers, whether your QA lead is available/ non available would impact on the need/objective of the mile stone.
Its true if an able/experienced person lives, the new resource takes time to learn/understand the procedure/application.
your workplan should include the time reqd to train the new resources, time in approval process, time involved in getting the requisite resources to meet your objective, factor in environmental delaytimes/other delays (this information has tobe an educated guess based on your past experience ofyour project, a thumb rule should be about 10% buffer time)
Hope this helps
by ansonrah
by sridharpandu
Split the task (In MS Project) so that it starts at a later date.
Right Click on the GANTT bar, Choose Split, position cursor on the date when the project came to a halt. Click and drag to a new date.
This discussion is closed to new replies.
Trending IT Employment posts
Sort by Trending