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.

Sumant Sood

Lean Six Sigma Black Belt
  • Joined

  • Last visited

Everything posted by Sumant Sood

  1. Scope creep refers to continuous small, incremental changes that can lead to uncontrolled and unauthorized growth in the original project scope. It starts with a small change and as the changes increase the project scope keeps on becoming complex and unmanageable. Scope creep is usually not advisable in a project but its not always possible to avoid as there are multiple stakeholders involved and as the project progresses, concerned people get more insights and to improve the experience for end customer keeps changing the scope. Scope creep usually uses additional resources and leads to reduced profits and delays project timelines which leads to frustration and anxiety in the team. Scope creep is not always detrimental but is sometimes helpful as it helps to build a better relationship with client, increases revenue if client is willing to pay for it & pushes the project team to look for opportunities and this can lead to a better project management in next projects. Scope creep generally is due to following reasons: 1) New addition in client team 2) Asking additional features in the name of delighting end user 3) Scope not defined clearly at the beginning. Scope defines what will be done and importantly also mentions what will be the boundaries. For this the operational definition should be clear and understood by all the parties involved. We have seen that scope creep cannot be avoided altogether but it can be managed better so as to ensure that project deliverables are met without strain and stress 1) Define scope clearly: Involve the sponsor and get a clear understanding and have the communication channels defined. It’s a good idea to break the entire scope into manageable deliverables through Work Breakdown Structure. 2) Define the change process: Make a process on how the changes will be entertained and included in the scope. This way all the request changes will have a record and can be managed better. Revised scope can be discussed and agreed before going ahead with the change. 3) Stakeholder Involvement: Generally involvement of the stakeholders/ sponsor or client is there in the beginning but it thins down as the project progresses. Asking for key decisions is ok but bombarding with everyday work and queries will lead to their less involvement and commitment. 4) Communication with focus on stakeholders: Regularly communicating to the stakeholders is very important. This keeps them involved and committed towards project success. 5) Break Complex Projects: Simplify the complex project into manageable smaller projects. Different key people can manage each sub project, smaller projects are easy to focus and handle. This keeps the enthusiasm and timelines can be managed. 6) Monitor and Review closely: Close monitoring on the use of resources and timelines helps to keep a track and avoids things spiraling out of hands.

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.