Software Projects Caveat: Scope / Requirements
Published on: May 01, 2023
Last updated: May 07, 2024 Read in fullscreen view
Last updated: May 07, 2024 Read in fullscreen view
Recommended for you
- 18 Oct 2020
How to use the "Knowns" and "Unknowns" technique to manage assumptions 22/995 - 01 Oct 2020 Fail fast, learn faster with Agile methodology 15/977
- 12 Oct 2022 14 Common Reasons Software Projects Fail (And How To Avoid Them) 11/506
- 19 Oct 2021 Is gold plating good or bad in project management? 8/756
- 10 Nov 2022 Poor Code Indicators and How to Improve Your Code? 8/214
- 06 Feb 2021 Why fail fast and learn fast? 7/378
- 13 Oct 2021 Outsourcing Software Development: MVP, Proof of Concept (POC) and Prototyping. Which is better? 7/427
- 01 Sep 2022 Facts Chart: Why Do Software Projects Fail? 7/544
- 07 Oct 2025 Case Study: Using the “Messaging House” Framework to Build a Digital Transformation Roadmap 7/55
- 01 Mar 2023 Bug Prioritization - What are the 5 levels of priority? 6/207
- 06 Mar 2021 4 things you need to do before getting an accurate quote for your software development 6/617
- 08 Nov 2022 4 tips for meeting tough deadlines when outsourcing projects to software vendor 6/254
- 28 Jul 2022 POC, Prototypes, Pilots and MVP: What Are the Differences? 6/613
- 04 Oct 2022 Which ERP implementation strategy is right for your business? 5/279
- 12 Dec 2021 Zero Sum Games Agile vs. Waterfall Project Management Methods 5/377
- 16 Apr 2021 Insightful Business Technology Consulting at TIGO 5/379
- 05 Mar 2021 How do you minimize risks when you outsource software development? 5/318
- 14 Oct 2021 Advantages and Disadvantages of Time and Material Contract (T&M) 5/795
- 31 Aug 2022 What are the best practices for software contract negotiations? 5/215
- 18 Aug 2022 What are the consequences of poor requirements with software development projects? 5/244
- 18 Jul 2021 How To Ramp Up An Offshore Software Development Team Quickly 4/520
- 08 Oct 2022 KPI - The New Leadership 4/558
- 31 Oct 2021 Tips to Fail Fast With Outsourcing 4/377
- 17 Jun 2021 What is IT-business alignment? 3/346
- 23 Sep 2021 INFOGRAPHIC: Top 9 Software Outsourcing Mistakes 3/413
- 28 Dec 2021 8 types of pricing models in software development outsourcing 3/419
- 28 Oct 2022 Build Operate Transfer (B.O.T) Model in Software Outsourcing 3/365
- 04 Oct 2021 Product Validation: The Key to Developing the Best Product Possible 3/296
- 10 Apr 2021 RFP vs POC: Why the proof of concept is replacing the request for proposal 3/257
- 09 Mar 2022 Consultant Implementation Pricing 3/185
- 16 Feb 2021 Choose Outsourcing for Your Non Disclosure Agreement (NDA) 3/150
- 13 Dec 2020 Move fast, fail fast, fail-safe 3/294
- 17 Feb 2022 Prioritizing Software Requirements with Kano Analysis 3/285
- 07 Jul 2021 The 5 Levels of IT Help Desk Support 3/381
- 10 Dec 2023 Pain points of User Acceptance Testing (UAT) 3/419
- 01 Dec 2023 Laws of Project Management 3/250
- 14 Feb 2024 Systems Engineering Tools in Requirements Development 3/265
- 05 Sep 2023 The Cold Start Problem: How to Start and Scale Network Effects 3/167
- 03 Jul 2022 What is the difference between Project Proposal and Software Requirements Specification (SRS) in software engineering? 2/959
- 01 May 2024 Warren Buffett’s Golden Rule for Digital Transformation: Avoiding Tech Overload 2/188
- 07 Aug 2022 Things to Consider When Choosing a Technology Partner 2/255
- 07 Oct 2022 Digital Transformation: Become a Technology Powerhouse 2/220
- 19 Apr 2021 7 Most Common Time-Wasters For Software Development 2/527
- 30 Oct 2022 How Much Does MVP Development Cost in 2023? 1/173
- 09 Feb 2023 The Challenge of Fixed-Bid Software Projects 1/191
- 12 Aug 2024 Understanding Google Analytics in Mumbai: A Beginner's Guide 1/85
- 10 Jul 2025 Building AI-Driven Knowledge Graphs from Unstructured Data 1/117
- 01 Oct 2024 23 Overlooked Types of Non-Functional Requirements You Shouldn’t Ignore 1/19
- 01 May 2023 CTO Interview Questions 1/299
- 26 Dec 2023 Improving Meeting Effectiveness Through the Six Thinking Hats 1/205
- 05 Jan 2024 Easy ASANA tips & tricks for you and your team 1/181
- 11 Jan 2024 What are the Benefits and Limitations of Augmented Intelligence? 1/436
- 12 Mar 2024 How do you create FOMO in software prospects? /131
- 06 Mar 2024 [SemRush] What Are LSI Keywords & Why They Don‘t Matter /131
- 14 Mar 2024 Why should you opt for software localization from a professional agency? /117
- 01 Mar 2023 How do you deal with disputes and conflicts that may arise during a software consulting project? /145
- 17 Mar 2025 IT Consultants in Digital Transformation /62
- 20 Nov 2022 Software Requirements Are A Communication Problem /234
- 09 Jan 2022 How to Bridge the Gap Between Business and IT? /165
- 19 Oct 2021 Software development life cycles /628
- 06 Nov 2019 How to Access Software Project Size? /236
- 03 Nov 2022 Top questions and answers you must know before ask for software outsourcing /265
The IT industry is not that young anymore. However, there are still many never-ending projects; in addition, some projects end with low satisfaction on one or both sides – the customer and the developer side.
The most common problem is the scope of a project. Developers regularly complain to customers who repeatedly increase and enlarge their requirements during the project repeatedly. I agree this is a huge problem, and the scope of a project has to be defined and followed. However, I want to say couple of words from a point of view that is not often taken.
The most common problem is the scope of a project. Developers regularly complain to customers who repeatedly increase and enlarge their requirements during the project repeatedly. I agree this is a huge problem, and the scope of a project has to be defined and followed. However, I want to say couple of words from a point of view that is not often taken.
There are so many times when customers are not satisfied with an IT project because they can add requirements after the initial phase of functional analysis. They do not understand why it is so hard to add or change a functionality of an application, even if they explain the new functionality is crucial for them. So – why do developers assume their customers know their requirements in advance? Do the developers always know all of their needs and wishes in advance when they go shopping something? Of course they (we) do not. This is human – many times, you realize what you would want when you see what is possible. Take an example with mobile phones, there was a general idea somewhere in the ether how nice it would be to have a phone available anywhere. Then somebody invented mobile phone. After that, people got additional ideas with a built-in camera.
If you are a developer, you should take your customer’s point of view. You should anticipate at least three iterations of gathering the requirements. Of course, you have to limit the number of iterations. Consider preparing a proof-of-concept (POC) or proof-of-value (POV) for project or application. Show your users what can be done before you seal the scope. If you are a customer, remember that even developers do not know everything in advance. In addition, you should still be aware that the scope has to be determined in a moderate period if you want to finish your project some day.
[{"displaySettingInfo":"[{\"isFullLayout\":false,\"layoutWidthRatio\":\"\",\"showBlogMetadata\":true,\"includeSuggestedAndRelatedBlogs\":true,\"enableLazyLoad\":true,\"quoteStyle\":\"1\",\"bigHeadingFontStyle\":\"1\",\"postPictureFrameStyle\":\"1\",\"isFaqLayout\":false,\"isIncludedCaption\":false,\"faqLayoutTheme\":\"1\",\"isSliderLayout\":false}]"},{"articleSourceInfo":"[{\"sourceName\":\"\",\"sourceValue\":\"\"}]"},{"privacyInfo":"[{\"isOutsideVietnam\":false}]"},{"tocInfo":"[{\"isEnabledTOC\":true,\"isAutoNumbering\":false,\"isShowKeyHeadingWithIcon\":false}]"}]
Via
{content}
Explore more on these topics
Guest Blogging: The Definitive Guide
Top Trending Topics
Share This
Link copied!