Agile Strategy Development

The most common timeboxing mistake is treating it like a to-do list with deadlines. When you timebox correctly, you're not measuring success by task completion. You're learning how long things actually take, so you can better plan future work. If you don't finish a task in its allocated time block, don't bleed into the next one. Instead, ask yourself: "How many more timeboxes will I need to complete this?" Then, schedule accordingly. The key is focusing on input (your time and attention) rather than output (which you can't always control). By tracking and adjusting based on real data about how you spend your time, you become more realistic and effective with your planning. Remember that as long as you’re focused on what you said you’d do, when you said you’d do it, you’re succeeding.  Want more focus and productivity tips? Join 150,000+ subscribers to my weekly newsletter (link in my profile).

The Hard Truth About Why Agile Fails (And It’s Not the Framework) When Strategy Speaks, Culture Laughs. Scrum isn’t failing because teams don’t understand the framework. It’s failing because strategy speaks one language… and culture behaves in another. We keep blaming Scrum Masters and teams for “not collaborating.” But the truth is far more uncomfortable: You can’t build a collaborative culture on top of a competitive reward system. If your appraisal system rewards individuals instead of outcomes… if bonuses are tied to heroics instead of shared success… if promotions depend on outperforming the very people you work with every day… Then collaboration doesn’t just decline, it becomes a threat. The moment a team knows only one person will walk away with the highest rating or the fastest promotion, teammates quietly become rivals. Not because they’re toxic. Not because they’re unwilling. But because the system trains them to survive, not collaborate. And this is the absurdity nobody wants to acknowledge: ✅ Strategy demands collaboration ❌ Culture rewards competition ✅ Leaders talk about “psychological safety” ❌ HR policies incentivize greed ✅ Organizations want shared accountability ❌ Appraisals reward individual glory And ironically, the same leaders who designed the competitive system are the ones complaining the loudest about “poor collaboration.” This is why your transformation feels theatrical. This is why velocity becomes a costume. This is why retrospectives turn into polite rituals. Because the psychology of survival will always overpower the posters about agility. Your strategy can demand agility. Your culture decides whether people will live it. This carousel breaks down where the real damage happens — and what Scrum Masters and leaders can finally do about it. 👇 Start here. #ReTHINKscrum #ReTHINKagile Agilemania Agilemania Malaysia

I’ve been working as a contractual Program/Project Manager on complex projects for the past 7 years, most of which followed Agile methodologies. While the Software Development Life Cycle (SDLC) is designed to reduce risk, poor implementation can have the opposite effect. If not executed properly, it significantly increases the risk of project failure. Here’s a quick ranking of critical failure points that commonly derail software projects: 🔴 1. Unclear or Changing Requirements Poorly defined needs or constant scope changes break alignment early and often. ✅ Fix: Involve stakeholders early, use user stories and clarify DoD (definition of done), and validate frequently; another advice: make sure to define change request in the initial contract with the client. 🔴 2. Inadequate Planning & Estimation Unrealistic timelines or budgets create pressure that leads to shortcuts and burnout. ✅ Fix: Buffer for unknowns, involve tech leads in estimation. 🟠 3. Ineffective Communication Team silos and misalignment cause costly rework and delays. ✅ Fix: Daily stand-ups, shared documentation, clear ownership. The tech team needs to understand the functional requirement to be able to implement it technically. 🟠 4. Weak Design & Architecture Hasty or shortsighted technical decisions lead to rework and scalability issues. ✅ Fix: Involving a software architect who could support drafting the best scalable architecture choices within the available projects needs, constraints and budget 🟠 5. Insufficient Testing & QA Testing cut short = bugs in production, bad UX, security holes. ✅ Fix: Invest in a QA strategy to identify tests to be run by type of release, and automate critical time-consuming tests 🟡 6. Lack of Stakeholder Involvement Software built in isolation rarely meets business goals. ✅ Fix: Demo regularly (ideally after each milestone), build feedback into the cycle. 🟡 7. Poor Change & Config Management Inconsistent environments and chaotic updates derail progress. ✅ Fix: Version control, CI/CD, and clear change protocols. 🟡 8. Inadequate Risk Management Unexpected issues become blockers when risks aren't flagged early. ✅ Fix: Ongoing risk logs, contingency planning. 🟢 9. Neglecting Post-Launch Support No plan for support = user churn and poor adoption. ✅ Fix: Monitor performance, address issues fast. 🟢 10. Lack of DevOps & Automation Manual processes delay releases and increase error rates. ✅ Fix: Embrace CI/CD and infrastructure-as-code. Strong software isn’t just about great code—it’s about clarity, communication, and continuous feedback. A strong Project Manager implements the right processes and follows each step methodically to spot weak links early and address them proactively. And when issues do arise (as they often do), they stay calm, communicate transparently, and ensure all stakeholders remain aligned throughout the journey. #SoftwareDevelopment #SDLC #TechLeadership #ProjectManagement #Agile #DevOps #ProductDelivery

Long plans aren't ambitious, they are inaccurate. There is science to back this up. If you have a 10-year-plan, your chances of completing it are near 0%. If, however, you move your 10-year timeline of the same goal to something far shorter, 3 years or less, then your chances of hitting the goal increase dramatically. I'll share a few principles and studies that explain how this works, then finish with a few profound quotes: A few principles: - Parkinson's Law = work fills the space you give it. - Pareto Principle = the majority of outputs come from a small minority of inputs - Illich's Law (Threshold of Diminishing Returns) = at a certain point, productivity goes down due to fatigue or over-perfectionism, reaching diminishing returns. - Timeboxing = you assign overly short and fixed deadlines to a task, even if it's highly complex, to create more feedback loops. For example, rather than 2 days to complete something, you commit to a completion in 2 hours. This builds momentum through enforced sprints, forces focus and answers on what matters, exposes blindspots. - OODA Loop (Observe → Orient → Decide → Act) = Cycle faster than opponents; tempo creates advantage. A few research studies: - Ariely & Wertenbroch (2002) found that external deadlines were more effective than self-imposed ones - Knowles, Servátka, & Sullivan (2015/2017) found that with taks like charitable giving, a 1-week deadline produced significantly more effects than a 1-month... too much time to think about something generally leads to inaction, not better action - Lieberman et al. (2021, Scientific Reports) found that shorter deadlines drove action whereas long deadlines didn't - Bisin et al. (NBER field experiment) found that shorter deadlines curb procrastination - McCausland et al., 2008; replicated in logging industry, 2025 update) found deadlines don't just limit sprawl; with incentives, they amplify focus on essentials, reducing waste by 25% in project analogs - Pinkley et al., (2009) found Teams with 20% tighter quotas saw 15-25% gains in throughput, but only when goals were specific A few quotes: - Peter Thiel said, "If you have a 10-year plan of how to get [somewhere], you should ask: Why can't you do this in 6 months?" - Charles Richards said, "Don’t be fooled by the calendar. There are only as many days in the year as you make use of. One man gets only a week’s value out of a year while another man gets a full year’s value out of a week." Implications: - I've personally seen that 10-year plans are not only ineffective, but inaccurate - Any goal beyond 3 years out generally means you're not actually solving for the goal, but solving for some false "means" you think is required, and generally isn't - Seemingly impossible deadlines force you to clarify the "crux" - Faster feedback loops create momentum and learning ----- Access full audiobook of THE SCIENCE OF SCALING > https://scaling.com/ Access full audiobook of TIME IS A TOOL > https://scaling.com/time

