MAMuhammad Azharinrahnuma.hashnode.dev·2d ago · 4 min readWhy Your Sprints Always Slip (And How to Predict It 30 Days Early)Every engineering team knows the feeling. It’s Wednesday, the sprint ends on Friday, and a sudden realization hits the team: we are not going to ship on time. Again. Usually, we blame it on "unforesee00
MAMuhammad Azharinrahnuma.hashnode.dev·Jul 13 · 3 min readHow to Use AI for Sprint Planning (And Stop Guessing Deadlines) If your team is still estimating sprint tickets by sitting in a 2-hour meeting and holding up fingers for "Planning Poker," you are living in the past. Despite decades of Agile coaches telling us how 00
MAMuhammad Azharinrahnuma.hashnode.dev·Jul 9 · 3 min readThe Developer Burnout Epidemic (And Why Vacations Don't Fix It)Every year, tech companies try to solve developer burnout the same way: they offer a subscription to a meditation app, host a mandatory "wellness webinar," and tell you to take a long weekend. And eve00
MAMuhammad Azharinrahnuma.hashnode.dev·Jul 7 · 3 min readEngineering Metrics That Actually Matter (Hint: It's Not Lines of Code) If you want to make a software engineer instantly lose respect for their manager, start measuring their performance by "Lines of Code" (LOC) or the "Number of Commits." It is a tale as old as time. No00
MAMuhammad Azharinrahnuma.hashnode.dev·Jul 4 · 3 min readThe Death of the 2-Week Sprint (Why Agile is Failing Modern Teams) Let’s be honest: the 2-week sprint is starting to feel like a trap. Every other Monday, your engineering team gathers for a 2-hour planning meeting. You estimate tickets, argue over story points, and 00
