Ajay Adhikari Specialist

meeting notes

Shout out to @Tomislav Tobijas 

to maintain a positive and respectful atmosphere in the community. It’s a reminder that collaboration thrives when we all contribute to creating a space that’s helpful, inclusive, and inspiring!

rules and guidelines

Thanks, @Walter Buggenhout ! Really appreciate it. Before Jira, we used Microsoft Planner with a basic two-week time-boxed cycle (not formal sprints). It helped us track tasks, but lacked depth, no clear ownership, limited visibility, and harder to manage dependencies. Jira gave us structure and clarity. But the real shift…

Thanks, @Brita Moorus Completely agree! Small projects often turn into testing grounds, and that “just one more tweak” mindset adds up fast. Setting expectations early is key, and I love that you’ve built out lightweight templates, that’s a huge time-saver. On the Team-managed vs. Company-managed question: I usually start…

@Walter Buggenhout : Love your workshop example, that simple “how do you start your day” question cuts deep. I’ve found the same: making shadow work visible changes the game. We’ve used retros and short working sessions to uncover similar patterns and then fed those findings directly into our backlog, like you said,…

@Cash Coyne You’re absolutely right, the basics of a good standup should be simple. But the way they’re executed often drifts, even unintentionally. Your structure and facilitation method is solid, especially putting discussions at the end. The regression update placement is a smart move. As for your blockers (#1 and #2),…

welcome @AS 

Thanks for the insight, @Nigel Budd totally agree. ScrumBan hits that sweet spot between structure and adaptability. Planning still matters, even when chaos shows up at the door. And yes, resisting the urge to jump on all unplanned work is key. Prioritizing, tracking velocity, and folding in repeat offenders as backlog…

Thanks for sharing, @Stephen_Lugton Love the layered comms approach dashboards, syncs, embedded standups, even Excel (we have all been there!). It’s a great balance of visibility and flexibility. Really appreciate you sharing the behind the scenes, lots of takeaways here!

Thanks for sharing your perspective @Stephen_Lugton and totally agree, Kanban can be a much better fit for DevOps teams living in the land of constant change. The idea of keeping a two week priority cadence without the rigidity of sprint commitments is a great way to stay aligned while still being flexible. What I like…

Thank you

@Tanya Christensen Thanks! Haha, exactly! "Quick" 

Hi @Marco Nowak Thanks for sharing—totally agree that not every small request needs a full-blown setup. Your ROI-based approach and smart reuse of custom fields are great strategies. That said, I still lean toward using Jira even for smaller projects when possible. It keeps everything in one place, maintains visibility,…

Congratulations !!!

DSM

Thank you for the guideline. 

Love the session

Hello Everyone. I am a Project manager in service based Company in Nepla. 

Thank you for the roundup.