Do you timebox ? I've been practicing this time management technique over the past few years to help me manage myself better. With calendars being blocked and plenty of things that needs to go through your eyes this technique helps me schedule things better. A good 15 minute helps me box my activities better for the day. What is time boxing ? Time boxing is a time management technique where you allocate a fixed unit of time to an activity in advance, and you commit to stopping once the time is up. It's core purpose is to maintain focus and productivity by preventing procrastination or overworking. You "box" your time for a specific task, regardless of whether it's complete. For example: You set a 45-minute block from 9:00–9:45 AM to work on writing an article — and you stop at 9:45 no matter what. Now for those who might be confused between a calendar and time box, calendar is just a tool to efficiently manage. Here's how to do it effectively: 1. Define the Task Clearly Be specific about what you want to achieve during the timebox. Break larger projects into smaller, manageable tasks. 2. Set a Realistic Duration Decide how long you will spend on the task — not how long it should take, but how long you’re willing to give it. Start with short blocks (e.g., 25–50 minutes), then adjust based on your needs. 3. Use a Timer Use a digital timer or an app (like Pomodoro timers, Toggl, or Clockify) to keep track of your time. It creates urgency and helps you stay focused. 4. Work with Focus (No Multitasking) During the timebox, eliminate distractions (turn off notifications, close unnecessary tabs). Treat it as a commitment. 5. Stop When Time is Up Even if the task isn’t finished, stop. Review your progress, reassess, and either extend the timebox or schedule another one. 6. Review and Reflect After the timebox ends, ask: • Did I complete what I intended? • Was the timebox duration appropriate? • What can I improve next time? 7. Use Buffers and Breaks Don’t chain timeboxes back to back endlessly. Schedule short breaks to recharge. If you've tried this let me know how it works for you.

