information-technology-infrastructure-library

Information Technology Infrastructure Library

The Information Technology Infrastructure Library is a framework that was designed to standardize the IT services in a business, whether that be selection, planning, delivery, maintenance, or the overall lifecycle.

The Information Technology Infrastructure Library (ITIL) is a framework that describes the best practices for the delivery of IT services.

AspectExplanation
Concept OverviewInformation Technology Infrastructure Library (ITIL) is a widely adopted set of practices and guidelines for IT service management (ITSM) and IT operations. Developed by the UK government’s Central Computer and Telecommunications Agency (CCTA), ITIL provides a framework for effectively designing, delivering, managing, and improving IT services to meet business needs and align IT with business goals. ITIL emphasizes a customer-centric approach and continuous improvement.
Key ComponentsITIL comprises several key components:
1. Service Strategy: Focuses on defining the organization’s IT service strategy and aligning it with business goals.
2. Service Design: Involves designing IT services and related processes to meet business requirements and improve efficiency.
3. Service Transition: Ensures the smooth transition of services into the production environment, including change management and release management.
4. Service Operation: Manages IT services on a day-to-day basis, including incident management, problem management, and event management.
5. Continual Service Improvement: Promotes a culture of ongoing improvement in service quality and performance.
PrinciplesITIL is guided by several principles:
1. Customer Focus: Prioritizes customer needs and satisfaction, aligning IT services with business requirements.
2. End-to-End Service Delivery: Emphasizes the entire service lifecycle, from strategy to operation and improvement.
3. Value Creation: IT services should create value for the business, and investments should be justified.
4. Collaboration: Encourages collaboration and communication across IT and other business units.
5. Process Integration: Advocates for the integration of processes to achieve efficiency and effectiveness.
CertificationITIL offers certification levels, ranging from Foundation to Expert, to validate proficiency in IT service management practices. IT professionals can earn ITIL certifications to enhance their skills and career prospects.
ApplicationsITIL is applied in various industries and sectors, including information technology, healthcare, finance, and government, where IT services play a critical role in business operations. Organizations of all sizes, from small businesses to large enterprises, can benefit from ITIL practices.
BenefitsImplementing ITIL practices offers several benefits:
1. Improved Service Quality: ITIL helps ensure that IT services are reliable, efficient, and aligned with business needs.
2. Cost Reduction: Efficient processes and better resource utilization can lead to cost savings.
3. Enhanced Customer Satisfaction: Customer-focused practices improve user experience and satisfaction.
4. Risk Management: ITIL helps identify and mitigate IT-related risks.
5. Competitive Advantage: Organizations that excel in IT service management gain a competitive edge.
ChallengesChallenges in adopting ITIL include the need for cultural change within organizations, resource allocation, and the complexity of implementing and maintaining ITIL processes. Successful adoption requires commitment and support from leadership.

The history of ITILs

The first ITIL was developed in the 1980s by the Government of the United Kingdom’s Central Computer and Telecommunications Agency (CCTA).

When data centers decentralized and then adopted architectures that were more geographically diverse, process and deployment discrepancies caused substandard or inconsistent IT services within organizations.

In response to this problem, the CCTA reimagined IT and understood the importance of establishing consistent practices across the entire IT service lifecycle.

The first version of its ITIL – dubbed the Government Information Technology Infrastructure Management methodology – was printed for distribution in 1989 as a series of 31 books.

Version 2 was released in 2000 where each publication was streamlined by grouping various aspects of IT management.

Microsoft also utilized ITIL around this time to develop its Microsoft Operations Framework. 

Subsequent updates to the ITIL have occurred in 2007, 2011, and 2019. 

Contents of the Information Technology Infrastructure Library 

When ITIL V4 was released in 2019, it was similar to its predecessors with a core focus on process automation, service management improvement, and the integration of IT departments into the broader company. 

But it also made room for modern technology, tools, and software that enable organizations to be more agile and flexible.

