contextual-inquiry

What Is Contextual Inquiry? Contextual Inquiry In A Nutshell

Contextual inquiry is a research method based on user-centered design (USD) and is part of the contextual design methodology. Contextual inquiry as a research method does not involve setting people certain tasks. Instead, users are observed while they work in their own environments. The context of these environments typically encompasses the home, office, or somewhere else entirely.

ElementDescription
Concept OverviewContextual Inquiry is a user-centered research method used in the field of human-computer interaction (HCI) and user experience (UX) design. It involves direct observation and interaction with users in their real-world context to gain insights into their needs, tasks, and behaviors.
Key ComponentsContextual Inquiry typically includes the following components: (1) Context, (2) Partnership, (3) Observation, (4) Interview, (5) Interpretation, (6) Documentation, (7) Consolidation.
ContextThe process begins by understanding the context in which users operate. This includes identifying the physical environment, tools, artifacts, and social aspects that influence their work or tasks.
PartnershipEstablishing a collaborative partnership with users is essential. Researchers work closely with participants, seeking their active involvement and insights. This partnership fosters trust and ensures that users feel comfortable sharing their experiences.
ObservationResearchers observe users as they perform tasks or interact with products or systems. This direct observation provides rich data on how users navigate challenges, make decisions, and interact with technology.
InterviewContextual Inquiry combines observation with contextual interviews. Researchers ask open-ended questions while observing users, encouraging them to share their thought processes, goals, and pain points during their actions.
InterpretationData collected from observations and interviews are analyzed and interpreted to identify patterns, user needs, and usability issues. Researchers look for insights into user behaviors, preferences, and pain points to inform design decisions.
DocumentationFindings are documented in detail, often through field notes, photos, audio recordings, or video footage. These records capture the user’s context, actions, and quotes that are valuable for analysis and future reference.
ConsolidationResearchers consolidate and synthesize the data, identifying key findings, themes, and design recommendations. This step ensures that insights are effectively communicated to the design and development teams.
Implications of Contextual Inquiry– User-Centered Design: Contextual Inquiry places users at the center of the design process, ensuring that products and systems align with their needs. – In-Context Insights: It provides insights into real-world user behaviors and challenges, which are invaluable for designing user-friendly solutions. – Iterative Design: The iterative nature of contextual inquiry allows for ongoing refinement and improvement of designs based on user feedback.
Benefits of Contextual Inquiry– Deeper Understanding: It leads to a deeper understanding of user needs, preferences, and behaviors. – Improved Usability: Design decisions based on contextual insights result in more usable and user-friendly products. – Enhanced User Satisfaction: By addressing user pain points, products are more likely to meet user expectations and lead to higher satisfaction. – Reduced Development Costs: Early identification of usability issues and changes in context can save time and resources in the long run.
Drawbacks and Limitations– Resource-Intensive: Contextual Inquiry can be time-consuming and resource-intensive, requiring skilled researchers and access to users in their natural settings. – Limited Scalability: Due to its intensive nature, it may not be suitable for large-scale usability studies. – Potential Bias: Researchers may introduce bias unintentionally through their presence or questioning. – Ethical Considerations: Privacy and ethical concerns may arise when observing users in their private or sensitive settings.
Applications of the Approach– User Experience Design: Contextual Inquiry is widely used in UX design to inform the creation of user interfaces and digital products. – Product Development: It informs the development of physical products to ensure they meet user needs and are user-friendly. – Healthcare: Contextual Inquiry is applied in healthcare settings to understand clinical workflows, patient interactions, and usability of medical devices. – Education: It helps educators gain insights into the learning experiences of students and informs the design of educational tools and platforms.
Examples of Contextual Inquiry– Software Design: A software development team conducts contextual inquiry to observe how users interact with a new application, identifying usability issues and making iterative improvements. – Medical Device Development: Researchers visit healthcare facilities to understand how nurses use a medical device in patient care, leading to design changes that enhance efficiency and safety. – Product Redesign: A consumer product manufacturer observes users in their homes to understand how a household product is used and identify opportunities for design enhancements. – Educational Technology: Researchers visit schools to study how students and teachers use an educational technology platform, leading to improvements that better support learning outcomes.

Understanding contextual inquiry

During the observation process, researchers ask questions to understand how and why users do what they do. Since these users are interviewed in a “natural” environment, the analysis data collected through questioning are more realistic than the data collected in a laboratory. 

