Scope Creep - Business Vs. IT Team

Applications Delivery Requirements Management Scope Management

Prolay Chaudhury Practice Lead & Lead Solution Architect| Chaudhury, Inc. Bangalore, Karnataka, India

Dear Flocks,

Scope Creep - The one line definition - what business has asked to develop is not matching with the product delivery by the IT implementation team. Moreover, It implementation team deliver the right scope, but business has changed their minds after going through the developed application (Further enhancement, significant change management and so on and so forth).

The difference between the Business and It implementations Team is a boiling topic, and both the parties have their viewpoints and expectation over each other. What are the secret sauces for the Architects and the Project Managers to handle the diverse business stakeholders who are sponsoring the project and implement it successfully with the Agile methodologies and also maintaining the coordination with different dependent departments?

Looking for the expert suggestions and comments.

Posted: Dec 27, 2016 12:22 PM

Sort By:

< 1 2 >

Anupam India

Dec 28, 2016 8:56 AM

Replying to Prolay Chaudhury

...

Anupam, I do not believe there are any best practices in especially in Indian context. When the unexpected expectations from Strategic and Higher management are getting mobilized and thrown to the IT implementation and operation team, all the academic, and prior experiences (Here I meant Agile, Scrum, Product Owner and so and so forth) started vanishing. There is one and only pressure to the project team to complete the project with the impossible deadline.

And for a large project as an Architect we need to consider the E2E design of the whole process automation :) Which itself is very challenging due to the diversity, timezone and the project priorities and pipelines.

So, It is going to be the injustice if we think it only from the Agile perspective. I am talking about the whole organizational goal.

Secondly - By the word diverse Team I meant the Multi-Vendor project team. The project team members are coming from the different vendors.

Sorry to say but that's not really true :)
There are best practices and especially in Indian context.

Posted: Dec 28, 2016 9:14 AM

Wade Harshman Scrum Master| GDIT Indianapolis, In, United States

Prolay, you're on the right path when you mention Agile. Agile is not a solution for all problems, but it does recognize that scope is not fixed, especially in the realm of IT. Various Agile frameworks (I avoid the term "methodologies") trade this flexibility in scope with a disciplined focus on time- for example, the fixed sprints used in Scrum.

However, you can't implement this on your own. Your organization will have to adopt an Agile culture and support it from the top down. If that happens, you will not have true "project managers," but there are specific roles to support the development team or to work with the business. The Scrum Product Owner, for example, is the person who works with the stakeholders- the business and the customers- to determine scope, and this is the person who prioritizes the work that needs to be done. These priorities are subject to change if the scope changes.

Posted: Dec 28, 2016 9:48 AM

Sergio Luis Conte Helping to create solutions for everyone| Worldwide based Organizations Buenos Aires, Argentina

Dec 28, 2016 8:57 AM

Replying to Prolay Chaudhury

...

Agreed, @Sergio, but it depends on the context as per as my experience and understanding.

You have two posibilities: adapt to context or change the context. If you adapt to context then you have to accept scope creep and you do not have to have concerns about it.

Posted: Dec 28, 2016 12:03 PM

< 1 2 >

Please login or join to reply

Scope Creep - Business Vs. IT Team

Sponsors

Vendor Events

Guessing is not a strategy: How to build decision velocity with AI and real-time data

Newsletters