To that end, V4 accommodates philosophies such as Agile, DevOps, and Lean and has shifted the core focus from IT Service Management (ITSM) to one of general service management

Key stages of the ITIL

Within the ITIL are five key stages which collectively describe 26 processes. Let’s take a brief look at these stages and a non-exhaustive list of processes below:

  1. Service Strategy – how to design, develop, and implement ITSM. Processes include Strategy Management for IT Services, Service Portfolio Management, and Financial Management for IT Services.
  2. Service Design – how to design services and processes. Example processes include Service Catalogue Management, Availability Management, and Supplier Management.
  3. Service Transition – how to handle a new or changed service and ensure all service management processes balance. Processes include Transition Planning and Support, Change Management, and Service Asset and Configuration Management.
  4. Service Operation – guidance on how to deliver and run services smoothly and reliably. Processes include Access Management, Service Request Fulfillment, and Incident Management.
  5. Continual Service Improvement (CSI) – the fifth key stage clarifies how IT services can be realigned as the needs of the business change. CSI is itself comprised of seven steps that detail how data should be measured, gathered, processed, and analyzed.

ITIL V4 guiding principles

Based on the ITIL Practitioner Exam, the latest version of the ITIL also defines seven guiding principles that cover aspects such as change management, measurement and metrics, and communication. 

Many of these principles are influenced by ideas born in other disciplines such as manufacturing and software development.

The seven principles include:

  1. Start where you are.
  2. Focus on value.
  3. Collaborate and promote visibility.
  4. Keep it simple and practical.
  5. Optimize and automate.
  6. Progress iteratively with feedback, and
  7. Think and work holistically.

Key takeaways:

  • The Information Technology Infrastructure Library (ITIL) is a framework that describes the best practices for the delivery of IT services. 
  • The ITIL has undergone several updates over the years to reflect advances in tech, tools, software, and various business practices and philosophies.
  • Within the ITIL are five key stages which collectively describe 26 processes. The five stages are Service Strategy, Service Design, Service Transition, Service Operation, and Continual Service Improvement.

Key Highlights

  • Introduction to ITIL:
    • ITIL is a framework designed to standardize IT services within businesses, covering aspects like selection, planning, delivery, maintenance, and the entire lifecycle of IT services.
    • ITIL describes best practices for delivering IT services and has gone through several updates over the years to reflect technological advancements and evolving business practices.
  • History of ITIL:
    • The first version of ITIL was developed in the 1980s by the UK Government’s Central Computer and Telecommunications Agency (CCTA).
    • ITIL emerged as a response to the challenges posed by decentralized data centers and geographically diverse architectures that led to inconsistent IT services.
    • The initial version, known as the Government Information Technology Infrastructure Management methodology, was published in 1989 as a series of 31 books.
    • Subsequent updates to ITIL were released in 2000 (Version 2), and further updates followed in 2007, 2011, and 2019.
  • Contents of ITIL:
    • ITIL V4, released in 2019, retains its core focus on process automation, service management improvement, and integration of IT departments into the broader company.
    • ITIL V4 accommodates modern philosophies such as Agile, DevOps, and Lean, shifting the focus from IT Service Management (ITSM) to general service management.
    • ITIL V4 introduces five key stages with 26 processes collectively:
      • Service Strategy
      • Service Design
      • Service Transition
      • Service Operation
      • Continual Service Improvement
  • ITIL V4 Guiding Principles:
    • ITIL V4 defines seven guiding principles that cover areas like change management, measurement, communication, and more.
    • These principles draw inspiration from various disciplines like manufacturing and software development.
    • The seven guiding principles are:
      • Start where you are.
      • Focus on value.
      • Collaborate and promote visibility.
      • Keep it simple and practical.
      • Optimize and automate.
      • Progress iteratively with feedback.
      • Think and work holistically.
  • Key Takeaways:
    • ITIL is a framework for best practices in delivering IT services.
    • ITIL has evolved over time to incorporate advancements in technology, tools, software, and business practices.
    • ITIL V4 introduces five key stages and 26 processes, focusing on service strategy, design, transition, operation, and continual service improvement.
    • ITIL V4 also includes seven guiding principles to help organizations effectively manage their IT services.