The contextual inquiry technique is generally used at the start of a design process and allows the organization to gather rich information on work practices, user tools, and social, technical, and physical environments.

The four principles of contextual inquiry

Contextual inquiry is based on four guiding principles:

  1. Context – as hinted at earlier, the observation and interviewing of the user must take place in the context of use. Labs and conference rooms should be avoided.
  2. Partnership – to better understand what the participant is doing and why, a collaborative partnership between the researcher and participant is key. Contextual inquiries shift from observing to discussing and back again. Furthermore, the researcher should refrain from dominating the discussion lest important insights are missed.
  3. Mutual interpretation – this means the researcher explains the conclusions they have reached or the interpretations they have made to the participant throughout the process. Where applicable, the participant can correct or deepen particular observations made by the researcher.
  4. Focus – lastly, the researcher must remain focused on the topics worthy of further exploration. To that end, they may ask the participant to perform important tasks stipulated in the research brief.

Conducting a contextual inquiry

First and foremost, researchers are required to select suitably qualified participants in the field they are hoping to better understand. 

Once the appropriate expertise has been identified, researchers can follow this four-step process:

  1. Start with a primer – to help the participant feel more comfortable, researchers should informally introduce themselves and take the time to build rapport. They should outline what they hope to achieve from the process and ask for a summary of the work to be done during the allocated time.
  2. Transition – once pleasantries have been exchanged, an explicit transition should be made from the introduction to the contextual interview component of the meeting. The user should be notified of what to expect as they perform their work, including any interruptions if the researcher requires further clarification.
  3. The interview – an iterative, two-step process where the researcher observes the participant and initiates discussion points as required. Discussion should only occur for two reasons. The first is when the researcher has observed something they don’t understand. The second is to allow the participant to validate (or invalidate) the researcher’s understanding of their mental model. The researcher must also note the external resources being used and observe whether there are uncommon process variations or extra steps.
  4. Conclude – most contextual inquiries conclude within a few hours, but some larger studies may take a day or two. The researcher concludes by reviewing their notes and summarising what they learned from the interview. By discussing the interpretation of the observed process, both parties have a final chance to clarify important points.

When to Use Contextual Inquiry:

Contextual Inquiry is applicable in various user research scenarios:

  1. Product Development: Use it during the early stages of product development to uncover user needs and inform design decisions.
  2. Usability Testing: It complements usability testing by providing a deeper understanding of user behaviors and motivations.
  3. Service Design: Apply it to gain insights into how users interact with services and identify opportunities for improvement.
  4. Process Optimization: Use it in business process optimization to understand how employees perform tasks and identify bottlenecks.
  5. User Experience (UX) Design: Contextual Inquiry informs the design of user interfaces, ensuring they meet users’ real-world needs.

Drawbacks and Limitations of Contextual Inquiry:

While Contextual Inquiry offers numerous advantages, it also has certain drawbacks and limitations:

  1. Resource-Intensive: Conducting on-site observations can be resource-intensive, requiring time and travel expenses.
  2. Limited Generalizability: Findings may be specific to the observed participants and settings and may not generalize to all users.
  3. Influence of Observer: The presence of an observer may alter participants’ behaviors, potentially leading to biased observations.
  4. Interpretation Challenges: Analyzing and interpreting observational data can be subjective and challenging.
  5. Time-Consuming: Contextual Inquiry can be time-consuming, particularly when observing complex processes or workflows.

What to Expect from Using Contextual Inquiry:

Using Contextual Inquiry can lead to several outcomes and benefits:

  1. Deeper Understanding: Expect a deeper understanding of user needs, behaviors, and motivations within their natural context.
  2. Actionable Insights: Gain actionable insights that can inform product or service design, leading to more user-centered solutions.
  3. Improved Usability: Identify usability issues and opportunities for improvement by observing real-world interactions.
  4. Enhanced Empathy: Foster empathy for users by experiencing their challenges and pain points firsthand.
  5. Iterative Design: Support iterative design and development processes by continuously incorporating user insights.

Relevance in Modern User-Centered Design and Research:

Contextual Inquiry remains highly relevant in modern user-centered design and research, including:

  1. User Experience (UX) Design: UX designers use Contextual Inquiry to create designs that align closely with user needs and behaviors.
  2. Agile Development: Contextual Inquiry complements agile methodologies by providing continuous user feedback for ongoing improvements.
  3. Service Design: In service design, it helps organizations understand how customers interact with services and identify areas for enhancement.
  4. Digital Product Development: Digital product development teams use Contextual Inquiry to inform the design of websites, apps, and software.
  5. Human-Centered Design Thinking: Contextual Inquiry is a foundational element of human-centered design thinking processes.