Timeboxing is a total game-changer. Everything goes into the calendar. Not just meetings, but all the things you are working on. You decide what your priorities are and add them to the calendar alongside meetings and specific times for dealing with email, projects, research, and anything else you need to make time for. This creates visibility. It’s powerful - especially if you have multiple managers. Your workload becomes clear, not just to you, but to everyone you are working with. If something urgent comes in, the question becomes simple. Where? Not in a disrespectful way, but in a way that allows the right decision to be made. If it is urgent, something else moves. If it is not, it goes into the calendar at the right time. I hate to-do lists with a passion. They are like Medusa. You cut one head off and five more grow back. They are deeply depressing because you never feel you have achieved what you should have done. Timeboxing changes that. It allows you to timeline the tasks and projects you are working on so you know you have completed what you needed to do today. It creates focus. It creates clarity. And most importantly, it gives you control.

Clearing the Systemic Barriers to Authentic Agility Most so-called Agile “transformations” (oh, if ever there were a misnomer) don’t fail because of the framework, tooling, or training - they fail because of deeply embedded impediments that fall into four systemic categories: Culture, Structure, Process, and Technology. These factors form a complex ecosystem, and if you treat them like separate problems, you’ll get performative agility without real adaptability. Agility isn’t a checklist or a destination. It’s a continuous journey of adaptation. Ignore the interplay between these domains at your peril. Barrier #1: Culture - The Invisible Operating System That Resists Change Problem: Traditional organizational cultures prioritize control over creativity, rewarding compliance while punishing exploration. The result is risk-averse bureaucracy. Questions: Do people feel safe admitting mistakes? Are failures learning opportunities or liabilities? Can the status quo be challenged without retaliation? Strategies: Foster psychological safety with blameless retrospectives and candor-friendly spaces. Celebrate smart failures. Promote learning with cross-functional exposure, rotation programs, and curiosity-based metrics. Barrier #2: Structure - Your Org Chart Is Showing Problem: Hierarchical, siloed structures slow decisions and disconnect teams from value delivery. Questions: Are teams aligned to customer outcomes or department KPIs? Where do decisions get made? How often do handoffs or approvals delay progress? Strategies: Align teams to value streams. Push decision-making closer to the work. Use lightweight governance and clearly delegated authority to reduce drag. Barrier #3: Process - When Following Rules Becomes Valuable Problem: Agile rituals become performative when teams confuse ceremony with value. Questions: Are Agile events energizing or exhausting? Do metrics reflect outcomes or activity? Are teams allowed to evolve their way of working? Strategies: Design outcome-oriented processes. Audit meetings regularly. Enable process experimentation within safe bounds. Focus on feedback loops, not rituals. Barrier #4: Technology - Tools as Thrust or Drag Problem: Legacy systems and fragmented tools create cognitive friction, slow feedback, and kill momentum. Questions: Do your tools promote collaboration or reporting? Can teams release frequently without manual overhead? Does tech accelerate flow or block it? Strategies: Invest in CI/CD, test automation, and self-service platforms. Retire tools that reinforce control or don't add value. Prioritize fast feedback, simplicity, and team autonomy in tool selection. Agility Isn’t Implemented - It’s Cultivated True agility requires systemic change across all four domains. It’s messy, non-linear, and context-dependent. Focus on domain interactions. Create safe-to-learn environments. Measure progress by adaptability, not just delivery. Don't chase transformation; enable evolution.

