Tactical Planning In Project Management

Scrum Master Interview Question What is Capacity planning in Scrum and how to calculate? Capacity Planning in Agile is the process of determining the amount of work a team can handle during a sprint or iteration. In Agile methodologies, particularly Scrum, it helps teams plan and forecast their work while ensuring that they don’t overcommit or under-deliver. Agile teams focus on being adaptable, so capacity planning isn't about rigid long-term projections but instead about aligning work with available resources, team skills, and any potential disruptions. Sprint duration: 15 days (3-week sprint). Available hours per day for each developer: 6.5 hours (80% of 8 hours/day). Total available hours for the sprint: 591.5 hours. Maximum available hours (if everyone was available the entire sprint): 682.5 hours. Average velocity over the last three sprints: 35 story points. Available hours for the upcoming sprint: 591.5 hours. Step 1: Understanding Team Capacity The maximum hours if resources are available for the entire 15 days is 682.5 hours. But the actual available hours in the upcoming sprint is 591.5 hours. Step 2: Adjusting Velocity Based on Available Hours The average velocity from the last three sprints was 35 story points when the team had 682.5 hours available. Now, we need to adjust this velocity based on the available hours for the upcoming sprint, which is 591.5 hours. We can use the following formula to calculate the proportional velocity for the upcoming sprint: Adjusted Velocity=(Available Hours for Upcoming Sprint / Maximum Available Hours)×Average Velocity Plugging in the values: Adjusted Velocity=(591.5 / 682.5)×35 = 30 Step 3: Conclusion Based on the available 591.5 hours, the team can realistically plan for around 30 story points in the upcoming sprint, considering their historical velocity and current capacity.

Stop answering what's asked, Answer what's meant instead: When someone asks, "How's the project going?" most respond, "It's fine." But great leaders know this surface-level question masks deeper concerns: • "Should I be worried?" • "Are we meeting our goals?" • "When will I get the next update?" • "Do you need help?" Surface-level responses miss opportunities to: • Build trust through transparency • Provide actionable clarity • Demonstrate ownership • Address unspoken concerns Worse, vague answers breed doubt, cause churn, and trigger unnecessary escalations. Here's what to do instead: 1/ If you know the person: Use your understanding of their concerns and priorities. For example: • “It’s on track. We’re dialing up milestone M1 on Tuesday as planned. Our next status update is scheduled for Wednesday.” 2/ If you don’t know the person well: Provide an answer and invite clarity (demonstrates ownership). For example: • “The project is on track for delivery by XX/YY, and I’ve attached our latest bi-weekly update. Are there specific areas or concerns you’d like me to address?” Answering the question behind the question is a leadership superpower. PS: Questions are icebergs—90% lies beneath the surface. --- Follow me, tap the (🔔) Omar Halabieh for daily Leadership and Career posts.

It was 9:00 AM on a Tuesday in an Abu Dhabi high-rise. I was staring at a methodology binder thick enough to prop open a fire door. The PMO had dedicated tooling and an entirely certified team. But 12 of their last 15 projects had missed their delivery dates. I spent the first week reading their status reports. They were immaculate... ...and completely useless. Every project stayed green right up until the day it crashed. Earlier in my career, I thought a heavy methodology guaranteed execution. I believed a clean status report meant the project was healthy. I chose the safety of the template over the haqeeqat (ground reality) of the work. This month, I was diagnosing another stalled enterprise portfolio. And I realized that massive organizations do the exact same thing. We reward teams for looking good instead of being useful. Nobody gets credit for raising an early flag. They get credit for keeping their lane clean. When your culture teaches people to protect the report instead of the project, your PMO fails. It becomes a highly paid administrative burden. You must fix the incentives before you redesign the process. Here is the playbook we use to rebuild PMO culture: 𝐑𝐞𝐰𝐚𝐫𝐝 𝐭𝐡𝐞 𝐄𝐚𝐫𝐥𝐲 𝐑𝐞𝐝: Stop punishing PMs who report delays. Actively praise the first person to flag a blocker during the steering committee. Punishing early warnings guarantees catastrophic late-stage failures. 𝐊𝐢𝐥𝐥 𝐭𝐡𝐞 𝐆𝐫𝐞𝐥𝐥𝐨𝐰 𝐒𝐭𝐚𝐭𝐮𝐬: A project is either on track or it is at risk. Ban hybrid reporting colors that soften the truth. Allowing ambiguous statuses lets failing projects hide until they are unrecoverable. 𝐀𝐮𝐝𝐢𝐭 𝐟𝐨𝐫 𝐀𝐜𝐭𝐢𝐨𝐧: Do not review a status report for its formatting. Review it for the management decisions it forces. A beautiful report that triggers no executive action is just expensive typing. You cannot fix a culture of fear with a new software tool. Whether it is a global enterprise portfolio, or a heavy binder in Abu Dhabi. Khallas.

