Resource Library

Learn the ITIL® concepts of accountability, boundaries, and consistency (the ABCs) and discover how ITIL helps establish, manage, and maintain the ABCs.

This paper proposes a unifying model for project plans. A distinction will be made between the outputs of project planning and the project plan itself. The significance of this distinction is to allow projects of all types to be described at a high level, in a common language, regardless of the type of analysis used to develop the plan.

Resource management is always an issue in any project, especially when the stakeholders from whom we need time have operational duties to perform.  If our requirements team was at our disposal 100 percent, always completed activities on target, and worked a full eight hour day without distraction or a loss of productivity, then estimating time would be simple. Here, we explore standard approaches to time estimation, the dangers of multi-tasking, and estimation alternatives, which consider work habits and productivity norms.

The amount of data being produced does not seem to show any sign of slowing; if anything, it may in fact be exceeding projected growth rates. As these absolute limitations on raw hardware capacity begin to be felt, the importance of looking at all of the aspects of a computing infrastructure in order to tackle the future's truly large-scale computing demands, is imperative. This white paper examines how IBM's initiatives like Linux, Cloud Manager with OpenStack and the OpenPower Foundation IBM are meeting this challenge.

The National Institute of Standards and Technology (NIST) created a cloud definition that has been well-accepted across the IT industry. NIST was mandated to assist government agencies to adopt cloud computing for their IT operations. As part of their mandate, NIST created multiple working groups to define cloud computing, its architecture, and requirements. In this paper we explore the center core of NIST's cloud definition.

How can organizations in diverse industries continue to use familiar waterfall practices and at the same time be more agile? The answer is to use program management that is designed to be agile.

The process of subnetting is both a mathematical process and a network design process. Mathematics drives how subnets are calculated, identified, and assigned. The network design and requirements of the organization drive how many subnets are needed and how many hosts an individual subnet needs to support. Binary basics and IPv4 address structure were covered in part one of this two-part paper.

End of year IT project spending has a higher chance of failure. Instead, invest your funds in the resources that manage and own the technology—your people. Learn how to choose the best IT training company for you at the last minute..

Managing the change of DataStage components can often become a test of wills. Picture fitting a square peg in a round hole, and you might start to get the idea. The complexity of what is required to promote components from one environment to another during the development, testing, and eventual implementation in the production environments, should be and is often a controlled activity.

Nearly every WebSphere administrator has desired a deeper understanding of how passwords are created, used, stored, and encrypted. Learn about the different types of passwords used inside of the WebSphere Application Server and the recovery plans to help restore your server when passwords go awry.