Conclusion:

Contextual Inquiry is a powerful user research method that uncovers user needs and behaviors by observing them in their natural environments. By providing deep insights into how users interact with products, services, or systems, it informs user-centered design and decision-making. While recognizing its resource-intensive nature and limitations, organizations continue to rely on Contextual Inquiry as a fundamental tool in modern user-centered design and research efforts to create products and services that better meet user needs and expectations.

Examples

  • UX Design Agency: Conducts contextual inquiries with end-users to create user-friendly digital products, such as websites and mobile apps, by observing how they interact with interfaces.
  • Healthcare Research: Studies nurses’ workflows in hospitals to improve patient care through better-designed systems and technologies, enhancing the efficiency of medical staff.
  • Software Development Company: Observes project managers in various industries to inform the design of project management software, making it more intuitive and aligned with real-world needs.
  • E-learning Platform: Enhances user experience by conducting contextual inquiries with students to understand their study habits, preferences, and pain points, leading to more effective online learning environments.
  • Automotive Design: Studies driver behaviors and preferences through contextual inquiry to inform the design of future vehicle interfaces, safety features, and autonomous driving systems.
  • Customer Support Center: Observes support agents as they handle customer inquiries, helping organizations improve support processes, reduce response times, and enhance customer satisfaction.
  • Mobile App Development: Explores user app usage patterns by conducting contextual inquiries, enabling developers to prioritize feature enhancements, streamline navigation, and refine user interfaces.
  • Smart Home Technology: Observes residents in their homes to develop intuitive and user-friendly home automation systems, ensuring that technology seamlessly integrates into their daily lives.
  • Educational Institution: Conducts contextual inquiries with teachers and students to refine curriculum materials and classroom technologies, optimizing the learning experience.
  • Financial Services: Studies how financial advisors interact with software tools during client consultations to design more efficient and supportive financial planning platforms.
  • Manufacturing: Observes assembly line workers to improve ergonomics and workflow efficiency, leading to safer and more productive manufacturing processes.
  • Market Research: Conducts contextual inquiries with consumers to gain insights into their shopping behaviors, preferences, and decision-making processes, aiding in product development and marketing strategies.
  • Gaming Industry: Studies player interactions and feedback within video games to enhance gameplay, identify bugs, and create more immersive gaming experiences.
  • Library Services: Observes library patrons to optimize the library’s physical layout, catalog systems, and services, improving user satisfaction and access to resources.
  • Agriculture: Conducts contextual inquiries with farmers to develop agricultural technology solutions that address specific challenges in crop management and yield optimization.
  • Retail Stores: Studies customer behavior and interactions with in-store displays and layouts to enhance the shopping experience and boost sales.
  • Transportation Services: Observes commuters and travelers to improve public transportation systems, airport layouts, and passenger experiences.
  • Social Media Platforms: Conducts contextual inquiries with users to understand content creation habits and preferences, informing platform updates and algorithms.
  • Environmental Conservation: Studies park rangers and conservationists to design tools and systems for tracking and preserving natural habitats more effectively.
  • Human Resources: Observes HR professionals to develop HR software that streamlines recruitment, onboarding, and employee management processes.

Key takeaways:

  • Contextual inquiry is a research method based on user-centered design (USD) and is part of the contextual design methodology.
  • The four principles of contextual inquiry are context, partnership, mutual interpretation, and focus. Observation must take place in a contextual work environment, with labs and conference rooms avoided.
  • Contextual inquiry begins with identifying suitably qualified or knowledgeable participants. After which, researchers must start with a primer to build rapport and comfort levels. They should then transition to the interview itself, an iterative two-step process of observing and asking. Concluding the process means summarising what was observed and clarifying important points.