Case Studies

Case StudyDescriptionAnalysis
UK Government’s ITIL ImplementationThe United Kingdom’s government has adopted ITIL practices extensively to enhance the efficiency and quality of its IT services. By implementing ITIL frameworks and principles, the government has standardized its IT service management processes across various departments. This approach has led to improved service delivery, cost savings, and better alignment of IT with business objectives.The UK government’s ITIL adoption showcases how ITIL can be applied at a large scale to transform public sector IT operations and deliver better services to citizens.
Disney’s IT Service Management TransformationDisney, a global entertainment company, implemented ITIL practices to optimize its IT service management and support functions. By adopting ITIL processes, Disney achieved improved incident management, problem resolution, and change management, leading to enhanced IT service reliability and customer satisfaction. This transformation allowed Disney to provide seamless technology experiences to its guests and employees.Disney’s ITIL implementation demonstrates how ITIL frameworks can be tailored to meet the unique needs of large, multifaceted organizations, leading to enhanced IT service quality and user experiences.
NASA’s ITIL-Based IT Service ManagementNASA’s Jet Propulsion Laboratory (JPL) adopted ITIL practices to streamline its IT service management. JPL used ITIL principles to develop standardized processes for incident management, service request fulfillment, and change management. This implementation resulted in reduced downtime, quicker issue resolution, and improved collaboration among IT teams.NASA’s JPL case study highlights the effectiveness of ITIL in complex, mission-critical environments, where IT service reliability and efficiency are paramount.
IBM’s ITIL Adoption for Global IT OperationsIBM, a multinational technology company, incorporated ITIL practices into its global IT operations to enhance service quality and efficiency. By aligning ITIL processes with business goals, IBM improved incident response times, optimized resource utilization, and increased customer satisfaction. The company’s ITIL adoption facilitated a more agile and customer-focused IT environment.IBM’s ITIL adoption illustrates how large enterprises can leverage ITIL principles to enhance the agility and responsiveness of their IT operations while delivering value to clients and stakeholders.
Australian Government’s ITIL-Based Service DeskThe Australian Government’s Department of Human Services implemented ITIL-based service desk practices to provide efficient and user-focused customer support. This initiative involved the establishment of a centralized service desk and the adoption of ITIL processes for incident, problem, and change management. It resulted in improved service delivery and enhanced user satisfaction.The Australian Government’s case study demonstrates how ITIL-based service desk practices can help public sector organizations deliver efficient and user-centric services to citizens and stakeholders.
Microsoft’s ITIL Implementation for Azure CloudMicrosoft incorporated ITIL principles into the management of its Azure cloud platform. By applying ITIL practices, Microsoft enhanced incident management, service monitoring, and continuous improvement processes for Azure services. This led to improved service reliability and customer experiences for Azure users worldwide.Microsoft’s ITIL adoption for Azure showcases how ITIL can be integrated into cloud-based infrastructure to ensure the reliability and availability of critical services for global customers.
Boeing’s ITIL-Based IT Service ManagementBoeing, a leading aerospace and defense company, implemented ITIL practices to improve IT service management. By adopting ITIL frameworks, Boeing enhanced incident management, service request handling, and change management processes. This optimization resulted in increased IT service efficiency and responsiveness, supporting the company’s mission-critical operations.Boeing’s case study demonstrates how ITIL can be applied in complex and highly regulated industries to strengthen IT service management, align IT with business goals, and maintain operational excellence.
T-Mobile’s ITIL-Driven Service ImprovementT-Mobile, a telecommunications provider, utilized ITIL practices to drive service improvement initiatives. By implementing ITIL processes for incident, problem, and change management, T-Mobile reduced service disruptions, improved network performance, and enhanced customer experiences. This approach allowed T-Mobile to stay competitive in a dynamic industry.T-Mobile’s ITIL-driven service improvement exemplifies how ITIL frameworks can be leveraged to optimize network operations, enhance service quality, and meet the evolving needs of telecommunications customers.
University of Oxford’s ITIL-Based ITSMThe University of Oxford adopted ITIL-based IT service management (ITSM) practices to enhance its IT support services for students and staff. By implementing ITIL processes, the university improved incident resolution times, increased customer satisfaction, and achieved greater IT service transparency. This ITIL-driven transformation supported the university’s educational and research objectives.The University of Oxford’s case study illustrates how ITIL can be applied in educational institutions to provide reliable IT services, support academic activities, and meet the diverse needs of students and faculty members.
Related ConceptsDescriptionWhen to Apply
Information Technology Infrastructure Library (ITIL)ITIL is a framework of best practices for IT service management (ITSM) that focuses on aligning IT services with business needs and delivering value to customers. It provides a set of guidelines, processes, and procedures for managing IT services throughout their lifecycle, from design and transition to operation and improvement. ITIL helps organizations improve service quality, reduce costs, and increase efficiency by standardizing service delivery, enhancing collaboration, and fostering continuous improvement.– When implementing IT service management or enhancing service delivery. – Particularly in understanding ITIL principles, processes, and roles, and in exploring techniques to adopt ITIL practices, such as service design, incident management, and change control, to optimize IT service performance, align IT investments with business objectives, and improve customer satisfaction and user experience while reducing risks and maximizing value for the organization and its stakeholders.
Service DesignService Design is a phase in the ITIL service lifecycle that focuses on designing IT services to meet business requirements and customer needs effectively and efficiently. It involves defining service offerings, processes, and service level agreements (SLAs) and identifying the resources, capabilities, and technologies required to deliver and support services throughout their lifecycle. Service design aims to create value for customers and stakeholders by ensuring that services are reliable, scalable, and aligned with business goals and ITIL best practices.– When developing new IT services or improving existing services. – Particularly in understanding service design principles, methodologies, and tools, and in exploring techniques to implement service design practices, such as service catalog management, service level management, and capacity planning, to design and deliver IT services that meet customer expectations, support business objectives, and enable organizational growth and competitive advantage in dynamic and evolving markets.
Service TransitionService Transition is a phase in the ITIL service lifecycle that focuses on managing changes to IT services and transitioning them into production environments effectively and efficiently. It involves planning, testing, and deploying changes, releases, and service assets while minimizing disruptions and risks to service quality and continuity. Service transition aims to ensure that changes are implemented smoothly, validated against business requirements, and supported by appropriate documentation, training, and communication to stakeholders.– When implementing changes or deploying new services. – Particularly in understanding service transition processes, procedures, and controls, and in exploring techniques to manage service transitions, such as change management, release management, and knowledge management, to assess and mitigate risks, streamline deployment processes, and ensure the successful introduction of changes and new services into the production environment while maintaining service stability and minimizing disruptions to business operations.
Service OperationService Operation is a phase in the ITIL service lifecycle that focuses on delivering and supporting IT services to meet agreed service levels and customer expectations. It involves executing day-to-day operational activities, such as incident management, problem management, and request fulfillment, to ensure that IT services are available, reliable, and responsive to user needs and business demands. Service operation aims to maximize service uptime, minimize service disruptions, and optimize operational efficiency and effectiveness.– When managing IT operations or resolving service issues. – Particularly in understanding service operation processes, functions, and roles, and in exploring techniques to improve service operation performance, such as incident prioritization, service desk automation, and performance monitoring, to enhance service quality, responsiveness, and resilience, and to minimize service downtime and disruptions that impact business productivity and customer satisfaction.
Continual Service Improvement (CSI)Continual Service Improvement (CSI) is a phase in the ITIL service lifecycle that focuses on evaluating, analyzing, and improving IT services, processes, and performance over time. It involves setting clear objectives, collecting and analyzing performance data, identifying opportunities for improvement, and implementing corrective actions and initiatives to enhance service quality and efficiency continuously. CSI aims to drive innovation, foster a culture of continuous learning and improvement, and align IT services with changing business needs and customer expectations.– When optimizing IT service performance or driving organizational change. – Particularly in understanding CSI principles, methodologies, and metrics, and in exploring techniques to implement CSI practices, such as service measurement, benchmarking, and maturity assessments, to assess performance gaps, identify improvement opportunities, and drive strategic initiatives that enhance IT service value, agility, and resilience while maximizing business outcomes and customer satisfaction.
IT Service Management (ITSM)IT Service Management (ITSM) is an approach to designing, delivering, and supporting IT services to meet business needs and customer expectations effectively and efficiently. It involves adopting ITIL best practices, frameworks, and standards to manage IT services throughout their lifecycle, from strategy and design to operation and improvement. ITSM aims to align IT investments with business objectives, optimize service delivery processes, and improve IT service quality, reliability, and responsiveness to support organizational goals and enhance customer satisfaction.– When aligning IT with business objectives or improving service delivery. – Particularly in understanding ITSM principles, frameworks, and practices, and in exploring techniques to implement ITSM processes, such as service strategy, service design, and service operation, to optimize IT service performance, reduce costs, and mitigate risks, and to foster a customer-centric IT culture and mindset that prioritizes service excellence, innovation, and continuous improvement in a rapidly changing and competitive business environment.
IT GovernanceIT Governance is a framework of policies, processes, and controls that ensure IT investments and activities support business objectives, manage risks, and comply with regulatory requirements and industry standards. It involves defining decision rights, accountability structures, and performance metrics to align IT investments with business strategies, optimize resource allocation, and enhance IT service delivery and value creation. IT governance aims to maximize the business value of IT assets and capabilities while minimizing risks and costs.– When aligning IT with business strategy or managing IT risks. – Particularly in understanding IT governance frameworks, such as COBIT and ISO 27001, and in exploring techniques to establish IT governance structures, such as governance committees, risk assessments, and performance dashboards, to provide oversight, guidance, and assurance that IT investments and activities are aligned with business goals, comply with legal and regulatory requirements, and deliver measurable value and outcomes to the organization and its stakeholders.
Risk ManagementRisk Management is the process of identifying, assessing, and mitigating risks that may impact IT services, operations, or projects. It involves identifying potential threats and vulnerabilities, analyzing their likelihood and potential impact, and implementing controls and mitigation strategies to minimize risks to acceptable levels. Risk management aims to protect IT assets, safeguard business continuity, and enable informed decision-making and resource allocation to achieve business objectives effectively and securely.– When managing IT projects or protecting sensitive data. – Particularly in understanding risk management frameworks, such as ISO 31000 and NIST, and in exploring techniques to conduct risk assessments, such as risk registers, threat modeling, and vulnerability scanning, to identify and prioritize risks, develop risk mitigation plans, and monitor risk exposure and compliance to mitigate IT-related risks and vulnerabilities and ensure the resilience and security of IT services and operations.
Change ManagementChange Management is the process of planning, implementing, and controlling changes to IT services, systems, and infrastructure to minimize disruptions and ensure that changes are aligned with business objectives and ITIL best practices. It involves assessing change requests, analyzing their impact, obtaining approvals, and coordinating communication, training, and documentation to support successful change implementation and adoption. Change management aims to maximize the benefits of changes while minimizing risks and disruptions to service quality and continuity.– When implementing system upgrades or deploying new technologies. – Particularly in understanding change management processes, such as change evaluation and change authorization, and in exploring techniques to manage change requests, such as change advisory boards, change models, and change calendars, to assess and prioritize changes, mitigate risks, and facilitate change implementation and adoption while ensuring minimal impact on IT service stability and business operations.
Incident ManagementIncident Management is the process of restoring normal service operation as quickly as possible following an unplanned interruption or degradation of IT services. It involves logging, categorizing, prioritizing, and resolving incidents through effective diagnosis, escalation, and resolution procedures to minimize the impact on business operations and customer satisfaction. Incident management aims to restore service availability, performance, and quality to meet agreed service levels and restore business operations to normalcy promptly.– When responding to service outages or resolving technical issues. – Particularly in understanding incident management processes, such as incident detection and incident resolution, and in exploring techniques to streamline incident response, such as incident prioritization, escalation procedures, and incident post-mortems, to minimize service downtime, restore service availability, and mitigate the impact of incidents on business operations and customer experience while ensuring timely and effective incident resolution and communication with stakeholders.

