دانلود کتاب انتقال پایگاه داده حرفه ای به Azure – نوسازی داده ها برای سازمان

As any old timer in the IT industry can tell you, planning always helps when managing a project from inception to conclusion. Simple projects can go much more smoothly with an appropriately simple plan, such as a checklist. At the same time, projects that are complex and involve multiple teams are quite likely to need a commensurately more sophisticated plan with the input of many subject matter experts (SMEs) from both the business and IT side of your organization to ensure success. That is not to say that most projects actually get the level of attention to planning that they need and deserve, considering their importance to the organization. But even simple projects with relatively few steps can often go astray. Many IT practitioners have thought “I know what I’m getting into and I know what I’m doing. This’ll be three clicks of the mouse and I’m done,” only to find that they now have to spend three days fixing what they thought was going to be a three-hour project. In fact, many projects go astray even when there is a good plan in place, with the likelihood of difficulties increasing in proportion to the complexity of the IT project at hand. Yet the priority that most managers put on speedy action encourages the IT practitioners to play fast and loose with what should be an orderly, standardized process. Shortcuts are taken. Teams fail to communicate. Bad decisions are implemented with a passing thought to “We’ll fix that later.” Blind spots are missed. Requirements are misunderstood. Testing and quality assurance steps are shortchanged, with the expectation that the tests will come up roses without the need for any fixes.