What is the Fagan Inspection Method? Can this old method still save your project?”
Last updated: September 29, 2025 Read in fullscreen view
- 01 Dec 2022
Difference between Set-based development and Point-based development 124/481 - 14 Aug 2024
From Steel to Software: The Reluctant Evolution of Japan's Tech Corporates 124/664 - 19 Oct 2021
Software development life cycles 119/797 - 21 May 2022
"Fail Fast, Fail Often, Fail Forward" is the answer to Agile practices of software success 114/1161 - 18 Oct 2020
How to use the "Knowns" and "Unknowns" technique to manage assumptions 113/1205 - 13 Oct 2021
Outsourcing Software Development: MVP, Proof of Concept (POC) and Prototyping. Which is better? 112/586 - 10 Apr 2022
Agile self-organizing teams: What are they? How do they work? 111/654 - 06 Nov 2023
How do you streamline requirement analysis and modeling? 109/345 - 04 Oct 2021
Product Validation: The Key to Developing the Best Product Possible 109/417 - 03 Jul 2022
Manifesto for Agile Software Development 107/374 - 13 Dec 2020
Move fast, fail fast, fail-safe 106/433 - 27 Oct 2020
8 principles of Agile Testing 102/1412 - 28 Oct 2023
The GOLDEN Rules of Software Engineering 100/672 - 06 Feb 2021
Why fail fast and learn fast? 99/566 - 11 Jan 2024
What are the Benefits and Limitations of Augmented Intelligence? 98/579 - 13 Oct 2021
What is Bug Convergence? Why is it important for User Acceptance Testing (UAT)? 97/859 - 08 Dec 2021
What Are The 4 Types of Maintenance Strategies? 96/1271 - 21 Apr 2026
Vibe Coding vs. Expert Shopify Development: What AI Tools Can (and Can't) Do? 96/115 - 16 Jul 2022
What are disadvantages of Agile Methodology? How to mitigate the disadvantages ? 95/488 - 12 Aug 2024
Understanding Google Analytics in Mumbai: A Beginner's Guide 94/191 - 01 Oct 2020
Fail fast, learn faster with Agile methodology 93/1162 - 12 Oct 2022
14 Common Reasons Software Projects Fail (And How To Avoid Them) 93/656 - 13 May 2022
IT Training and Development: The most effective options for upskilling IT staff 93/1321 - 20 Jan 2021
Fail early, fail often, fail cheap, fail safe but always fail forward 91/883 - 10 Dec 2021
What is a Kano Analysis? 91/1001 - 11 Nov 2021
What is an IT Self-service Portal? Why is it Important to Your Business? 91/534 - 18 Aug 2022
What are the consequences of poor requirements with software development projects? 89/347 - 14 Mar 2024
Why should you opt for software localization from a professional agency? 87/226 - 07 Oct 2025
Case Study: Using the “Messaging House” Framework to Build a Digital Transformation Roadmap 87/166 - 28 Nov 2023
Scrum Team Failure — Scrum Anti-Patterns Taxonomy 86/337 - 02 Jan 2024
What is User Provisioning & Deprovisioning? 84/663 - 31 Aug 2022
What are the best practices for software contract negotiations? 84/351 - 02 Dec 2022
3 Levels of Quality in KANO Analysis Model 82/1247 - 23 Sep 2021
INFOGRAPHIC: Top 9 Software Outsourcing Mistakes 82/505 - 05 Mar 2021
How do you minimize risks when you outsource software development? 81/413 - 02 Nov 2021
[Case Study] Streamlined Data Reporting using Tableau 81/383 - 11 Oct 2021
10 Myths About Low-End Project Management Software 78/412 - 05 May 2021
TIGO Magic Scale - PoC tool for you to apply dichotomous thinking before submitting RFP 76/405 - 05 Jun 2023
Bespoke Solution: Annual Maintenance Contract (AMC) Software 75/264 - 07 Dec 2023
The Myths Of Requirements 74/329 - 01 Jun 2022
How Your Agile Development Team is Just Like a Football Team? 73/291 - 06 Mar 2024
[SemRush] What Are LSI Keywords & Why They Don‘t Matter 73/268 - 05 Sep 2023
The Cold Start Problem: How to Start and Scale Network Effects 73/264 - 20 Nov 2022
Agile working method in software and football 72/411 - 08 Oct 2022
KPI - The New Leadership 71/677 - 28 Dec 2021
8 types of pricing models in software development outsourcing 71/505 - 14 Oct 2021
Advantages and Disadvantages of Time and Material Contract (T&M) 67/949 - 07 Oct 2020
How To Manage Expectations at Work (and Why It's Important) 67/399 - 14 Oct 2021
Stream Story - Low land stream or fast moving stream? 66/689 - 28 Jul 2022
POC, Prototypes, Pilots and MVP: What Are the Differences? 66/797 - 02 Dec 2022
Success Story: Satsuki - Sales Management Software, back office app for School Subscription Management 63/300 - 13 Feb 2021
Why is TIGOSOFT a software house for Enterprise Application Development? 63/443 - 10 Nov 2021
Automated QA Outsourcing – Hire a Professional Software Testing Team 63/646 - 05 Aug 2024
Revisiting the Mistake That Halted Japan's Software Surge 63/409 - 20 Jan 2022
TIGO Self-Organization Practice: Change Management Workflow 62/529 - 10 Dec 2023
Pain points of User Acceptance Testing (UAT) 62/516 - 12 Dec 2021
Zero Sum Games Agile vs. Waterfall Project Management Methods 61/471 - 03 Sep 2022
The secret of software success: Simplicity is the ultimate sophistication 59/263 - 09 Oct 2022
Key Advantages and Disadvantages of Agile Methodology 58/762 - 01 Jan 2024
The pros and cons of the Centralized Enterprise Automation Operating model 58/277 - 01 Dec 2023
Laws of Project Management 57/371 - 19 Apr 2021
7 Most Common Time-Wasters For Software Development 57/602 - 12 Oct 2020
The Agile Manifesto - Principle #8 57/551 - 01 May 2024
Warren Buffett’s Golden Rule for Digital Transformation: Avoiding Tech Overload 57/264 - 18 Jul 2021
How To Ramp Up An Offshore Software Development Team Quickly 56/645 - 04 Oct 2022
Which ERP implementation strategy is right for your business? 56/409 - 19 Oct 2021
Is gold plating good or bad in project management? 54/885 - 10 Nov 2022
Poor Code Indicators and How to Improve Your Code? 53/270 - 03 Apr 2021
How digital asset management streamlines your content workflow? 53/381 - 05 Jan 2024
Easy ASANA tips & tricks for you and your team 51/248 - 12 Mar 2024
How do you create FOMO in software prospects? 50/218 - 31 Oct 2021
Tips to Fail Fast With Outsourcing 50/438 - 28 Oct 2022
Build Operate Transfer (B.O.T) Model in Software Outsourcing 49/452 - 01 Mar 2023
Bug Prioritization - What are the 5 levels of priority? 49/275 - 01 Oct 2020
Handling tight project deadlines as a business analyst 47/374 - 21 Jun 2021
6 Useful Tips To Streamline Business Processes and Workflows 46/575 - 16 Jun 2022
Rapid Application Development (RAD): Pros and Cons 45/920 - 17 Feb 2022
Prioritizing Software Requirements with Kano Analysis 42/346 - 02 Apr 2022
Productivity vs. Efficiency – What Are the Differences? 41/250 - 01 Mar 2022
Why Does Scrum Fail in Large Companies? 41/304 - 26 Dec 2023
Improving Meeting Effectiveness Through the Six Thinking Hats 41/312 - 21 Oct 2022
Virtual meeting - How does TIGO save cost, reduce complexity and improve quality by remote communication? 39/223 - 03 Nov 2022
Questions and answers about Kano Model 39/929 - 05 Feb 2024
Bespoke Solution: Visitor Management System for Corporate 38/296 - 10 Oct 2022
Should Your Business Go Agile? (Infographic) 37/161 - 02 Nov 2022
Frequently Asked Questions about Agile and Scrum 35/432 - 06 Nov 2019
How to Access Software Project Size? 33/290
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