Related Business Frameworks

AIOps

aiops
AIOps is the application of artificial intelligence to IT operations. It has become particularly useful for modern IT management in hybridized, distributed, and dynamic environments. AIOps has become a key operational component of modern digital-based organizations, built around software and algorithms.

Agile Methodology

agile-methodology
Agile started as a lightweight development method compared to heavyweight software development, which is the core paradigm of the previous decades of software development. By 2001 the Manifesto for Agile Software Development was born as a set of principles that defined the new paradigm for software development as a continuous iteration. This would also influence the way of doing business.

Agile Project Management

agile-project-management
Agile project management (APM) is a strategy that breaks large projects into smaller, more manageable tasks. In the APM methodology, each project is completed in small sections – often referred to as iterations. Each iteration is completed according to its project life cycle, beginning with the initial design and progressing to testing and then quality assurance.

Agile Modeling

agile-modeling
Agile Modeling (AM) is a methodology for modeling and documenting software-based systems. Agile Modeling is critical to the rapid and continuous delivery of software. It is a collection of values, principles, and practices that guide effective, lightweight software modeling.

Agile Business Analysis

agile-business-analysis
Agile Business Analysis (AgileBA) is certification in the form of guidance and training for business analysts seeking to work in agile environments. To support this shift, AgileBA also helps the business analyst relate Agile projects to a wider organizational mission or strategy. To ensure that analysts have the necessary skills and expertise, AgileBA certification was developed.

