Project Management

Please login or join to subscribe to this thread

How do you keep agile practices meaningful in long-running projects?

linkedin twitter facebook   Agile   Decision Making   Disciplined Agile  
avatar
Pavan Maddi
Community Champion
Buona Vista, Singapore

I’ve noticed that in longer projects, agile routines like stand-ups and retros can start feeling repetitive or rushed. In some cases, teams go through the motions without real reflection.



Have you faced this too? What’s helped you keep agile ceremonies effective and engaging over time?
Sort By:
avatar
Kiron Bondale Retired | Mentor| Retired Welland, Ontario, Canada
Pavan -

If the team is truly trying to "be" agile, then they should have feedback loops regularly on the processes they use to deliver value. This could be done by critiquing their ceremonies and practices on a regular basis (e.g. in a sprint retrospective or even a quick team huddle), identifying what they might like to change (e.g. format, frequency) and running experiments to see if they make things better.

Disciplined Agile captures this in its concept of guided continuous improvement.

Kiron
avatar
Luis Branco CEO| Business Insight, Consultores de Gestão, Ldª Carcavelos, Lisboa, Portugal
Pavan Maddi
That’s a great question — and yes, I’ve definitely encountered the same challenge in long-running agile projects.
Over time, ceremonies like stand-ups and retrospectives can start feeling repetitive or rushed, especially when the original purpose behind them gets lost in routine.
From my experience leading teams and projects across different contexts, here’s what has helped keep agile practices meaningful and engaging over time:
- Reaffirm the Purpose
Every few months, I take a moment with the team to revisit why we hold each ceremony. Reconnecting with the purpose helps shift the mindset from “just another meeting” to “a space for reflection, alignment and improvement.”
- Adapt the Format to the Team’s Reality
Variety can make a huge difference. We switch up retrospective formats (e.g., 4Ls, Sailboat, Start-Stop-Continue) and sometimes take creative approaches like storytelling or themed retros.
The key is to keep the conversation fresh and relevant.
- Allow Space for Reflection — and Breaks if Needed
In long projects, teams can experience ceremony fatigue.
When this happens, a short pause, a retrospective on the process itself, or a slight adjustment in cadence (e.g., bi-daily stand-ups) can help reset energy levels.
- Rotate Facilitation
Inviting different team members to facilitate retros or stand-ups increases ownership, engagement, and brings diverse styles to the table.
- Keep it Outcome-Oriented
When teams see that feedback from retrospectives leads to real changes — whether in workflow, communication, or team dynamics — motivation tends to increase naturally.
- Listen to the Signals
I regularly ask the team: “Is this ceremony still serving us? What would make it more valuable?”
Their input is essential in co-creating improvements.

Ultimately, I believe sustaining agile practices in long-term projects is about keeping purpose, adaptability, and team voice at the center.
Agile was never meant to be rigid — and that flexibility is our greatest ally in staying meaningful over time.
avatar
Wei Wu NanJing, JS, China, Mainland
The company calture
avatar
Sergio Luis Conte Helping to create solutions for everyone| Worldwide based Organizations Buenos Aires, Argentina
The key point here is map some things like daily stand ups as something which are agile practices. The main objective to us agile is to gain into agility. Agility is beyond using methods like Scrum and things like that. It´s too much. But, if your question is related to Scrum then I am with Kiron related to feedback if and only if the feedback includes quantitative feedback. If not, it is waste. At the end, nothing new below the sun. It is a matter to demonstrate value to all the stakeholders.
avatar
Sandeep Kashyap CEO| ProofHub India

Yes, this is a common challenge in longer projects; teams fall into routine, and the purpose behind agile practices gets diluted.



Here’s what’s helped me keep things meaningful:



* Find the room for improvement: Every now and then, we revisit the purpose of stand-ups and retros. That small practice often surfaces new opportunities and gaps.



* Switch things up. If a format feels stale, we change it. Sometimes it's a new retro style, sometimes it’s just shorter stand-ups or async check-ins.



* Pause when needed. If the team looks drained, it’s okay to take a break or tweak the frequency. Agile isn’t about rigidity — it’s about value.



* Involve the team. Let others lead the ceremonies. It adds ownership and makes the sessions more dynamic.



* Focus on impact. When teams see real change come out of retros, engagement naturally improves.



At the end of the day, agile is a mindset, not just a calendar of ceremonies. If something’s not working, that’s the best reason to adapt.

Please login or join to reply

Content ID:
ADVERTISEMENTS

"Man who waits for roast duck to fly into mouth must wait very, very long time."

- Chinese Proverb

ADVERTISEMENT

Sponsors







Vendor Events

See all Vendor Events

Newsletters

Jun 3: The Career Problem Facing New PMs
May 20: Your PM Career as a Project Life Cycle
May 13: The Big Lie After Layoffs

See all newsletters