When Teams Grow, Design Their Experience: An LXD Perspective. Rapid growth is often celebrated as a marker of success. Teams expand, business objectives increase, and new responsibilities are introduced. Yet growth often comes faster than the systems and processes that support it , leaving teams misaligned, overwhelmed, and disengaged. A sales team I worked with had grown from 10 to 25 members over six months. While expansion brought exciting opportunities , it also introduced a host of challenges: 📝 Increased administrative work and reporting requirements 📅 More frequent meetings for alignment across an expanded team 🎯 Higher performance expectations and KPIs ❓ Ambiguity in roles and responsibilities as new members joined Despite their enthusiasm and capability, the team began reporting stress, confusion, and a sense of constant pressure. From a Learning Experience Design perspective, processes that worked for a smaller team often do not scale without adjustment. The team’s capacity their available time, attention, and cognitive bandwidth did not expand in line with expectations. Role ambiguity and overlapping responsibilities created duplication of effort and accountability gaps. Here came an opportunity to redesign the team’s capacity and learning ecosystem rather than simply redistribute tasks. Key interventions included: 🔍 Conduct a Capacity Audit: Every task, meeting, and reporting requirement was analyzed to identify bottlenecks, duplication, and low-value activities. 📌 Prioritize Strategic Work: Non-essential tasks were delegated or removed. Core responsibilities aligned with business impact were clearly highlighted. ⚙️ Redesign Processes: Reporting templates were streamlined, recurring meetings reduced, and approvals standardized to reduce friction. 💡 Embed Reflection and Learning: Weekly “team retrospectives” were introduced, where team members shared wins, challenges, and lessons learned, enabling process improvement and knowledge transfer. 🧩 Clarify Roles and Responsibilities: Each team member’s tasks and ownership were mapped, eliminating overlap and increasing accountability. The results were striking. Performance stabilized as team members could focus on fewer, high-impact activities. Engagement increased 💪 because individuals felt their work mattered, and they had the space to contribute strategically rather than simply execute. Teams are more than output machines they are human systems. Rapid expansion can overwhelm these systems if we fail to consider capacity, clarity, and reflection. Designing growth with empathy and learning in mind ensures that teams remain motivated, skilled, and aligned. Ultimately, success comes not from doing more, but from doing better, together 🤝. #microlearning #learningeveryday #learningwithhiral #LearningExperienceDesign #EmployeeEngagement #Leadership #TeamDevelopment #ContinuousLearning #TeamCollaboration #LeadershipDevelopment

Your team missed forecast by $1.4M last quarter. You're about to put 2 reps on PIPs and post 3 new headcount reqs. That will cost you roughly $180K in recruiting, ramp, & severance. And none of it will fix the actual problem. Before you touch the roster, pull up four numbers. 1. Pipeline coverage by rep, trailing 90 days. If coverage is above 3x but conversion is dropping, your reps have enough at-bats. They're just swinging wrong, which is a COACHING deficit. Your manager is running pipeline reviews but skipping deal strategy sessions. They're asking "what's the update" instead of "where's this deal vulnerable and what's your plan for the CFO." 2. Avg ramp time for hires in the last 12 months versus the 12 months before that. If ramp is stretching, your onboarding infrastructure is degrading. Usually because the manager who used to ride along on every new hire's first 10 calls now has 11 reps instead of 7, and those ride-alongs quietly stopped around rep number 9. 3. Forecast variance by team (vs by rep). If one manager's team consistently calls their number within 5% and another's team swings 20%, that gap has nothing to do with talent distribution. The accurate team has a manager running structured deal reviews with exit criteria at every stage. The volatile team has a manager who asks reps "how confident are you" and writes down whatever they say. 4 Rep attrition by tenure. If you're losing people in months 8-14, they're leaving because they stopped getting developed. The first six months had structure. Ride-alongs, coaching cadences, weekly skill drills. After that, they got a weekly 1:1 that turned into a "lemme know if you need anything!" convo and nothing more. Four symptoms. All of them show up as rep performance problems on a dashboard. All of them trace back to manager capacity. If you think this sucks now, this will only get worse as you scale. Every rep you add without manager capacity compounds the degradation. - Your 8th rep gets 80% of the coaching your 4th rep got. - Your 12th rep gets closer to 40%. - And that 12th rep is the one who misses number in Q3 and becomes the PIP conversation that should have been a manager hiring conversation six months earlier. I'm not suggesting that replacing people doesn't have its place when fixing a team. It does. But IMO the first thing you should be doing is asking whether the person who's supposed to be building them has the bandwidth to actually do the job. Headcount solves a coverage problem, for sure. Manager capacity, meanwhile, solves everything else.