Business Model Innovation

business-model-innovation
Business model innovation is about increasing the success of an organization with existing products and technologies by crafting a compelling value proposition able to propel a new business model to scale up customers and create a lasting competitive advantage. And it all starts by mastering the key customers.

Continuous Innovation

continuous-innovation
That is a process that requires a continuous feedback loop to develop a valuable product and build a viable business model. Continuous innovation is a mindset where products and services are designed and delivered to tune them around the customers’ problem and not the technical solution of its founders.

Design Sprint

design-sprint
A design sprint is a proven five-day process where critical business questions are answered through speedy design and prototyping, focusing on the end-user. A design sprint starts with a weekly challenge that should finish with a prototype, test at the end, and therefore a lesson learned to be iterated.

Design Thinking

design-thinking
Tim Brown, Executive Chair of IDEO, defined design thinking as “a human-centered approach to innovation that draws from the designer’s toolkit to integrate the needs of people, the possibilities of technology, and the requirements for business success.” Therefore, desirability, feasibility, and viability are balanced to solve critical problems.

DevOps

devops-engineering
DevOps refers to a series of practices performed to perform automated software development processes. It is a conjugation of the term “development” and “operations” to emphasize how functions integrate across IT teams. DevOps strategies promote seamless building, testing, and deployment of products. It aims to bridge a gap between development and operations teams to streamline the development altogether.

