background preloader

Information Technology Infrastructure Library

Information Technology Infrastructure Library
ITIL (formerly known as the Information Technology Infrastructure Library) is a set of practices for IT service management (ITSM) that focuses on aligning IT services with the needs of business. In its current form (known as ITIL 2011 edition), ITIL is published as a series of five core volumes, each of which covers a different ITSM lifecycle stage. Although ITIL underpins ISO/IEC 20000 (previously BS15000), the International Service Management Standard for IT service management, the two frameworks do have some differences. ITIL describes processes, procedures, tasks, and checklists which are not organization-specific, but can be applied by an organization for establishing integration with the organization's strategy, delivering value, and maintaining a minimum level of competency. It allows the organization to establish a baseline from which it can plan, implement, and measure. It is used to demonstrate compliance and to measure improvement. History[edit] The Five Volumes : Related:  Development ProcessesProfessional Necessities

The Open Group Architecture Framework Structure of the TOGAF Architecture Development Method (ADM).[1] The Open Group Architecture Framework (TOGAF) is a framework for enterprise architecture which provides an approach for designing, planning, implementing, and governing an enterprise information technology architecture.[2] TOGAF has been a registered trademark of The Open Group in the United States and other countries since 2011.[3] TOGAF is a high level approach to design. It is typically modeled at four levels: Business, Application, Data, and Technology. It relies heavily on modularization, standardization, and already existing, proven technologies and products. Overview[edit] An architecture framework is a set of tools which can be used for developing a broad range of different architectures.[4] It should: TOGAF is such an architecture framework. The Architecture Development Method (ADM) is core of TOGAF which describes a method for developing and managing the lifecycle of enterprise architecture. History[edit]

itilfrance The Pomodoro Technique® What is The Pomodoro Technique? EASY for anyone to use! Improves productivity IMMEDIATELY! FUN to do! Why Pomodoro? The Pomodoro Technique isn’t like any other time-management method on the market today. For many people, time is an enemy. Essential to the Pomodoro Technique is the notion that taking short, scheduled breaks while working eliminates the “running on fumes” feeling you get when you’ve pushed yourself too hard. Whether it’s a call, a Facebook message, or suddenly realizing you need to change the oil in your car, many distracting thoughts and events come up when you’re at work. Most of us are intimately acquainted with the guilt that comes from procrastinating. Who does the technique work for? These are all ways real folks use the Pomodoro Technique: Motivate yourself to write.Limit distractions.Keep track of how long you’re spending brainstorming / writing / revising.Reduce back and neck pain by walking around during Pomodoro breaks.Draft a book in three weeks. How It works

Checklist SLA OLA ITIL Process: ITIL 2011 Service Design - Service Level Management Checklist Category: Templates ITIL 2011 - Service Design Source: Checklist "Service Level Agreement (SLA), Operational Level Agreement (OLA)" from the ITIL Process Map Overview This checklist serves as a template for a Service Level Agreement (SLA), and an Operational Level Agreement (OLA). It covers two document types which use identical structures: Service Level Agreement (SLA) - an agreement between an IT service provider and a customer. The following statements on Service Level Agreements are therefore equally applicable to OLAs, with one important point to consider: When agreeing an SLA, the Service Provider acts as a provider of services to the business; in the case of an OLA, the agreement is between two parties within the service provider organization. The SLA document evolves from the Service Level Requirements during the Service Design process. Service Level Agreement - Contents Service name Contract duration Glossary=

Configuration management database A configuration management database (CMDB) is a repository that acts as a data warehouse for information technology (IT) installations. It holds data relating to a collection of IT assets (commonly referred to as configuration items (CI)), as well as to descriptive relationships between such assets. When populated, the repository provides a means of understanding: the composition of critical assets such as information systemsthe upstream sources or dependencies of assetsthe downstream targets of assets Purpose and benefits[edit] CMDBs are used to keep track of the state of different things that are normally referred to as assets, such as products, systems, software, facilities, and people as they exist at specific points in time, as well as the relationships between such assets. The Information Technology Infrastructure Library (ITIL) framework, describes the use of CMDBs as part of infrastructure operations and support. Contents[edit] CI attributes and data[edit] CI types are:

Zachman Framework The Zachman Framework of enterprise architecture The Zachman Framework is not a methodology in that it does not imply any specific method or process for collecting, managing, or using the information that it describes.;[2] rather, it is an Ontology whereby a schema for organizing architectural artifacts (in other words, design documents, specifications, and models) is used to take into account both whom the artifact targets (for example, business owner and builder) and what particular issue (for example, data and functionality) is being addressed.[3] The framework is named after its creator John Zachman, who first developed the concept in the 1980s at IBM. It has been updated several times since.[4] Overview[edit] The term "Zachman Framework" has multiple meanings. Collage of Zachman Frameworks as presented in several books on Enterprise Architecture from 1997 to 2005. The framework is a logical structure for classifying and organizing the descriptive representations of an enterprise.

itSMF France Scrum (software development) Scrum is an iterative and incremental agile software development framework for managing product development. It defines "a flexible, holistic product development strategy where a development team works as a unit to reach a common goal", challenges assumptions of the "traditional, sequential approach" to product development, and enables teams to self-organize by encouraging physical co-location or close online collaboration of all team members, as well as daily face-to-face communication among all team members and disciplines in the project. A key principle of Scrum is its recognition that during a project the customers can change their minds about what they want and need (often called "requirements churn"), and that unpredicted challenges cannot be easily addressed in a traditional predictive or planned manner. Later, Schwaber with others founded the Scrum Alliance and created the Certified Scrum Master programs and its derivatives. Each sprint is started by a planning meeting.

seeks full-time senior GNU/Linux systems administrator Update: The deadline for this position has been extended to June 2nd, 2014. The ideal candidate will be a well-rounded GNU/Linux systems administrator who thrives on constant broad-based learning and problem-solving. (S)he will be familiar with the free software community and how it works, and will be more interested in making a substantial contribution to software freedom and having employment consistent with ethical ideals than obtaining the highest salary. This is an opportunity to work for the organization that started the GNU Project, launched the free software movement, and safeguards the GNU General Public License. The position includes frequent contact and collaboration with many of the core GNU developers, and currently reports to the executive director. Together, the senior systems administrators have a great deal of influence over technology decisions within the FSF, and do crucial work empowering thousands of others to develop free software. Useful specific experience includes:

Configuration management Top level Configuration Management Activity model Configuration management (CM) is a systems engineering process for establishing and maintaining consistency of a product's performance, functional and physical attributes with its requirements, design and operational information throughout its life.[1][2] The CM process is widely used by military engineering organizations to manage complex systems, such as weapon systems, vehicles, and information systems. Outside the military, the CM process is also used with IT service management as defined by ITIL, resp. ISO/IEC 20000, and with other domain models in the civil engineering and other industrial engineering segments such as roads, bridges, canals, dams, and buildings.[3][4][5] Introduction[edit] CM, when applied over the life cycle of a system, provides visibility and control of its performance, functional and physical attributes. History[edit] Overview[edit] Software[edit] Configuration management database[edit] Information assurance[edit]

Related:  Sp2Wikipedia