Agile Principle on Change has been misunderstood for too long.Many orgs and teams view it as an excuse to make rash changes.But this couldn’t be further from the truth. In reality, effective change stewardship is critical to succeeding with Agile. Agile Principle #2 states:“Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.” This doesn’t mean that changes should be made haphazardly or without involving the right stakeholders. An example of this Principle often being abused is:Product Owner, Engineering manager or an influential stakeholder repeatedly brining in scope creep into a Sprint after the Sprint starts, justifying by saying that team should welcome change. The correct way to do tackle such a change would be to bring it to the Product Backlog; reprioritizing the Backlog working with the team. Such an approach to violating and abusing Agile Principles leads to bad habits and anti-patterns. Remember, as Agile leaders, practitioners, and project managers, we have a responsibility to manage change effectively. This means embracing change as an opportunity, not a burden, and taking a thoughtful and strategic approach to change management. Effective change stewardship, therefore, requires clear communication, collaboration, and a willingness to adapt. It involves not just the project team, but also the stakeholders and customers who will be impacted by the change. As Agile practitioners, we must be willing to challenge ourselves and our teams to think differently about change management. We should ask ourselves: The truth is, effective change management is not easy. It requires us to be proactive, to seek out feedback, and to constantly adapt to new challenges. But when we manage change effectively, we can deliver more value to our customers, improve our processes, and achieve our project goals. So, Agile practitioners, let’s embrace change as an opportunity for growth and improvement. Let’s challenge ourselves to think differently and to be proactive in managing change. And on a surprising note, the Agile Manifesto Principle on Change is not just about managing change during development. It also applies to our own personal growth as Agile professionals. As we continue to learn, grow, and adapt to new challenges, we are harnessing change for our own competitive advantage. (taken from Amit’s Linkedin post “February 27, 2023”)

Is your Product delivery approach holding you back?Are you sacrificing quality for the sake of cost and time?It’s time to take a closer look at the Agile Triangle of Constraints(also known as the Project Management Triangle or the Iron Triangle) Refer(left most) In traditional Waterfall project management, the scope is fixed (“required”) and the project timeline and budget are inflexible. This approach is largely plan driven and often results in teams working overtime to finish all the fixed requirements in fixed time with a fixed budget As a result, the fourth constraint quality often suffers. [Refer middle image2] Customers are unhappy, teams look burnt down, there is finger pointing But there is a better way. By turning the triangle upside down (refer to right most image3), Agile product management acknowledges that cost/budget and time are fixed, but the “requirements” are variable(aka “scope”) and are prioritized. By building products with systems thinking in mind, and working closely with users and customers we can focus on the most important items in the backlog and drop or delay less critical items (at the bottom of backlog) And by writing contracts with this updated Agile Triangle of Constraints in mind, we can avoid conflicts between fixed scopes and Agile values and thinking. Let’s break free from the limitations of traditional project management and embrace the flexibility and quality that Agile can offer. Are you ready to turn the triangle upside down?