Dual Track Agile

dual-track-agile
Product discovery is a critical part of agile methodologies, as its aim is to ensure that products customers love are built. Product discovery involves learning through a raft of methods, including design thinking, lean start-up, and A/B testing to name a few. Dual Track Agile is an agile methodology containing two separate tracks: the “discovery” track and the “delivery” track.

Feature-Driven Development

feature-driven-development
Feature-Driven Development is a pragmatic software process that is client and architecture-centric. Feature-Driven Development (FDD) is an agile software development model that organizes workflow according to which features need to be developed next.

eXtreme Programming

extreme-programming
eXtreme Programming was developed in the late 1990s by Ken Beck, Ron Jeffries, and Ward Cunningham. During this time, the trio was working on the Chrysler Comprehensive Compensation System (C3) to help manage the company payroll system. eXtreme Programming (XP) is a software development methodology. It is designed to improve software quality and the ability of software to adapt to changing customer needs.

Lean vs. Agile

lean-methodology-vs-agile
The Agile methodology has been primarily thought of for software development (and other business disciplines have also adopted it). Lean thinking is a process improvement technique where teams prioritize the value streams to improve it continuously. Both methodologies look at the customer as the key driver to improvement and waste reduction. Both methodologies look at improvement as something continuous.

Lean Startup

