We live in a extremely dynamic world where the only constant is Change . Change is inevitable and it has to be managed. One of the key factors of success in any project is the way in which we manage change. There is ever changing market forces that influence the project and as a product owner and development team, one is constantly trying their best to match these forces by factoring such change.

First of all one needs to validate whether such a change is essential . Then one needs to analyse the possible ramifications of such a change on Cost, Schedule and requirements and then classify it as minor or major (based on the impact). These three constitute the triple constraints of a project. One of the foremost factors that will be considered while accepting change will be the impact analysis of such change on an ongoing project. This exercise determines the cost overrun (increase resources) due to such change on the WBS (Work breakdown structures) within the project.Concurrently we also need to assess if such change impact the overall project strategy as well as the scope of the project. This is followed by effective coordination with product owner and team to align stakeholder expectation to the project. Care need be taken that excessive change does not lead to project failure.

We at Railsfactory imbibe the Best of PM practices in the IT Industry that combines both conventional Project Management Techniques as well as Agile practices to ensure that the product owner has the flexibility to introduce any change on the feature that are to be developed in future sprints. In this practice change is proactive and therefore it strives best to meet stakeholder expectation. One thing that is a definite no is to introduce a change creep in the features of an existing Sprint. The brighter side of all this is that effective Change management leads to increase in stakeholder satisfaction thereby project success in evincing greater value for the Product owner.