Nonprofit Department Heads - here's a critical mistake to avoid when submitting your department plan and budget this year. It's committing yourself - and your team - to work beyond your true capacity. Listen, ambition is important. We're out here trying to solve - or at least stem the tide on - big issues for the people and places we serve. Dreaming of a better world and working to make it a reality are hallmarks of our sector. But you know what doesn't work? → Overpromising and underdelivering. → Overworking your team because you focused more on the potential capacity represented by your new department org chart than on your team's actual capacity. → Setting goals based on "making the Board happy" rather than reality. → Using the "in a perfect world" approach to planning rather than one grounded in your current reality. Exacerbating staff turnover by overcommitting is destabilizing your team and putting you even further behind on your big goals. Failing to recognize and account for the ongoing high staff turnover rates in the nonprofit sector as you plan is a huge mistake. If you need help understanding your true capacity, start here: Know your vacancy rate. The vacancy rate is: • The number of vacant positions on your team • Divided by the total number of positions on your team • Multiplied by 100 So, if your department has: • 5 open positions • Out of 23 total positions • Your vacancy rate is 𝟮𝟮% Here's why it matters: When you're making your plans and budget, are you: • Creating workloads and investments with a full team in mind? • Or are you dialing it back by at least 22%? I say "at least" because there's still family and disability leave, onboarding time, mandatory training, collaboration across the organization, and other important elements that need to be factored in. As department heads, it's critical to align our aspirations with our capabilities - and to bring a practical understanding of the progress we can make with the people, tools, and resources we actually have. We need to care less about what looks good on paper and instead focus on what works well in real life. Knowing our team's true capacity - so we don't start from a place of overcommitment - is essential to creating plans and budgets we can actually deliver on. #nonprofit #leadership #management #OrganizationalEffectiveness #TeamEffectiveness ---- Hi, I'm Veronica LaFemina. As a strategic advisor to nonprofit CEOs and department leaders, this is one of the ways I help - enabling you to explore the bigger strategic questions facing your organization, avoid common pitfalls, and navigate the day-to-day complexities of nonprofit leadership. Ready to get the right support to help you and your team succeed? Send me a DM and we'll set up time to connect. If this post resonated with you, be sure to follow me here on LinkedIn, where I write about practical approaches to improving the ways we think, plan, and work.

Your Sprint Planning Fails Because You Treat Capacity Like a Guess, Not a Strategy (The Practical Kiran Way) Most teams say, “We’ll figure it out during the sprint.” And that’s the exact reason sprint goals collapse. Let’s look at this the practical way — with a real example every Scrum Master deals with 👇 🟦 1️⃣ Real capacity ≠ Headcount capacity Team size: 8 people Sprint length: 10 working days Most teams assume: 8 × 8 × 10 = 640 hours And then they plan work as if those 640 hours actually exist. But here’s what really happens: Dev1 → 1 day training = 8 hrs Dev2 → ½ day production support every day = 20 hrs QA → testing a previous release = 12 hrs Team → ceremonies + refinement = 16 hrs Actual usable hours ≠ 640 Actual = 640 − 56 = 584 hrs A sprint plan built on imaginary hours will ALWAYS fail. A sprint plan based on real availability will always feel predictable. 🟩 2️⃣ Story size should match capacity Here’s the mistake I see daily: Teams bring huge stories like: “Integrate entire payment module” (13 SP) But in reality, capacity allows only: ✔ “Add card selection UI” (3 SP) ✔ “Save payment method” (5 SP) ✔ “Basic validation for card number” (3 SP) Small slices → faster flow → faster testing → real Done. If your stories can’t fit inside the real capacity, no sprint plan will work. 🟧 3️⃣ Align commitment with actual velocity (with example) Past 3 sprint velocity: ➡ 32 SP ➡ 35 SP ➡ 34 SP Average = 34 SP Now check actual capacity this sprint: → Two devs have leave → Team has a production deployment → QA is training a new member Capacity is down by roughly 20%. So the sprint commitment should also adjust: 34 SP × 0.8 = 27 SP This is not theory. This is how predictable teams work. 🟪 4️⃣ Swarm early — don’t distribute stories like tasks Here’s a real scenario: Wrong approach: Dev1 takes Story A Dev2 takes Story B QA waits Both stories reach QA on the last day → spillover Right approach: Team swarms Story A UI + backend + QA collaborate Story A gets Done mid-sprint Then team moves to Story B Swarming = early Done Early Done = less risk Less risk = predictable sprint 🎯 Kiran Way Summary Sprints don’t fail because teams are slow. Sprints fail because: ❌ Capacity is guessed ❌ Stories are too big ❌ Velocity is misused ❌ Work is done in silos Fix the flow, fix the slicing, fix the planning — and sprint outcomes become stable. 💬 What’s the most practical capacity challenge your team faces today? #Agile #Scrum #SprintPlanning #CapacityPlanning #Velocity #ScrumMaster #AgileCoach #DeliveryExcellence #KiranWay