startup-company
A startup company is a high-tech business that tries to build a scalable business model in tech-driven industries. A startup company usually follows a lean methodology, where continuous innovation, driven by built-in viral loops is the rule. Thus, driving growth and building network effects as a consequence of this strategy.

Kanban

kanban
Kanban is a lean manufacturing framework first developed by Toyota in the late 1940s. The Kanban framework is a means of visualizing work as it moves through identifying potential bottlenecks. It does that through a process called just-in-time (JIT) manufacturing to optimize engineering processes, speed up manufacturing products, and improve the go-to-market strategy.

Rapid Application Development

rapid-application-development
RAD was first introduced by author and consultant James Martin in 1991. Martin recognized and then took advantage of the endless malleability of software in designing development models. Rapid Application Development (RAD) is a methodology focusing on delivering rapidly through continuous feedback and frequent iterations.

Scaled Agile

scaled-agile-lean-development
Scaled Agile Lean Development (ScALeD) helps businesses discover a balanced approach to agile transition and scaling questions. The ScALed approach helps businesses successfully respond to change. Inspired by a combination of lean and agile values, ScALed is practitioner-based and can be completed through various agile frameworks and practices.

Spotify Model

spotify-model
The Spotify Model is an autonomous approach to scaling agile, focusing on culture communication, accountability, and quality. The Spotify model was first recognized in 2012 after Henrik Kniberg, and Anders Ivarsson released a white paper detailing how streaming company Spotify approached agility. Therefore, the Spotify model represents an evolution of agile.

Test-Driven Development

test-driven-development
As the name suggests, TDD is a test-driven technique for delivering high-quality software rapidly and sustainably. It is an iterative approach based on the idea that a failing test should be written before any code for a feature or function is written. Test-Driven Development (TDD) is an approach to software development that relies on very short development cycles.

Timeboxing

timeboxing
Timeboxing is a simple yet powerful time-management technique for improving productivity. Timeboxing describes the process of proactively scheduling a block of time to spend on a task in the future. It was first described by author James Martin in a book about agile software development.

Scrum

what-is-scrum
Scrum is a methodology co-created by Ken Schwaber and Jeff Sutherland for effective team collaboration on complex products. Scrum was primarily thought for software development projects to deliver new software capability every 2-4 weeks. It is a sub-group of agile also used in project management to improve startups’ productivity.

Scrum Anti-Patterns

scrum-anti-patterns
Scrum anti-patterns describe any attractive, easy-to-implement solution that ultimately makes a problem worse. Therefore, these are the practice not to follow to prevent issues from emerging. Some classic examples of scrum anti-patterns comprise absent product owners, pre-assigned tickets (making individuals work in isolation), and discounting retrospectives (where review meetings are not useful to really make improvements).

Scrum At Scale

scrum-at-scale
Scrum at Scale (Scrum@Scale) is a framework that Scrum teams use to address complex problems and deliver high-value products. Scrum at Scale was created through a joint venture between the Scrum Alliance and Scrum Inc. The joint venture was overseen by Jeff Sutherland, a co-creator of Scrum and one of the principal authors of the Agile Manifesto.
Scroll to Top

Discover more from FourWeekMBA

Subscribe now to keep reading and get access to the full archive.

Continue reading

FourWeekMBA