Avoid Scheduling Failures
来源:互联网 发布:js 调用微信打开链接 编辑:程序博客网 时间:2024/04/29 10:09

Avoid Scheduling Failures
Norman Carnovale
FAilEd pRojECTS CAn HAppEn FoR A MulTiTudE oF REASonS. One of the most common sources of failure is altering the project schedule in mid- stream without proper planning. This kind of failure is avoidable, but it can require major effort on the part of multiple people. Adjusting the timeline or increasing resources on a project are not normally of concern. Problems start when you are asked to do more in the same timeline or when the schedule is shortened without reducing the workload.
The idea that schedules can be shortened in order to reduce cost or speed up delivery is a very common misconception. You’ll commonly see attempts to require overtime or sacrifice “less important scheduled tasks” (like unit test- ing) as a way to reduce delivery dates, or increase functionality while keeping the delivery dates as is. Avoid this scenario at all costs. Remind those request- ing the changes of the following facts:
• A rushed design schedule leads to poor design, bad documentation, and probable quality assurance or user acceptance problems.
• A rushed coding or delivery schedule has a direct relationship to the number of bugs delivered to the users.
• A rushed test schedule leads to poorly tested code and has a direct rela- tionship to the number of testing issues encountered.
• All of the above lead to production issues, which are much more expensive to fix.


The end result is an increase in cost as opposed to a reduction. This is nor- mally why the failures happen.
As an architect you will one day find yourself in the position of having to act quickly to increase the likelihood of success. Speak up early. First try to maintain quality by negotiating the originally planned timeline. If a shortened schedule is necessary, then try to move noncritical functionality to future release(s). Obviously this will take good preparation, negotiating skills, and a knack for influencing people. Prepare by sharpening your skills in those areas today. You will be glad you did.
Norman Carnovale is an IT architect working for Lockheed Martin Professional Services on Homeland Security–related projects. He was formerly a software consultant, instructor, and architect for Davalen, LLC (http://www.davalen.com), a Premier IBM Business Partner specializing in WebSphere Portlet Factory, Web- Sphere Portal, and Lotus Domino projects.
- Avoid Scheduling Failures
- Software Development Failures
- ORACLE DBA_JOBS中的FAILURES
- Avoid Procrastination
- Avoid Finalizers
- gpl avoid
- avoid zombie
- type of failures and recovery
- dba_jobs里面的failures字段
- 解决DataNode Volume Failures故障
- CPU Scheduling
- scheduling class
- POJ1180Batch Scheduling
- scheduling algorithm
- Process scheduling
- Batch Scheduling
- Scheduling Tasks
- 关于Too many fetch-failures错误
- 架构师速成8.3-架构师必须要了解的规则
- IT忍者神龟之Microsoft Office Enterprise 2007 简体版 企业版 序列号
- Eclipse中10个最有用的快捷键组合
- 字符统计3 SDUT 2104
- 架构师速成8.3-可用性
- Avoid Scheduling Failures
- 復之之理
- 如何提高nodejs程序的稳定性,健壮性
- Qt中使用ActiveX(一)
- AForge类库调用摄像头
- Algorithms—143.Reorder List
- IOS开发-文件管理(二)
- codeforces(567A)--A. Lineland Mail--B. Berland National Library
- 产品健康度模型(1) 任务介绍