You’re overloading your team, and it’s costing you more than you think. Most agency founders don’t realise it - that’s why I have the 80% capacity rule. The workload of your team stacks up fast. Back-to-back projects. No breathing room. People stretched thin, juggling deadlines, burning out quietly. As an agency growth coach, I’ve seen this pattern repeat across agencies of all sizes. At first, it looks like peak performance: - Packed schedules - Rapid turnarounds - And constant activity But beneath the surface? - Missed details - Declining creativity - Reactive decisions (and high employee turnover) A team operating at 100% capacity isn’t effective. It’s fragile. One sick day creates bottlenecks. One unexpected task leads to delays. One high-pressure client causes stress to spiral. That’s why I advise agencies to keep their teams at 80% capacity. It’s not about working less. It’s about creating space to work better. At 80%, there’s room to: - Think strategically instead of reacting to every task - Handle surprises without derailing the week - Improve processes proactively, not fix them in crisis - Develop new skills because there’s time to learn - Innovate instead of sticking with what’s familiar Projects run smoother. Clients get better service. Retention improves for both clients and employees - and the business grows sustainably. PS: How do you manage capacity in your team?

Let’s talk about capacity planning when absences are involved. In my last post, I talked about keeping capacity planning simple: Use your team’s velocity, and follow this formula: 👉 Velocity - Carry Over = New Work But some of you might have thought: “What if there are vacations or someone is away?” And you’d be absolutely right, the simple approach would have you over committing in that case. That’s often why equations are brought into capacity planning. The most common one is: Adjusted Velocity = Team Velocity × (Available Team Capacity ÷ Full Team Capacity) For example: Team Size: 5 Velocity: 50 points Full team capacity: 40 days (10 days × 80% focus time) Sprint capacity: 32 days (one vacation) ➡️ Adjusted Velocity = 50 × (32 ÷ 40) = 40 points Seems simple, right? But if you’ve used this in practice, you’ve probably noticed it still leads to over commitment. That means more carry over work, and when vacations stack up, it can quickly create a pile of unfinished tickets. Why does this happen? In my view, the formula doesn’t account for team connections. Let’s revisit the idea of communication connections between team members. If you treat the team as a connected graph, where nodes are people and lines are communication, the number of connections grows fast: • 4 people = 6 connections • 5 people = 10 • 6 people = 15 • 7 people = 21 Now imagine a team of 7 where one person goes on vacation. That’s 6 connections lost. Those connections represent all the small but important team interactions: A quick question here, a pair programming session there, or a helpful comment in a code review. The usual capacity equation treats each person like an island, as if removing one person only removes their output. But teams don’t work in isolation. They’re systems of collaboration, and when a person is away, those missing connections ripple across the team. Let’s adjust the same example with that in mind: Team Size: 5 Velocity: 50 points Full team’s connections: 10 This sprint’s connections (with one away): 6 ➡️ Adjusted Velocity = 50 × (6 ÷ 10) = 30 points That’s 10 points less than the traditional equation! Considering the team’s connections paints a better picture than assuming isolation. Still, the truth lies somewhere in between; no one works entirely alone, but not everyone is deeply connected to everyone else. So here’s my simple approach: Still use the traditional equation, but subtract a “connection delta”, a small reduction to represent the impact of missing teammates. Start by reducing 5 points for each person away. In the example above, instead of pulling in 40 points, commit to 35. Adjust over time as you gather more data. And of course, remember to remove carry-over work: 👉 New Work = Adjusted Velocity - Carry Over Have you noticed that traditional capacity equations tend to over commit teams? How do you handle capacity planning when people are away? #Agile #Scrum #TeamDynamics #CapacityPlanning #AgileLeadership

How I Make My Weekly Status Reports Actually Useful as a Program Manager at Amazon Let’s be honest… Most status reports are either ignored, unread, or unclear. I’ve learned that if it doesn’t help your team or your leadership…it’s just noise. Here’s how I make mine cut through the noise: 1/ I use a consistent structure ↳ 3 sections: What happened…What’s next…What’s blocked ↳ Same order, every week ↳ Familiarity saves everyone time 2/ I lead with the headline ↳ “Model ingestion is 92% complete, on track for EOW” ↳ No burying the lede ↳ If they only read one line—they get the point 3/ I highlight risks early ↳ One section called “Risks + Mitigations” ↳ I name the risk, owner, and our plan ↳ It builds trust and prevents surprises 4/ I make it scannable ↳ Bullets over paragraphs ↳ Bold key decisions ↳ One glance = full picture 5/ I tailor it for the audience ↳ My team gets detail ↳ My leadership gets clarity ↳ I write for the reader…not to check a box A good status report doesn’t just report status. It drives alignment. It earns trust. And it keeps your project moving without extra meetings. What’s one section you always include in your updates?