Back to Insights

Continual Reflection: An Agile Element to Hone and Prepare IT Projects

ShareLinkedInEmail

The article "The New New Product Development Game," published in the Harvard Business Review by Hirotaka Takeuchi and Ikujiro Nonaka in 1986, was foundational to the development of agile-type methods of project management. In it, they compared project management to rugby, a sport where everyone has to contribute.

Collaboration in rugby matters most in the scrum, where players from both teams huddle with their heads down and compete for the ball. If a team does not coordinate its movements and adjust strategy dynamically in that pivotal moment, its weakest point gets breached and it loses possession.

IT project teams work the same way. They need to continuously reflect on the situation and adjust as a group. That habit of adjustment leads to more evolved efforts that better meet client needs.

Why reflection belongs between iterations

T2 Tech's approach involves completing small iterative sessions. When you incorporate iteration into a project, you gain the chance to review and reflect between sessions and reassess scope and objectives before the next one begins.

That reframes how a team treats change. Using an iterative approach, a change request stops being a sign of failure. It becomes an opportunity to collaborate and implement improvements, whether that means a process adjustment or a change in scope.

Iterative reflection improves the overall result

Most people dislike scope changes, but those changes are inevitable. An agile-based method gives you the tools to manage change and prepare for the unavoidable, applied at the right place and the right time. When you fold in lessons learned from reflection and review, you surface improvement opportunities and adapt to shifting requirements across the whole project.

A structured stakeholder review lets teams absorb scope change between iterations. The end goals and the physical work needed may shift. You might start out planning to build a new server, then discover you no longer need one, or uncover a security requirement that reshapes the infrastructure design entirely.

Changes to scope equal changes to the overall project, and the end-product savings from regular, consistent review between iterations can be significant, in both capital and operating expense. This is where reflection pays for itself: catching a wrong assumption at iteration two costs far less than discovering it after the build is finished.

Change may come from emerging business needs or from constraints that were not visible at the start. Balancing over-planning against under-planning is genuinely difficult, but an approach that builds in review and reflection lets you adapt to whatever arises. Prepare for the unexpected. Reflect between iterations to accommodate both scope and process changes.

A note on the rugby scrum

Just as a rugby team collaborates and dynamically improves to win the ball in the scrum, review and reflection between iterations let you implement change before completion. Those changes may be small adjustments to process or team interaction, or they may be larger shifts to the overall scope.

Either way, implementing change between iterations fortifies your team, addresses inevitable change head-on, and produces better solutions for the specific needs of a client or situation. The teams that treat reflection as a scheduled part of the work, rather than something they get to if time allows, are the ones that consistently finish stronger than they started.

A practical way to build reflection in

The hardest part is not agreeing that reflection matters, it is making sure it actually happens. Under deadline pressure, the review step is the first thing teams quietly skip. The fix is to treat reflection as a fixed, scheduled part of each iteration rather than an optional extra, with a short, honest conversation at the close of every session: what did we assume that turned out to be wrong, what changed, and what should the next iteration do differently. Kept short and regular, that habit compounds across a project.

What comes next

Reflection enables agile adaptability, but deliberate planning matters too. In a related discussion we look at how a hybrid methodology, combining waterfall and agile elements, is well suited to implementing IT projects in healthcare environments where predictability and adaptability both matter.

Ready to explore a partnership?

Let's Connect

We use cookies. View our Privacy Policy