This is probably one of the most discussed topic... but proper
planning and budgeting the appropriate amount of time seems to be
always among the top three root causes of failure for all projects... There is a term that many people who are in the business of building
software use, :"Change Control"... wonder if this is a used
effectively ? Most cases, its adding to the scope with no change is
timeline... of delivery. And then again, we discuss a change control
for 12 hours, and the real change probably can be one in 1/2 and
tested in 4 hours.. ha!
Few days back, I asked my kids if you have a 12 gallon bucket , how
many pounds is that?
My thought was around a mathematical response.. you know... ( US
gallon of water weighs 8.34 pounds) .. but guess what kids being
kids... they said, if you take a lot of news paper and keep stuffing
them into the bucket you can fit in more.. and then another responded
that you can actually wet the news paper in water ( making a paper
pulp) and it will be have more pounds to it. What great answers... I am thinking about keeping a bucket of water at work, and every time
a change control comes in, print it out.. and let it soak into the
bucket... lets see how many we can fit in... And then again, change is a fact of life.. ( others being death and
taxes) ... so it is expected.. and must be handled... so a proper
analysis is needed, and that can only be done with a partnership
between the end user and the team to is building the tool/software for
the end user... However, we (including yours truly) seem to have the
habit of getting a signoff on a contract .. when we really need the
collaboration. Agile.. Anyone?
planning and budgeting the appropriate amount of time seems to be
always among the top three root causes of failure for all projects... There is a term that many people who are in the business of building
software use, :"Change Control"... wonder if this is a used
effectively ? Most cases, its adding to the scope with no change is
timeline... of delivery. And then again, we discuss a change control
for 12 hours, and the real change probably can be one in 1/2 and
tested in 4 hours.. ha!
Few days back, I asked my kids if you have a 12 gallon bucket , how
many pounds is that?
My thought was around a mathematical response.. you know... ( US
gallon of water weighs 8.34 pounds) .. but guess what kids being
kids... they said, if you take a lot of news paper and keep stuffing
them into the bucket you can fit in more.. and then another responded
that you can actually wet the news paper in water ( making a paper
pulp) and it will be have more pounds to it. What great answers... I am thinking about keeping a bucket of water at work, and every time
a change control comes in, print it out.. and let it soak into the
bucket... lets see how many we can fit in... And then again, change is a fact of life.. ( others being death and
taxes) ... so it is expected.. and must be handled... so a proper
analysis is needed, and that can only be done with a partnership
between the end user and the team to is building the tool/software for
the end user... However, we (including yours truly) seem to have the
habit of getting a signoff on a contract .. when we really need the
collaboration. Agile.. Anyone?
No comments:
Post a Comment