Key Highlihgts:

  • Introduction to Contextual Inquiry:
    • Contextual inquiry is a user-centered research method and part of the contextual design methodology.
    • It involves observing users in their natural environments while they work, without giving them specific tasks to perform.
  • Key Principles of Contextual Inquiry:
    • Context: Observation and interviewing take place in the actual context of use (home, office, etc.) rather than artificial environments.
    • Partnership: A collaborative relationship between the researcher and participant is essential for understanding user actions and motivations.
    • Mutual Interpretation: The researcher shares their interpretations with the participant, who can validate, correct, or deepen insights.
    • Focus: Researchers should stay focused on exploring relevant topics identified in the research brief.
  • Process of Conducting Contextual Inquiry:
    • Participant Selection: Choose participants with suitable expertise in the field of study.
    • Start with a Primer: Build rapport, introduce the process, and discuss the goals of the inquiry.
    • Transition: Explicitly move from the introduction to the contextual interview phase.
    • The Interview: An iterative process involving observation and discussion points. Discussions occur to clarify observations and validate the researcher’s understanding of the participant’s mental model.
    • Conclude: Summarize the interview, review notes, and clarify important points. Larger studies may take a day or two to conclude.
Related FrameworksDescriptionWhen to Apply
Contextual InquiryContextual Inquiry is a user-centered research method used to understand users’ behaviors, needs, and challenges in their natural environment. It involves observing users directly, asking open-ended questions, and capturing contextually relevant information.When conducting user research for product design or service improvement, understanding user behaviors and needs in their real-world context, or gathering insights to inform design decisions and product development.
Ethnographic ResearchEthnographic Research is a qualitative research method that involves immersing researchers in the daily lives and routines of users to understand their behaviors, beliefs, and cultural contexts. It provides deep insights into user experiences and perspectives.When exploring cultural influences on consumer behaviors and preferences, understanding user lifestyles and cultural norms, or identifying unmet needs and opportunities for innovation in diverse cultural contexts.
User InterviewsUser Interviews are structured conversations with users aimed at gathering insights into their attitudes, behaviors, and needs. They can be conducted in person, over the phone, or online and provide valuable qualitative data to inform design decisions.When seeking user feedback on existing products or services, exploring user preferences and pain points, or validating design concepts and feature ideas through direct user input and insights.
User PersonasUser Personas are fictional representations of target users based on research and data. They embody key characteristics, behaviors, and goals of different user segments, helping teams empathize with users and make user-centered design decisions.When developing user-centered design strategies, empathizing with target users, or aligning product features and marketing messages with user needs and preferences to create more relevant and engaging experiences.
Journey MappingJourney Mapping is a visualization technique used to illustrate the user’s end-to-end experience with a product or service. It helps teams understand the user’s interactions, emotions, and pain points at each touchpoint, identifying opportunities for improvement.When analyzing user experiences across multiple touchpoints, identifying pain points and opportunities for enhancement, or optimizing customer journeys to create seamless and engaging experiences throughout the user lifecycle.
Usability TestingUsability Testing involves observing users as they interact with a product or prototype to identify usability issues and gather feedback. It helps teams evaluate the effectiveness, efficiency, and satisfaction of a product’s user interface and design.When evaluating the usability of digital products or interfaces, identifying navigation issues and usability barriers, or validating design decisions and iterating prototypes based on user feedback to improve overall user experience.
Card SortingCard Sorting is a method used to understand how users categorize and organize information. It involves asking users to group content or features into categories that make sense to them, providing insights into their mental models and preferences.When designing information architecture or navigational structures, organizing website content or menu items, or validating user-centered taxonomy and menu labels to improve findability and user comprehension.
Co-creation WorkshopsCo-creation Workshops bring together stakeholders, designers, and users to collaborate on generating ideas, designing solutions, and solving problems. They foster creativity, empathy, and cross-functional collaboration, leading to innovative and user-centered outcomes.When fostering collaboration and creativity in problem-solving, generating innovative ideas and design concepts, or aligning stakeholders and users around shared goals and design objectives for better outcomes and solutions.
A/B TestingA/B Testing is a quantitative research method used to compare two or more versions of a webpage, email, or app feature to determine which one performs better in terms of user engagement or conversion metrics. It helps optimize design decisions based on real user data and behavior.When evaluating design variations or feature alternatives, optimizing conversion rates or user engagement, or validating design hypotheses and iterating designs based on statistically significant results from user testing.
Heuristic EvaluationHeuristic Evaluation is a method where usability experts evaluate a user interface against a set of recognized usability principles or heuristics. It helps identify usability issues and design flaws early in the design process, improving overall usability and user satisfaction.When conducting quick evaluations of user interfaces, identifying usability issues and design violations, or providing feedback to inform design improvements and iterative refinements based on established usability principles.

