Wednesday, December 14, 2011
Think about this situation...?
Consider the following...you are an experienced programmer working on a project that deals with timing mechanisms. The project you are working on has fallen behind the original development schedule and a great deal of pressure is being applied by your organization's management to get back on schedule. Your manager comes you to with a plan on how to "get back on track" quickly. Unfortunately, it involves cutting the amount of "testing" of the new product by about 50%. You voice your concerns because the programming effort is extremely complex and the potential for programming errors is high. Your manager acknowledges your objections, but also indicates that this project represents considerable income to your organization...not only with the current project but also future contracts. Meeting the deadline is key to future efforts and involves millions in revenue and thousands of jobs. Your manager decides the risk has to be taken. What should you do? (Note. Realize that you could potentially lose your job if you object to loudly)
Subscribe to:
Post Comments (Atom)
0 comments:
Post a Comment