To-Do Lists Don’t Work—Try Time Boxing Instead I used to rely on to-do lists, but here’s the problem: they never end. Lists are fine to capture tasks, but tasks pile up, priorities shift, and by the end of the day, it feels like nothing truly important got done. That’s why I time box every morning—blocking specific time slots on my calendar for my most critical tasks. Instead of hoping I’ll “find time,” I make time. ☑️ Prioritize with Intention – Deep work doesn’t happen by accident; I schedule it. ☑️ Increase Focus & Efficiency – A time limit creates urgency and eliminates distractions. ☑️ Prevent Overcommitment – If it’s not on the calendar, it’s not getting done. As highlighted in the latest HBR IdeaCast, time boxing transforms productivity by ensuring the most important work gets the attention it deserves. Try it: Tomorrow morning, instead of a to-do list, schedule when and for how long you’ll tackle your top priority. What’s one thing you’ll time box this week?

Three things we bucket under "estimation" in game dev: 1. Timeboxing 2. Estimating 3. Measuring Timeboxing is creating a comparatively arbitrary box around something based on either a desire to not let things run indefinitely OR hard constraints based on time and/or budget. They are very helpful when used well, but are often abused by filling out entire plans with timeboxes that don't make sense. Example: "See how far you can get the weapon skin in three days." Example Technique: Time-based block to accomplish the task - classic project planning does a lot of this. Estimating is (done well) an analytical, unbiased process through which a prediction of the future or some other unknown thing is made. Estimation takes more effort than timeboxing, but (again, if done well) also provides higher accuracy. Even better when estimation reveals just how much uncertainty exists through relative estimation or the use of ranges. Example: "Comparing that to previous work we've done, I would say it will take between 4 and 8 weeks to complete." Example Technique: Using affinity estimation to relatively size different tickets. Measuring is looking at something that already exists or has happened in the past and quantifying it. Measuring creates data, and if the system is sufficiently stable, having measurements of what has happened allows better prediction (through data-informed estimates) of what will happen in the future. Example: "Over the last 4 iterations we've averaged 5 items completed per iteration." Example Technique: Throughput (which can then be turned around to make predictions) Each of these methods has a time and a place where it shines, and each has it's own issues and fallacies. The techniques can also interrelate, as in Monte Carlo Simulation where you use measurement to create an estimate. One of the biggest challenges I see in game development around estimation is not bad technique, it is inappropriately applied technique often driven by poor behavior around estimation. People timebox and think they've estimated, or estimate and think they've somehow measured the future. They measure, and think that guarantees what will happen. When you treat a timebox like a measurement, getting angry when something is late makes sense to you. But the reality is you've used the wrong tool at the wrong time. Be aware of what you're doing, and pick the right method for the situation you are in. #gameproduction #gamedevelopment #gameindustry #estimation

Ever wondered how most influential leaders juggle countless projects, roles, and responsibilities? The answer might surprise you: Timeboxing. This powerful technique isn't just about managing time—it's about maximizing creativity and driving innovation. So, what is timeboxing? Timeboxing involves allocating a fixed, uninterrupted period to a specific activity before you start. It's like putting your tasks into boxes of time on your calendar. You give your full focus to one task at a time, with a clear start and end point, transforming the intangible (time) into something tangible (a box on your calendar). Benefits: 💡 You can enhance your focus by dedicating specific blocks of time to tasks. 💡 It creates a sense of urgency, reducing procrastination and encouraging task completion within set periods. 💡 Through prioritization, timeboxing helps you to focus on what moves the needle. The technique and benefits might sound familiar to many of you, but the real challenge lies in execution. Here are a few steps I follow to make timeboxing work: ✅ I began by timeboxing my routine tasks, which helped me understand how long things really take. ✅ I always add a buffer for unexpected issues when allocating time for each task. ✅ I've found that scheduling short, timeboxed breaks keeps my productivity high throughout the day. ✅ At the end of each week, I review what worked and tweak my timeboxes accordingly. This constant refinement has been key. Timeboxing has revolutionized the way I manage my workday, helping me stay focused, productive, and in control. Have you tried timeboxing? What strategies have worked best for you? Let me know in the comments below. #productivity #work #management #timemanagment #techniques