Connected Agile 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.

AgileSHIFT

AgileSHIFT
AgileSHIFT is a framework that prepares individuals for transformational change by creating a culture of agility.

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 Program Management

agile-program-management
Agile Program Management is a means of managing, planning, and coordinating interrelated work in such a way that value delivery is emphasized for all key stakeholders. Agile Program Management (AgilePgM) is a disciplined yet flexible agile approach to managing transformational change within an organization.

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.

Agile Leadership

agile-leadership
Agile leadership is the embodiment of agile manifesto principles by a manager or management team. Agile leadership impacts two important levels of a business. The structural level defines the roles, responsibilities, and key performance indicators. The behavioral level describes the actions leaders exhibit to others based on agile principles. 

Bimodal Portfolio Management

bimodal-portfolio-management
Bimodal Portfolio Management (BimodalPfM) helps an organization manage both agile and traditional portfolios concurrently. Bimodal Portfolio Management – sometimes referred to as bimodal development – was coined by research and advisory company Gartner. The firm argued that many agile organizations still needed to run some aspects of their operations using traditional delivery models.

Business Innovation Matrix

business-innovation
Business innovation is about creating new opportunities for an organization to reinvent its core offerings, revenue streams, and enhance the value proposition for existing or new customers, thus renewing its whole business model. Business innovation springs by understanding the structure of the market, thus adapting or anticipating those changes.

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.

Constructive Disruption

constructive-disruption
A consumer brand company like Procter & Gamble (P&G) defines “Constructive Disruption” as: a willingness to change, adapt, and create new trends and technologies that will shape our industry for the future. According to P&G, it moves around four pillars: lean innovation, brand building, supply chain, and digitalization & data analytics.

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.

ICE Scoring

ice-scoring-model
The ICE Scoring Model is an agile methodology that prioritizes features using data according to three components: impact, confidence, and ease of implementation. The ICE Scoring Model was initially created by author and growth expert Sean Ellis to help companies expand. Today, the model is broadly used to prioritize projects, features, initiatives, and rollouts. It is ideally suited for early-stage product development where there is a continuous flow of ideas and momentum must be maintained.

Innovation Funnel

innovation-funnel
An innovation funnel is a tool or process ensuring only the best ideas are executed. In a metaphorical sense, the funnel screens innovative ideas for viability so that only the best products, processes, or business models are launched to the market. An innovation funnel provides a framework for the screening and testing of innovative ideas for viability.

Innovation Matrix

types-of-innovation
According to how well defined is the problem and how well defined the domain, we have four main types of innovations: basic research (problem and domain or not well defined); breakthrough innovation (domain is not well defined, the problem is well defined); sustaining innovation (both problem and domain are well defined); and disruptive innovation (domain is well defined, the problem is not well defined).

Innovation Theory

innovation-theory
The innovation loop is a methodology/framework derived from the Bell Labs, which produced innovation at scale throughout the 20th century. They learned how to leverage a hybrid innovation management model based on science, invention, engineering, and manufacturing at scale. By leveraging individual genius, creativity, and small/large groups.

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.

Scrumban

scrumban
Scrumban is a project management framework that is a hybrid of two popular agile methodologies: Scrum and Kanban. Scrumban is a popular approach to helping businesses focus on the right strategic tasks while simultaneously strengthening their processes.

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.

Stretch Objectives

stretch-objectives
Stretch objectives describe any task an agile team plans to complete without expressly committing to do so. Teams incorporate stretch objectives during a Sprint or Program Increment (PI) as part of Scaled Agile. They are used when the agile team is unsure of its capacity to attain an objective. Therefore, stretch objectives are instead outcomes that, while extremely desirable, are not the difference between the success or failure of each sprint.

Waterfall

waterfall-model
The waterfall model was first described by Herbert D. Benington in 1956 during a presentation about the software used in radar imaging during the Cold War. Since there were no knowledge-based, creative software development strategies at the time, the waterfall method became standard practice. The waterfall model is a linear and sequential project management framework. 

Read Also: Continuous InnovationAgile MethodologyLean StartupBusiness Model InnovationProject Management.

Read Next: Agile Methodology, Lean Methodology, Agile Project Management, Scrum, Kanban, Six Sigma.

Main Guides:

Main Case Studies:

Scroll to Top

Discover more from FourWeekMBA

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

Continue reading

FourWeekMBA