Skip to content
View in the app

A better way to browse. Learn more.

Benchmark Six Sigma Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Topics

Leaderboard

Popular Content

Showing content with the highest reputation on 11/15/2024 in Posts

  1. In real life scenarios we witness many such failures in a Tech Product or Tech Tool where root cause can be linked to a flaw in the Business Requirement Document (BRD). BRD is a document that articulates product or tool requirement to solve business problem or improve business performance and this document is taken as a guidebook by supplier to develop Tech product or Tech tool. BRD generally consists of the feature, functionality, performance expectation of the product and also the constraints of the project. Thus, it's clear that any ambiguity or inaccuracy may result in potential failure in product or tool. There can be multiple reasons for this: 1. Lack of Articulation: Articulating the exact requirement in BRD is a tough task. Generally, the user has dream Tech product conceptualization in mind but articulating that in exactly the same way can play significant role in success or failure of Tech product or Tech tool. Example: Apple's BRD on Maps could not convey the requirement of precise location with accuracy that resulted in significant map errors, improper navigations and low quality satellite images. 2. Lack of Prioritization: In many cases people want it all in BRD and give all the possible features in Tech product or Tech tool which may result in lack of prioritization to unique and most valuable features. Example: Windows Vista is a perfect example for this where BRD listed so many features without clear prioritization on performance focus. Ultimately, it failed due to frequent crashes and compatibility problems and had to be replaced with Windows 7. 3. Misinterpretation of Business Needs: In many BRDs specificity is missing which may create misinterpretation. Example: If requirement is on support with multiple payment options for e-business application, then developer might miss one of the important integrations (exp-Bit Coin payment option) which may result in loss of potential sales. 4. Poor Definition of Success Criteria: This, I believe is the most important reason as Success Criteria for the Tech product or Tool must be defined with respect to performance, quality, durability and cost effectiveness. Example: JioChat where despite so many Jio Users the app could not succussed as it was lacking success criteria like target for user adoption, engagement and market spread. Thus, it is important to articulate 360deg angle on Business Requirement in BRD so there is zero misalignment.
This leaderboard is set to Kolkata/GMT+05:30

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.