What is the Fagan Inspection Method? Can this old method still save your project?”
Last updated: September 29, 2025 Read in fullscreen view
- 10 Apr 2022
Agile self-organizing teams: What are they? How do they work? 28/435 - 28 Oct 2023
The GOLDEN Rules of Software Engineering 27/522 - 18 Oct 2020
How to use the "Knowns" and "Unknowns" technique to manage assumptions 21/989 - 08 Dec 2021
What Are The 4 Types of Maintenance Strategies? 20/1031 - 21 May 2022
"Fail Fast, Fail Often, Fail Forward" is the answer to Agile practices of software success 18/941 - 01 Oct 2020
Fail fast, learn faster with Agile methodology 13/973 - 12 Oct 2022
14 Common Reasons Software Projects Fail (And How To Avoid Them) 10/504 - 05 Feb 2024
Bespoke Solution: Visitor Management System for Corporate 10/221 - 02 Dec 2022
3 Levels of Quality in KANO Analysis Model 8/1000 - 13 Oct 2021
What is Bug Convergence? Why is it important for User Acceptance Testing (UAT)? 8/684 - 13 May 2022
IT Training and Development: The most effective options for upskilling IT staff 7/1021 - 19 Oct 2021
Is gold plating good or bad in project management? 7/754 - 10 Nov 2022
Poor Code Indicators and How to Improve Your Code? 7/213 - 28 Jul 2022
POC, Prototypes, Pilots and MVP: What Are the Differences? 6/606 - 01 Mar 2023
Bug Prioritization - What are the 5 levels of priority? 6/207 - 14 Oct 2021
Stream Story - Low land stream or fast moving stream? 6/569 - 13 Oct 2021
Outsourcing Software Development: MVP, Proof of Concept (POC) and Prototyping. Which is better? 6/424 - 20 Jan 2022
TIGO Self-Organization Practice: Change Management Workflow 6/430 - 06 Feb 2021
Why fail fast and learn fast? 6/375 - 10 Dec 2021
What is a Kano Analysis? 6/810 - 05 Aug 2024
Revisiting the Mistake That Halted Japan's Software Surge 6/322 - 14 Aug 2024
From Steel to Software: The Reluctant Evolution of Japan's Tech Corporates 6/488 - 07 Oct 2025
Case Study: Using the “Messaging House” Framework to Build a Digital Transformation Roadmap 5/45 - 05 Mar 2021
How do you minimize risks when you outsource software development? 5/317 - 20 Nov 2022
Agile working method in software and football 5/323 - 31 Aug 2022
What are the best practices for software contract negotiations? 5/215 - 16 Jun 2022
Rapid Application Development (RAD): Pros and Cons 5/800 - 05 May 2021
TIGO Magic Scale - PoC tool for you to apply dichotomous thinking before submitting RFP 4/297 - 12 Dec 2021
Zero Sum Games Agile vs. Waterfall Project Management Methods 4/374 - 01 Jan 2024
The pros and cons of the Centralized Enterprise Automation Operating model 4/165 - 04 Oct 2022
Which ERP implementation strategy is right for your business? 4/278 - 14 Oct 2021
Advantages and Disadvantages of Time and Material Contract (T&M) 4/789 - 18 Jul 2021
How To Ramp Up An Offshore Software Development Team Quickly 3/516 - 08 Oct 2022
KPI - The New Leadership 3/557 - 03 Nov 2022
Questions and answers about Kano Model 3/805 - 31 Oct 2021
Tips to Fail Fast With Outsourcing 3/375 - 20 Jan 2021
Fail early, fail often, fail cheap, fail safe but always fail forward 3/688 - 01 Dec 2023
Laws of Project Management 3/249 - 18 Aug 2022
What are the consequences of poor requirements with software development projects? 3/242 - 05 Sep 2023
The Cold Start Problem: How to Start and Scale Network Effects 3/167 - 02 Dec 2022
Success Story: Satsuki - Sales Management Software, back office app for School Subscription Management 2/219 - 01 May 2024
Warren Buffett’s Golden Rule for Digital Transformation: Avoiding Tech Overload 2/188 - 02 Nov 2021
[Case Study] Streamlined Data Reporting using Tableau 2/276 - 07 Dec 2023
The Myths Of Requirements 2/203 - 10 Dec 2023
Pain points of User Acceptance Testing (UAT) 2/416 - 03 Jul 2022
Manifesto for Agile Software Development 2/240 - 13 Dec 2020
Move fast, fail fast, fail-safe 2/292 - 28 Dec 2021
8 types of pricing models in software development outsourcing 2/417 - 28 Oct 2022
Build Operate Transfer (B.O.T) Model in Software Outsourcing 2/361 - 23 Sep 2021
INFOGRAPHIC: Top 9 Software Outsourcing Mistakes 2/411 - 17 Feb 2022
Prioritizing Software Requirements with Kano Analysis 2/280 - 11 Nov 2021
What is an IT Self-service Portal? Why is it Important to Your Business? 2/364 - 04 Oct 2021
Product Validation: The Key to Developing the Best Product Possible 2/295 - 12 Oct 2020
The Agile Manifesto - Principle #8 2/447 - 07 Oct 2020
How To Manage Expectations at Work (and Why It's Important) 2/266 - 13 Feb 2021
Why is TIGOSOFT a software house for Enterprise Application Development? 1/336 - 01 Oct 2020
Handling tight project deadlines as a business analyst 1/313 - 19 Apr 2021
7 Most Common Time-Wasters For Software Development 1/525 - 12 Aug 2024
Understanding Google Analytics in Mumbai: A Beginner's Guide 1/84 - 05 Jan 2024
Easy ASANA tips & tricks for you and your team 1/180 - 11 Jan 2024
What are the Benefits and Limitations of Augmented Intelligence? 1/434 - 02 Jan 2024
What is User Provisioning & Deprovisioning? 1/480 - 26 Dec 2023
Improving Meeting Effectiveness Through the Six Thinking Hats 1/205 - 03 Apr 2021
How digital asset management streamlines your content workflow? 1/312 - 01 Jun 2022
How Your Agile Development Team is Just Like a Football Team? /206 - 02 Apr 2022
Productivity vs. Efficiency – What Are the Differences? /196 - 02 Nov 2022
Frequently Asked Questions about Agile and Scrum /372 - 03 Sep 2022
The secret of software success: Simplicity is the ultimate sophistication /186 - 16 Jul 2022
What are disadvantages of Agile Methodology? How to mitigate the disadvantages ? /353 - 01 Dec 2022
Difference between Set-based development and Point-based development /298 - 28 Nov 2023
Scrum Team Failure — Scrum Anti-Patterns Taxonomy (3) /228 - 01 Mar 2022
Why Does Scrum Fail in Large Companies? /243 - 06 Nov 2023
How do you streamline requirement analysis and modeling? /184 - 14 Mar 2024
Why should you opt for software localization from a professional agency? /117 - 12 Mar 2024
How do you create FOMO in software prospects? /127 - 05 Jun 2023
Bespoke Solution: Annual Maintenance Contract (AMC) Software /179 - 11 Oct 2021
10 Myths About Low-End Project Management Software /274 - 21 Jun 2021
6 Useful Tips To Streamline Business Processes and Workflows /515 - 27 Oct 2020
8 principles of Agile Testing /1196 - 19 Oct 2021
Software development life cycles /628 - 09 Oct 2022
Key Advantages and Disadvantages of Agile Methodology /666 - 10 Oct 2022
Should Your Business Go Agile? (Infographic) /108 - 10 Nov 2021
Automated QA Outsourcing – Hire a Professional Software Testing Team /514 - 21 Oct 2022
Virtual meeting - How does TIGO save cost, reduce complexity and improve quality by remote communication? /166 - 06 Nov 2019
How to Access Software Project Size? /236 - 06 Mar 2024
[SemRush] What Are LSI Keywords & Why They Don‘t Matter /131
There are several methods to find errors during software development, such as reviews, walkthroughs, and inspections. Among them, Inspection, also known as the Fagan Inspection, is considered the most effective. It was developed by Michael Fagan at IBM in the 1970s.
What is the Fagan Inspection Method?
The Fagan Inspection method is a process designed to identify defects at any stage of a project—whether in documents, source code, or implementation processes.
In software projects, documents are just as important as code. Technical specifications (Functional Specifications), user requirements (User Requirement Specifications), and business requirements (Business Requirement Specifications) are all essential inputs for the software system. If the inputs are poor, the outputs cannot be perfect. This means the documents themselves may contain many errors.
Living documents, such as schedules, milestone-based WBS, or sprint plans, are continuously updated during the project lifecycle. Early inspection for these is less critical. But frozen documents, like BRS, URS, or Functional Specifications, cannot easily be changed because they are tied to contracts or formal agreements. For these, early inspection is highly recommended.
Stages of the Fagan Inspection Process
- Planning: Managed by the project management team.
- Overview Meeting: Introduce the work product and its context.
- Preparation: Inspectors review the work product to identify potential defects.
- Inspection Meeting: The author presents the work piece by piece, and inspectors point out defects in each section.
- Rework: Make changes according to the actions identified in the inspection meeting.
- Follow-up: Verify that all changes have been correctly applied.
The Preparation, Inspection Meeting, and Rework stages can be repeated multiple times if needed.
How to Conduct Fagan Inspections
- Ensure results are balanced, considering both the effort of the creator and the benefits of inspection.
- Inspectors should not only find defects but also remain impartial, recognizing good work and quantifying outstanding results.
- Make the benefits of the inspection clear and tangible.
- Use inspection results to inform future project planning as part of overall project management.
Why Are Inspections Rarely Used?
Fagan Inspection is highly useful for quality assurance, though not many people know its name. Different inspection approaches follow similar logic. When applied correctly and at the right time, it can be very effective. Overuse, however, can create unforeseen problems. Some reasons to consider before using this method include:
- There is no absolute measure of success.
- Benefits are not immediately obvious and require careful analysis to ensure time and cost savings.
- Deep technical insights may be overlooked, limiting the opportunity to answer "Why".
- It may create a divide between implementers and inspectors.
- It can foster a critical work environment, which may conflict with a culture where staff feel comfortable admitting mistakes or sharing information.
Source: TIGO Solutions










Link copied!
Recently Updated News